You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm currently trying to upgrade ABM3 to work with the latest version of ActivitySim. While testing sandag-abm3-example I noticed that the Sharrow cache was being written to a location in the C:\Users folder for my account on the modeling server I'm running it on. When I tried setting the sharrow_cache_dir setting, it still looked for/wrote to that same location in C:\Users. I was hoping that we could store the cache in a centralized location and copy from it or even point to it when our modelers run the model. We have 12 modelers and 15 modeling servers so modelers needing to compile Sharrow every time a modeler runs the model on a server they haven't run it on yet isn't feasible.
To Reproduce
Steps to reproduce the behavior:
Set sharrow_cache_dir in the settings file for a run.
After the skims are read in and once some steps are run, open the logfile.
Look for the text "flow.cache_dir" and look to where the cache is being written.
Expected behavior
I was expecting the Sharrow cache to be written to the directory specified by sharrow_cache_dir.
Screenshots
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm currently trying to upgrade ABM3 to work with the latest version of ActivitySim. While testing sandag-abm3-example I noticed that the Sharrow cache was being written to a location in the C:\Users folder for my account on the modeling server I'm running it on. When I tried setting the sharrow_cache_dir setting, it still looked for/wrote to that same location in C:\Users. I was hoping that we could store the cache in a centralized location and copy from it or even point to it when our modelers run the model. We have 12 modelers and 15 modeling servers so modelers needing to compile Sharrow every time a modeler runs the model on a server they haven't run it on yet isn't feasible.
To Reproduce
Steps to reproduce the behavior:
sharrow_cache_dir
in the settings file for a run.Expected behavior
I was expecting the Sharrow cache to be written to the directory specified by
sharrow_cache_dir
.Screenshots
The text was updated successfully, but these errors were encountered: