You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had copies of c0, c1, c2, c1000, and p5 in marbl_kinds_mod.F90, and I am in the process of moving them to a new marbl_constants_mod.F90 module, but it appears they are also stored in marbl_parms.F90 Obviously these only need to be stored in one place, but which module to use should depend on what other constants / parameters we end up saving and where we stick the parameters (will there be a marbl_params_type inside marbl_interface_class?)
The text was updated successfully, but these errors were encountered:
I still need to move pi from marbl_ciso_mod to marbl_constants -- one possibility is to hard-code a value and store pi as a parameter (CVMix uses 3.14159265358979323846, but I need to see if that is bit-for-bit with MARBL's 4*atan(1)
We had copies of
c0
,c1
,c2
,c1000
, andp5
inmarbl_kinds_mod.F90
, and I am in the process of moving them to a newmarbl_constants_mod.F90
module, but it appears they are also stored inmarbl_parms.F90
Obviously these only need to be stored in one place, but which module to use should depend on what other constants / parameters we end up saving and where we stick the parameters (will there be amarbl_params_type
insidemarbl_interface_class
?)The text was updated successfully, but these errors were encountered: