Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

functional test ERS.f19_g16.I failed

Dear ALL,

My porting of CESM failed with ERS.f19_g16.I. Any idea?

Platform: X86_64 Linux cluster
Compiler: Intel 11.1.072

When building, got the following message:

The following files were not found, this is informational only
Input Data List Files Found:
/scratch/pingluo/testeos/Buildconf/clm.input_data_list
/scratch/pingluo/testeos/Buildconf/cpl.input_data_list
/scratch/pingluo/testeos/Buildconf/datm.input_data_list
File status unknown: I2000CN_f19_g16_c100503.clm2.r.0001-01-01-00000.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-01.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-02.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-03.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-04.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-05.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-06.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-07.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-08.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-09.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-10.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-11.nc
File status unknown: UNSET/Solar6Hrly/clmforc.Qian.c2006.T62.Solr.2003-12.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-01.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-02.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-03.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-04.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-05.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-06.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-07.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-08.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-09.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-10.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-11.nc
File status unknown: UNSET/Precip6Hrly/clmforc.Qian.c2006.T62.Prec.2003-12.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-01.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-02.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-03.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-04.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-05.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-06.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-07.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-08.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-09.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-10.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-11.nc
File status unknown: UNSET/TmpPrsHumWnd3Hrly/clmforc.Qian.c2006.T62.TPQW.2003-12.nc
 
The problem has not been solved. Any suggestions?

It appears that CESM didn't set the path for DIN_LOC_ROOT_CLMQIAN in env_run.xml. DIN_LOC_ROOT_CLMQIAN remained be UNSET.
 
I got it. I didn't specify DIN_LOC_ROOT_CLMQIAN in the machine configuration file. After putting a value for it, all the clmforc.Qian.* can be downloaded.

However, I still have "File status unknown: I2000CN_f19_g16_c100503.clm2.r.0001-01-01-00000.nc " error.
 
BTW, the error "File status unknown: I2000CN_f19_g16_c100503.clm2.r.0001-01-01-00000.nc " is not from the functional test. It is from a complete new case, created with:

create_newcase -case casename -res f19_g16 -mach mymachine -compset I
 
Hy bro, File status unknown: I2000CN_f19_g16_c100503.clm2.r.0001-01-01-00000.nc did you solve this error that time?I am getting the same error, i am really confused about the reason.I will be really thankful, if you help me.Thanks
 
Top