Currently, in rrfs-workflow, MPAS-Model generates two set of output files:
history.nc (with accompanying diag.nc) for post-processing through MPASSIT, UPP
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:
-
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.
-
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.
Currently, in rrfs-workflow, MPAS-Model generates two set of output files:
history.nc(with accompanyingdiag.nc) for post-processing throughMPASSIT,UPPmpasout.nc(with accompanyinginvariant.nc) for data assimilation and reinitialization of next cycle MPAS-Model forecastsFor 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:
combine
history.ncandmpasout.ncinto one file (similar to thewrfoutfile in the WRF era)A preliminary comparison of fields in both files will be provided in the following post.
only output
mpasout.ncat forecast hour 1 (or and hour 2) and outputhistory.ncfor all forecast hoursIt looks like at this moment we cannot achieve this. No such an option is available in the steam
output_intervalsetting.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_out2inframework/xml_stream_parser.cor the following part incore_atmosphere/physics/mpas_atmphys_manager.FA few other thoughts:
history.nccontains lots of static fields, if we can only output variant fields intohistory.ncand read static fields frominvariant.ncorstatic.nc, it may save us a decent amount of disk spaces.not sure whether
history.ncfiles are enough for JEDI to computehofx(i.e. the model counter parts at the observation locations). If not, we may still need to generate long forecastmpasout.ncfilesTag @clark-evans @hu5970 @SamuelTrahanNOAA for awareness.