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

Request for 0.25° surfdata File for FSPCAMM Compset in CESM2

Status
Not open for further replies.

feifeiya

Bifeiya
New Member
Hi

I am currently working with CESM2, specifically running the FSPCAMM compset at a 0.25° resolution, but I have encountered some issues regarding the surface data (fsurdata) input files.

  1. When I attempted to use the surfdata_0.23x0.31_simyr2000_c100406.nc file, I received an error message indicating that the GLACIER_REGION variable was missing:
    ERROR: GLACIER_REGION NOT on surfdata file ERROR in glcBehaviorMod.F90 at line.
  2. I then tried using the surfdata_0.9x1.25_hist_16pfts_Irrig_CMIP6_simyr2000_c190214.nc file, but encountered issues due to the resolution mismatch, and my attempts to interpolate the data were unsuccessful.
As I was unable to find a suitable 0.25° resolution surfdata file that works for my FSPCAMM configuration, I would like to inquire if there is any way to obtain the 0.25° version of the surfdata file or an alternative solution to this problem.

If this data is not currently available, I would greatly appreciate any guidance on how to proceed, or any recommendations for generating or interpolating the necessary surface data for my use case.

Thanks!






Describe your problem or question:
 

peverley

Courtney Peverley
Moderator
Staff member
Hi,

Can you elaborate on what dycore/grid you are using? You say quarter degree - are you using the f02_f02 grid?

Thanks,
Courtney
 
Vote Upvote 0 Downvote

feifeiya

Bifeiya
New Member
Hi,

Can you elaborate on what dycore/grid you are using? You say quarter degree - are you using the f02_f02 grid?

Thanks,
Courtney
Hi Courtney,

Thanks for getting back to me!

Yes, I’m using the f02_f02_mg17 grid at 0.25° resolution for my FSPCAMM setup in CESM2.

Let me know if you need any more details from my side, or if there’s anything specific I can do to work around the surfdata issue.

Looking forward to your advice!
 
Vote Upvote 0 Downvote

feifeiya

Bifeiya
New Member
Hi Courtney,

Thanks for getting back to me!

Yes, I’m using the f02_f02_mg17 grid at 0.25° resolution for my FSPCAMM setup in CESM2.

Let me know if you need any more details from my side, or if there’s anything specific I can do to work around the surfdata issue.

Looking forward to your advice!
I also wanted to mention that I used the Python xesmf library to successfully regrid the GLACIER_REGION variable and added it to the original surfdata file that was missing this variable. However, after re-running the model, I encountered the following error:

Image PC Routine Line Source
cesm.exe 0000000002934DFD Unknown Unknown Unknown
cesm.exe 000000000270D119 pio_support_mp_pi 118 pio_support.F90
cesm.exe 000000000270AF16 pio_utils_mp_chec 74 pio_utils.F90
cesm.exe 00000000026F1960 nf_mod_mp_pio_inq 1288 nf_mod.F90
cesm.exe 0000000001D32F96 ncdio_pio_mp_chec 360 ncdio_pio.F90.in
cesm.exe 0000000001DAACAE surfrdmod_mp_surf 514 surfrdMod.F90
cesm.exe 0000000001DA8B8A surfrdmod_mp_surf 394 surfrdMod.F90
cesm.exe 0000000001C47E94 clm_initializemod 175 clm_initializeMod.F90
cesm.exe 0000000001C2C6D9 lnd_comp_mct_mp_l 199 lnd_comp_mct.F90
cesm.exe 0000000000439640 component_mod_mp_ 267 component_mod.F90
cesm.exe 0000000000425CC7 cime_comp_mod_mp_ 1237 cime_comp_mod.F90
cesm.exe 0000000000436441 MAIN__ 114 cime_driver.F90
cesm.exe 000000000041471E Unknown Unknown Unknown
libc-2.17.so 00002B639DAE53D5 __libc_start_main Unknown Unknown
cesm.exe 0000000000414629 Unknown Unknown Unknown
Abort(1) on node 1 (rank 1 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 1
/opt/gridview/slurm/spool/slurmd/job17041015/slurm_script: line 52: syntax error: unexpected end of file

I’ve attached my cesm.log and lnd_in file for reference, in case it might provide additional context to help troubleshoot this issue.
Thanks,
Bifeiya
 
Vote Upvote 0 Downvote

peverley

Courtney Peverley
Moderator
Staff member
Hi Bifeiya,

Thanks for the additional context! I'm going to move this to the land forum in the hopes that the experts over there can help!
 
Vote Upvote 0 Downvote

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I don't see any attachments. The snippet you provided however points to line 514 of surfrdMod.F90. In release-cesm2.1.5, that line is:

call check_dim(ncid, 'nglcecp1', maxpatch_glcmec+1 )

Maybe you don't have nglcecp1 as a dimension in your surface dataset?
 
Vote Upvote 0 Downvote

feifeiya

Bifeiya
New Member
I don't see any attachments. The snippet you provided however points to line 514 of surfrdMod.F90. In release-cesm2.1.5, that line is:

call check_dim(ncid, 'nglcecp1', maxpatch_glcmec+1 )

Maybe you don't have nglcecp1 as a dimension in your surface dataset?
Hi,

Thanks for your reply, and sorry for forgetting to attach the files in my last message! This time, I’ve attached both the cesm.log and lnd_in files.

I also took a look at the surfrdMod.F90 file in CESM2.1.3, and I see that line 514 is the same:

call check_dim(ncid, 'nglcecp1', maxpatch_glcmec+1)

I checked my surfdata, and it turns out that it’s missing the nglcecp1 dimension. Currently, I’m using the older surfdata_0.23x0.31_simyr2000_c100406.nc, which lacks some variables. I’ve only added the glacier region from surfdata_0.9x1.25_hist_16pfts_Irrig_CMIP6_simyr2000_c190214.nc after regridding it, but from the current situation, there are still some missing pieces.

So, I was wondering: would it be feasible to use Python’s xesmf library to regrid all the variables from surfdata_0.9x1.25_hist_16pfts_Irrig_CMIP6_simyr2000_c190214.nc to the 0.23x0.31 grid? I realize this might take some time, but I’m not sure if there’s a better way to do it.

Alternatively, do you have any recommendations for obtaining a surfdata file that would work for the f02_f02_mg17 case? If you happen to have a newer version of the 0.23x0.31 surfdata, it would be greatly appreciated, as I believe others might need it as well.

Thanks!​
 

Attachments

  • lnd_in.txt
    6.1 KB · Views: 1
  • cesm.log.17041015.txt
    1.7 KB · Views: 1
  • regrid.py.txt
    1.1 KB · Views: 1
Vote Upvote 0 Downvote

slevis

Moderator
Staff member
Looking on derecho here:
/glade/campaign/cesm/cesmdata/cseg/inputdata/lnd/clm2/surfdata_map
/glade/campaign/cesm/cesmdata/cseg/inputdata/lnd/clm2/surfdata_esmf/ctsm5.2.0
/glade/campaign/cesm/cesmdata/cseg/inputdata/lnd/clm2/surfdata_esmf/ctsm5.3.0
I do not see that resolution, suggesting that it's not one of the resolutions that we provide.

I am not aware of a regridding tool for fsrudat files. We provide a tool for generating new fsurdat files, the mksurfdata_esmf tool available since ctsm5.2. In earlier versions you will find the predecessor tool (mksurfdata_map I think). Both have README files explaining how to use them. The older tool has documentation in the User's Guide, as well:
 
Vote Upvote 0 Downvote
Status
Not open for further replies.
Top