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

Running WACCM for 'present day' case

Are there any restrictions or other impediments that prevent me from running WACCM (F_2000_WACCM) for a run that begins in August, 2014? I had been running CESM-DART on an earlier 2008 case. Now I would like to run it for the 2014 case, making sure that I properly specify the needed input files. Thanks.George Modica
 

mmills

CSEG and Liaisons
Staff member
Are you interested in doing a "time-slice" run, where you repeat the year 2014? Or do you want a transient run, where emissions change year-to-year, starting in 2014 and continuing into the future according to an RCP scenario?If you want to do a time-slice, F_2000_WACCM is a good place to start. You can modify the namelist to cycle emissions over the year 2014 instead of the default year 2000.If, however, you want to do a transient run, you might want to start from one of our transient WACCM compsets.For data ocean (F-compsets), the only transient we have is F_1955-2005_WACCM_CN. This could be modified to use emissions from one of our RCP scenarios starting in the year 2014. We have a number of other transient WACCM compsets with full ocean (B-compsets). Those that cover the years 2005-2100 with full chemistry are:
  • B_RCP2.6_WACCM_CN
  • B_RCP4.5_WACCM_CN
  • B_RCP8.5_WACCM_CN
We also have equivalent specified chemistry compsets:
  • B_RCP2.6_WACCM_SC_CN
  • B_RCP4.5_WACCM_SC_CN
  • B_RCP8.5_WACCM_SC_CN
 
Hello Mike,We are interested in running WACCM for a relatively short (i.e., 1-month) period of time in support of field operations involving high-altitude measurements. From your reply it sounds like either scenario (time-slice or transient) would be acceptable, but I'm sure you have a better informed opinion about that than do I.For the time-slice option, would any other namelist changes be necessary other than the one to modify the namelist to cycle emissions over 2014? For example, I have several lines in my usr_nl_cam with file names like ar5_mam3_so2_elev_1850-2010_c20100902_v12.nc.Thanks.George
 

mmills

CSEG and Liaisons
Staff member
Before proceeding, I should ask you which WACCM output fields you are interested in, and at what altitudes. Depending on your needs, I can see recommending one of at least 3 approaches:
  1. We may be able to provide you with WACCM output from one of our previous runs, particularly if you are interested in climatological values.
  2. Running an F_2000_WACCM case might be appropriate, if you are not concerned about the specific meteorology of the time period for your field operations.
  3. For field operations, we generally would nudge WACCM winds and temperatures with meteorological fields based on observations. We call this “specified dynamics”, or SD-WACCM We do provide an SD-WACCM compset, F_SD_WACCM. While we do have winds and temperatures from GEOS5 through November 6, 2014 (yesterday), we do not have sea surface temperatures or solar inputs for 2014, which we would normally use to drive the model. I could help you to modify an F_2000_WACCM case to use specified dynamics with climatological sea surface temperatures and solar inputs, if the particular winds and temperatures from the time period of your field operations is important.
 
Mike,We are interested in the wind, temperature, and density fields at heights of up to 80 km.It sounds like your approach #3 is closest to what we would like to do. Our goal is to use all met obs (and COSMIC) plus a special profiling lidar to generate a best estimate of the atmosphere at a given place and time. We are not as interested in a forecast as much as using all available data to produce the best retrospective diagnosis.We have already configured F_2000_WACCM to run with DART; please let me know how you would prefer to proceed. Thank you very much for your help.George
 

raeder

Member
Hi George,

Mike asked me to jump into your conversation, since it has turned towards DART.
If I'm following the discussion correctly, I believe that you'll want to find
a way to use the actual SSTs from 2014.  If you don't, there will be a constant
inconsistency between the forcing from the SSTs and the observations at the lower
levels of WACCM.  My limited understanding is that the upper regions of WACCM
are strongly forced by the troposphere, so you'll want to minimize the noise
that comes from down there.

Unfortunately, I don't see SSTs for 2014 in the standard SST data ocean files:
/glade/p/cesmdata/cseg/inputdata/atm/cam/sst/sst_HadOIBl_bc_1x1_*.nc
The mechanism that's used to generate those files yields unreliable
results in the last 2-3 months, so in theory August 2014 would be at the boundary
right now, but should give better results than using a climatological SST.
In the past, the new year isn't added to the time series until at least several
months into the next year, but it may be possible to convince the creators to
make an intermediate file.  But you probably wouldn't want to go beyond August
at this point.

I've checked with the people I know who might have generated ocean analyses
for 2014 using DART, but none of them have.

I'm a little skeptical about using the specified dynamics WACCM in your context.
It sounds like you're trying to use DART and all available observations to figure
out the dynamics, so you wouldn't want to constrain the dynamics by some external
model run or analyses.

Let me know if I missed the point(s).

Kevin
~                                                
 
Hello Kevin,One of my (perhaps naive) notions regarding WACCM-DART is that the initial condition file is provided by GEOS5, which, presumably, was generated with the latest observed SSTs. Wouldn't that mitigate somewhat the inconsistency if I had to settle for climo SSTs? Is it even possible to acquire the August 2014 GEOS5 initial condition file for WACCM-DART? Since my interest is mostly in the upper stratosphere/lower mesosphere, I wonder if by incorporating high-altitude observations like COSMIC and SABER I can minimize the potential impact of the less-than-optimal SST.I share your concern about SD-WACCM. In addition to that I have invested a significant amount of 'sweat-equity' in WACCM-DART, so I would very much prefer to apply it to the August case.Thanks again for your help--George
 

raeder

Member
The influence of the initial condition file, which is used to start the whole
assimilation, would persist only through the atmospheric state, because during the
forecasts the SSTs would come completely from the data ocean input file to CESM.
The IC file influence would diminish with time, as the assimilation blends the
observations with the influences of the data ocean and the ICs.

When we start an assimilation we typically see a "large" RMSE of the ensemble,
relative to the observations.  As more observations are assimilated,
the RMSE will fall to some fairly stable value, at which point it has forgotten
about the ICs, and the ensemble error is in balance with the observational error.
If we've started from a very naive ensemble, the initial RMSE will be very large.
If we've started from something close to the observations (like, presumably, GOES5)
then the RMSE won't be as large, but it will still be larger than the steady values
later in the assimilation.  It's generally safe to assume that an analysis like
GOES5 has its own biases, which are different from CESM's and it will take a few
assilation cycles for the assimilation to resolve those differences.

I don't have any experience with GOES5, so I don't know what dates are available.

Lots of observations at high altitude will definitely help overcome sub-optimal SSTs,
but there will be a persistent struggle between them.  You could use your 2008 case
to test how big of an effect this is by running 2 assimilations with the 2 kinds
of SSTs you're considering, keeping everything else the same; time period, ICs,
observation set, ....  Meanwhile, I've contacted a collaborator who has used WRF+DART
in field campaigns to find out how he handled SSTs, or whether it was even an issue,
maybe because his entire domain was over land.  I'll let you know what he says.

Kevin
 
Kevin,Forgetting for the moment the issue of the SSTs, if I have atmospheric observations for Aug 2014 (say, prepBUFR and COSMIC), is it possible to run WACCM-DART using the F_2000_WACCM compset?Thanks,George
 

raeder

Member
The surest way to know is to build a single, non-DART, WACCM
and try to run it for a day in August 2014.  If you need to have some
idea ahead of time, you can look in the {atm,ice,lnd}_in_0001
in your run directory.  It will have a bunch of files with years in the
names.  If those time spans don't include 2014, and the directories
where they live don't have files that cover 2014, then it's likely that
WACCM won't run for Aug 2014.

Kevin
cleardot.gif
 
Top