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

Various parameter checking issues #164

Open
mirenradia opened this issue Mar 4, 2021 · 3 comments
Open

Various parameter checking issues #164

mirenradia opened this issue Mar 4, 2021 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@mirenradia
Copy link
Member

ChomboParameters::warn_array_parameter is calling check_parameter rather than warn_parameter. This is incorrect.

Also, when called in BinaryBH/SimulationParameters.hpp, it using bh1_params.mass in the validity check for momentumB rather than bh2_params.mass.

I've also realised that there are some checks in the TwoPunctures part which are implemented in a non-standard way and should be changed to the standard check_parameter. This parameter loading code is duplicated in the standalone TwoPunctures example. Ideally, the parameter loading code for TwoPunctures params should be in a function in the TwoPunctures repository which can be called in the BinaryBH example.

@mirenradia mirenradia added the bug Something isn't working label Mar 4, 2021
@mirenradia mirenradia self-assigned this Mar 4, 2021
@mirenradia
Copy link
Member Author

A warning should also be added that the restart file time is strictly less than the stop_time parameter (yes I did just accidentally submit a job with a stop_time that was the same as the restart file time and wasted its time in the queue).

@KAClough
Copy link
Member

It would be useful to check whether TWOPUNCTURES_SOURCE is set, and if so also check if a mandatory TwoPunctures param (e.g. TP_momentum_plus ) exists in the parameter file and then print an error message like “You are running with TwoPunctures, make sure the TwoPunctures params are set or unset TWOPUNCTURES_SOURCE and recompile.”

It is easy to forget that you set TP and then wonder why it is looking for the params for that...

@mirenradia
Copy link
Member Author

Another thing I have just noticed is this line which should default vars_parity_diagnostic to an enum value from the parity enum rather than the BC Type enum.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants