register_diagnostic_variable - no matching specific subroutine

[jornbr]

Do you resolve it? I have the similar issue as:
error #8486: There is no matching specific subroutine for this type bound generic subroutine call. [REGISTER_DIAGNOSTIC_VARIABLE]

Originally posted by @bwang63 in #9 (comment)

[jornbr]

This is likely a different issue than the one you commented on (#9 was an ERSEM issue that has been fixed). Which code line triggers this error?

[bwang63]

Dear Bruggeman, Thank you very much for the quick reply. I am sorry for my late reply. The issue that I commented has been resolved. But I have another error when I compile the model: ***@***.*** The code causing this error is as follows. When I change “do” to “do_column”, the model can be compiled successfully but the results calculated are all NaNs. Best wishes Bin ***@***.*** From: Jorn Bruggeman ***@***.***> Date: Wednesday, August 17, 2022 at 6:33 AM To: fabm-model/fabm ***@***.***> Cc: Bin Wang ***@***.***>, Mention ***@***.***> Subject: Re: [fabm-model/fabm] register_diagnostic_variable - no matching specific subroutine (Issue #24) CAUTION: The Sender of this email is not from within Dalhousie. This is likely a different issue than the one you commented on (#9<#9> was an ERSEM issue that has been fixed). Which code line triggers this error? — Reply to this email directly, view it on GitHub<#24 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANQPCDRVAFVRPDVKW6PK7TTVZSWU3ANCNFSM56Y2B7GQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jornbr]

It seems GitHub views your error message as an e-mail address and masks it accordingly. You might want to edit it before sending, e.g., by removing any @.

In any case, "do" and "do_column" have different function and syntax, even though both process the pelagic. "do" is preferred, as it allows FABM and the host model to decide in which order points in space are processed (typically that will be along the first dimension in Fortran). "do_column" processes one water column at a time (the spatial loop is forced to be in the vertical), either top-to-bottom (the default) or bottom-to-top. This is required for processes in which the values in one cell depend on the values above or below it. This is notably the case for light transmission and attenuation.

Note that these routines have different syntax:

subroutine do(self, _ARGUMENTS_DO_)
   class (...), intent(in) :: self
   _DECLARE_ARGUMENTS_DO_

   _LOOP_BEGIN_
      ...
   _LOOP_END_
end subroutine do

versus

subroutine do_column(self, _ARGUMENTS_DO_COLUMN_)
   class (...), intent(in) :: self
   _DECLARE_ARGUMENTS_DO_COLUMN_

   _DOWNWARD_LOOP_BEGIN_
      ...
   _DOWNWARD_LOOP_END_
end subroutine do_column

(DOWNWARD could be replaced by UPWARD as needed)

I would need to see a code snippet to understand better what might be going wrong in your case.

[jornbr]

Closing this issue given the lack of further responses.