The mismatch of the actual and reference date – in #9: CCLM

in #9: CCLM

Hello,

I got date mismatch error ( ERROR CODE : 8102) while running CCLM -v5.0_clm15 with 0.44deg resolution for future period. I have already used almost the same script for the simulation of reference period and I didn’t encounter any problems. You can find my attempts below to solve the problem but the error still exists.

  • I restarted the model run after reproducing the int2lm data again.
  • I rerun the model by changing number of the processors.
  • I restarted the model after replacing the lbfd2092081906.nc file with a working file in case it was corrupted.

I’m attaching the log-file and YUSPECIF . Does any of you have an idea about the reason of the problem?

Cheers,

Cemre

  @cemreyürük in #e1679c9

Hello,

I got date mismatch error ( ERROR CODE : 8102) while running CCLM -v5.0_clm15 with 0.44deg resolution for future period. I have already used almost the same script for the simulation of reference period and I didn’t encounter any problems. You can find my attempts below to solve the problem but the error still exists.

  • I restarted the model run after reproducing the int2lm data again.
  • I rerun the model by changing number of the processors.
  • I restarted the model after replacing the lbfd2092081906.nc file with a working file in case it was corrupted.

I’m attaching the log-file and YUSPECIF . Does any of you have an idea about the reason of the problem?

Cheers,

Cemre

The mismatch of the actual and reference date

Hello,

I got date mismatch error ( ERROR CODE : 8102) while running CCLM -v5.0_clm15 with 0.44deg resolution for future period. I have already used almost the same script for the simulation of reference period and I didn’t encounter any problems. You can find my attempts below to solve the problem but the error still exists.

  • I restarted the model run after reproducing the int2lm data again.
  • I rerun the model by changing number of the processors.
  • I restarted the model after replacing the lbfd2092081906.nc file with a working file in case it was corrupted.

I’m attaching the log-file and YUSPECIF . Does any of you have an idea about the reason of the problem?

Cheers,

Cemre

View in channel

Can you send the output of
ncdump -v time /data/data_int2lm_mpi_med044_rcp85/lbfd2092081906.nc
please.

  @burkhardtrockel in #3dba9c1

Can you send the output of
ncdump -v time /data/data_int2lm_mpi_med044_rcp85/lbfd2092081906.nc
please.

Can you send the output of
ncdump -v time /data/data_int2lm_mpi_med044_rcp85/lbfd2092081906.nc
please.

Dear Burkhardt,

You can find the output file in the attachment.

Regards,
Cemre

  @cemreyürük in #e66cfed

Dear Burkhardt,

You can find the output file in the attachment.

Regards,
Cemre

Dear Burkhardt,

You can find the output file in the attachment.

Regards,
Cemre

The is an overflow in an integer precision when calculating a time difference. Actually a bug in the program.
Can you try to replace in src_input.f90

       iref_act = iref_actsp * 60 + isec - isec_ref         !--br 15.05.19

by
      iref_act = INT(iref_actsp,int_dp) * 60_int_dp + INT(isec,int_dp) - INT(isec_ref,int_dp)         !--br 15.07.20

compile COSMO - CLM and try again?
If this does not work and you are sure that all your input data have the right date you can try to comment out the following lines in src_input.f90 and compile the program again:
      IF (iref_act /= itimepassed) THEN
        ierror = 10
      ENDIF

  @burkhardtrockel in #b751f8c

The is an overflow in an integer precision when calculating a time difference. Actually a bug in the program.
Can you try to replace in src_input.f90

       iref_act = iref_actsp * 60 + isec - isec_ref         !--br 15.05.19

by
      iref_act = INT(iref_actsp,int_dp) * 60_int_dp + INT(isec,int_dp) - INT(isec_ref,int_dp)         !--br 15.07.20

compile COSMO - CLM and try again?
If this does not work and you are sure that all your input data have the right date you can try to comment out the following lines in src_input.f90 and compile the program again:
      IF (iref_act /= itimepassed) THEN
        ierror = 10
      ENDIF

The is an overflow in an integer precision when calculating a time difference. Actually a bug in the program.
Can you try to replace in src_input.f90

       iref_act = iref_actsp * 60 + isec - isec_ref         !--br 15.05.19

by
      iref_act = INT(iref_actsp,int_dp) * 60_int_dp + INT(isec,int_dp) - INT(isec_ref,int_dp)         !--br 15.07.20

compile COSMO - CLM and try again?
If this does not work and you are sure that all your input data have the right date you can try to comment out the following lines in src_input.f90 and compile the program again:
      IF (iref_act /= itimepassed) THEN
        ierror = 10
      ENDIF

iref_act is calculated in src_input.f90 as;
> iref_act = iref_act * 60._ireals + isec – isec_ref

