Hi Svetla,
If you’re aiming to define your own, custom standard variable, you can do it like this:
type (type_horizontal_standard_variable), parameter :: precipitation = type_horizontal_standard_variable(name='precipitation',units='m/s')
You can then use “precipitation” whenever you want the specify a standard variable (e.g., instead of standard_variables%xx)
You could potentially also skip the definition of the parameter and directly do something like
call self%register_dependency(self%id_precip, type_horizontal_standard_variable(name='precipitation',units='m/s'))
That’s formally correct, but worth noting that there are at least some compilers (old Cray ones in particular) that have trouble with this.
Cheers,
Jorn
--
You received this message because you are subscribed to the Google Groups "FABM-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabm-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fabm-users/a1506453-b067-4e11-9e7f-3ade67c46610n%40googlegroups.com.
Hi Svetla,
I’m not aware of GETM (or GOTM) providing precipitation to FABM by default. But if your GETM version doesn’t, you can relatively easily make it do so by editing src/3d/getm_fabm.F90. There, you’ll already find
call model%link_horizontal_data(id_bottom_depth_below_geoid,H(i,j))
call model%link_horizontal_data(id_bottom_depth,D(i,j))
You can send precipitation by adding
call model%link_horizontal_data(type_horizontal_standard_variable(name='precipitation',units='m/s'),precip(i,j))
As long as the standard variable name and units used by GETM and by your BGC model match, FABM will ensure the data gets across.
To view this discussion on the web visit https://groups.google.com/d/msgid/fabm-users/794bc5f6-aee9-4dd4-8d2b-1e6fafdebf05n%40googlegroups.com.