Closed chunhuazhou closed 5 months ago
Thanks @chunhuazhou for preparing the background and ensebmles. This is a great start for us to explore creating a good mpasjedi test case.
Chunhua's MPAS runs used a new physics which cannot be handled by current mpasjedi in RDASApp. So @Junjun-NOAA is working to repeat this case but with the community version MPAS model.
@guoqing-noaa 2024052700 case is good for RDAS test since there are more observations available at 00z. Let's focus on 00z case. Could you let's know what is the reason that RDAS mpasjedi cannot handle the new physics in MPAS?
@guoqing-noaa 2024052700 case is good for RDAS test since there are more observations available at 00z. Let's focus on 00z case. Could you let's know what is the reason that RDAS mpasjedi cannot handle the new physics in MPAS?
We can still use the 2024052700 case. But we have to use the community MPAS_model at the moment. MPASJEDI bump localization crashed due to inconsistent physics settings. Please refer to this issue #87 for more information.
@Junjun-NOAA Please set up the case at 2024052700z. Thanks!
FYI, We reran the 2024052700z case using the community model version (i.e. no GSL new physics) and so far the bumploc has been completed successfully. With this confirmation, @Junjun-NOAA is now working on generating 30 ensembles.
Updates on this:
We used the old namelist.atmosphere
(not the one from Chunhua's run) and we successfully ran the bumploc and a pure 3DEnVar run (see the below figure). So Chunhua's case also works!
But there is still one issue: if we want to test BJ's static BE, we would want to run 55 vertical levels. This is adapted from BJ's communication about static BE:
One thing I didn't mention is ... the interpolating the global B statistic from one mesh to another mesh works only in horizontal direction, but NOT in vertical direction. Thus we should configure the vertical coordinate the same. In all of my testing, I am using the default configuration of MPAS, that is 55 vertical levels with a 30 km model top. If needed, a procedure interpolating the B statistics between different vertical configurations should be developed further.
we will use GSL's MPAS version eventually, but at the moment, @chunhuazhou's setting has 60 vertical levels while @Junjun-NOAA 's rerun has 55 levels. It may be easier to test BE-related things with a 55-vertical level setting. @TingLei-NOAA @ShunLiu-NOAA @hu5970 Do you also favor a 55 vertical level setting? Thanks!
Close this issue as a MPAS conus12km 30 members case has been established, see issue #92 . Thank @chunhuazhou and @Junjun-NOAA for your work on this!
@hongli-wang, please follow the above instructions from @chunhuazhou and this MPAS tutorial guide:https://docs.google.com/document/d/1ytJq-pFGKEkGsgGnp2z-RgBL_0tYYtgvWCvKgtqEzso/edit.
We use the community model default settings. If you want to have a quick setup, @Junjun-NOAA or @chunhuazhou can help you generate the grid.nc ans static.nc you need.
@guoqing-noaa Thanks. I will contact Chunhua and Junjun for assistance. One more question is on use of GEFS ensemble. It seems you are running JEDI with a regional MPAS ensemble with 30 members. If I heard correctly, you mentioned JEDI/MPAS can use GEFS ensemble. Is that correct?
@chunhuazhou, I'm currently trying to run some assimilation experiments of only wind observations using this test case. I'm getting a warning like:
WARNING: Variable uReconstructZonal not in input file.
WARNING: Variable uReconstructMeridional not in input file.
And then I get zero increments. I think this is why I can't get my wind assimilation tests to work properly--I've gotten temperature assimilation to work. Is it possible to add these 3D wind variables restart.nc background file?
@chunhuazhou and @delippi I suspect the wind analysis issue is related to the issue https://github.com/NOAA-EMC/RDASApp/issues/148 @Junjun-NOAA @SamuelDegelia-NOAA . I will also refer to Donne 's info from there.
The goal is to create a CONUS domain with 12km resolution and to prepare for building the RRFSv2 test system.
The workflow follows the NSSL MPAS run, using the GSL-NSSL MPAS model that has RUC-LSM and some other changes. I copied / linked the real-time workflow from /misc/whome/role.wrfruc/HRRRv5 and made some changes to run it for the CONUS-12km domain, initialized from GFS/ GEFS at /lfs4/BMC/wrfruc/Chunhua.Zhou/JEDI-tests/HRRRv5-12km.
Under /lfs4/BMC/wrfruc/Chunhua.Zhou/JEDI-tests/HRRRv5-12km, use workflow.ens/hrrrv5.xml to run GEFS initialized ensemble forecast and workflow/hrrrv5.xml to run GFS initialized deterministic forecast.
Step 1: Download global 12km uniform meshes from https://mpas-dev.github.io/
$ wget https://www2.mmm.ucar.edu/projects/mpas/atmosphere_meshes/x1.4096002.tar.gz
$ wget https://www2.mmm.ucar.edu/projects/mpas/atmosphere_meshes/x1.4096002_static.tar.gz
Untar and get the following files:
Step 2: Create a CONUS 12km domain from the global 12km meshes - grid.nc
Using the file conus.custom.pts from MPAS-Limited-Area/docs/points-examples/ and modify it for the desired conus domain:
Use the
create_region
python script from MPAS-Limited-Area/ to get grid.nc file for the customized CONUS domain:$ create_region conus.custom.pts x1.4096002.grid.nc
Output: conus12km_mpas.grid.nc conus12km_mpas.graph.info
Step 3: Run init_atmosphere_model and get conus12km_mpas.static.nc
$ cp /lfs4/BMC/wrfruc/Chunhua.Zhou/JEDI-tests/HRRRv5-12km/exec/init_atmosphere_model . $ cp /lfs4/BMC/wrfruc/Chunhua.Zhou/JEDI-tests/skylab/mpas/MPAS-Model.master/namelist.init_atmosphere . $ cp /lfs4/BMC/wrfruc/Chunhua.Zhou/JEDI-tests/skylab/mpas/MPAS-Model.master/streams.init_atmosphere .
Modify streams.init_atmosphere:
Modify namelist.init_atmosphere:
Run init_atmosphere_model, using the following example run script (run_init.sh):
Output: conus12km_mpas.static.nc
Step 4: Use metis to partition the mesh for parallel run
Copy the source code from MPAS-DATA/metis-5.1.0.tar.gz Under /lfs4/BMC/wrfruc/Chunhua.Zhou/JEDI-tests/skylab/mpas/metis-5.1.0
$ module load gnu/13.2.0 intel/2023.2.0 $ make config $ make
Example command to partition the mesh for using 120 cores: $ gpmetis -minconn -contig -niter=200 conus12km_mpas.graph.info 120
Output: conus12km_mpas.graph.info.part.120
Step 5: Run a deterministic MPAS forecast, using workflow/hrrrv5.xml , with GFS GRIB2 data as IC/LBC
Main namelist entries for running the 12-km CONUS test:
Suggested number of cores: 120 cores as tested on Jet.
Step 6: Run 30-member ensemble forecast, using workflow.ens/hrrrv5.xml, with GEFS GRIB2 data as IC/LBC
The 1-hour forecast files (deterministic and 30-member ensemble, initialized at 12Z 05/20/2024, valid at 13Z), along with the RAP PrepBUFR observations:
Another test case, initialized at 18Z 05/26/2024, valid at 00Z 05/27/2024, is also available: