Replicating the behavior of the prior timeseries diagnostics

From Geos-chem
Jump to: navigation, search

Previous | Next | Guide to GEOS-Chem History diagnostics

  1. Overview of History diagnostics
  2. Legend for History diagnostics
  3. Collections for History diagnostics
  4. History collections for advection and mixing
  5. History collections for aerosols
  6. History collections for budgets
  7. History collections for chemistry and photolysis
  8. History collections for convection and wet deposition
  9. History collections for dry deposition
  10. History collections for mercury and POPs
  11. History collections for met fields and related quantities
  12. History collections for methane
  13. History collections for species concentrations
  14. History collections for TransportTracers
  15. Replicating the behavior of the prior timeseries diagnostics
  16. Adding new History diagnostics


On this page we discuss our plans to replicate specialty diagnostic outputs (timeseries, local-time diagnostics, etc.) in with the GEOS-Chem History diagnostics..

ND40 planeflight diagnostic

At present, there are no plans to remove the planeflight diagnostic in GEOS-Chem classic. You may continue to use it.

The ObsPack diagnostic can also archive point data at selected station sites. The coordinates (lat, lon, altitude, species) must be contained in in NOAA ObsPack-format netCDF files.

--Bob Yantosca (talk) 14:18, 22 July 2019 (UTC)

ND48 station diagnostics

The GEOS-Chem History diagnostics are unable to replicate the point station data output of the prior ND48 station timeseries. If you need to archive this type of data, we would recommend that you consider using the ObsPack diagnostic, which can save GEOS-Chem output at point locations.

--Bob Yantosca (talk) 20:46, 19 July 2019 (UTC)

ND49 instantaneous timeseries diagnostic

You can replicate the ND49 bpch diagnostic (instantaneous timeseries) as follows:

  1. Define a diagnostic collection in HISTORY.rc:
    • Specify instantaneous output:
      • Set mode: instantaneous
    • Specify the desired output frequency:
      • Set frequency: 00000000 010000 for hourly output
      • Set frequency: 00000000 030000 for 3-hourly output
      • Set frequency: 00000000 120000 for 12-hourly output, etc.
        • You can also use the full date/time descriptor (00000000 010000, etc.)
    • Specify that a new netCDF file should be created every 24 hours = 1 day:
      • Set duration: 00000001 000000
        • You can also use the full date/time descriptor (00000001 000000)
  2. Within this diagnostic collection, you can add archive any available quantity from the State_Met, State_Chm, or State_Diag objects.

Example:

#===================================================================
# Add an instantaneous timeseries collection to the master list
#===================================================================
COLLECTIONS: 'inst3hr',
::
#====================================================================
# Define the properties of the instantaneous timeseries collection 
#====================================================================
  inst3hr.template:      '%y4%m2%d2_%h2%n2z.nc4',
  inst3hr.format:        'CFIO'
  inst3hr.frequency:      00000000 030000,
  inst3hr.duration:       00000001 000000,
  inst3hr.mode:          'instantaneous',
  inst3hr.fields:        'SpeciesConc_?ADV?', 'GIGCchem',
                         'Met_T',             'GIGCchem',
                         'DryDepVel_?DRY?',   'GIGCchem',
::

--Bob Yantosca (talk) 14:20, 22 July 2019 (UTC)

ND50 24-hr average timeseries diagnostic

You can replicate the ND50 bpch diagnostic (24-hr average timeseries) as follows:

  1. Define a diagnostic collection in HISTORY.rc:
    • Specify time-averaged output:
      • Set mode: time-averaged
    • Specify daily output frequency. This will also set the averaging interval to be daily.
      • Set frequency: 00000001 000000
    • Specify that a new netCDF file should be created every 24 hours:
      • Set duration: 00000001 000000
  2. Within this diagnostic collection, you can add archive any available quantity from the State_Met, State_Chm, or State_Diag objects.

Example:

#===================================================================
# Add an 24-hr average timeseries collection to the master list
#===================================================================
COLLECTIONS: avg24hr',
::
#===================================================================
# Define the properties of the 24-hr average timeseries collection
#===================================================================
  avg24hr.template:      '%y4%m2%d2_%h2%n2z.nc4',
  avg24hr.format:        'CFIO'
  avg24hr.frequency:     00000001 000000
  avg24hr.duration:      00000001 000000
  avg24hr.mode:          'time-averaged',
  avg24hr.fields:        'SpeciesConc_?ADV?', 'GIGCchem',
                         'Met_T',             'GIGCchem',
                         'DryDepVel_?DRY?',   'GIGCchem',
::

--Bob Yantosca (talk) 21:58, 7 June 2018 (UTC)

ND51 satellite diagnostic

Aaron van Donkelaar wrote:

I wanted to double check about how the satellite-overpass diagnostic (ND51) was being included. There was some mention of it within the (netCDF diagnostic) presentation, but I wasn’t clear to me how the time-averaged netcdf collection could be made to output something similar to the current ND51.

My main concern was that ND51 samples between two defined local times once each day. From what I understood of the time-averaged collection via netcdf, it could be set to regularly sample between a defined interval of time (e.g. every six hours), but I didn’t understand how this could be set to sample between, say, 10am-12pm local time each day. Neither local time, nor once per day seemed an option.

Apologies if I’ve just misunderstood, but I thought I should check that an ND51-type output would still be possible.

Bob Yantosca replied:

At this time we don't yet have a good substitute for the ND51 satellite timeseries diagnostics. We may be able to replicate this with some type of satellite simulator package, but that remains to be seen as of yet. Right now we are focusing our efforts on implementing the netCDF diagnostics that are required for benchmarking. (Specialty diagnostics will be added later.)

We have designed the netCDF diagnostics for GC-Classic to replicate the behavior of the diagnostics in GCHP. Having the diagnostics work the same way in both configurations of GC facilitates benchmarking and comparing GC-Classic to GCHP. It also makes it easier for users to switch between GC-Classic to GCHP. But GCHP does not allow for local-time diagnostics. GCHP relies on the MAPL library, and its diagnostic package (aka "History") only allows for instantaneous or time-averaged output.

One could save e.g hourly timeseries, along with a local time field, to netCDF, and apply the local time comparison in post-processing. This would be doable but it would also end up generating a ton of output.

The good news is that we will preserve the bpch diagnostics in v11-02 (I need to update the wiki better to reflect that). We will not remove the bpch diagnostics until we have found a suitable replacement for the local-time diagnostics. So for the time being you can still rely on ND51.

--Bob Yantosca (talk) 15:33, 15 November 2017 (UTC)



Previous | Next | Guide to GEOS-Chem History diagnostics