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

Make output mesh CLI argument in precice-aste-run optional #169

Open
davidscn opened this issue Feb 9, 2023 · 0 comments
Open

Make output mesh CLI argument in precice-aste-run optional #169

davidscn opened this issue Feb 9, 2023 · 0 comments
Labels
good first issue Starter projects for newcomer

Comments

@davidscn
Copy link
Member

davidscn commented Feb 9, 2023

Currently, using precice-aste-run without an --output argument leads to a strange error, i.e., the user is forced to specify an output mesh. If a user (for whatever reason) wants to get the maapped data on the same mesh as used for the input, the user could define the input mesh as an output mesh. However, this will simply override (i.e. erase) the input mesh and all the data it contains.

We should allow the user to omit the --output flag and append the mapped data to the already existing data sets in such a case.

@davidscn davidscn added the good first issue Starter projects for newcomer label Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Starter projects for newcomer
Projects
None yet
Development

No branches or pull requests

1 participant