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

Specifying variables in outputfile #5

Open
fplpml opened this issue Sep 14, 2021 · 1 comment
Open

Specifying variables in outputfile #5

fplpml opened this issue Sep 14, 2021 · 1 comment

Comments

@fplpml
Copy link

fplpml commented Sep 14, 2021

Hello,
When I have created a setup at L4 with non-benthic fabm.yaml file which had all bilogical modules switched off (use: false) I wanted to save only a handful of variables into the output file. An error was rised at initialisation of the run as follows:
bL2_c_sms_tot_calculator_result benthic calcite c_sms_tot_calculator result
Using Eulerian solver
Using euler_forward()
done.
Using constant fabm/input/mole_fraction_of_carbon_dioxide_in_air= 385.00000000000000
Using constant fabm/input/absorption_of_silt= 7.0000000000000007E-002
Using constant fabm/input/bottom_stress= 0.0000000000000000
FATAL ERROR: create_load_commands: Variable particulate_organic_absorption_coefficient_calculator/result is marked for preloading but has no valid data.
Note: The following floating-point exceptions are signalling: IEEE_DENORMAL
STOP 1

If I include bottom values saving source: * into the gotm.yaml file this error doesnt appear and the simulation completes correctly.

A similar error occours with a setup including benthic system and all biology switched on. Here bottom values need to be saved including all variables (source: *) to let the run complete correctly otherwise similar error would appear:

Using constant fabm/input/absorption_of_silt= 7.0000000000000007E-002
Using constant fabm/input/bottom_stress= 0.0000000000000000
FATAL ERROR: create_load_commands: Variable total_bioturbation_activity_at_bottom_calculator/result is marked for preloading but has no valid data.
Note: The following floating-point exceptions are signalling: IEEE_DENORMAL
STOP 1

@jimc101
Copy link
Member

jimc101 commented Sep 14, 2021

Not yet sure whether this is an ERSEM issue, a FABM issue or a problem with the config files. Whatever, the error message feels a little cryptic given the change that causes it. @jornbr - do you have a take on the FABM question?

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

2 participants