Reformat Site Prep Guide 1 - Total Operational Weather Readiness - Satellites (TOWR-S)
Site Preparation Guide - Old Content
Previous Format - Site Preparation Guide for the TOWR-S RPM
1/27/22 TOWR-S RPM v22: No new LDM/pqact updates are required for TOWR-S v22.
Click here to return to the TOWR-S RPM Installation instructions.
TOWR-S RPM Version 21 (May 2021): Below are LDM instructions for preparing AWIPS to receive new satellite products for TOWR-S RPM version 21. The Full Disk Geostationary Lightning Mapper (GLM) gridded products (flash extent density, minimum flash area, total optical area--a GLM quick guide is available at this link), S-NPP/NOAA-20 VIIRS Active Fires, and CIMSS GOES Turbulence Probability products are continued, while configurations that have been baselined are removed. Although Geocolor is not widely fielded with this update, the configurations for edex ingest and cave display are maintained and compatible for sites who are continuing the Geocolor APP evaluation.
These site prep instructions enable data flow and complement the TOWR-S RPM Installation instructions.
Follow steps A.21 - G.21, below sequentially for TOWR-S RPM Version 21. If you do not plan on configuring any of the above new products, skip to C.21 for a note on pqact updates related to AWIPS base version 20.2.1 as it relates to previous RPMs v18.5-v20.
A.21 Updates to cpsbn1 ldmd.conf
A.21.1. On cpsbn1, as ldm, first check the ability to connect to the LDAD LDM:
root@cpsbn1# su - ldm
ldmping ls1-xxx (xxx is your lowercase 3-letter ID)
if an IDM site:
sudo -u ldm /usr/local/ldm/bin/ldmping ls1-xxx
A.21.2. Add or confirm the following entries in /usr/local/ldm/etc/ldmd.conf on cpsbn1 for each desired new product, replacing <tab> with the literal TAB keyboard function:
(as user ldm) vi ldmd.conf
vi /usr/local/ldm/etc/ldmd.conf
if an IDM site:
sudo -u ldm vi /usr/local/ldm/etc/ldmd.conf
(note: add the commented line starting w/ # as well as the line starting w/REQUEST for each desired product. xxx is your site's lower case 3-letter id, some may just use ls1 here w/o the -xxx. For Central Region, offices do not need to make the individual request entries for this file. Instead, CR offices have a statement: request ANY * ls1-xxx in their ldmd conf file. CR Offices can skip to step B.21.)
The following entry (intro'd in towr-s v21) should be added:
#GOES Meso Sector Fire Hot Spot from CR feed
REQUEST<tab>EXP<tab>"^OR_ABI-L2-FDCM"<tab>ls1-xxx
A # symbol above indicates a comment, to be included in the ldmd.conf.
B.21 Updates to pqact conf template on dx1:
The following are steps to edit pqact.conf.xxx (where xxx is your lower-case site id), on dx1 to add pqact entries for relevant products from step A.21, above.
Log in to dx1 as ldm.
root@dx1# su - ldm
[ldm@dx1]$ cd /usr/local/ldm/etc
[ldm@dx1]$ vi pqact.conf.xxx
if an IDM site:
sudo -u ldm vi /usr/local/ldm/etc/pqact.conf.xxx
Open /usr/local/ldm/etc/pqact.conf.xxx as shown above with vi. For the relevant entry(ies) in Section A.21 above, add the following corresponding expressions, replacing <tab> with the literal TAB keyboard function:
a)
#GOES Meso Sector Fire Hot Spot from CR feed
EXP<tab>^(OR_ABI-L2-FDCM.*)
<tab>FILE<tab>-overwrite -log -close -edex<tab>/data_store/goes-r/%Y%m%d/%H/\1_(seq)
If your site also plans bring in the West Conus (PACUS) sector GOES-17 Fog and Low Stratus products when they're released on the SBN later this summer, then add the following pattern to /usr/local/ldm/etc/pqact.conf.xxx, in addition to the ones above.
# GOES-West Fog and Low Stratus Products from the SBN
ANY<tab>^(IXTE89) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -log -close -edex<tab>/data_store/goes-r/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
NOTE: The "ANY" or "EXP" lines above are on one line and everything from <tab>FILE, or <tab>PIPE are on another line. Also note that the series of dots (..) which appear on the first rows with parentheses have no spaces between them within the parentheses. Ensure that the portion of the expressions above have only one space before and one space after (KNES) . In the Fog and Low stratus entry there is one space after -overwrite, -log, -close, and -edex.
The # in each of the lines above indicates a comment to be included in the file.
NOTE: A dot (.) star/asterisk (*) is used in each line above starting w/EXP. The number one (1) is used in the expressions above at the end of the data path, \1_(seq). The "EXP" line is one line and everything from <tab>FILE through the %d%H is on another line. There is one space after -overwrite, -log, and -close. There is a tab after -edex (between -edex and /data_store). A template file (also linked above) containing each of the above v21 entries with the proper tabs to ADD is included here. Note (5/28): does not include geocolor entries, which will be provided separately (stay tuned for details).
Any ^IXTR entries for the now-deactivated CONUS/PACUS GLM (any ^IXTR88/98/89/99) should be deleted because they were replaced by Full Disk GLM products (e.g. OR_GLM patterns introduced in towr-s V20):
(Remove these entries:)
#GOES-16
EXP<tab>^(IXTR98) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -close -edex -log<tab>/data_store/glm/(\3:yyyy)(\3:mm)\3/\4/GOES-16/\1_\2_\3\4\5_(seq).%Y%m%d%H%M
#GOES-17
EXP<tab>^(IXTR88) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -close -edex -log<tab>/data_store/glm/(\3:yyyy)(\3:mm)\3/\4/GOES-17/\1_\2_\3\4\5_(seq).%Y%m%d%H%M
The following entry (intro'd in towr-s v20) should be deleted because SCATSAT data is no longer and will no longer be available from the source due to an instrument issue:
(Remove this entry:)
#SCATSAT sea surface winds
EXP<tab>^(nc_SCATSAT.*)
<tab>FILE<tab>-overwrite -log -close -edex<tab>/data_store/polar/%Y%m%d/%H/\1_(seq)
A template file (also linked above) containing examples of each of the above entries with the the proper tabs to REMOVE is included here.
C.21 For sites at baseline AWIPS 20.2.1 or higher:
A note for sites installing baseline AWIPS 20.2.x. If AWIPS 20.2.1 or higher is installed, some of the local pqact updates (previously) detailed in these instructions for TOWR-S v18.5 (Mar 2020) and/or v19 (Aug 2020) have been baselined, and should no longer reside in the site pqact conf template. The AWIPS living release notes have this information (the link is here, see DCS 21477 under the OB 20.2.1 tab), but it is also described here:
In baseline AWIPS 20.2.1 or higher, there is a new pqact.conf.base.national entry (on cpsbn1) for the blended hydro (polar sat) TPW/Rain Rate Products:
ANY<tab>^(TI[CT]X..) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/polar/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H .
There is also a new pqact.conf.base.conus entry (on cpsbn1) for the GOES-17 Derived Motion Winds (DMWs) for baseline AWIPS 20.2.1 or higher:
ANY<tab>^(IXTU89) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/goes-r/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
Remove these 2 patterns (above) from your dx1 pqact.conf.xxx. They will be accounted for when the config_awips2.sh script is run since they are now baselined. If this applies, and edits are required to remove them, remove, then save your modified template and continue with steps D.21 and E.21, below.
D.21 Check the syntax of local pqact entries:
D.21.1 Copy files: On dx1, as user ldm:
[ldm@dx1]$ cd /usr/local/ldm/etc
scp -p pqact.conf.xxx dx2:/usr/local/ldm/etc/
scp -p pqact.conf.xxx cpsbn1:/usr/local/ldm/etc/
if an IDM site:
FROM the /usr/local/ldm directory:
sudo -u ldm chmod 644 pqact.conf.xxx
sudo scp /usr/local/ldm/etc/pqact.conf.xxx dx2:/usr/local/ldm/etc/
sudo scp /usr/local/ldm/etc/pqact.conf.xxx cpsbn1:/usr/local/ldm/etc/
Each of the scp commands consist of a single line of commands. This is prep for the config_awips2.sh script, which will be run, below. Even though the "config_awips2.sh ldm XXX" localization checks the syntax of the pqact.conf.xxx before it pushes it to the CPs, it is recommended to run the "ldmadmin pqactcheck -p etc/pqact.conf.xxx" command (coming up, next) to verify the file/s are correct after any edits, first. This step assumes the "ldmadmin" tool is not installed on dx1, and assumes you must log in to the CPs to do this and run it on a local copy of pqact.conf.xxx, there:
D.21.2 running pqactcheck:
As root on cpsbn1, switch user to ldm:
root@cpsbn1# su - ldm
[ldm@cpsbn1]$ ldmadmin pqactcheck -p etc/pqact.conf.xxx
if an IDM site:
FROM the /usr/local/ldm directory
sudo -u ldm /usr/local/ldm/bin/ldmadmin pqactcheck -p etc/pqact.conf.xxx
D.21.3. Run the ldm task to create the pqact.conf. (Assumes pqact.conf.xxx file checks out)
As root on dx1
root@dx1# cd /data/fxa/sdc
root@dx1# ./config_awips2.sh ldm XXX
(where XXX is the site 3-letter in all capital letters)
if an IDM site: sudo /data/fxa/sdc/config_awips2.sh ldm XXX
(where XXX is the site 3-letter in all capital letters)
E.21 Restart the cpsbn1 LDM:
a) The config_awips2 script, above, restarts the CP's LDM processes, but it can be done manually as well. On the CPSBN that is currently ingesting SBN data (CPSBN1 by default), restart LDM as ldm with the commands:
root@cpsbn1# su - ldm
ldm@cpsbn1# ldmadmin stop
ldm@cpsbn1# ldmadmin clean
ldm@cpsbn1# ldmadmin start
if an IDM site:
sudo -i -u ldm ldmadmin stop
sudo -i -u ldm ldmadmin clean
Then:
sudo -i -u ldm ldmadmin start
b) As a validation that LDM is running smoothly, execute ldmadmin watch (data should stream by on the screen to indicat LDM is running):
sudo -i -u ldm ldmadmin watch
Note: When running sudo for the ldmadmin command, it is important that IdM sites should use the -i flag (as shown above) to ensure new files from LDM are written with the proper permissions. LDM will then write all new files with group fxalpha write permissions, ensuring proper edex ingest and clean-up processes.
F.21 Update the LDAD LDM for any Products added in B.21 and C.21:
Log into LDAD. As user ldm, modify LDAD LDM config to request and store from feed EXP for the desired products/patterns specified in previous steps:
root@ls1# su - ldm
vi etc/ldmd.conf
if an IDM site:
sudo -u ldm vi /usr/local/ldm/etc/ldmd.conf
F.21.1 Add or confirm the following entries in /usr/local/ldm/etc/ldmd.conf on LDAD for each desired product, replacing <tab> with the literal TAB keyboard function. Substitute "your_regional_ldm_server" with your regional server's name:
#GOES Meso Sector Fire Hot Spot from CR feed
REQUEST<tab>EXP<tab>"^OR_ABI-L2-FDCM"<tab>your_regional_ldm_server
The # above indicates a comment, to be included in the ldmd.conf.
Any ^IXTR entries for the now-deactivated CONUS/PACUS GLM (any ^IXTR88/98/89/99) should be deleted because they were replaced by Full Disk GLM products (e.g. OR_GLM patterns introduced in towr-s V20):
(e.g. Remove this entry)
REQUEST<tab>EXP<tab>^IXTR[89]9<tab> etc
The following entry (intro'd in towr-s v20) should be deleted because SCATSAT data is no longer and will no longer be available from the source due to an instrument issue:
(Remove this entry:)
#SCATSAT Sea surface winds
REQUEST<tab>EXP<tab>"^nc_SCATSAT"<tab>your_regional_ldm_server
Check with your region if you need the information that goes into "your_regional_ldm_server", above (e.g. for Western Region it is galileo3.wrh.noaa.gov).
F.21.2. Finally, add or ensure you also have in /usr/local/ldm/etc/ldmd.conf on LDAD:
ALLOW<tab>ANY<tab>gw-xxx
where xxx above is your site's lowercase 3-letter ID (e.g. xxx=oax for site OAX).
G.21 Restart the LDAD LDM:
a) As user ldm, restart the LDAD LDM with the commands:
root@ls1# (or root@ls2)# su - ldm
ldm@ls1# ldmadmin stop && ldmadmin clean
ldm@ls1# ldmadmin start
if an IDM site:
sudo -i -u ldm ldmadmin stop
sudo -i -u ldm ldmadmin clean
Then:
sudo -i -u ldm ldmadmin start
b) As a validation that LDM is running smoothly, execute ldmadmin watch. Data should stream by on the screen, indicating that LDM is running:
sudo -i -u ldm ldmadmin watch
Note: When running sudo for the ldmadmin command, it is important that IdM sites should use the -i flag (as shown above) to ensure new files from LDM are written with the proper permissions. LDM will then write all new files with group fxalpha write permissions, ensuring proper edex ingest and clean-up processes.
As a best practice, copy the modified ldmd conf file to the inactive LDAD server (typically ls3) for failover purposes.
That's it. VERSION 21 Site Prep is now COMPLETED
That's it, LDM is now configured for TOWR-S RPM Version 21. Return to the TOWR-S RPM Installation instructions. For more information, contact Lee Byerle (lee.byerle@noaa.gov) or John Evans (john.d.evans@noaa.gov). You can also join the NWS Chatroom group ("towr-s") for questions or information. Here is a link back to the TOWR-S RPM Installation instructions.
########################################################################################################
Below are older instructions for previous RPM Versions:
########################################################################################################
TOWR-S RPM Version 20 (old version) Instructions are here:
Follow steps A.20 - G.20, below sequentially for towr-s RPM Version 20 preparation. If you do not plan on configuring any of the above products, skip to C.20 for a note on pqact updates related to AWIPS base version 20.2.1 as it relates to previous RPMs v18.5-v19.
A.20 Updates to cpsbn1 ldmd.conf
A.20.1. On cpsbn1, as ldm, first check the ability to connect to the LDAD LDM:
root@cpsbn1# su - ldm
ldmping ls1-xxx (xxx is your lowercase 3-letter ID)
if an IDM site:
sudo -u ldm /usr/local/ldm/bin/ldmping ls1-xxx
A.20.2. Add or confirm the following entries in /usr/local/ldm/etc/ldmd.conf on cpsbn1 for each desired product, replacing <tab> with the literal TAB keyboard function (GOES-GLM is highly recommended because the CONUS/PACUS grids will turn off after a short period of overlap):
(as user ldm) vi ldmd.conf
vi /usr/local/ldm/etc/ldmd.conf
if an IDM site:
sudo -u ldm vi /usr/local/ldm/etc/ldmd.conf
(note: add the commented line starting w/ # as well as the line starting w/REQUEST for each desired product. xxx is your site's lower case 3-letter id, some may just use ls1 here w/o the -xxx. For Central Region, offices do not need to make the individual request entries for this file. Instead, CR offices have a statement: request ANY * ls1-xxx in their ldmd conf file. CR Offices can skip to step B.20.):
a) GOES GLM:
#GOES GLM Full Disk Tiles
REQUEST<tab>EXP<tab>"^OR_GLM-L[23]-GLMF-M[3-6]_G1[67]_T"<tab>ls1-xxx
(For G16 (GOES-East) or G17 (GOES-West) GLM but not both, remove the 6 or the 7 after G1)
12/2/2020: Please note change in REQUEST line below has been made from -TURB- to -TURBC-
b) CIMSS GOES Turbulence Probability:
#CIMSS GOES Turbulence probability
REQUEST<tab>EXP<tab>"^uwssec_isatss_L3-TURBC-M[3-6]_G1[67]_T"<tab>ls1-xxx
(For G16 (East) or G17 (West) Turbulence Prob, but not both, remove the 6 or the 7 after G1)
c) SCATSAT sea surface winds:
#SCATSAT Sea surface winds
REQUEST<tab>EXP<tab>"^nc_SCATSAT"<tab>ls1-xxx
d) GOES Cryosphere (Ice concentration, thickness):
#GOES Cryosphere Ice concentration, thickness
REQUEST<tab>EXP<tab>"^[OD]R_ABI-L2-AI(CEF|TAF)-M[3-6]_G1[67]_"<tab>ls1-xxx
(If you would like G16 (East) or G17 (West) but not both, remove the 6 or the 7 after G1)
e) GOES Cryosphere Ice motion:
#GOES Cryosphere Ice motion
REQUEST<tab>EXP<tab>"^IR_ABI-L2-AIMF-M[3-6]_G1[67]_"<tab>ls1-xxx
(If you would like G16 (East) or G17 (West) but not both,remove the 6 or the 7 after G1)
f) S-NPP and NOAA-20 VIIRS Active Fires:
#S-NPP and NOAA-20 VIIRS Active Fires
REQUEST<tab>EXP<tab>"^viirs_fires"<tab>ls1-xxx
The # in each of the lines above indicates a comment.
B.20 Updates to pqact conf template on dx1:
The following are steps to edit pqact.conf.xxx (where xxx is your lower-case site id), on dx1 to add pqact entries for each of relevant products from step A.20, above. A template file with each formatted pqact template entry for towr-s RPM version 20 (containing the proper tabs) is included here, and as of 12/2/2020, this template includes the correction to the Turbulence probability product pattern as -TURBC- (was previously -TURB-).
Log in to dx1 as ldm.
root@dx1# su - ldm
[ldm@dx1]$ cd /usr/local/ldm/etc
[ldm@dx1]$ vi pqact.conf.xxx
if an IDM site:
sudo -u ldm vi /usr/local/ldm/etc/pqact.conf.xxx
Open /usr/local/ldm/etc/pqact.conf.xxx as shown above with vi. For (only) relevant entries in Section A.20 above, add the following corresponding expressions, replacing <tab> with the literal TAB keyboard function:
a) GOES GLM:
#GLM Full Disk Tiles
EXP<tab>^(OR_GLM-L[23]-GLMF-M[3-6]_G1[67]_T.*)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/goes-r/%Y%m%d/%H/\1_(seq)
(For G16 (GOES-East) or G17 (GOES-West) GLM but not both, remove the 6 or the 7 after G1)
12/2/2020: Please note change in REQUEST line below has been made from -TURB- to -TURBC-
b) CIMSS GOES Turbulence Probability:
#CIMSS GOES Turbulence probability
EXP<tab>^(uwssec_isatss_L3-TURBC-M[3-6]_G1[67]_T.*)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/goes-r/%Y%m%d/%H/\1_(seq)
(For G16 (East) or G17 (West) Turbulence probability but not both, remove the 6 or the 7 after G1)
c) SCATSAT sea surface winds:
#SCATSAT sea surface winds
EXP<tab>^(nc_SCATSAT.*)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/polar/%Y%m%d/%H/\1_(seq)
d) GOES Cryosphere Ice concentration, thickness:
#GOES Cryosphere Ice concentration, thickness
EXP<tab>^([OD]R_ABI-L2-AI(CEF|TAF)-M[3-6]_G1[67]_.*)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/goes-r/%Y%m%d/%H/\1_(seq)
(If you would like G16 (East) or G17 (West) but not both, remove the 6 or the 7 after G1)
e) GOES Cryosphere Ice motion:
#GOES Cryosphere Ice motion
EXP<tab>^(IR_ABI-L2-AIMF-M[3-6]_G1[67]_.*)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/goes-r/%Y%m%d/%H/\1_(seq)
(If you would like G16 (East) or G17 (West) but not both, remove the 6 or the 7 after G1)
f) S-NPP and NOAA-20 VIIRS Active Fires:
#S-NPP and NOAA-20 VIIRS Active Fires
EXP<tab>^(viirs_fires.*)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/polar/%Y%m%d/%H/\1_(seq)
The # in each of the lines above indicates a comment.
NOTE: A dot (.) star/asterisk (*) is used in each line above starting w/EXP. The number one (1) is used in the expressions above at the end of the data path, \1_(seq). The "EXP" line is one line and everything from <tab>FILE through the %d%H is on another line. There is one space after -overwrite, -log, -close, and -edex. Items c) and f) have a sub-dir called polar, while the others use the goes-r subdir. A template file (also linked above) containing each of the above v20 entries with the the proper tabs is is included here, and as of 12/2/2020, this template includes the correction to the Turbulence probability product pattern as -TURBC- (was previously -TURB-).
C.20 For sites at baseline AWIPS 20.2.1 or higher:
A note for sites installing baseline AWIPS 20.2.x. If AWIPS 20.2.1 or higher is installed, some of the local pqact updates (previously) detailed in these instructions for TOWR-S v18.5 (Mar 2020) and/or v19 (Aug 2020) have been baselined, and should no longer reside in the site pqact conf template. The AWIPS release notes have this information, but it is also described here:
In baseline AWIPS 20.2.1 or higher, there is a new pqact.conf.base.national entry (on cpsbn1) for the blended hydro (polar sat) TPW/Rain Rate Products:
ANY<tab>^(TI[CT]X..) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/polar/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H .
There is also a new pqact.conf.base.conus entry (on cpsbn1) for the GOES-17 Derived Motion Winds (DMWs) for baseline AWIPS 20.2.1 or higher:
ANY<tab>^(IXTU89) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/goes-r/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
Therefore, check to make sure these two patterns are removed from your dx1 pqact.conf.xxx. They will be accounted for when the config_awips2.sh script is run since they are now baselined. If this applies, and edits are required to remove them, remove, then save your modified template and continue with steps D.20 and E.20, below.
D.20 Check the syntax of local pqact entries:
D.20.1 Copy files: On dx1, as user ldm:
[ldm@dx1]$ cd /usr/local/ldm/etc
scp -p pqact.conf.xxx dx2:/usr/local/ldm/etc/
scp -p pqact.conf.xxx cpsbn1:/usr/local/ldm/etc/
if an IDM site:
FROM the /usr/local/ldm directory:
sudo /bin/scp -p /usr/local/ldm/etc/pqact.conf.xxx dx2:/usr/local/ldm/etc/
sudo /bin/scp -p /usr/local/ldm/etc/pqact.conf.xxx cpsbn1:/usr/local/ldm/etc/
Each of the scp commands consist of a single line of commands. This is prep for the config_awips2.sh script, which will be run, below. Even though the "config_awips2.sh ldm XXX" localization checks the syntax of the pqact.conf.xxx before it pushes it to the CPs, it is recommended to run the "ldmadmin pqactcheck -p etc/pqact.conf.xxx" command (coming up, next) to verify the file/s are correct after any edits, first. This step assumes the "ldmadmin" tool is not installed on dx1, and assumes you must log in to the CPs to do this and run it on a local copy of pqact.conf.xxx, there:
D.20.2 running pqactcheck:
As root on cpsbn1, switch user to ldm:
root@cpsbn1# su - ldm
[ldm@cpsbn1]$ ldmadmin pqactcheck -p etc/pqact.conf.xxx
if an IDM site:
FROM the /usr/local/ldm directory
sudo -u ldm /usr/local/ldm/bin/ldmadmin pqactcheck -p etc/pqact.conf.xxx
D.20.3. Run the ldm task to create the pqact.conf. (Assumes pqact.conf.xxx file checks out)
As root on dx1
root@dx1# cd /data/fxa/sdc
root@dx1# ./config_awips2.sh ldm XXX
(where XXX is the site 3-letter in all capital letters)
if an IDM site: sudo /data/fxa/sdc/config_awips2.sh ldm XXX
(where XXX is the site 3-letter in all capital letters)
E.20 Restart the cpsbn1 LDM:
a) The config_awips2 script, above, restarts the CP's LDM processes, but it can be done manually as well. On the CPSBN that is currently ingesting SBN data (CPSBN1 by default), restart LDM as ldm with the commands:
root@cpsbn1# su - ldm
ldm@cpsbn1# ldmadmin stop && ldmadmin clean
ldm@cpsbn1# ldmadmin start
if an IDM site:
sudo -i -u ldm ldmadmin stop
sudo -i -u ldm ldmadmin clean
Then:
sudo -i -u ldm ldmadmin start
b) As a validation that LDM is running smoothly, execute ldmadmin watch (data should stream by on the screen to indicat LDM is running):
sudo -i -u ldm ldmadmin watch
Note: When running sudo for the ldmadmin command, it is important that IdM sites should use the -i flag (as shown above) to ensure new files from LDM are written with the proper permissions. LDM will then write all new files with group fxalpha write permissions, ensuring proper edex ingest and clean-up processes.
F.20 Update the LDAD LDM for any Products added in B.20 and C.20:
Log into LDAD. As user ldm, modify LDAD LDM config to request and store from feed EXP for the desired products/patterns specified in previous steps:
root@ls1# su - ldm
vi ldmd.conf
if an IDM site:
sudo -u ldm -vi /usr/local/ldm/etc/ldmd.conf
F.20.1 Add or confirm the following entries in /usr/local/ldm/etc/ldmd.conf on LDAD for each desired product, replacing <tab> with the literal TAB keyboard function (GOES-GLM is highly recommended because the CONUS/PACUS grids will turn off after a short period of overlap). Substit "your_regional_ldm_server" with your regional server's name:
a) GOES GLM:
#GOES GLM Full Disk Tiles
REQUEST<tab>EXP<tab>"^OR_GLM-L[23]-GLMF-M[3-6]_G1[67]_T"<tab>your_regional_ldm_server
(For G16 (GOES-East) or G17 (GOES-West) GLM but not both, remove the 6 or the 7 after G1)
12/2/2020: Please note change in REQUEST line below has been made from -TURB- to -TURBC-
b) CIMSS GOES Turbulence Probability:
#CIMSS GOES Turbulence probability
REQUEST<tab>EXP<tab>"^uwssec_isatss_L3-TURBC-M[3-6]_G1[67]_T"<tab>your_regional_ldm_server
(For G16 (East) or G17 (West) Turbulence Prob, but not both, remove the 6 or the 7 after G1)
c) SCATSAT sea surface winds:
#SCATSAT Sea surface winds
REQUEST<tab>EXP<tab>"^nc_SCATSAT"<tab>your_regional_ldm_server
d) GOES Cryosphere (Ice concentration, thickness):
#GOES Cryosphere Ice concentration, thickness
REQUEST<tab>EXP<tab>"^[OD]R_ABI-L2-AI(CEF|TAF)-M[3-6]_G1[67]_"<tab>your_regional_ldm_server
(If you would like G16 (East) or G17 (West) but not both, remove the 6 or the 7 after G1)
e) GOES Cryosphere Ice motion:
#GOES Cryosphere Ice motion
REQUEST<tab>EXP<tab>"^IR_ABI-L2-AIMF-M[3-6]_G1[67]_"<tab>your_regional_ldm_server
(If you would like G16 (East) or G17 (West) but not both,remove the 6 or the 7 after G1)
f) S-NPP and NOAA-20 VIIRS Active Fires:
#S-NPP and NOAA-20 VIIRS Active Fires
REQUEST<tab>EXP<tab>"^viirs_fires"<tab>your_regional_ldm_server
The # in each of the lines above indicates a comment.
Check with your region if you need the information that goes into "your_regional_ldm_server", above (e.g. for Western Region it is galileo3.wrh.noaa.gov).
F.20.2. Finally, add or ensure you also have in /usr/local/ldm/etc/ldmd.conf on LDAD:
ALLOW<tab>ANY<tab>gw-xxx
where xxx above is your site's lowercase 3-letter ID (e.g. xxx=oax for site OAX).
G.20 Restart the LDAD LDM:
a) As user ldm, restart the LDAD LDM with the commands:
root@ls1# (or root@ls2)# su - ldm
ldm@ls1# ldmadmin stop && ldmadmin clean
ldm@ls1# ldmadmin start
if an IDM site:
sudo -i -u ldm ldmadmin stop
sudo -i -u ldm ldmadmin clean
Then:
sudo -i -u ldm ldmadmin start
b) As a validation that LDM is running smoothly, execute ldmadmin watch. Data should stream by on the screen, indicating that LDM is running:
sudo -i -u ldm ldmadmin watch
Note: When running sudo for the ldmadmin command, it is important that IdM sites should use the -i flag (as shown above) to ensure new files from LDM are written with the proper permissions. LDM will then write all new files with group fxalpha write permissions, ensuring proper edex ingest and clean-up processes.
As a best practice, copy the modified ldmd conf file to the inactive LDAD server (typically ls3) for failover purposes.
That's it. VERSION 20 Site Prep is now COMPLETED
That's it, LDM is now configured for TOWR-S RPM Version 20. Return to the TOWR-S RPM Installation instructions. For more information, contact Lee Byerle (lee.byerle@noaa.gov) or John Evans (john.d.evans@noaa.gov). You can also join the NWS Chatroom group ("towr-s") for questions or information.
################################################################
TOWR-S RPM Version 19 and Prior RPM Instructions are here:
SECTION A.
Below are LDM-related directions for preparing your site's AWIPS system to receive new satellite products. These include GOES-16 and GOES-17 data, Multi-sat geostationary imagery composites (SBN Sept 2020 w/RPM v19), Blended polar sat TPW/Rain Rate (SBN March 2020 w/v18.5), West CONUS GOES-West Derived Motion Winds (DMWs) (SBN March 2020 w/v18.5), and GLM gridded products from CRH LDM. Note: The GOES-East Fog and Low Stratus Products w/RPM v19 do not require any new LDM updates, as the WMO header pattern is already in the baseline.
SECTION A Step 1 covers initial NOAAPort information. Go to Step 8 (GLM Products) if your site has already been receiving imagery and products from GOES-16 and GOES-17. A Note on GLM Products: Instructions for GLM (GOES-16 and GOES-17) are also included in steps 8-13 of this Section (SECTION A.). However, these steps are only needed if you're not already receiving the CONUS/PACUS GLM gridded products (e.g., Flash Extent Density).
August-September 2020 Version 19: Global, multi-satellite geostationary composite imagery IR, WV, VIS mosaics (GOES-16, GOES-17, Meteosat-8, Meteosat-11, and Himawari) will be added to the SBN on Sept 16, 2020. LDM configuration is needed to receive these products until AWIPS 21.3.1 is installed (later in CY 21). Scroll down to SECTION C for configuration steps for these products. A note on the new NESDIS Fog and Low Stratus products. FLS products will have IXTE99 KNES for the WMO header. The current baseline accounts for this satellite product entry, and no additional LDM configuration is required. Upon completing Section C, return to the TOWR-S RPM Installation Instructions.
MARCH 2020 (for v18.5 and v19): GOES-17 PACUS sector Derived Motion Winds (DMWs) and Global Blended Hydro polar satellite products (TPW, Rain Rain, Pct normal TPW) have been added to the the SBN: LDM configuration (new pqact entries) is/(are) needed (until AWIPS 20.2.1) to receive the global blended hydro (polar sat) and GOES-17 PACUS sector DMWs that are now activated over the SBN. Scroll down to SECTION B, under the heading entitled "SBN Global Blended Hydro (polar satellite products) and/or GOES-17 PACUS DMWs Activation". If you completed these steps this past Spring/Summer with the v18.5 update to receive the G-17 DMWs and/or new Blended Hydro, they do not need to be re-accomplished w/v19.
Upon completion of the below steps, continue with the TOWR RPM Installation Instructions.
To configure site CPs (cpsbn1/cpsbn2) to receive GOES-16/GOES-17 data, ensure the following:
1. Verify routing on both CPs with “route -n ”. Routes must include the following (order is not important):
224.0.1.10 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
224.0.1.9 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
224.0.1.8 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
224.0.1.3 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
224.0.1.2 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
224.0.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
224.0.1.7 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
224.0.1.6 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
224.0.1.5 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
224.0.1.4 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
2. If any routes are missing, add them to /etc/sysconfig/network-scripts/route-eth1 . To keep from having to restart the network service, add the routes manually with commands of the form:
route add 224.0.x.y eth1
where ‘x’ and ‘y’ are the last two digits of the Multicast IP address to be added.
3. Verify the DVB receivers on both CPSBN1 and CPSBN2 are configured to receive the two GOES-R channel PIDs and the EXP channel PID:
cmcs -ip 10.0.5.10 -pw AWIPS -shpid
which should produce a list like:
MPE PIDs being processed: 101 102 103 104 105
107 108 151
where:
107 = GOES-17 (West)
108 = GOES-16 (East)
If you run into any issues and need to turn off the flow of GOES-17 data, issue the following command for each CP (CPSBN1 and 2):
cmcs -ip 10.0.5.10 -pw AWIPS -del 107
4. If PIDs 107 or 108 are missing, add them with the command:
cmcs -ip 10.0.5.10 -pw AWIPS -add 107 108
5. NOTE -- To receive data on the EXP channel (e.g. the GOES-16 derived products), add PID 106 using the same command as in step 4.
7. Make sure all instances of noaaportIngester have the ‘-c’ flag (post-16.2.1 only). The number 4 after the -u option in each entry (above) is associated with the rsyslog facility used for product logging. When multiple instances of noaportIngester specify the same value, then product entries from the different channels are logged into the same log file. For instance, when GRE and GRW have the value -u 4, then all GOES-R products will be written to the same log file (goes_add.log), which is defined in /etc/rsyslog.d/cpawips.conf. While changing this from a different number that already may be present (e.g. from -u 7 to -u 4) is not required, it adds consistency if sites use "-u 4" since this number is used at several GOES-R channel processing sites.
8. If your site needs configuration for GLM products, continue at this step (Step 8) through Step 13. If your site needs configuration for the global blended hydro (polar sat) products (TPW, Rain Rate, Percent Normal TPW--as of March 2020) or GOES-17 PACUS sector derived motion winds (DMWs--as of March 2020), instructions are found, below, in SECTION B. If your site needs the new multi-satellite, global geostationary imagery composites (SBN in Sept 2020), skip to SECTION C.
Configure the LDAD LDM for GOES-16 and GOES-17 Geostationary Lightning Mapper (GLM) products
Geostationary Lightning Mapper Extended Evaluation sites. About 24 sites were originally part of an "extended evaluation" of additional GLM grid products. These sites received a different data feed that includes the Flash Extent Density (FED) (similar to all sites), but also Total Optical Energy (TOE) and Ave Flash Area (AFA) products. The list of sites receiving these products has grown considerably. If your site would like to receive the extra GLM fields, please contact Lee Byerle on the TOWR-S team (lee.byerle@noaa.gov). Beginning in version 20 of the towr-s RPM (late Fall 2020), all sites will receive a Full Disk FED, TOE, and Minimum Flash Area (MFA)--the latter will replace the Average Flash Area. The instructions for this update will be forthcoming, and will temporarily overlap the current CONUS/PACUS GOES sectors, whose configuration steps are described below.
Here is a somewhat dated list of sites pulling in a data feed which contains the additional GLM fields (AFA and TOE in addition to FED): AWCN, ABQ, BCQ, BOU, CAE, CHS, EHU, FFC, FWD, GID, HGX, HUN, ICT, ILN, ILX, JAX, LKN, LOT, LUB, LWX, MAF, MEG, MFL, MFR, MHX, MKX, MLB, MRX, OPGA, OUN, PHI, PQR, PUB, RAH, RLX, RNK, SHV, SLC, TAE, TSA, VHW, VUY, CLE, EAX, UNR, MQT, GRR, GRB, DMX, LSX, EWX, BOI, MSO, LOX, PDT, BYZ, SGX, GJT, KEY.
A note on the data feeds: There are distinct GLM products flowing over the CRH LDM. The steps below delineate them, but here is a description of what each feed pattern/filename contains (FED=Flash Extent Density, AFA=Average Flash Area, TOE=Total Optical Energy):
GOES-East:
a. IXTR99 KNES is GOES-East 1- and 5-minute FED
b. IXTR98 KNES is GOES-East 1- and 5-minute FED, AFA, TOE <--Note, the FED here is the same FED as in IXTR99
GOES-West:
c. IXTR89 KNES is GOES West 1- and 5-minute FED
d. IXTR88 KNES is GOES-West 1- and 5-minute FED, AFA, TOE <--Note, the FED here is the same FED as in IXTR89
As listed above, the same FED is contained in two different feeds for a given satellite. Therefore, it is important not to configure LDM to receive both GOES-East (a. and b.) (or GOES-West c. and d.) data feeds. It should be only one or the other for GOES-East (same for GOES-West), or you will receive duplicate messages in the edex satellite ingest logs. If you want FED, AFA, TOE for both GOES-16 and -17, then the pqact should be configured for b. and d., above. The steps below walk through this configuration in detail. In the AWIPS baseline pqact configuration, IXTR99 KNES is already present. However, if a site is bringing in the FED/TFA/TOE feeds (e.g. b. and/or d., above), then IXTR99 is not relevant (nor does it need to be removed from the pqact.conf... base file), because only the patterns for IXTR98 and IXTR88 are requested.
A) As user ldm on ls1, edit /usr/local/ldm/etc/ldmd.conf to add/update the following entry (previously, the instruction for this entry only applied to GOES-16. Below provides set-up for GOES-16 and GOES-17 GLM). All instances of <tab>should be replaced with literal TAB characters. The REQUEST and ALLOW entries in ldmd.conf are usually grouped together. For ease of maintenance, this is considered a best practice. NOTE: your-regional-LDM will be supplied by your respective regions. It may not be the same server from which you request other data.
su - ldm
REQUEST<tab>EXP<tab>^IXTR[89]9<tab>your-regional-LDM (GLM Extended Eval sites: use ^IXTR[89]8 instead of ^IXTR[89]9. The sites/IDs that are "GLM Extended Eval" are listed at the top of this page )
ALLOW<tab>ANY<tab>gw-xxx
Replace xxx above with your site's lowercase 3-letter ID.
B) Restart LDM. As user ldm…
ldmadmin stop && ldmadmin start
C) Copy the modified ldmd.conf to the inactive LDAD server (typically ls3) for failover purposes.
Note: No configuration of pqact.conf on LDAD is required. Now continue to step 9.
9. Configure the CPSBN LDM for GLM products
OB 17.3.1+ Site Note: The ldmd.conf file on CPSBN1 will likely be overwritten with any AWIPS install. Please make a backup copy of ldmd.conf to a safe location after adding the REQUEST line.
An AWIPS RC has been implemented at all sites to allow the CPSBN LDM to communicate directly with the LDAD LDM. The GLM ingest will take advantage of this capability.
A) As user ldm on cpsbn1, confirm the ability to connect to the LDAD LDM.
su - ldm
ldmping ls1-xxx (xxx is your lowercase 3-letter ID)
B) As ldm on cpsbn1 (or using appropriate idm user commands, see Section B for examples), edit ldmd.conf to enable request of the GLM grids from LDAD by updating/adding the IXTR* line for GLM (not that the instruction for this line update was previously for GOES-16 only; the below expression updates the entry for GOES-16 and GOES-17 GLM). All instances of <tab> should be replaced with literal TAB characters.
#GOES-16 and GOES-17 GLM
REQUEST<tab>EXP<tab>^IXTR[89]9<tab>ls1-xxx (GLM Extended Eval sites: use ^IXTR[89]8 instead of ^IXTR[89]9)
Replace xxx above with your site's lowercase 3-letter ID.
Note: IXTR[89]9 (above) (or ^IXTR[89]8 for GLM Extended Eval sites) will pull data for both G16 and G17. The IXTR9x files are from G16 and the IXTR8x products are from G17. If an office only wants/needs the data from one satellite, they can adjust the pattern accordingly (e.g. IXTR99 to pull ONLY the FED file from G16; or IXTR98 to pull the FED, TOE, AFA fields only from G16. The same TOWR-S RPM is used for either file types (see top of this page for the list of "GLM Extended evaluation" sites).
C) Copy the ldmd.conf file from CPSBN1 to CPSBN2 for failover.
Continue to step 10.
10. Steps to accomplish on dx1: If you are a GLM Extended evaluation site (the list of sites is at the top of this page), skip to step 10B (below).
A) (If you are a GLM Extended test site go to step B, otherwise accomplish this step, 10A): As root on dx1, edit /usr/local/ldm/etc/pqact.conf.xxx (where xxx is your site ID), and add the following entry:
#GOES-17 GLM
EXP<tab>^(IXTR89) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -close -edex -log<tab>/data_store/glm/(\3:yyyy)(\3:mm)\3/\4/GOES-17/\1_\2_\3\4\5_(seq).%Y%m%d%H%M
Note that there is a space after the closed parentheses above; i.e., after IXTR89) and before (KNES.. Additionally, there is a space after the (KNES) expression.
Note: the pattern for GOES-16 GLM (^(IXTR99) (KNES) etc) is in the base pqact, already in the GOES PDA products expression which includes ^(IXT[A-RU]99).
Note: To remove GOES-16 GLM (IXTR99..), and to only receive GOES-17 GLM, remove the letter R from the existing base pqact entry for GOES Derived products (see pqact.conf.base.conus or pqact.conf.base.pacific. Search for active "IXT" in this pattern: ^(IXT[A-RU]99). Remove the R so that it reads ^(IXT[A-U]99) ).
Now continue to step 10C.
B) GLM Extended test sites, only: As root on dx1, edit /usr/local/ldm/etc/pqact.conf.xxx (where xxx is your site ID), and add the following entry (if your site has previously evaluated GOES-16 GLM, the GOES-16 entry may exist already:
#GOES-16
EXP<tab>^(IXTR98) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -close -edex -log<tab>/data_store/glm/(\3:yyyy)(\3:mm)\3/\4/GOES-16/\1_\2_\3\4\5_(seq).%Y%m%d%H%M
#GOES-17
EXP<tab>^(IXTR88) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -close -edex -log<tab>/data_store/glm/(\3:yyyy)(\3:mm)\3/\4/GOES-17/\1_\2_\3\4\5_(seq).%Y%m%d%H%M
C) All sites: Run the "ldm" task as root on dx1 (XXX is your site's uppercase 3-letter ID):
cd /usr/local/ldm/etc
scp -p pqact.conf.xxx dx2:/usr/local/ldm/etc/
cd /data/fxa/sdc
/data/fxa/sdc/config_awips2.sh ldm XXX
Pqact file ref: https://www.unidata.ucar.edu/software/ldm/ldm-current/basics/pqact.conf.html
Can test with the command (running from the cp machine): ldmadmin pqactcheck
Note: Items above describe needed changes to the pqact.conf.template because otherwise by just adding them to your pqact.conf can cause duplicates, and will be problematic. Each time you do a software build, this template will be overwritten by a new baseline template. Your site needs to re-incorporate any changes into the new template every time, unfortunately. If you only save off a template that you made changes to, and just copy that one in, it's possible you will miss any new changes in the baseline.
11. On the CPSBN that is currently ingesting SBN data (CPSBN1 by default), restart LDM as ldm with the commands :
su ldm
ldmadmin stop && ldmadmin start
12. Verify reception of GOES-16/17 SBN data by tailing the LDM logs ( tail -F /data/ldm/logs/[gnop]*.log ). GOES-R products will be logged in /data/ldm/logs/goes_add.log along with GINI GOES and Data Delivery products. GLM data will appear in /data/ldm/logs/ldmd.log. GLM data flow verification steps (notifyme commands) can be found in the are included in the RPM Installation Guide, Section IV. GLM Troubleshooting. Additionally, join the NWS Chat group 'towr-s' for further guidance at https://nwschat.weather.gov. POC: Lee Byerle (nws-lee.byerle)
13. If your site hasn't removed the previous, then installed the latest TOWR-S RPM, then continue with the TOWR-S RPM Installation Instructions. GLM data will appear under the East CONUS and/or West CONUS submenus (the Center position menus will be empty and are used when a satellite is in the Center/Test position
at 89.5W).
SECTION B.
SBN Global Blended Hydro (polar satellite products) and/or GOES-West (GOES-17) PACUS Derived Motion Winds Activation (March 10, 2020)
Blended hydro (polar sat) products are now activated over the SBN on the NOAAPORT_OPT channel (PID 104), as described in this service change notice (SCN). In addition GOES-West (GOES-17) PACUS DMWs will are now activated on the GOES-West (GRW) channel (PID 107) (see this service change notice link).
An update to AWIPS and LDM configurations are required per the steps below. DCS 21477 is in work to add these updates to AWIPS 20.2.1.
This update provides menus and edex plugin configurations for AWIPS. Following these LDM/configuration prep steps, instructions in the VLab will walk through how to un-install the old, then install the latest TOWR-S RPM. After that RPM is installed, then the following new pattern for blended hydro products will appear in
/awips2/edex/data/utility/common_static/site/site_name/distribution/netcdfGrid.xml:
<regex>^TI[CT]X.*</regex>
Additionally, the following new pattern for GOES (16 and 17) DMWs will appear (after the TOWR-S RPM is installed) in:
/awips2/edex/data/utility/common_static/site/site_name/distribution/dmw.xml:
<regex>^IXTU.*</regex>
Return to the TOWR-S RPM Installation instructions after first going through the steps, below:
1. The following are steps to edit pqact.conf.xxx (where xxx is your lower-case site id), on DX1:
Log in to dx1 as ldm.
root@dx1# su - ldm
[ldm@dx1]$ cd /usr/local/ldm/etc
[ldm@dx1]$ vi pqact.conf.xxx
(if an IDM site:
sudo -u ldm vi /usr/local/ldm/etc/pqact.conf.xxx )
Open /usr/local/ldm/etc/pqact.conf.xxx as shown above with vi. Add the following expression replacing <tab> with the literal TAB keyboard function (a template file containing the blended polar sat entry and proper tabs can be found here at this link ):
# Global Blended Hydro (TPW, Rain Rate, PCT Normal TPW)
ANY <tab> ^(TI[CT]X..) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/polar/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
NOTE: The "ANY" line is one line and everything from <tab>FILE through the %d%H is on another line. Also note that two dots (..) appear after the letter X within parentheses, with no spaces between them. Ensure that the portion of the expression above has only one space before and one space after (KNES) . Also, there is one space after -overwrite, -log, -close, and -edex.
If your site also plans to receive the West Conus (PACUS) sector GOES-17 Derived Motion Winds (DMWs) product, then add the following pattern to /usr/local/ldm/etc/pqact.conf.xxx, in addition to the one above; otherwise, go to Step 2 (a template file containing the GOES-West DMW entry and proper tabs can be found here at this link ):
# GOES-17/West Derived motion winds from PDA
ANY <tab> ^(IXTU89) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/goes-r/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
NOTE: The "ANY" line is one line and everything from <tab>FILE through the %d%H is on another line. Also note that two dots (..) appear after the letter X within parentheses, with no spaces between them. Ensure that the portion of the expression above has only one space before and one space after (KNES) . Also, there is one space after -overwrite, -log, -close, and -edex.
Go to step 2.
2. Check the syntax of the pqact.conf.xxx file on CPSBN1.
As user ldm:
[ldm@dx1]$ cd /usr/local/ldm/etc
scp -p pqact.conf.xxx dx2:/usr/local/ldm/etc/
scp -p pqact.conf.xxx cpsbn1:/usr/local/ldm/etc/
( if an IDM site:
FROM /usr/local/ldm
sudo /bin/scp -p /usr/local/ldm/etc/pqact.conf.xxx dx2:/usr/local/ldm/etc/
sudo /bin/scp -p /usr/local/ldm/etc/pqact.conf.xxx cpsbn1:/usr/local/ldm/etc/
)
Even though the "config_awips2.sh ldm XXX" localization checks the syntax of the pqact.conf.xxx before it pushes it to the CPs, it is recommended to run the "ldmadmin pqactcheck -p etc/pqact.conf.xxx" command to verify the file/s are correct after any edits, first. Unfortunately the "ldmadmin" tool is not installed on dx1, so you must login to the CPs to do this and run it on a local copy of pqact.conf.xxx, there.
As root on cpsbn1, switch user to ldm:
root@cpsbn1# su - ldm
[ldm@cpsbn1]$ ldmadmin pqactcheck -p etc/pqact.conf.xxx
( if an IDM site:
FROM /usr/local/ldm
sudo -u ldm /usr/local/ldm/bin/ldmadmin pqactcheck -p etc/pqact.conf.xxx
)
3. Running the ldm task to create the pqact.conf: After the local pqact.conf.xxx file checks out, run the AWIPS LDM localization script as root on dx1.
root@dx1# cd /data/fxa/sdc
root@dx1# ./config_awips2.sh ldm XXX
(if an IDM site: sudo /data/fxa/sdc/config_awips2.sh ldm XXX )
Ensure no duplicates: Log back into cpsbn1 and as LDM to check for any duplicates for the new patterns in /usr/local/ldm/etc/pqact.conf (this file has been newly created in this step).
Duplicate check for GOES DMWs (if you added this pattern above): On cpsbn1, search your newly-created /usr/local/ldm/etc/pqact.conf file created as a result of Step 3, to ensure patterns for GOES-16 and -17 Derived Motion Winds appear in that file only once:
For the GOES-17 DMWs (IXTU89) and GOES-16 DMWs (IXTU99):
root@cpsbn1# su - ldm
ldm@cpsbn1# cd etc
ldm@cpsbn1# grep IX pqact.conf
(if an IDM site:
sudo -u ldm grep IX /usr/local/ldm/etc/pqact.conf.xxx )
This may return several lines for the IX pattern. The GOES-16 DMWs should be covered in the pattern ^(IXT[A-RU]99), and the GOES-17 DMWs should be covered in a new pattern ^(IXTU89), each with a sequence number (_(seq)) in the FILE dir path. Confirm the sequence number appears (_(seq), which is crucial for avoiding duplicate ingest errors to edex, and make sure no pattern will produce IXTU89 or IXTU99 more than once.
4. Restart LDM: The config_awips2 script restarts the CP's LDM processes, but it can be done manually as well. On the CPSBN that is currently ingesting SBN data (CPSBN1 by default), restart LDM as ldm with the commands:
root@cpsbn1# su - ldm
ldm@cpsbn1# ldmadmin stop && ldmadmin clean
ldm@cpsbn1# ldmadmin start
(if an IDM site:
sudo -i -u ldm ldmadmin stop
sudo -i -u ldm ldmadmin clean
Then:
sudo -i -u ldm ldmadmin start
As a validation that LDM is running smoothly, execute ldmadmin watch:
sudo -i -u ldm ldmadmin watch
)
Note: When running sudo for the ldmadmin command, it is important that IdM sites should use the -i flag (as shown above) to ensure new files from LDM are written with the proper permissions. LDM will then write all new files with group fxalpha write permissions, ensuring proper edex ingest and clean-up processes.
That's it, LDM is now configured for the G-17 DMWs and/or new global blended hydro products. Return to the TOWR-S RPM Installation instructions. For more information, contact Lee Byerle (lee.byerle@noaa.gov) or John Evans (john.d.evans@noaa.gov). You can also join the NWS Chatroom group ("towr-s") for questions or information.
SECTION C.
SBN Global Multi-satellite Geostationary Imagery Composites (activating on Sept 16, 2020)
New, near-global (70N-70S), multi-satellite geostationary composites will be activated over the SBN on the NOAAPORT_OPT channel (PID 104) on Sept 16, 2020. They will replace the legacy NH composites after about a 3 month overlap. If you are not interested in adding these products, or have already made the update, return to the TOWR-S RPM installation instructions.
An update to AWIPS and LDM configurations are required per the steps below. DCS 22108 is in work to add these updates to AWIPS 21.3.1.
Return to the TOWR-S RPM Installation instructions after first going through the steps, below:
C.1 The following are steps to edit pqact.conf.xxx (where xxx is your lower-case site id), on DX1:
Log in to dx1 as ldm.
root@dx1# su - ldm
[ldm@dx1]$ cd /usr/local/ldm/etc
[ldm@dx1]$ vi pqact.conf.xxx
(if an IDM site:
sudo -u ldm vi /usr/local/ldm/etc/pqact.conf.xxx )
Open /usr/local/ldm/etc/pqact.conf.xxx as shown above with vi. Add the following expression replacing <tab> with the literal TAB keyboard function:
# Global 5-Sat Geostationary Imagery Composites. GOES-16/17, Meteosat-8/11, Himawari
ANY <tab> ^(TICF0[28]|TICF14) (KNES) (..)(..)(..)
<tab>FILE<tab>-overwrite -log -close -edex /data_store/goes-r/(\3:yyyy)(\3:mm)\3/\4/\1_\2_\3\4\5_(seq).%Y%m%d%H
NOTE: The "ANY" line is one line and everything from <tab>FILE through the %d%H is on another line. Ensure that the portion of the expression above has only one space before and one space after (KNES) . Also, there is one space after -overwrite, -log, -close, and -edex.
Go to Step C. 2.
C.2. Check the syntax of the pqact.conf.xxx file on CPSBN1.
As user ldm:
[ldm@dx1]$ cd /usr/local/ldm/etc
scp -p pqact.conf.xxx dx2:/usr/local/ldm/etc/
scp -p pqact.conf.xxx cpsbn1:/usr/local/ldm/etc/
( if an IDM site:
FROM /usr/local/ldm
sudo /bin/scp -p /usr/local/ldm/etc/pqact.conf.xxx dx2:/usr/local/ldm/etc/
sudo /bin/scp -p /usr/local/ldm/etc/pqact.conf.xxx cpsbn1:/usr/local/ldm/etc/
)
Even though the "config_awips2.sh ldm XXX" localization checks the syntax of the pqact.conf.xxx before it pushes it to the CPs, it is recommended to run the "ldmadmin pqactcheck -p etc/pqact.conf.xxx" command to verify the file/s are correct after any edits, first. Unfortunately the "ldmadmin" tool is not installed on dx1, so you must login to the CPs to do this and run it on a local copy of pqact.conf.xxx, there.
As root on cpsbn1, switch user to ldm:
root@cpsbn1# su - ldm
[ldm@cpsbn1]$ ldmadmin pqactcheck -p etc/pqact.conf.xxx
( if an IDM site:
FROM /usr/local/ldm
sudo -u ldm /usr/local/ldm/bin/ldmadmin pqactcheck -p etc/pqact.conf.xxx
)
Go to step C.3
C.3. Running the ldm task to create the pqact.conf: After the local pqact.conf.xxx file checks out, run the AWIPS LDM localization script as root on dx1.
root@dx1# cd /data/fxa/sdc
root@dx1# ./config_awips2.sh ldm XXX
(if an IDM site: sudo /data/fxa/sdc/config_awips2.sh ldm XXX )
Go to step C.4
C.4. Restart LDM: The config_awips2 script restarts the CP's LDM processes, but it can be done manually as well. On the CPSBN that is currently ingesting SBN data (CPSBN1 by default), restart LDM as ldm with the commands:
root@cpsbn1# su - ldm
ldm@cpsbn1# ldmadmin stop && ldmadmin clean
ldm@cpsbn1# ldmadmin start
(if an IDM site:
sudo -i -u ldm ldmadmin stop
sudo -i -u ldm ldmadmin clean
Then:
sudo -i -u ldm ldmadmin start
As a validation that LDM is running smoothly, execute ldmadmin watch:
sudo -i -u ldm ldmadmin watch
)
Note: When running sudo for the ldmadmin command, it is important that IdM sites should use the -i flag (as shown above) to ensure new files from LDM are written with the proper permissions. LDM will then write all new files with group fxalpha write permissions, ensuring proper edex ingest and clean-up processes.
That's it, LDM is now configured for the new multi-satellite, geostationary imagery products. Return to the TOWR-S RPM Installation instructions. For more information, contact Lee Byerle (lee.byerle@noaa.gov) or John Evans (john.d.evans@noaa.gov). You can also join the NWS Chatroom group ("towr-s") for any specific questions or information.