--
You received this message because you are subscribed to the Google Groups "FABM-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabm-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fabm-devel/1f61c5a5-45ff-4378-a8c4-bae85d71170an%40googlegroups.com.
Thank you Carsten! So, I either have to downgrade my version of FABM or to change the ECOSMO code to make it compatible with the current version, whereas the latter would be the more sustainable solution, right?
carsten...@googlemail.com schrieb am Donnerstag, 4. November 2021 um 13:02:38 UTC+1:Dear Kai,This is a shortcoming of the current implementation of the SCHISM host, it is not a problem within FABM itself. The error is generated for FABM with current API (official FABM), not the old API (Hereon local repo) which you probably want to use with NERSC/ecosmo.Cheers,CarstenAm 04.11.2021 um 12:56 schrieb Kai Logemann <kai.lo...@gmail.com>:Dear all,when trying to compile the official NERSC-ECOSMO version I get the following error message:/work/bg1184/g260110/icon_ecosmo/fabm/src/models/nersc/ecosmo.F90(461): error #8486: There is no matching specific subroutine for this type bound generic subroutine call. [REGISTER_DEPENDENCY]call self%register_dependency(self%id_f2det,'ECO_F2De')What does it mean?Thanks in advance,Kai Logemann--
You received this message because you are subscribed to the Google Groups "FABM-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabm-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fabm-devel/1f61c5a5-45ff-4378-a8c4-bae85d71170an%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "FABM-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabm-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fabm-devel/1b12625c-23c2-44d0-8718-be4f32e9c1adn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fabm-devel/a34213fb-aff7-4655-9743-9a206b742b4fn%40googlegroups.com.
Hi Kai, Carsten,
My guess that this specific issue can be solved by adding the units and long name in the call to register, like this:
call self%register_dependency(self%id_f2det,'ECO_F2De', 'UNITS', 'LONG_NAME')
The syntax without units and long name was deprecated quite long ago.
In general, there should be very few changes to biogeochemical codes needed when upgrading FABM [with the exception of models that read their configuration from namelists – they need to move to the yaml format introduced in FABM in 2014]
Cheers,
Jorn
To view this discussion on the web visit https://groups.google.com/d/msgid/fabm-devel/a34213fb-aff7-4655-9743-9a206b742b4fn%40googlegroups.com.