CESM prestage script "File status unknown" ... in multi-instance situations

[thoar]

I run CESM 1.2.1 with multiple instances (in this case 4) and I am specifying a hybrid case.Why is only the last instance 'File status unknown'?  None of the instances are known at this point.The filenames are correct for my implementation. I manually stage them after the cesm_prestagescript has finished.It's also a little disturbing that the "the following files were not found ..." and the very next line is "... Files Found."If no files were not found, perhaps a comment to indicate a successful termination would be appropriate.-------------------------------------------------------------------------
CESM PRESTAGE SCRIPT STARTING
- Case input data directory, DIN_LOC_ROOT, is /glade/p/cesmdata/cseg/inputdata
- Checking the existence of input datasets in DIN_LOC_ROOTThe following files were not found, this is informational only
Input Data List Files Found:
/glade/p/work/thoar/cases/test_cesm1_2_1/Buildconf/cpl.input_data_list
/glade/p/work/thoar/cases/test_cesm1_2_1/Buildconf/cam.input_data_list
/glade/p/work/thoar/cases/test_cesm1_2_1/Buildconf/clm.input_data_list
/glade/p/work/thoar/cases/test_cesm1_2_1/Buildconf/cice.input_data_list
/glade/p/work/thoar/cases/test_cesm1_2_1/Buildconf/pop2.input_data_list
/glade/p/work/thoar/cases/test_cesm1_2_1/Buildconf/rtm.input_data_list
File status unknown: cam_initial_0004.nc
File status unknown: cesm_hybrid.clm2_0004.r.2004-01-10-00000.ncCESM PRESTAGE SCRIPT HAS FINISHED SUCCESSFULLY
-------------------------------------------------------------------------

 

[tcraig]

The check_input_list output does need a revision to make it more clear.  The information it's writing out can largely be ignored except when it complains that a file is missing.  The multi-instance inputs are handled separately and "file status unknown" means that the file is in the input_data_list but is not checked for existance.  check_input_list is working correctly as far as we know, we will update the information dumped to the screen to make it more clear what's happening.

 

[santos]

In more recent versions of the scripts (i.e. CESM 1.3 development), there is an explanatory message at the beginning of this section that might help, but that might need to be further refined.The issue with "File status unknown" files is that in the majority of cases these files are not needed at all, but in a few they are. In general, this is hard to figure out beforehand, because it depends on details of, e.g., how each component does restarts, and the contents of the files themselves. The best we can do is to warn the user, so that if there is a problem, they can go back and look to see if any of these files were needed. But I agree that the message in this case is not at all clear.

 

[thoar]

Lets not miss the point that - for my 4 instance example - there are 4 files that should have 'file status unknown'. Only the last one is reported, which makes me wonder about the others.