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

Input boundary SST dataset

Hi,

1) I created a case using CESM1_2_2 version, F_2000_CAM5 compset, ne120_ne120 resolution.

The default SST file is on 1x1deg
/glade/p/cesm/cseg/inputdata/atm/cam/sst/sst_HadOIBl_bc_1x1_clim_c101029.nc

2) I created another similar case based on an earlier CESM model, i.e., CESM1_0_5 version, F_2000_CAM5 compset, f02_f02 resolution.

The default SST file is on 0.25x0.25 deg resolution, /glade/p/cesm/cseg/inputdata/ocn/docn7/SSTDATA/sst_HadOIBl_bc_0.23x0.31_clim_c061106.nc

My question is why would the default boundary SST file in the first case is on 1x1 deg for models running on 0.25x0.25 deg? For the second case, it makes sense to me that the boundary SST files is on 0.25x0.25deg.

Thanks,
Ying
 

hannay

Cecile Hannay
AMWG Liaison
Staff member
The observated SST comes from a 1x1 degree. It is the same datasets that it used for all CESM resolutions.In older version of CESM, we were regridding the 1x1 degree observation SSTs on the CESM grid. (this is your case 1)

Now we do this interpolation on the fly while CESM is running. (this is your case 2)Cecile
 

hannay

Cecile Hannay
AMWG Liaison
Staff member
The observated SST comes from a 1x1 degree. It is the same datasets that it used for all CESM resolutions.In older version of CESM, we were regridding the 1x1 degree observation SSTs on the CESM grid. (this is your case 1)

Now we do this interpolation on the fly while CESM is running. (this is your case 2)Cecile
 
Hi Cecile,Thanks for your response. So in the newer version of the model, it reads the 1x1 deg SST, and intepolates onto the 0.25x0.25 deg while the model is running. Actally, I need to do a prescribed SST run, and need to change the boundary SST. I already have the SST dataset on 0.25x0.25. If I simply change the input file to point to my own's SST dataset. I got the error message like this:742:INFO: 0031-306  pm_atexit: pm_exit_value is 1. 466:(shr_dmodel_readstrm) ERROR in data sizes     1152     768   64800466:(shr_sys_abort) ERROR: (shr_dmodel_readstrm) ERROR in data sizes(shr_dmodel_readstrm) ERROR in data sizes     1152     768   64800So could you please give me some advice on how to fix that?Thanks,Ying  
 
Hi Cecile,Thanks for your response. So in the newer version of the model, it reads the 1x1 deg SST, and intepolates onto the 0.25x0.25 deg while the model is running. Actally, I need to do a prescribed SST run, and need to change the boundary SST. I already have the SST dataset on 0.25x0.25. If I simply change the input file to point to my own's SST dataset. I got the error message like this:742:INFO: 0031-306  pm_atexit: pm_exit_value is 1. 466:(shr_dmodel_readstrm) ERROR in data sizes     1152     768   64800466:(shr_sys_abort) ERROR: (shr_dmodel_readstrm) ERROR in data sizes(shr_dmodel_readstrm) ERROR in data sizes     1152     768   64800So could you please give me some advice on how to fix that?Thanks,Ying  
 

hannay

Cecile Hannay
AMWG Liaison
Staff member
It looks like you are not using the appropriate domain files. These should match your SSTs.
 

hannay

Cecile Hannay
AMWG Liaison
Staff member
It looks like you are not using the appropriate domain files. These should match your SSTs.
 

mlevy

Michael Levy
CSEG and Liaisons
Staff member
Hi Ying,It sounds like you want to run on the ne120_ne120 grid using an SST data file meant for the f02_f02 grid, is that correct? Could you give more detail on what you changed in the ne120_ne120 case that provided the error you mentioned earlier ("ERROR in data sizes     1152     768   64800")?If you changed the SST data file by changing fileNames under fieldInfo in user_docn.streams.txt.prescribed then you need to also change the filePath and fileNames field under domainInfo. Instead of
   /glade/p/cesmdata/cseg/inputdata/ocn/docn7


   domain.ocn.1x1.111007.nc
you want to use
   /glade/p/cesmdata/cseg/inputdata/atm/cam/ocnfrac


   domain.camocn.0.23x0.31_gx1v6_101108.nc
~Mike
 

mlevy

