Hi CGD BB,
I'm in the process of porting CESM to Shaheen II, which is a Cray XC40 at King Abdullah University of Science and Technology.
I began by modifying the config_machines, config_compliers and config_batch xml files to add the new machine, using the existing cori-haswell entry (since it is also a Cray XC40) in each of those files as a starting point for the shaheen entry. After some trial and error I was able to get the prealpha tests for the intel compiler started:
cd $CIMEROOT/scripts
./create_test --xml-category prealpha --xml-machine cheyenne --xml-compiler intel --machine shaheen --compiler intel
A subset of the tests passed and I'm in the process of working through the failed tests to get them to pass.
One test, SMS_D.f09_g16.I1850Clm50BgcSpinup, is behaving peculiarly. When the case is setup it creates a datm.input_data_list that includes filepaths that don't reference $DIN_LOC_ROOT. For this port, $DIN_LOC_ROOT is set to:
/lustre/project/k1421/cesm_store/inputdata/
Instead the filepaths reference the BGCWG project space on GLADE:
/glade/p/cesm/bgcwg_dev/forcing/
This is unique to datm.input_data_list, the other data lists and stream files -- for example, clm.input_data_list -- all have filepaths that reference $DIN_LOC_ROOT. I've attached both of these files for comparison.
I've also attached the error messages that occur when trying to run case.submit.
What should I do here? Should I skip this test? Should I rewrite datm.input_data_list that it references $DIN_LOC_ROOT and try to get:
./check_input_data --download
to transfer the data?
Thank you,
Ben Johnson / johnsonb
I'm in the process of porting CESM to Shaheen II, which is a Cray XC40 at King Abdullah University of Science and Technology.
I began by modifying the config_machines, config_compliers and config_batch xml files to add the new machine, using the existing cori-haswell entry (since it is also a Cray XC40) in each of those files as a starting point for the shaheen entry. After some trial and error I was able to get the prealpha tests for the intel compiler started:
cd $CIMEROOT/scripts
./create_test --xml-category prealpha --xml-machine cheyenne --xml-compiler intel --machine shaheen --compiler intel
A subset of the tests passed and I'm in the process of working through the failed tests to get them to pass.
One test, SMS_D.f09_g16.I1850Clm50BgcSpinup, is behaving peculiarly. When the case is setup it creates a datm.input_data_list that includes filepaths that don't reference $DIN_LOC_ROOT. For this port, $DIN_LOC_ROOT is set to:
/lustre/project/k1421/cesm_store/inputdata/
Instead the filepaths reference the BGCWG project space on GLADE:
/glade/p/cesm/bgcwg_dev/forcing/
This is unique to datm.input_data_list, the other data lists and stream files -- for example, clm.input_data_list -- all have filepaths that reference $DIN_LOC_ROOT. I've attached both of these files for comparison.
I've also attached the error messages that occur when trying to run case.submit.
What should I do here? Should I skip this test? Should I rewrite datm.input_data_list that it references $DIN_LOC_ROOT and try to get:
./check_input_data --download
to transfer the data?
Thank you,
Ben Johnson / johnsonb