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

Streamline scratch logic #43

Open
mscho527 opened this issue Oct 16, 2024 · 2 comments
Open

Streamline scratch logic #43

mscho527 opened this issue Oct 16, 2024 · 2 comments

Comments

@mscho527
Copy link
Collaborator

          oh, i meant something slightly different -- i thought it would be useful to do a logic where
  1. if BE.scratch_dir was set, use this in the solver
  2. otherwise, use the input keyword
    but 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)

@ShaunWeatherly
Copy link
Contributor

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.

@oimeitei
Copy link
Owner

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.

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

3 participants