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

More thoughtful use of input and output files in tests and examples #320

Open
RobertPincus opened this issue Jan 4, 2025 · 0 comments
Open

Comments

@RobertPincus
Copy link
Member

As noted by @skosukhin in #319 the treatment of input and output files in tests/ and examples/ is inconsistent and sometimes makes file management during testing more complicated than it needs to be.

At a minimum we should have check_variants write to a separate output file rather than directly to the input file.

  • Should we do this programmatically (i.e. make a new output files with the same coordinates as the input) ormake a blank template file to copy over (any thoughts @skosukhin ?)

In general I should look over the use of files in testing and examples.

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

1 participant