-
Notifications
You must be signed in to change notification settings - Fork 23
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
mtuq.download_greens_tensors output path requested #208
Comments
Does an environment variable approach work for you? I believe the syngine download path can be specified through the environment variable SYNGINE_CACHE, but we could work on making it more robust (checking path existence, checking write permission, better documented) or implementing something else altogether. Please let us know if you have any preferences. -Ryan |
Actually, perhaps a little added documentation would be helpful.
SYNGINE_CACHE doesn't seem straightforward to find from just a Google
search, or perhaps I'm not looking in the right places. Would you mind
forwarding me your SYNGINE_CACHE reference just so that I have it?
Aileen
…On 3/18/23 09:44, Ryan Modrak wrote:
@aileen-fisher <https://github.com/aileen-fisher>,
Does an environment variable approach work for you? I believe the
syngine download path can be specified through the environment
variable SYNGINE_CACHE, but we could work on making it more robust
(checking path existence, checking write permission, better
documented) or implementing something else altogether. Please let us
know if you have any preferences.
-Ryan
—
Reply to this email directly, view it on GitHub
<#208 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6O6EFTCH6PHMZQLMNSGGR3W4W35XANCNFSM6AAAAAAV66WXUM>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Right now, it's just an undocumented feature implemented here: Let me think about if a more robust approach is possible. -Ryan |
Reqest ability to modify GFs output path. Writing files within the mtuq install folder becomes a problem on a multi-user system where not everyone has write permissions to that path.
The text was updated successfully, but these errors were encountered: