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
In the WarpX repository we have several (mostly Python) pre/post-processing tools that are not tested automatically.
Some are in the Tools directory, others are in the Examples directory, such as, for instance, the plotting scripts in Examples/Physics_applications/beam_beam_collision.
It would be good to have an automated CI workflow that runs these tools to make sure they work and are up-to-date.
The text was updated successfully, but these errors were encountered:
EZoni
No branches or pull requests
In the WarpX repository we have several (mostly Python) pre/post-processing tools that are not tested automatically.
Some are in the Tools directory, others are in the Examples directory, such as, for instance, the plotting scripts in Examples/Physics_applications/beam_beam_collision.
It would be good to have an automated CI workflow that runs these tools to make sure they work and are up-to-date.
The text was updated successfully, but these errors were encountered: