We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
oh, i meant something slightly different -- i thought it would be useful to do a logic where
BE.scratch_dir
Originally posted by @mscho527 in #41 (comment)
The text was updated successfully, but these errors were encountered:
It's currently setup in the reverse, ie if you set the input input keyword scratch_dir then that supersedes whatever is set in BE.scratch_dir.
scratch_dir
Sorry, something went wrong.
why not just use BE.scratch_dir instead of introducing a new input keyword? you can set BE.scratch_dir in an input rather easily.
No branches or pull requests
BE.scratch_dir
was set, use this in the solverbut i think we can address this in a later pr (reminder to create an issue upon merge) as this is okay as is
Originally posted by @mscho527 in #41 (comment)
The text was updated successfully, but these errors were encountered: