problem with gcm_to_cclm test – in #12: CCLM Starter Package Support

in #12: CCLM Starter Package Support

I assume that you run the original run_int2lm script without any modifications? In that case it might be a problem with your computer system, i.e. compiler and options, mpi version etc. If you provide information on

  • the name of the computing system you use
  • the name of the compiler and its version
  • the name of the mpi and its version
  • attach the Fopts file from /home/dokukin/work/cosmo/cclm-sp_2.4/src/int2lm

maybe someone from the CLM -Community using a similar configuration can help.

The different binary name is not the reason, because this is an information which has to be set by the user (see the following snippet from the subroutine info_int2lm.f90 ) and does not has any effect on the model run.


! Currently it is not possible with FORTRAN95 to get the information
! of the full path of binary name like the $0 in C. Additionally
! we cannot determine on which host(s) the binary is running and the
! domain of the data spread through the nodes.
! Therefore this information has to be defined manually. On using info_readnl()
! this information may be defined within the segment /info_defaults/ which
! has to reside within the named namelist of your choice. Missing information
! will be ignored silently.
! Currently following information may be defined within /info_defaults/:
! INFO_Options ..: List of print options
! INFO_BinaryName: Name (best: full path) of the binary
! INFO_RunMachine: The machine (OS) where the program is running
! INFO_Nodes ….: Description of the nodes the binary is running
! INFO_Domain …: The domain the binary is calculating

  @burkhardtrockel in #d8cb29b

I assume that you run the original run_int2lm script without any modifications? In that case it might be a problem with your computer system, i.e. compiler and options, mpi version etc. If you provide information on

  • the name of the computing system you use
  • the name of the compiler and its version
  • the name of the mpi and its version
  • attach the Fopts file from /home/dokukin/work/cosmo/cclm-sp_2.4/src/int2lm

maybe someone from the CLM -Community using a similar configuration can help.

The different binary name is not the reason, because this is an information which has to be set by the user (see the following snippet from the subroutine info_int2lm.f90 ) and does not has any effect on the model run.


! Currently it is not possible with FORTRAN95 to get the information
! of the full path of binary name like the $0 in C. Additionally
! we cannot determine on which host(s) the binary is running and the
! domain of the data spread through the nodes.
! Therefore this information has to be defined manually. On using info_readnl()
! this information may be defined within the segment /info_defaults/ which
! has to reside within the named namelist of your choice. Missing information
! will be ignored silently.
! Currently following information may be defined within /info_defaults/:
! INFO_Options ..: List of print options
! INFO_BinaryName: Name (best: full path) of the binary
! INFO_RunMachine: The machine (OS) where the program is running
! INFO_Nodes ….: Description of the nodes the binary is running
! INFO_Domain …: The domain the binary is calculating

I assume that you run the original run_int2lm script without any modifications? In that case it might be a problem with your computer system, i.e. compiler and options, mpi version etc. If you provide information on

  • the name of the computing system you use
  • the name of the compiler and its version
  • the name of the mpi and its version
  • attach the Fopts file from /home/dokukin/work/cosmo/cclm-sp_2.4/src/int2lm

maybe someone from the CLM -Community using a similar configuration can help.

The different binary name is not the reason, because this is an information which has to be set by the user (see the following snippet from the subroutine info_int2lm.f90 ) and does not has any effect on the model run.


! Currently it is not possible with FORTRAN95 to get the information
! of the full path of binary name like the $0 in C. Additionally
! we cannot determine on which host(s) the binary is running and the
! domain of the data spread through the nodes.
! Therefore this information has to be defined manually. On using info_readnl()
! this information may be defined within the segment /info_defaults/ which
! has to reside within the named namelist of your choice. Missing information
! will be ignored silently.
! Currently following information may be defined within /info_defaults/:
! INFO_Options ..: List of print options
! INFO_BinaryName: Name (best: full path) of the binary
! INFO_RunMachine: The machine (OS) where the program is running
! INFO_Nodes ….: Description of the nodes the binary is running
! INFO_Domain …: The domain the binary is calculating