INT2LM error with CFU – in #10: INT2LM

in #10: INT2LM

Good afternoon.

I have a next error (Error.jpg), when I’m trying to run calculations.

I have compiled a new version of COSMO - CLM -v.50_clm16, int2lm2.7 and CFU version from the cclm-sp-v3.1.1.

How can I fixed this error?

Best regards,
Evgenii

  @evgeniichuriulin in #a774314

Good afternoon.

I have a next error (Error.jpg), when I’m trying to run calculations.

I have compiled a new version of COSMO - CLM -v.50_clm16, int2lm2.7 and CFU version from the cclm-sp-v3.1.1.

How can I fixed this error?

Best regards,
Evgenii

INT2LM error with CFU

Good afternoon.

I have a next error (Error.jpg), when I’m trying to run calculations.

I have compiled a new version of COSMO - CLM -v.50_clm16, int2lm2.7 and CFU version from the cclm-sp-v3.1.1.

How can I fixed this error?

Best regards,
Evgenii

View in channel

my subchain file

my subchain file

In job_settings the definition

HINCBOUND=6          # time increment of boundary data

should have 2-digits
HINCBOUND=06          # time increment of boundary data

Sorry for this trap!

I found at least two other things:

DO=/sw/rhel6-x64/cdo/cdo-1.6.9-magicsxx-gcc48/bin/cdo      # absolute path of the CDO binary 

CDO is missing a “C”
CDO=/sw/rhel6-x64/cdo/cdo-1.6.9-magicsxx-gcc48/bin/cdo      # absolute path of the CDO binary 

HOUT _INC must be in the form hh:mm::ss, i.e. in the form that you commented out

#HOUT_INC=(7 01:00:00 01:00:00 01:00:00 03:00:00 06:00:00 24:00:00 24:00:00) # time increment for each GRIBOUT hh:mm:ss
HOUT_INC=(7 1 1 1 3 6 24 24) # time increment for each GRIBOUT hh:mm:ss

  @burkhardtrockel in #fa5bd31

In job_settings the definition

HINCBOUND=6          # time increment of boundary data

should have 2-digits
HINCBOUND=06          # time increment of boundary data

Sorry for this trap!

I found at least two other things:

DO=/sw/rhel6-x64/cdo/cdo-1.6.9-magicsxx-gcc48/bin/cdo      # absolute path of the CDO binary 

CDO is missing a “C”
CDO=/sw/rhel6-x64/cdo/cdo-1.6.9-magicsxx-gcc48/bin/cdo      # absolute path of the CDO binary 

HOUT _INC must be in the form hh:mm::ss, i.e. in the form that you commented out

#HOUT_INC=(7 01:00:00 01:00:00 01:00:00 03:00:00 06:00:00 24:00:00 24:00:00) # time increment for each GRIBOUT hh:mm:ss
HOUT_INC=(7 1 1 1 3 6 24 24) # time increment for each GRIBOUT hh:mm:ss

In job_settings the definition

HINCBOUND=6          # time increment of boundary data

should have 2-digits
HINCBOUND=06          # time increment of boundary data

Sorry for this trap!

I found at least two other things:

DO=/sw/rhel6-x64/cdo/cdo-1.6.9-magicsxx-gcc48/bin/cdo      # absolute path of the CDO binary 

CDO is missing a “C”
CDO=/sw/rhel6-x64/cdo/cdo-1.6.9-magicsxx-gcc48/bin/cdo      # absolute path of the CDO binary 

HOUT _INC must be in the form hh:mm::ss, i.e. in the form that you commented out

#HOUT_INC=(7 01:00:00 01:00:00 01:00:00 03:00:00 06:00:00 24:00:00 24:00:00) # time increment for each GRIBOUT hh:mm:ss
HOUT_INC=(7 1 1 1 3 6 24 24) # time increment for each GRIBOUT hh:mm:ss

Dear Burkhardt,

Thank you for your help.

Best, Evgenii

  @evgeniichuriulin in #d419d83

Dear Burkhardt,

Thank you for your help.

Best, Evgenii

Dear Burkhardt,

Thank you for your help.

Best, Evgenii