.. DO NOT EDIT. .. THIS FILE WAS AUTOMATICALLY GENERATED BY SPHINX-GALLERY. .. TO MAKE CHANGES, EDIT THE SOURCE PYTHON FILE: .. "generated/met_tool_wrapper/GenEnsProd/GenEnsProd.py" .. LINE NUMBERS ARE GIVEN BELOW. .. only:: html .. note:: :class: sphx-glr-download-link-note :ref:`Go to the end ` to download the full example code. .. rst-class:: sphx-glr-example-title .. _sphx_glr_generated_met_tool_wrapper_GenEnsProd_GenEnsProd.py: GenEnsProd: Basic Use Case ========================== met_tool_wrapper/GenEnsProd/GenEnsProd.conf .. GENERATED FROM PYTHON SOURCE LINES 9-27 Scientific Objective -------------------- Generate ensemble products. This use case demonstrates how to configure the gen_ens_prod tool if you expect that there will occasionally be missing ensembles. 7 ensemble paths are specified but only 6 of them exist in the sample input data set. The wrapper will mark ensembles that are not found with the MISSING keyword in the file-list file that is read by the tool. Also, one of the ensembles is listed as the control member. The gen_ens_prod application will error and exit if the control member is included in the ensemble list, but the GenEnsProd wrapper will automatically remove the control member from the ensemble list. This makes it easier to configure the tool to change the control member without having to change the ensemble list. The number of expected members (defined with GEN_ENS_PROD_N_MEMBERS) is 6 (7 members - 1 control member). The actual number of ensemble members that will be found in this example is 5 (arw-tom-gep4 is not included). The ens.ens_thresh value (defined by GEN_ENS_PROD_ENS_THRESH) is set to 0.8. There are ~0.833 (5/6) valid ensemble members so the application will run. .. GENERATED FROM PYTHON SOURCE LINES 29-41 Datasets -------- **Input:** WRF ARW ensemble 24 hour precipitation accumulation **Location:** All of the input data required for this use case can be found in the met_test sample data tarball. Click here to the METplus releases page and download sample data for the appropriate release: https://github.com/dtcenter/METplus/releases This tarball should be unpacked into the directory that you will set the value of INPUT_BASE. See the `Running METplus`_ section for more information. .. GENERATED FROM PYTHON SOURCE LINES 43-48 METplus Components ------------------ This use case utilizes the METplus GenEnsProd wrapper to generate a command to run the MET tool gen_ens_prod if all required files are found. .. GENERATED FROM PYTHON SOURCE LINES 50-60 METplus Workflow ---------------- GenEnsProd is the only tool called in this example. It processes the following run time(s): | **Initialization:** 2009-12-31 12Z | **Forecast Lead:** 24 hour | .. GENERATED FROM PYTHON SOURCE LINES 62-69 METplus Configuration --------------------- parm/use_cases/met_tool_wrapper/GenEnsProd/GenEnsProd.conf .. highlight:: bash .. literalinclude:: ../../../../parm/use_cases/met_tool_wrapper/GenEnsProd/GenEnsProd.conf .. GENERATED FROM PYTHON SOURCE LINES 71-83 MET Configuration --------------------- .. note:: See the :ref:`GenEnsProd MET Configuration` section of the User's Guide for more information on the environment variables used in the file below. parm/met_config/GenEnsProdConfig_wrapped .. highlight:: bash .. literalinclude:: ../../../../parm/met_config/GenEnsProdConfig_wrapped .. GENERATED FROM PYTHON SOURCE LINES 85-95 Running METplus --------------- Provide the use case .conf configuration file to the run_metplus.py script. /path/to/METplus/parm/use_cases/met_tool_wrapper/GenEnsProd/GenEnsProd.conf See the :ref:`running-metplus` section of the System Configuration chapter for more details. .. GENERATED FROM PYTHON SOURCE LINES 97-127 Expected Output --------------- A successful run will output the following to the screen and the logfile:: INFO: METplus has successfully finished running. Refer to the value set for **OUTPUT_BASE** to find where the output data was generated. Output for this use case will be found in met_tool_wrapper/gen_ens_prod (relative to **OUTPUT_BASE**) and will contain the following file(s): * gen_ens_prod_20100101_120000V_ens.nc A file-list file will also be generated in stage/file_lists called: * 20091231120000_24_gen_ens_prod.txt It should contain a list of 6 files in {INPUT_BASE} with 1 file marked as missing because it was not found:: file_list {INPUT_BASE}/met_test/data/sample_fcst/2009123112/arw-sch-gep2/d01_2009123112_02400.grib {INPUT_BASE}/met_test/data/sample_fcst/2009123112/arw-tom-gep3/d01_2009123112_02400.grib MISSING/{INPUT_BASE}/met_test/data/sample_fcst/2009123112/arw-tom-gep4/d01_2009123112_02400.grib {INPUT_BASE}/met_test/data/sample_fcst/2009123112/arw-fer-gep5/d01_2009123112_02400.grib {INPUT_BASE}/met_test/data/sample_fcst/2009123112/arw-sch-gep6/d01_2009123112_02400.grib {INPUT_BASE}/met_test/data/sample_fcst/2009123112/arw-tom-gep7/d01_2009123112_02400.grib .. GENERATED FROM PYTHON SOURCE LINES 129-142 Keywords -------- .. note:: * GenEnsProdToolUseCase * GRIBFileUseCase * EnsembleAppUseCase Navigate to :ref:`quick-search` to discover other similar use cases. .. GENERATED FROM PYTHON SOURCE LINES 142-144 .. code-block:: Python # .. _sphx_glr_download_generated_met_tool_wrapper_GenEnsProd_GenEnsProd.py: .. only:: html .. container:: sphx-glr-footer sphx-glr-footer-example .. container:: sphx-glr-download sphx-glr-download-jupyter :download:`Download Jupyter notebook: GenEnsProd.ipynb ` .. container:: sphx-glr-download sphx-glr-download-python :download:`Download Python source code: GenEnsProd.py ` .. container:: sphx-glr-download sphx-glr-download-zip :download:`Download zipped: GenEnsProd.zip ` .. only:: html .. rst-class:: sphx-glr-signature `Gallery generated by Sphinx-Gallery `_