Also, iref_actsp and int_dp wasn’t defined in src_input.f90 so it gives error when I compile COSMO - CLM again. I have attached the src_input.f90

  @cemreyürük in #6e54e4c

iref_act is calculated in src_input.f90 as;
> iref_act = iref_act * 60._ireals + isec – isec_ref

Also, iref_actsp and int_dp wasn’t defined in src_input.f90 so it gives error when I compile COSMO - CLM again. I have attached the src_input.f90

iref_act is calculated in src_input.f90 as;
> iref_act = iref_act * 60._ireals + isec – isec_ref

Also, iref_actsp and int_dp wasn’t defined in src_input.f90 so it gives error when I compile COSMO - CLM again. I have attached the src_input.f90

You do not run the latest version:
https://redc.clm-community.eu/projects/cclm/wiki/Downloads
COSMO- CLM -v5.0_clm16.tar.gz
If you use this version even my proposed change in src_input.f90 may not be necessary.

  @burkhardtrockel in #ea961a8

You do not run the latest version:
https://redc.clm-community.eu/projects/cclm/wiki/Downloads
COSMO- CLM -v5.0_clm16.tar.gz
If you use this version even my proposed change in src_input.f90 may not be necessary.

You do not run the latest version:
https://redc.clm-community.eu/projects/cclm/wiki/Downloads
COSMO- CLM -v5.0_clm16.tar.gz
If you use this version even my proposed change in src_input.f90 may not be necessary.

You are right, I was running COSMO - CLM -v5.0_clm15 in the latest version of starter package. Now, I replaced it with the new version ( COSMO - CLM -v5.0_clm16) and compiled the program again. Then, I restarted cclm script but it did not work. Finally, I changed iref_act with the proposed line and now it seems cclm is working without error! To be on the safe side, would you suggest simulating the whole time period from the beginning?

Thank you very much for your suggestions and help.

  @cemreyürük in #1456679

You are right, I was running COSMO - CLM -v5.0_clm15 in the latest version of starter package. Now, I replaced it with the new version ( COSMO - CLM -v5.0_clm16) and compiled the program again. Then, I restarted cclm script but it did not work. Finally, I changed iref_act with the proposed line and now it seems cclm is working without error! To be on the safe side, would you suggest simulating the whole time period from the beginning?

Thank you very much for your suggestions and help.

You are right, I was running COSMO - CLM -v5.0_clm15 in the latest version of starter package. Now, I replaced it with the new version ( COSMO - CLM -v5.0_clm16) and compiled the program again. Then, I restarted cclm script but it did not work. Finally, I changed iref_act with the proposed line and now it seems cclm is working without error! To be on the safe side, would you suggest simulating the whole time period from the beginning?

Thank you very much for your suggestions and help.

Changes from 5.0clm15 to 5.0clm16 are

  • corrected a bug for netCDF restart files when running long time simulations: change some variable definitions to higher precision
    affected modules:

* src_input.f90
  • add cell_method “time: point” to instantaneous quantities.
    affected modules:
* netcdf_io.f90
  • allow for missing_value==-1.E20 in CIN _MU, CIN _ML, CAPE _MU, CAPE _ML in case of netCDF output
    affected modules:
* src_output.f90


These should not affect the results. However, you can also just replace the src_input.f90 in your clm5-code by the one you changed in the clm16 version to avoid inconsistencies in the output meta data.

  @burkhardtrockel in #b52c3d8

Changes from 5.0clm15 to 5.0clm16 are

  • corrected a bug for netCDF restart files when running long time simulations: change some variable definitions to higher precision
    affected modules:

* src_input.f90
  • add cell_method “time: point” to instantaneous quantities.
    affected modules:
* netcdf_io.f90
  • allow for missing_value==-1.E20 in CIN _MU, CIN _ML, CAPE _MU, CAPE _ML in case of netCDF output
    affected modules:
* src_output.f90


These should not affect the results. However, you can also just replace the src_input.f90 in your clm5-code by the one you changed in the clm16 version to avoid inconsistencies in the output meta data.

Changes from 5.0clm15 to 5.0clm16 are

  • corrected a bug for netCDF restart files when running long time simulations: change some variable definitions to higher precision
    affected modules:

* src_input.f90
  • add cell_method “time: point” to instantaneous quantities.
    affected modules:
* netcdf_io.f90
  • allow for missing_value==-1.E20 in CIN _MU, CIN _ML, CAPE _MU, CAPE _ML in case of netCDF output
    affected modules:
* src_output.f90


These should not affect the results. However, you can also just replace the src_input.f90 in your clm5-code by the one you changed in the clm16 version to avoid inconsistencies in the output meta data.