From d6eaf24e3720cb206c4f7002fcbef40c181eb0b3 Mon Sep 17 00:00:00 2001 From: John Halley Gotway Date: Wed, 6 Mar 2024 22:07:08 +0000 Subject: [PATCH 01/11] Per #2729, get rid of extra blank line in log message about manually deleting temp files. --- src/basic/vx_config/temp_file.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/basic/vx_config/temp_file.cc b/src/basic/vx_config/temp_file.cc index 0a8ab6c715..5fc63f79c6 100644 --- a/src/basic/vx_config/temp_file.cc +++ b/src/basic/vx_config/temp_file.cc @@ -74,7 +74,7 @@ void remove_temp_file(const ConcatString file_name) { if (nullptr != keep_temp && (0 == strcmp(keep_temp, "true") || 0 == strcmp(keep_temp, "yes"))) { mlog << Debug(2) << "The temporary file (" - << file_name << ") was not deleted. Please remove it manually\n\n"; + << file_name << ") was not deleted. Please remove it manually.\n"; return; } From a2a295dc73a67d9d3edeefe9de5dab42bdf1cf10 Mon Sep 17 00:00:00 2001 From: John Halley Gotway Date: Thu, 7 Mar 2024 20:33:08 +0000 Subject: [PATCH 02/11] Per #2729, fix log message describing the range/azimuth grid. --- src/libcode/vx_grid/tcrmw_grid.cc | 3 +-- src/tools/tc_utils/tc_diag/tc_diag.cc | 4 ++-- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/src/libcode/vx_grid/tcrmw_grid.cc b/src/libcode/vx_grid/tcrmw_grid.cc index 031c71c65e..e4fa013f4f 100644 --- a/src/libcode/vx_grid/tcrmw_grid.cc +++ b/src/libcode/vx_grid/tcrmw_grid.cc @@ -213,8 +213,7 @@ RLLD.rot_lat_ll = 90.0 - range_max_deg; RLLD.rot_lon_ll = 0.0; RLLD.delta_rot_lat = range_max_deg/(Range_n - 1); -// RLLD.delta_rot_lon = 360.0/Azimuth_n; -RLLD.delta_rot_lon = 360.0/(Azimuth_n - 1); +RLLD.delta_rot_lon = 360.0/Azimuth_n; RLLD.Nlat = Range_n; RLLD.Nlon = Azimuth_n; diff --git a/src/tools/tc_utils/tc_diag/tc_diag.cc b/src/tools/tc_utils/tc_diag/tc_diag.cc index 332587b9eb..f007624c46 100644 --- a/src/tools/tc_utils/tc_diag/tc_diag.cc +++ b/src/tools/tc_utils/tc_diag/tc_diag.cc @@ -2211,8 +2211,8 @@ void TmpFileInfo::setup_nc_file(const DomainInfo &di, << "Defining cylindrical coordinates for (Lat, Lon) = (" << pnt_ptr->lat() << ", " << pnt_ptr->lon() << "), Range = " << ra_grid.range_n() << " every " << ra_grid.range_delta_km() - << ra_grid.range_n() << " every " << ra_grid.range_delta_km() - << "km, Azimuth = " << ra_grid.azimuth_n() << "\n"; + << " km, Azimuth = " << ra_grid.azimuth_n() << " every " + << ra_grid.azimuth_delta_deg() << " degrees.\n"; // Write track info write_tc_storm(tmp_out, From a29a5d70a7373778698ec5fa87fd97394f48a1ce Mon Sep 17 00:00:00 2001 From: John Halley Gotway Date: Mon, 11 Nov 2024 22:17:22 +0000 Subject: [PATCH 03/11] Per #2729, Update TC-Diag Python driver code to convert rotation angles from degree clockwise from due East to radians counter-clockwise from due East. --- .../tc_diag/tc_diag_driver/post_resample_driver.py | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/scripts/python/tc_diag/tc_diag_driver/post_resample_driver.py b/scripts/python/tc_diag/tc_diag_driver/post_resample_driver.py index 445470ca52..1bc1606fc5 100644 --- a/scripts/python/tc_diag/tc_diag_driver/post_resample_driver.py +++ b/scripts/python/tc_diag/tc_diag_driver/post_resample_driver.py @@ -140,7 +140,14 @@ def diag_calcs( land_lut = diag_vars.get_land_lut(land_lut_file) radii_1d = input_data[config.in_radii_name] _validate_radii(config.radii_to_validate, radii_1d, data_path) - azimuth_1d = input_data[config.in_azimuth_name] + + # MET #2729: Modify the azimuth values reported by MET + # - Subtract from 360 degrees to convert rotation angle + # from clockwise to counter-clockwise + # - Convert from degrees to radians + azimuth_1d_deg = (360 - input_data[config.in_azimuth_name]) % 360 + azimuth_1d = np.deg2rad(azimuth_1d_deg) + theta_2d, radii_2d = np.meshgrid(azimuth_1d, radii_1d) atcf_tech_id = _parse_atcf_id(input_data[config.full_track_line_name]) track = _dataset_track_lines_to_track( From e3590b1afbd2ba8af2237e1849bd2013b7199cbe Mon Sep 17 00:00:00 2001 From: John Halley Gotway Date: Tue, 12 Nov 2024 00:29:15 +0000 Subject: [PATCH 04/11] Per #2729, complete the TC-Diag documentation. --- docs/Users_Guide/tc-diag.rst | 91 ++++++++++++++++++++++++++++++++---- 1 file changed, 82 insertions(+), 9 deletions(-) diff --git a/docs/Users_Guide/tc-diag.rst b/docs/Users_Guide/tc-diag.rst index edcafa62dd..f6d224d4be 100644 --- a/docs/Users_Guide/tc-diag.rst +++ b/docs/Users_Guide/tc-diag.rst @@ -63,8 +63,6 @@ Optional Arguments for tc_diag 6. The **-v level** option indicates the desired level of verbosity. The contents of "level" will override the default setting of 2. Setting the verbosity to 0 will make the tool run with no log messages, while increasing the verbosity above 1 will increase the amount of logging. -.. note:: Setting the **MET_KEEP_TEMP_FILE** (:numref:`met_keep_temp_file`) environment variable retains the temporary NetCDF cylindrical coordinate files for development, testing, and debugging purposes. - tc_diag Configuration File -------------------------- @@ -130,7 +128,7 @@ The **domain_info** entry is an array of dictionaries. Each dictionary consists The **n_range** entry is an integer specifying the number of equally spaced range intervals in the range-azimuth grid to be used for this data source. -The **n_azimuth** entry is an integer specifying the number of equally spaced azimuth intervals in the range-azimuth grid to be used for this data source. The azimuthal grid spacing is 360 / **n_azimuth** degrees. +The **n_azimuth** entry is an integer specifying the number of equally spaced azimuth intervals in the range-azimuth grid to be used for this data source. The azimuthal grid spacing is 360 / **n_azimuth** degrees. Azimuths are defined by MET as *degrees clockwise* from due east. However, the TC-Diag Python code expects them as *radians counter-clockwise* from due east. The **tc_diag_driver/post_resample_driver.py** driver script performs the neccessary rotation and conversion operations. The **delta_range_km** entry is a floating point value specifying the spacing of the range rings in kilometers. @@ -249,23 +247,98 @@ The TC-Diag tool writes up to three output data types, as specified by flags in **CIRA Diagnostics Output** -When the **cira_diag_flag** configuration entry is set to true, an ASCII CIRA diagnostics output file is written for each model track provided. +When the **cira_diag_flag** configuration entry is set to true, an ASCII CIRA diagnostics output file is written for each model track provided. These files are named using the **output_base_format**, described above, followed by the **_diag.dat** suffix. + +These output files contain tabular ASCII data with the computed diagnostic values for a single track. One output file is created for each track from each model source. The output consists of the following sections: + + - Two header lines list the model name, initialization time, storm basin, and storm number (of the season). + + - The **STORM DATA** section contains single diagnostic values computed for each forecast lead time. This section begins with a line named **TIME** defining the forecast lead times in hours. The storm diagnostics computed for each line type follow. For example, **RMW** contains the radius of maximum wind value found within the range/azimuth grid. + + - The **SOUNDING DATA** section contains diagnostics computed separately for each pressure level. This section begins with two lines named **NLEV** and **TIME** defining the vertical level values and forecast lead times for which diagnostics were computed, respectively. The level name is appended to the diagnostic name. For example, the **T_0850** contains the average temperature value within the range/azimuth grid at the 850 mb pressure level. + + - Each diagnostic output line contains: + + - Diagnostic name (with or without the level) e.g. **SHR_MAG** for magnitude of wind shear -TODO: Details will be added for issue dtcenter/MET#2729. + - Units string enclosed in parenthesis e.g. **(KT)** for knots + + - The diagnostic values computed for each lead time e.g. **13 10 14 ...** **NetCDF Diagnostics Output** -When the **nc_diag_flag** configuration entry is set to true, a NetCDF output file containing the computed diagnostics is written for each model track provided. +When the **nc_diag_flag** configuration entry is set to true, a NetCDF output file containing the computed diagnostics is written for each model track provided. These files contain the same data provided in the CIRA Diagnostics Output but formatted in NetCDF instead of ASCII. These files are named using the **output_base_format**, described above, followed by the **_diag.nc** suffix. + +.. _table_TC-Diag_Dimensions_NetCDF_diagnostics: -TODO: Details will be added for issue dtcenter/MET#2729. +.. list-table:: Dimensions defined in NetCDF Diagnostics output + :widths: auto + :header-rows: 2 + + * - tc_diag NETCDF DIMENSIONS + - + * - NetCDF Dimension + - Description + * - time + - Time dimension for the number of track point valid times + * - pressure + - Vertical dimension for the number of pressure levels + +.. role:: raw-html(raw) + :format: html + +.. _table_TC-Diag_Variables_NetCDF_diagnostics: + +.. list-table:: Variables defined in NetCDF Diagnostics output + :widths: auto + :header-rows: 2 + + * - tc_diag NETCDF VARIABLES + - + - + * - NetCDF Variable + - Dimension + - Description + * - storm_id + - NA + - Tropical Cyclone Storm ID (BBNNYYYY) consisting of 2-letter basin name, 2-digit storm number, and 4-digit year + * - model + - NA + - Track ATCF ID model name + * - init_time + - NA + - Track initialization time string in YYYYMMDD_HHMMSS format + * - init_time_ut + - NA + - Track initialization time string in unixtime (seconds since January 1, 1970) format + * - valid_time + - time + - Track point valid time string in YYYYMMDD_HHMMSS format + * - valid_time_ut + - time + - Track point valid time string in unixtime (seconds since January 1, 1970) format + * - lead_time + - time + - Track point forecast lead time string in HHMMSS format + * - lead_time_sec + - time + - Track point forecast lead time integer number of seconds + * - {DOMAIN}_domain + - NA + - Attributes define the range/azimuth grid for the {DOMAIN} domain: **n_range**, **n_azimuth**, **delta_range_km** + * - Diagnostic values + - time or time and pressure + - Computed diagnostic values for each track point and, optionally, pressure level. The **units** attribute defines the units of the diagnostic values. **NetCDF Range-Azimuth Output** When the **nc_rng_azi_flag** configuration entry is set to true, a NetCDF output file containing the cylindrical coordinate range-azimuth data is written for each combination of model track provided and domain specified. For example, if three model tracks are provided and data for both *parent* and *nest* domains are provided, six of these NetCDF output files will be written. -The NetCDF range-azimuth output is named using the following naming convention: +The NetCDF range-azimuth output is named using the **output_base_format**, described above, followed by **_cyl_grid_{DOMAIN}.nc**, where **{DOMAIN}** is specified by the **domain** string in each **domain_info** array entry. + +This NetCDF file contains a concatenation of the data from the temporary NetCDF files created for each track point. For each track point, TC-Diag creates a temporary NetCDF file and calls Python code to read the cylindrical coordinates data and compute diagnostics. By default, these temporary NetCDF files are deleted at the end of each run, but if the **nc_rng_azi_flag** is true, the data for each track point is concatenated into a single output file for each track. -**tc_diag_STORMID_TECH_YYYYMMDDHH_cyl_grid_DOMAIN.nc** where STORMID is the 2-letter basin name, 2-digit storm number, and 4-digit year, TECH is the acronym for the objective technique, YYYYMMDDHH is the track initialization time, and DOMAIN is the domain name. +.. note:: Setting the **MET_KEEP_TEMP_FILE** (:numref:`met_keep_temp_file`) environment variable retains the temporary NetCDF cylindrical coordinate files for development, testing, and debugging purposes. The NetCDF range-azimuth file contains the dimensions and variables shown in :numref:`table_TC-Diag_Dimensions_NetCDF_range_azimuth` and :numref:`table_TC-Diag_Variables_NetCDF_range_azimuth`. From 8c57b187c36200b59e7a4999e491037817349db7 Mon Sep 17 00:00:00 2001 From: John Halley Gotway Date: Tue, 12 Nov 2024 00:36:06 +0000 Subject: [PATCH 05/11] Per #2729, more tweaks --- docs/Users_Guide/tc-diag.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/Users_Guide/tc-diag.rst b/docs/Users_Guide/tc-diag.rst index f6d224d4be..9ba8838cb9 100644 --- a/docs/Users_Guide/tc-diag.rst +++ b/docs/Users_Guide/tc-diag.rst @@ -209,7 +209,7 @@ Configuring Vortex Removal Option The **vortex_removal** flag entry is a boolean specifying whether or not vortex removal logic should be applied. -.. note:: As of MET version 11.1.0, vortex removal logic is not yet supported. +.. note:: As of MET version 12.0.0, vortex removal logic is not yet supported. Configuring Data Input and Output Options ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -251,11 +251,11 @@ When the **cira_diag_flag** configuration entry is set to true, an ASCII CIRA di These output files contain tabular ASCII data with the computed diagnostic values for a single track. One output file is created for each track from each model source. The output consists of the following sections: - - Two header lines list the model name, initialization time, storm basin, and storm number (of the season). + - Two header lines list the model name, initialization time, storm basin, and integer storm number (of the season). - The **STORM DATA** section contains single diagnostic values computed for each forecast lead time. This section begins with a line named **TIME** defining the forecast lead times in hours. The storm diagnostics computed for each line type follow. For example, **RMW** contains the radius of maximum wind value found within the range/azimuth grid. - - The **SOUNDING DATA** section contains diagnostics computed separately for each pressure level. This section begins with two lines named **NLEV** and **TIME** defining the vertical level values and forecast lead times for which diagnostics were computed, respectively. The level name is appended to the diagnostic name. For example, the **T_0850** contains the average temperature value within the range/azimuth grid at the 850 mb pressure level. + - The **SOUNDING DATA** section contains diagnostics computed separately for each vertical level. The vertical levels are typically the surface (e.g. **SURF**) followed by pressure levels (e.g. **0850**). This section begins with two lines named **NLEV** and **TIME** defining the number of vertical levels and their values and the forecast lead times for which diagnostics were computed, respectively. The level name is appended to each diagnostic name. For example, the **T_0850** contains the average temperature value within the range/azimuth grid at the 850 mb pressure level. - Each diagnostic output line contains: From 6f0fb08d351efaa3a5632447ae7c5c04baab2e44 Mon Sep 17 00:00:00 2001 From: John Halley Gotway Date: Tue, 12 Nov 2024 12:51:07 -0700 Subject: [PATCH 06/11] Per #2729, clarify that some diagnostics are directly extracted from the ATCF track file rather than being computed from the cylindrical coordinates grid. --- docs/Users_Guide/tc-diag.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Users_Guide/tc-diag.rst b/docs/Users_Guide/tc-diag.rst index 9ba8838cb9..d42e13692a 100644 --- a/docs/Users_Guide/tc-diag.rst +++ b/docs/Users_Guide/tc-diag.rst @@ -249,11 +249,11 @@ The TC-Diag tool writes up to three output data types, as specified by flags in When the **cira_diag_flag** configuration entry is set to true, an ASCII CIRA diagnostics output file is written for each model track provided. These files are named using the **output_base_format**, described above, followed by the **_diag.dat** suffix. -These output files contain tabular ASCII data with the computed diagnostic values for a single track. One output file is created for each track from each model source. The output consists of the following sections: +These output files contain tabular ASCII data with diagnostic values either extracted directly from the input ATCF track file or computed from the gridded data, after converting it to a storm-centric cylindrical coordinates grid. One output file is created for each track from each model source. The output consists of the following sections: - Two header lines list the model name, initialization time, storm basin, and integer storm number (of the season). - - The **STORM DATA** section contains single diagnostic values computed for each forecast lead time. This section begins with a line named **TIME** defining the forecast lead times in hours. The storm diagnostics computed for each line type follow. For example, **RMW** contains the radius of maximum wind value found within the range/azimuth grid. + - The **STORM DATA** section contains single diagnostic values either extracted from the ATCF track file or computed from the cylindrical coordinates grid for each forecast lead time. This section begins with a line named **TIME** defining the forecast lead time of each track point in hours. The following lines contain the requested storm diagnostics. For example, **MAXWIND** contains the maximum wind speed reported in the ATCF track file and **SST** contains the average sea surface temperature computed in the range/azimuth grid. - The **SOUNDING DATA** section contains diagnostics computed separately for each vertical level. The vertical levels are typically the surface (e.g. **SURF**) followed by pressure levels (e.g. **0850**). This section begins with two lines named **NLEV** and **TIME** defining the number of vertical levels and their values and the forecast lead times for which diagnostics were computed, respectively. The level name is appended to each diagnostic name. For example, the **T_0850** contains the average temperature value within the range/azimuth grid at the 850 mb pressure level. From 8b17c30a9fb2881bae6ad2a190c0ddd0582117d4 Mon Sep 17 00:00:00 2001 From: John Halley Gotway Date: Tue, 12 Nov 2024 16:03:49 -0700 Subject: [PATCH 07/11] Update docs/Users_Guide/tc-diag.rst Co-authored-by: KathrynNewman --- docs/Users_Guide/tc-diag.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Users_Guide/tc-diag.rst b/docs/Users_Guide/tc-diag.rst index d42e13692a..e7342d8e00 100644 --- a/docs/Users_Guide/tc-diag.rst +++ b/docs/Users_Guide/tc-diag.rst @@ -249,7 +249,7 @@ The TC-Diag tool writes up to three output data types, as specified by flags in When the **cira_diag_flag** configuration entry is set to true, an ASCII CIRA diagnostics output file is written for each model track provided. These files are named using the **output_base_format**, described above, followed by the **_diag.dat** suffix. -These output files contain tabular ASCII data with diagnostic values either extracted directly from the input ATCF track file or computed from the gridded data, after converting it to a storm-centric cylindrical coordinates grid. One output file is created for each track from each model source. The output consists of the following sections: +These output files contain tabular ASCII data with diagnostic values either extracted directly from the input ATCF track file or computed from the gridded data, after converting it to a storm-centric cylindrical grid. One output file is created for each track from each model source. The output consists of the following sections: - Two header lines list the model name, initialization time, storm basin, and integer storm number (of the season). From f23babd738221fd48a83bae1f6d354afa0c14db4 Mon Sep 17 00:00:00 2001 From: John Halley Gotway Date: Tue, 12 Nov 2024 16:04:04 -0700 Subject: [PATCH 08/11] Update docs/Users_Guide/tc-diag.rst Co-authored-by: KathrynNewman --- docs/Users_Guide/tc-diag.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Users_Guide/tc-diag.rst b/docs/Users_Guide/tc-diag.rst index e7342d8e00..3a7e0a0c2e 100644 --- a/docs/Users_Guide/tc-diag.rst +++ b/docs/Users_Guide/tc-diag.rst @@ -253,7 +253,7 @@ These output files contain tabular ASCII data with diagnostic values either extr - Two header lines list the model name, initialization time, storm basin, and integer storm number (of the season). - - The **STORM DATA** section contains single diagnostic values either extracted from the ATCF track file or computed from the cylindrical coordinates grid for each forecast lead time. This section begins with a line named **TIME** defining the forecast lead time of each track point in hours. The following lines contain the requested storm diagnostics. For example, **MAXWIND** contains the maximum wind speed reported in the ATCF track file and **SST** contains the average sea surface temperature computed in the range/azimuth grid. + - The **STORM DATA** section contains single diagnostic values either extracted from the ATCF track file or computed from the cylindrical grid for each forecast lead time. This section begins with a line named **TIME** defining the forecast lead time of each track point in hours. The following lines contain the requested storm diagnostics. For example, **MAXWIND** contains the maximum wind speed reported in the ATCF track file and **SST** contains the average sea surface temperature computed in the range/azimuth grid. - The **SOUNDING DATA** section contains diagnostics computed separately for each vertical level. The vertical levels are typically the surface (e.g. **SURF**) followed by pressure levels (e.g. **0850**). This section begins with two lines named **NLEV** and **TIME** defining the number of vertical levels and their values and the forecast lead times for which diagnostics were computed, respectively. The level name is appended to each diagnostic name. For example, the **T_0850** contains the average temperature value within the range/azimuth grid at the 850 mb pressure level. From bd006290d75cf98a3e779e2fa80fc248302945a1 Mon Sep 17 00:00:00 2001 From: John Halley Gotway Date: Tue, 12 Nov 2024 16:04:10 -0700 Subject: [PATCH 09/11] Update docs/Users_Guide/tc-diag.rst Co-authored-by: KathrynNewman --- docs/Users_Guide/tc-diag.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Users_Guide/tc-diag.rst b/docs/Users_Guide/tc-diag.rst index 3a7e0a0c2e..60b44e485a 100644 --- a/docs/Users_Guide/tc-diag.rst +++ b/docs/Users_Guide/tc-diag.rst @@ -332,7 +332,7 @@ When the **nc_diag_flag** configuration entry is set to true, a NetCDF output fi **NetCDF Range-Azimuth Output** -When the **nc_rng_azi_flag** configuration entry is set to true, a NetCDF output file containing the cylindrical coordinate range-azimuth data is written for each combination of model track provided and domain specified. For example, if three model tracks are provided and data for both *parent* and *nest* domains are provided, six of these NetCDF output files will be written. +When the **nc_rng_azi_flag** configuration entry is set to true, a NetCDF output file containing the cylindrical range-azimuth data is written for each combination of model track provided and domain specified. For example, if three model tracks are provided and data for both *parent* and *nest* domains are provided, six of these NetCDF output files will be written. The NetCDF range-azimuth output is named using the **output_base_format**, described above, followed by **_cyl_grid_{DOMAIN}.nc**, where **{DOMAIN}** is specified by the **domain** string in each **domain_info** array entry. From 546a70f7bea66f66617c14ef64b1dfa63cb883f2 Mon Sep 17 00:00:00 2001 From: John Halley Gotway Date: Tue, 12 Nov 2024 16:04:34 -0700 Subject: [PATCH 10/11] Update docs/Users_Guide/tc-diag.rst Co-authored-by: KathrynNewman --- docs/Users_Guide/tc-diag.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Users_Guide/tc-diag.rst b/docs/Users_Guide/tc-diag.rst index 60b44e485a..1929f80245 100644 --- a/docs/Users_Guide/tc-diag.rst +++ b/docs/Users_Guide/tc-diag.rst @@ -336,7 +336,7 @@ When the **nc_rng_azi_flag** configuration entry is set to true, a NetCDF output The NetCDF range-azimuth output is named using the **output_base_format**, described above, followed by **_cyl_grid_{DOMAIN}.nc**, where **{DOMAIN}** is specified by the **domain** string in each **domain_info** array entry. -This NetCDF file contains a concatenation of the data from the temporary NetCDF files created for each track point. For each track point, TC-Diag creates a temporary NetCDF file and calls Python code to read the cylindrical coordinates data and compute diagnostics. By default, these temporary NetCDF files are deleted at the end of each run, but if the **nc_rng_azi_flag** is true, the data for each track point is concatenated into a single output file for each track. +This NetCDF file contains a concatenation of the data from the temporary NetCDF files created for each track point. For each track point, TC-Diag creates a temporary NetCDF file and calls Python code to read the cylindrical grid data and compute diagnostics. By default, these temporary NetCDF files are deleted at the end of each run, but if the **nc_rng_azi_flag** is true, the data for each track point is concatenated into a single output file for each track. .. note:: Setting the **MET_KEEP_TEMP_FILE** (:numref:`met_keep_temp_file`) environment variable retains the temporary NetCDF cylindrical coordinate files for development, testing, and debugging purposes. From 5b609314731fdfbefea721466805da2b1e04057b Mon Sep 17 00:00:00 2001 From: John Halley Gotway Date: Tue, 12 Nov 2024 16:04:44 -0700 Subject: [PATCH 11/11] Update docs/Users_Guide/tc-diag.rst Co-authored-by: KathrynNewman --- docs/Users_Guide/tc-diag.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Users_Guide/tc-diag.rst b/docs/Users_Guide/tc-diag.rst index 1929f80245..14c6e5ffbd 100644 --- a/docs/Users_Guide/tc-diag.rst +++ b/docs/Users_Guide/tc-diag.rst @@ -338,7 +338,7 @@ The NetCDF range-azimuth output is named using the **output_base_format**, descr This NetCDF file contains a concatenation of the data from the temporary NetCDF files created for each track point. For each track point, TC-Diag creates a temporary NetCDF file and calls Python code to read the cylindrical grid data and compute diagnostics. By default, these temporary NetCDF files are deleted at the end of each run, but if the **nc_rng_azi_flag** is true, the data for each track point is concatenated into a single output file for each track. -.. note:: Setting the **MET_KEEP_TEMP_FILE** (:numref:`met_keep_temp_file`) environment variable retains the temporary NetCDF cylindrical coordinate files for development, testing, and debugging purposes. +.. note:: Setting the **MET_KEEP_TEMP_FILE** (:numref:`met_keep_temp_file`) environment variable retains the temporary NetCDF cylindrical grid files for development, testing, and debugging purposes. The NetCDF range-azimuth file contains the dimensions and variables shown in :numref:`table_TC-Diag_Dimensions_NetCDF_range_azimuth` and :numref:`table_TC-Diag_Variables_NetCDF_range_azimuth`.