INT2LM in routine vert_interpol – in #10: INT2LM

in #10: INT2LM

I guess that there are some unrealistic values in the files
/SCRATCH/acad/cclm/MPI- ESM -LR/historical/year1987/caf1987080318.nc
/SCRATCH/acad/cclm/MPI- ESM -LR/historical/year1989/caf1989081612.nc
However, several colleagues from the CLM -Community already used the data without any problem.
Have you checked the data files by using ncview or/and cdo info or/and setting the idbg_level in the namelist to a high value (which gives more information in the log file. It is better to run int2lm for the idbg_level test with nprocx = 1, nprocy = 1 for the test to get a cleaner logfile)?

  @burkhardtrockel in #c1d5af3

I guess that there are some unrealistic values in the files
/SCRATCH/acad/cclm/MPI- ESM -LR/historical/year1987/caf1987080318.nc
/SCRATCH/acad/cclm/MPI- ESM -LR/historical/year1989/caf1989081612.nc
However, several colleagues from the CLM -Community already used the data without any problem.
Have you checked the data files by using ncview or/and cdo info or/and setting the idbg_level in the namelist to a high value (which gives more information in the log file. It is better to run int2lm for the idbg_level test with nprocx = 1, nprocy = 1 for the test to get a cleaner logfile)?

I guess that there are some unrealistic values in the files
/SCRATCH/acad/cclm/MPI- ESM -LR/historical/year1987/caf1987080318.nc
/SCRATCH/acad/cclm/MPI- ESM -LR/historical/year1989/caf1989081612.nc
However, several colleagues from the CLM -Community already used the data without any problem.
Have you checked the data files by using ncview or/and cdo info or/and setting the idbg_level in the namelist to a high value (which gives more information in the log file. It is better to run int2lm for the idbg_level test with nprocx = 1, nprocy = 1 for the test to get a cleaner logfile)?