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

Settable data location #34

Open
j-woz opened this issue Oct 31, 2018 · 3 comments
Open

Settable data location #34

j-woz opened this issue Oct 31, 2018 · 3 comments

Comments

@j-woz
Copy link
Contributor

j-woz commented Oct 31, 2018

Do not force big input data to reside inside a git clone. This forces code and big data to reside on the same FS (I use a soft link to get around this), and is likely to trigger git mistakes.

@jmohdyusof
Copy link
Contributor

Does this mean you want the 'Data' directory to reside outside the Benchmarks directory? Do we want a standard way to set the Data dir base address?

@j-woz
Copy link
Contributor Author

j-woz commented Oct 31, 2018

Yes, I think that should be possible. For example, on some machines I want to clone the Benchmarks in my home directory (fully backed up, small quota) but keep the input data in some project scratch directory (data possibly lost or evicted, large quota).

@jmohdyusof
Copy link
Contributor

Resurrecting this, since it is still relevant and I have been working with Tom on it. The CANDLE_DATA_DIR environment variable is starting to get to this, but we need more generally to implement the IO going to writeable filesystem locations, as needed by both e.g. Summit and singularity containers

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

No branches or pull requests

2 participants