Michael Levy
CSEG and Liaisons
Staff member
Hi Ying,It sounds like you want to run on the ne120_ne120 grid using an SST data file meant for the f02_f02 grid, is that correct? Could you give more detail on what you changed in the ne120_ne120 case that provided the error you mentioned earlier ("ERROR in data sizes     1152     768   64800")?If you changed the SST data file by changing fileNames under fieldInfo in user_docn.streams.txt.prescribed then you need to also change the filePath and fileNames field under domainInfo. Instead of
   /glade/p/cesmdata/cseg/inputdata/ocn/docn7


   domain.ocn.1x1.111007.nc
you want to use
   /glade/p/cesmdata/cseg/inputdata/atm/cam/ocnfrac


   domain.camocn.0.23x0.31_gx1v6_101108.nc
~Mike
 
Hi Mike,Thanks for your reply. Yes. The SST boundary data I would like to use was orignially used in the CAM5.1, FV dynamic core. But I would like to do the exact same experiments with CAM5.2, SE dynamic core.  Here are the basic changes I made in my ne120_ne120 case, (case directory is in /glade/u/home/yingli/cesm/runs/f.F2000C5.ne120_ne120.test.001)./create_newcase -case $CASEDIR -res ne120_ne120 -compset F_2000_CAM5 -mach yellowstone./xmlchange -file env_run.xml -id SSTICE_DATA_FILENAME -val "./sst_oi_climo_mon_mean_CAMgrid_KOE_control.nc"copied the sst_oi_climo_mon_mean_CAMgrid_KOE_control.nc to the run directoryThanks,Ying 
 
Hi Mike,Thanks for your reply. Yes. The SST boundary data I would like to use was orignially used in the CAM5.1, FV dynamic core. But I would like to do the exact same experiments with CAM5.2, SE dynamic core.  Here are the basic changes I made in my ne120_ne120 case, (case directory is in /glade/u/home/yingli/cesm/runs/f.F2000C5.ne120_ne120.test.001)./create_newcase -case $CASEDIR -res ne120_ne120 -compset F_2000_CAM5 -mach yellowstone./xmlchange -file env_run.xml -id SSTICE_DATA_FILENAME -val "./sst_oi_climo_mon_mean_CAMgrid_KOE_control.nc"copied the sst_oi_climo_mon_mean_CAMgrid_KOE_control.nc to the run directoryThanks,Ying 
 

mlevy

Michael Levy
CSEG and Liaisons
Staff member
You also need to update the SSTICE_GRID_FILENAME variable. Try: $ ./xmlchange SSTICE_GRID_FILENAME='$DIN_LOC_ROOT/atm/cam/ocnfrac/domain.camocn.0.23x0.31_gx1v6_101108.nc' 
 

mlevy

Michael Levy
CSEG and Liaisons
Staff member
You also need to update the SSTICE_GRID_FILENAME variable. Try: $ ./xmlchange SSTICE_GRID_FILENAME='$DIN_LOC_ROOT/atm/cam/ocnfrac/domain.camocn.0.23x0.31_gx1v6_101108.nc' 
 
Thanks Mike. I changed SSTICE_GRID_FILENAME. and got the follwoing error mesage: ERROR 1 from file /project/sprelcot/build/rcots007a/src/ppe/lapi/Sam.cpp line 879Case directory is: /glade/u/home/yingli/cesm/runs/f.F2000C5.ne120_ne120.test.003
 
Thanks Mike. I changed SSTICE_GRID_FILENAME. and got the follwoing error mesage: ERROR 1 from file /project/sprelcot/build/rcots007a/src/ppe/lapi/Sam.cpp line 879Case directory is: /glade/u/home/yingli/cesm/runs/f.F2000C5.ne120_ne120.test.003
 

mlevy

Michael Levy
CSEG and Liaisons
Staff member
I wonder if that's a hardware issue, because it didn't get as far as your previous run... maybe just try submitting it again and see if that error occurs again?
 

mlevy

Michael Levy
CSEG and Liaisons
Staff member
I wonder if that's a hardware issue, because it didn't get as far as your previous run... maybe just try submitting it again and see if that error occurs again?
 
I tried again, and the run crased again. 7605:ERROR 1 from file /project/sprelcot/build/rcots007a/src/ppe/lapi/Sam.cpp line 8797605:Sam::CheckTimeout TIMEOUT happened 7605:Error received in error handler.
 
Top