I would like to run regional MPAS in a cycling mode and be able to assimilate either sounding data or surface data. Currently, I am running a Regional MPAS 12-hour forecast. As such, I generate lateral boundary conditions for each forecast time (every 3 hours) and then the history files. Also, it is outputting one "restart*.nc" file, just for the final forecast hour. I am trying to get the big picture so some very broad questions if I may: 1) what does the restart*.nc file contain? 2) For running MPAS in a 'cycling' mode, I assume I start the forecast cycling back up via the 'restart*.nc' file? 3) and also the matter of updating the LBC's via updated GFS fields...(and eventually assimilating local sounding data/surface data).
I am starting to look at DART for the actual data assimilation portion, but wanted to make sure I can understand how to run Regional MPAS in a cycling mode first.
One note - I saw that some EPA personnel created MPAS add-on code to do data assimilation via obs nudging (2018). This would have been ideal, but this code does not appear to have made it into the current MPAS release. Thus, I was looking toward DART for the data assimilation.
Thanks for any info.
I am starting to look at DART for the actual data assimilation portion, but wanted to make sure I can understand how to run Regional MPAS in a cycling mode first.
One note - I saw that some EPA personnel created MPAS add-on code to do data assimilation via obs nudging (2018). This would have been ideal, but this code does not appear to have made it into the current MPAS release. Thus, I was looking toward DART for the data assimilation.
Thanks for any info.