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
Can we automount the ISIS data archive (a CIFS share) from the Python backend when required? We would still have to ask for username/password.
If users already have the data archive mounted, or the code is being run on an instrument PC, we will need a way of detecting or allowing the user to set the location as an option.
The text was updated successfully, but these errors were encountered:
On my Windows machine, it seems enough to do a set JV2_RUN_LOCATOR_PREFIX=\\isis\inst$ at the top of the batch file that I'm using to launch the backend and frontend. This correctly overrides what's in config.py. Note that if you do this change by altering run_locator_prefix in config.py instead, you need to stop the double slash being reinterpreted, e.g. by setting to r"\\isis\inst$"
Can we automount the ISIS data archive (a CIFS share) from the Python backend when required? We would still have to ask for username/password.
If users already have the data archive mounted, or the code is being run on an instrument PC, we will need a way of detecting or allowing the user to set the location as an option.
The text was updated successfully, but these errors were encountered: