How to generate topo file for f05_f05_mg17

[Han Lubin]

Hello everyone,

I am trying to run CESM2.1.3 at the resolution f05_f05_mg17. It seems there is no topo file corresponding to 0.47x0.63 available for CAM6 in https://svn-ccsm-inputdata.cgd.ucar.edu/trunk/inputdata/atm/cam/topo. I realize that the resampling tool in interpic_new can create my own topo file, but I don't find the template file for the resolution 0.47x0.63.

According to "README", I attempt to generate the template file for 0.47x0.63 resolution.

% ncks -v lat,lon baroclinic1.nc SE_temp.nc

Where is the test case file baroclinic1.nc? Where can I find the template file corresponding to 0.47x0.63? Can someone help me with this problem?

Thanks in advance!

 

[nusbaume]

Hi Han Lubin,

Although I have never personally used interpic_new on a topo file, I believe the template file you used in this forum post:

How to get the ncdata corresponding to 0.47x0.63

Hello everyone, I try to get the output including GRAINC_TO_FOOD with 1/2 degree by CESM2.1.3. The surface file and landuse file corresponding to f05_g17 have been generated, and I run this case with compset HIST_DATM%GSWP3v1_CLM50%BGC-CROP_SICE_SOCN_MOSART_SGLC_SWAV and resolution f05_g17...

bb.cgd.ucar.edu

Can be used to interpolate the topo file as well. Otherwise you can find a FV 0.47x0.63 template file in the input data server here:

https://svn-ccsm-inputdata.cgd.ucar.edu/trunk/inputdata/atm/cam/coords/fv_0.47x0.63.nc

Also, just an FYI that the instructions that use the baroclinic1.nc file are for the SE dycore, and thus may result in a bad input file if you try to use them directly for a simulation using the FV dycore (with the one exception being for the vertical coordinate as explained in the linked forum post).

Anyways, I hope that helps, and have a great day!

Jesse

 

[Han Lubin]

Hi Jesse,

Many thanks for your reply! According to your suggestion, I have generated fv_0.47x0.63_L32.nc successfully.

But when I execute

./interpic -t fv_0.47x0.63.nc fv_0.9x1.25_nc3000_Nsw042_Nrs008_Co060_Fi001_ZR_sgh30_24km_GRNL_c170103.nc fv_0.47x0.63_nc3000_Nsw042_Nrs008_Co060_Fi001_ZR_sgh30_24km_GRNL_1_c230219.nc

, I get an error message forrtl: severe (174): SIGSEGV, segmentation fault occurred.

Despite the error message occurs, it seems that the topo file corresponding to 0.47x0.63 generated at the same time. I run this case with compset HIST_CAM60_CLM50%BGC-CROP_CICE%PRES_DOCN%DOM_MOSART_SGLC_SWAV and res f05_f05_mg17, and I set the topo file as my own file in user_nl_cam.

So far, the case is still running and no errors are reported. I am curious about the cause of above error. How can I solve this problem? If the output can be got in this case successfully, does it mean that the generated 0.47x0.63 topo file can be used?

The following are the error message and steps. Thanks in advance!

./interpic -t fv_0.47x0.63.nc fv_0.9x1.25_nc3000_Nsw042_Nrs008_Co060_Fi001_ZR_sgh30_24km_GRNL_c170103.nc fv_0.47x0.63_nc3000_Nsw042_Nrs008_Co060_Fi001_ZR_sgh30_24km_GRNL_1_c230219.nc

Error message:

