Skip to content

combine history.nc and mpasout.nc or only output mpasout.nc at forecast hour 1 (or and hour 2) #191

@guoqing-noaa

Description

@guoqing-noaa

Currently, in rrfs-workflow, MPAS-Model generates two set of output files:

  1. history.nc (with accompanying diag.nc) for post-processing through MPASSIT, UPP
  2. mpasout.nc (with accompanying invariant.nc) for data assimilation and reinitialization of next cycle MPAS-Model forecasts

For high resolution, and/or large domain, and/or long forecasts, this will take lots of unnecessary duplicate disk spaces.

There may be two routes to address this issue:

  1. combine history.nc and mpasout.nc into one file (similar to the wrfout file in the WRF era)
    A preliminary comparison of fields in both files will be provided in the following post.

  2. only output mpasout.nc at forecast hour 1 (or and hour 2) and output history.nc for all forecast hours
    It looks like at this moment we cannot achieve this. No such an option is available in the steam output_interval setting.
    Modifications to MPAS-Model source codes may be needed
    I was trying to find where we should make such a change. But I did not have a clear clue yet. I only found something so far like filename_interval = interval_out2 in framework/xml_stream_parser.c or the following part in core_atmosphere/physics/mpas_atmphys_manager.F

 if(trim(stream_interval) /= 'none') then
    call mpas_set_timeInterval(alarmTimeStep,timeString=stream_interval,ierr=ierr)

A few other thoughts:

  • history.nc contains lots of static fields, if we can only output variant fields into history.nc and read static fields from invariant.nc or static.nc, it may save us a decent amount of disk spaces.

  • not sure whether history.nc files are enough for JEDI to compute hofx (i.e. the model counter parts at the observation locations). If not, we may still need to generate long forecast mpasout.nc files

Tag @clark-evans @hu5970 @SamuelTrahanNOAA for awareness.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions