Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use ISIS Data Archive #26

Open
trisyoungs opened this issue Oct 6, 2021 · 1 comment
Open

Use ISIS Data Archive #26

trisyoungs opened this issue Oct 6, 2021 · 1 comment

Comments

@trisyoungs
Copy link
Member

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.

@JoeKelleher
Copy link

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$"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants