You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Example, user_nl_datm_streams for TRENDY.2020 simulation for NUOPC coupler #1701
The previous years TRENDY simulations were done using the MCT coupler and hence the user_datm.streams.txt.* files that were used no longer function for the NUOPC coupler. As such we need to develop new user_nl_datm_streams example files that can be used for this type of purpose.
! CO2 time series for TRENDY 1700 to 2020
co2tseries.20tr:year_first = 1700
co2tseries.20tr:year_align = 1700
co2tseries.20tr:year_last = 2020
co2tseries.20tr:datafiles = $DIN_LOC_ROOT_CLMFORC/fco2_datm_global_simyr_1750-2014_CMIP6_c180929.nc
One issue with the above is that previously for TRENDY we used a domain file that had a land-mask. The mesh standard mesh file being used here is 1 everywhere.
The other issue I have with actually running the above case is that there are some NetCDF4 files somewhere in the list that the model can't read.
thanks for starting this issue, @ekluzek . I wonder if we want to make these CRU-JRA55 data available as a compset for more regular model testing? It seems like the only reanalysis that's being updated.
Yes, let's talk more Thursday. When they update do they add the latest year to the end of the series, or do they redo the entire sequence? The first would be more sustainable for us. The second might mean we don't update every year, but maybe less often.
On Mon, Apr 11, 2022 at 8:51 AM Erik Kluzek ***@***.***> wrote:
Yes, let's talk more Thursday. When they update do they add the latest
year to the end of the series, or do they redo the entire sequence? The
first would be more sustainable for us. The second might mean we don't
update every year, but maybe less often.
—
Reply to this email directly, view it on GitHub
<#1701 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFABYVAQDVLVWY43MK3OMW3VEQ4ANANCNFSM5S7YPMUA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
@ekluzek I tried to run using the user_datm_streams from above, and the converted files, but am getting the following error in the cesm log file.
26: ERROR:
26: (datm_init_pointers): ERROR: wind and tbot must be in streams for CLMNCEP
WIND and TBOT which point to wind and tbot are on the files that Keith converted, so I'm not sure where the error is coming from. My case is here, which is running from the most modern ctsm.
@olyson is correct. Actually, I setup the names according to the previous example MCT for 2020. And there some of the names of the variables on the files were different as well as the stream variable names. The variable names and stream names are pairs in the "<datavars>" element. The names on the files are on the left, and the names within CDEPS:datm are on the right. From looking at both the default names and the names on the files, the default values for datavars looks correct. So actually what you should do is remove all of the settings for datavars in the user_nl_datm_streams file. It looks like that should work (at least get you to the next problem).
OK. Tried removing the datavars from user_nl_datm_streams and am now getting more standard errors on the first timestep.
g, newsum_lwrad_g, sum_wts_g, forc_lwrad_g: 4
3.970527130136304E+112 0.990000000000000 4.010633464784145E+112
iam = 0: local gridcell index = 4
iam = 0: global gridcell index = 5470
iam = 0: gridcell longitude = 214.7500000
iam = 0: gridcell latitude = -86.2500000
ENDRUN:
ERROR:
ERROR: Energy conservation error downscaling longwaveERROR in atm2lndMod.F90 a
t line 561
Note that I also tried running at the more standard f09 resolution, because I know that we have had problems with the 0.5degree resolution before (though using out of box CRUNCEP forcing, it ran fine at this resolution). With the f09 resolution, I got a column-level water balance error instead. Maybe the mesh file being 1 everywhere is a problem, especially if the actual realistic data coverage in the CRUJRA forcing is not complete, which I think it is not.
I tried with this new mesh file, but am running into a different problem, not sure if this is related to NUOPC or not. I am setting DIN_LOC_ROOT_CLMFORC in env_run.xml to the location of some TRENDY data that @olyson has stored for me.
But, the datm.streams.xml file doesn't seem to be picking this up. The user_nl_datm_streams file has lines like this:
But the resulting datm.streams.xml file has lines like this (pointing to the wrong location, and probably the out of the box location):
/glade/p/cesmdata/cseg/inputdata_CLMFORC/three_stream_files/clmforc.TRENDY.c2020.0.5x0.5.Solr.1901.nc
Case directory is here: /glade/u/home/dlawren/cases/clm5sp_hd_crujra2020_createICs
I checked and it looks like adding the line
CLMCRUNCEPv7.Solar:meshfile = $DIN_LOC_ROOT/share/meshes/clmforc.crujra200728.cdf5.c2016.0.5d.ESMFmesh_c20220504.nc
into user_nl_datm_streams changes the outcome of the datm.streams.xml file. If that line is in user_nl_datm_streams, then the value of $DIN_LOC_ROOT_CLMFORC in env_run.xml is ignored and the default is used instead.
@dlawrenncar your last result is really odd to me. But, it makes me wonder if you copy the mesh file pointed to inside of $DIN_LOC_ROOT_CLMFORC/three_stream_files/ if that would work? I actually intended to do that, but didn't have permission. @olyson could you open up /glade/p/cgd/tss/people/oleson/TRENDY2020_Forcing to group write so that we could add files there?
Moving the mesh file into the $DIN_LOC_ROOT_CLMFORC location worked. I ran for a few months and the results look reasonable. @ekluzek I'm not sure what the next step is to close this issue out. This is not a standard out-of-the-box forcing dataset, so maybe the fact that it works is sufficient. Perhaps a topic to discuss at next software meeting.
Thanks. One other thing that we should decide about going forward, as we make decisions about CRU-JRA and how we want to manage annual updates to it via TRENDY, is whether or not we should start using the downwelling longwave radiation. Several years ago, with one of the first CRU-NCEP (predecessor to CRU-JRA), we decided not to use downwelling longwave from the forcing dataset and instead to calculate it from forcing level T and Q. We did this because the downwelling longwave looked really odd in those original data, including a negative global historical trend that is inconsistent with climate change. We should probably revisit this issue if/when we transition to using CRU-JRA as our default forcing dataset.
I wondered if we should also have a discussion on input datm data we'll support moving forward for CTSM development? Could be a topic for the Thursday SE and Science meetings?
Activity
ekluzek commentedon Apr 9, 2022
I have a sample that creates the namelist and streams files.
It relies on the following setting of DIN_LOC_ROOT_CLMFORC
./xmlchange --force DIN_LOC_ROOT_CLMFORC="/glade/p/cgd/tss/people/dll/TRENDY2020_Forcing"user_nl_datm_streams.txt
An example from the file for CO2 is like this:
ekluzek commentedon Apr 9, 2022
One issue with the above is that previously for TRENDY we used a domain file that had a land-mask. The mesh standard mesh file being used here is 1 everywhere.
The other issue I have with actually running the above case is that there are some NetCDF4 files somewhere in the list that the model can't read.
ekluzek commentedon Apr 9, 2022
The CO2 file is fine, but it looks like the forcing files are in NetCDF-4 format and will need to be converted.
wwieder commentedon Apr 11, 2022
thanks for starting this issue, @ekluzek . I wonder if we want to make these CRU-JRA55 data available as a compset for more regular model testing? It seems like the only reanalysis that's being updated.
ekluzek commentedon Apr 11, 2022
Yes, let's talk more Thursday. When they update do they add the latest year to the end of the series, or do they redo the entire sequence? The first would be more sustainable for us. The second might mean we don't update every year, but maybe less often.
dlawrenncar commentedon Apr 11, 2022
dlawrenncar commentedon Apr 12, 2022
@olyson converted some files for testing. There are ten years here (1901-1910):
/glade/p/cgd/tss/people/oleson/TRENDY2020_Forcing/three_stream_files
These were converted from: /glade/p/cgd/tss/people/dll/TRENDY2020_Forcing/three_stream_files/
dlawrenncar commentedon Apr 12, 2022
@ekluzek I tried to run using the user_datm_streams from above, and the converted files, but am getting the following error in the cesm log file.
26: ERROR:
26: (datm_init_pointers): ERROR: wind and tbot must be in streams for CLMNCEP
WIND and TBOT which point to wind and tbot are on the files that Keith converted, so I'm not sure where the error is coming from. My case is here, which is running from the most modern ctsm.
/glade/u/home/dlawren/cases/clm5sp_hd_crujra2020_createICs
olyson commentedon Apr 12, 2022
@ekluzek can confirm but I think the stream variable names have changed:
swdndr -> Faxa_swdndr
swdndf -> Faxa_swdndf
precn -> Faxa_precn
tbot -> Sa_tbot
wind -> Sa_wind
shum -> Sa_shum
pbot -> Sa_pbot
ekluzek commentedon Apr 12, 2022
@olyson is correct. Actually, I setup the names according to the previous example MCT for 2020. And there some of the names of the variables on the files were different as well as the stream variable names. The variable names and stream names are pairs in the "<datavars>" element. The names on the files are on the left, and the names within CDEPS:datm are on the right. From looking at both the default names and the names on the files, the default values for datavars looks correct. So actually what you should do is remove all of the settings for datavars in the user_nl_datm_streams file. It looks like that should work (at least get you to the next problem).
dlawrenncar commentedon Apr 12, 2022
OK. Tried removing the datavars from user_nl_datm_streams and am now getting more standard errors on the first timestep.
g, newsum_lwrad_g, sum_wts_g, forc_lwrad_g: 4
3.970527130136304E+112 0.990000000000000 4.010633464784145E+112
iam = 0: local gridcell index = 4
iam = 0: global gridcell index = 5470
iam = 0: gridcell longitude = 214.7500000
iam = 0: gridcell latitude = -86.2500000
ENDRUN:
ERROR:
ERROR: Energy conservation error downscaling longwaveERROR in atm2lndMod.F90 a
t line 561
Note that I also tried running at the more standard f09 resolution, because I know that we have had problems with the 0.5degree resolution before (though using out of box CRUNCEP forcing, it ran fine at this resolution). With the f09 resolution, I got a column-level water balance error instead. Maybe the mesh file being 1 everywhere is a problem, especially if the actual realistic data coverage in the CRUJRA forcing is not complete, which I think it is not.
10 remaining items
dlawrenncar commentedon May 6, 2022
I tried with this new mesh file, but am running into a different problem, not sure if this is related to NUOPC or not. I am setting DIN_LOC_ROOT_CLMFORC in env_run.xml to the location of some TRENDY data that @olyson has stored for me.
But, the datm.streams.xml file doesn't seem to be picking this up. The user_nl_datm_streams file has lines like this:
CLMCRUNCEPv7.Solar:datafiles = $DIN_LOC_ROOT_CLMFORC/three_stream_files/clmforc.TRENDY.c2020.0.5x0.5.Solr.1901.nc, \
But the resulting datm.streams.xml file has lines like this (pointing to the wrong location, and probably the out of the box location):
/glade/p/cesmdata/cseg/inputdata_CLMFORC/three_stream_files/clmforc.TRENDY.c2020.0.5x0.5.Solr.1901.nc
Case directory is here: /glade/u/home/dlawren/cases/clm5sp_hd_crujra2020_createICs
dlawrenncar commentedon May 6, 2022
I checked and it looks like adding the line
CLMCRUNCEPv7.Solar:meshfile = $DIN_LOC_ROOT/share/meshes/clmforc.crujra200728.cdf5.c2016.0.5d.ESMFmesh_c20220504.nc
into user_nl_datm_streams changes the outcome of the datm.streams.xml file. If that line is in user_nl_datm_streams, then the value of $DIN_LOC_ROOT_CLMFORC in env_run.xml is ignored and the default is used instead.
ekluzek commentedon May 6, 2022
@dlawrenncar your last result is really odd to me. But, it makes me wonder if you copy the mesh file pointed to inside of $DIN_LOC_ROOT_CLMFORC/three_stream_files/ if that would work? I actually intended to do that, but didn't have permission. @olyson could you open up /glade/p/cgd/tss/people/oleson/TRENDY2020_Forcing to group write so that we could add files there?
olyson commentedon May 6, 2022
Ok, done.
dlawrenncar commentedon May 17, 2022
Moving the mesh file into the $DIN_LOC_ROOT_CLMFORC location worked. I ran for a few months and the results look reasonable. @ekluzek I'm not sure what the next step is to close this issue out. This is not a standard out-of-the-box forcing dataset, so maybe the fact that it works is sufficient. Perhaps a topic to discuss at next software meeting.
dlawrenncar commentedon May 17, 2022
To be clear, adding this (and equivalents for Precip and TPQW) to user_datm_streams worked:
CLMCRUNCEPv7.Solar:meshfile = $DIN_LOC_ROOT_CLMFORC/three_stream_files/clmforc.crujra200728.cdf5.c2016.0.5d.ESMFmesh_c20220504.nc
dlawrenncar commentedon May 17, 2022
@olyson Could you convert (not sure what needed to be converted anymore, can't remember) the rest of the 2020 CRU-JRA forcing dataset?
olyson commentedon May 17, 2022
I've converted all of the available years (1901-2019):
/glade/p/cgd/tss/people/oleson/TRENDY2020_Forcing/three_stream_files
These were converted from: /glade/p/cgd/tss/people/dll/TRENDY2020_Forcing/three_stream_files/
dlawrenncar commentedon May 17, 2022
Thanks. One other thing that we should decide about going forward, as we make decisions about CRU-JRA and how we want to manage annual updates to it via TRENDY, is whether or not we should start using the downwelling longwave radiation. Several years ago, with one of the first CRU-NCEP (predecessor to CRU-JRA), we decided not to use downwelling longwave from the forcing dataset and instead to calculate it from forcing level T and Q. We did this because the downwelling longwave looked really odd in those original data, including a negative global historical trend that is inconsistent with climate change. We should probably revisit this issue if/when we transition to using CRU-JRA as our default forcing dataset.
wwieder commentedon May 17, 2022
I wondered if we should also have a discussion on input datm data we'll support moving forward for CTSM development? Could be a topic for the Thursday SE and Science meetings?
ekluzek commentedon Jun 30, 2022
OK, there is an issue to resolve about supporting CRUJRA, but the core of this issue having an example for TRENDY is now done.