create var PHIS ndims=           2  dids=           2           1  vid=
          13
 create var LANDFRAC ndims=           2  dids=           2           1  vid=
          14
 create var SGH ndims=           2  dids=           2           1  vid=
          15
 create var SGH30 ndims=           2  dids=           2           1  vid=
          16
 create var LANDM_COSLAT ndims=           2  dids=           2           1  vid=
          17
 create var TERR_UF ndims=           2  dids=           2           1  vid=
          18
 create var SGH_UF ndims=           2  dids=           2           1  vid=
          19
 create var GBXAR ndims=           2  dids=           2           1  vid=
          20
 create var MXDIS ndims=           3  dids=           2           1           7
  vid=          21
 create var RISEQ ndims=           3  dids=           2           1           7
  vid=          22
 create var FALLQ ndims=           3  dids=           2           1           7
  vid=          23
 create var MXVRX ndims=           3  dids=           2           1           7
  vid=          24
 create var MXVRY ndims=           3  dids=           2           1           7
  vid=          25
 create var ANGLL ndims=           3  dids=           2           1           7
  vid=          26
 create var ANGLX ndims=           3  dids=           2           1           7
  vid=          27
 create var ANISO ndims=           3  dids=           2           1           7
  vid=          28
 create var ANIXY ndims=           3  dids=           2           1           7
  vid=          29
 create var HWDTH ndims=           3  dids=           2           1           7
  vid=          30
 create var WGHTS ndims=           3  dids=           2           1           7
  vid=          31
 create var CLNGT ndims=           3  dids=           2           1           7
  vid=          32
 create var CWGHT ndims=           3  dids=           2           1           7
  vid=          33
 create var COUNT ndims=           3  dids=           2           1           7
  vid=          34
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC                Routine            Line        Source             
interpic           000000000046E714  Unknown               Unknown  Unknown
libpthread-2.17.s  00007F6B9FFA5630  Unknown               Unknown  Unknown
libnetcdf.so.15.0  00007F6BA0B0824F  ncx_getn_double_d     Unknown  Unknown
libnetcdf.so.15.0  00007F6BA0ACA500  Unknown               Unknown  Unknown
libnetcdf.so.15.0  00007F6BA0AC3094  NC3_get_vara          Unknown  Unknown
libnetcdf.so.15.0  00007F6BA0AA87FF  NC_get_vara           Unknown  Unknown
libnetcdff.so.6.2  00007F6BA04DD8BD  nf_get_vara_doubl     Unknown  Unknown
interpic           000000000045E350  wrap_get_vara_dou         161  wrap_nf.F90
interpic           000000000041B9FE  driver_                   327  driver.F90
interpic           00000000004283B1  MAIN__                    217  fmain.F90
interpic           0000000000409B8E  Unknown               Unknown  Unknown
libc-2.17.so       00007F6B9FBEA555  __libc_start_main     Unknown  Unknown
interpic           0000000000409AA9  Unknown               Unknown  Unknown

Steps:

./create_newcase --case cam_f05_V --compset HIST_CAM60_CLM50%BGC-CROP_CICE%PRES_DOCN%DOM_MOSART_SGLC_SWAV --res f05_f05_mg17 --run-unsupported --compiler intel --mach bscca3

cd cam_f05_V
./case.setup

vi user_nl_clm
hist_nhtfrq=0,0
hist_mfilt=1,12
hist_fincl2='GRAINC_TO_FOOD'
hist_dov2xy=.true.,.false.
irrigate=.true.
fsurdat='/public1/home/sc93599/CESM2.1.3/my_cesm_sandbox/components/clm/tools/mksurfdata_map/surfdata_0.47x0.63_hist_78pfts_CMIP6_simyr1850_c230128.nc'
flanduse_timeseries='/public1/home/sc93599/CESM2.1.3/my_cesm_sandbox/components/clm/tools/mksurfdata_map/landuse.timeseries_0.47x0.63_hist_78pfts_CMIP6_simyr1850-2015_c230131.nc'

vi user_nl_cam
ncdata='/public1/home/sc93599/CESM2.1.3/my_cesm_sandbox/components/cam/tools/interpic_new/cami-mam3_0000-01-01_0.47x0.63_L32_c230219.nc'
bnd_topo='/public1/home/sc93599/CESM2.1.3/my_cesm_sandbox/components/cam/tools/interpic_new/fv_0.47x0.63_nc3000_Nsw042_Nrs008_Co060_Fi001_ZR_sgh30_24km_GRNL_1_c230219.nc'

./xmlchange STOP_OPTION=nyears
./xmlchange STOP_N=1
./xmlchange RESUBMIT=0
./xmlchange RUN_STARTDATE=1979-01-01
./xmlchange DOUT_S=TRUE

./case.build --skip-provenance-check
./check_case
./check_input_data
./case.submit

By the way, the same error occurs using fv_0.47x0.63_L32.nc instead of fv_0.47x0.63.nc.

 

[Han Lubin]

Hi Jesse,

This case has finished running. Although it takes a lot of time, it seems to have succeeded in getting the output results I need. I guess the error message may be related to my machine. Can I assume that the 0.47x0.63 topo file has been successfully generated?

 

[nusbaume]

Hi Han Lubin,

I am not sure what caused your use of interpic to segfault, but one way to check if everything looks reasonable is to simply look at the variables in your new regridded topo file (say, using ncview) and see if they generally appear to look the same as the original topo file you regridded from. If so then you are probably good to go. If not then please let me know and I'll see if I can reproduce the segfault on my end.

Thanks, and have a great day!

Jesse

 

[Han Lubin]

Hi Jesse,

I appreciate your response on this matter.

Although the task is not interrupted by any error, I suppose the 0.47x0.63 topo file used may be not appropriate for this case. Comparing the new regridded topo file with original file, I realize resolution of the resampled file seems to be different from the template. And the value of some variables is 0, which also does not match the original file. The generated topo file is too large, so I only attach screenshots of the error message. Do you encounter segfault when generating the topo file corresponding to 0.47x0.63? Thanks in advance.