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

CTSM resolution problem

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I think that script just creates global or latitude-band CO2 files for use by datm using as input CAM ghg files.
To my knowledge all of the files have been created and are at:

/glade/p/cesmdata/cseg/inputdata/atm/datm7/CO2/
 

maruf2812

Montasir Maruf
Member
Hi @oleson, I have used this line to create surface data for 1 deg run (./getregional_datasets.pl -sw 25,235 -ne 52.9375,292). In this case what will be my input file?
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I haven't done this before but I imagine your input files would need to be global 1deg domain and surface datasets. You could get these filenames by creating a 1deg global case, running preview_namelists, and then looking at lnd_in. @erik may be able to provide further guidance here. If you are using CTSM master/main then the subset_data.py might be an alternative script to use, although I think there is further development of this script in an upcoming tag.
 

maruf2812

Montasir Maruf
Member
Hi @oleson, Thank you for your kind help. I have followed your instruction: create a case for 1 deg, get the surface and atm dataset from ./getregional_datasets.pl. I put the atm and surface dataset in my user_nl_clm but in case.build step is failing and showed the following error. I have attached the screenshots.

2.JPG

1.JPG
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I think you need to remove fatmlndfrac from your user_nl_clm and instead specify the path and filename in env_run.xml using LND_DOMAIN_PATH and LND_DOMAIN_FILE.
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
You are requesting more processors than the number of land grid cells. Your env_mach_pes.xml is probably still setup for a global case. Try reducing the number of tasks (NTASKS in env_mach_pes.xml).
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I think your ATM_DOMAIN_FILE needs to be set to the NLDAS2 resolution if that is what your forcing data is.
 

maruf2812

Montasir Maruf
Member
Hi @oleson thank you again. Can I use my 0.125 deg resolution run ATM_DOMAIN_FILE (domain.lnd.0.125nldas2_0.125nldas2.190410.nc) for this 1 deg run? In that case do I need to only change the surface dataset that I got from ./getregional?
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
You could create an NLDAS2 1deg forcing file. But you should be able to force your 1deg surface with the NLDAS2 atm data, I must be missing something. I'll take a closer look at this in a day or two.
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
Ok, I think I have something that is working now. A 1deg surface forced by NLDAS atm.
Rather than go into all of the details, here is a case you can look at:

/glade/work/oleson/ctsm_runs/CTSM_CLM5.0_1deg_V1

I started by cloning this case:

/glade/u/home/maruf/CTSM_CLM5.0_SP_V1

So just look at the differences in files between yours and mine (e.g., user_nl_clm, env_run.xml, user_nl_datm, env_mach_pes.xml, etc.).

Your 1deg surface data domain is larger than the NLDAS forcing domain so you'll get some strange results at the boundaries of your domain.
 
Top