This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
> The cron did get installed, but did not load until cron was restarted. Not > usually needed. > Only remaining issue is the GLM files not plotting (OR_GLM_L2*) that are > produced by cspp-geo, or available on the IDD. > There are those GribModel* entires showing in the product browser that could > be configured. > > A quick note after installing this for Gary, this version overall looks > really good! Great job. > The GLM did plot before with the old versions. I see the awips2-glmdecoder is > not there. > The only change I made were to the /awips2/edex/conf/resources to increase > the threads on the satellite and grids. He actually has a 40 core server. > HTOP shows its hardly touching any resources even in standalone mode. > Hello, I briefly looked into a couple of the GribModel entries, they seem to be some of the HiRes-ARW, GFS-LAMP, and some SPCGuidance probs. Do you have your previous version of your pqact.conf that you were using? Please note, that the NSF Unidata AWIPS that we provide is not a one-to-one with the NWS version. There are some major differences between the two. One of those big differences is how we re-distribute and ingest the GOES data over our IDD/LDM to our users and therefore how our pqact's are set-up for that information. For the single channel ABI products, we receive these individual GOES tiles data via NOAAPort, then run a process here locally that combines all of those tiles into one single product, and that's what we distribute to our users and what our default entry in pqact.conf.priority is: #/data/ldm/pub/native/satellite/GOES/GOES16/Products/CloudAndMoistureImagery/Mesoscale-2/Channel03/20210528/OR_ABI-L2-CMIPM2-M6C03_G16_s20211481451520_e20211481451520_c20211481451520.nc # GOES 16/17 Single Channel (ABI) via Unidata IDD -(using) NIMAGE ^/data/ldm/pub/native/satellite/GOES/([^/]*)/Products/CloudAndMoistureImagery/([^/]*)/([^/]*)/([0-9]{8})/([^/]*)(c[0-9]{7})(..)(.....).nc FILE -close -edex /awips2/data_store/GOES/\4/\7/CMI-IDD/\5\6\7\8.nc4 Additionally, we receive the gridded GLM product tiles via ISatSS (from the NWS), again process them locally to combine all of the tiles into a single product, and distribute that. The associated entry in the pqact.conf.priority is: #GOES GLM Stitched gridded products via ISatSS (using) SPARE|NIMAGE ^/data/ldm/pub/native/satellite/GOES/([^/]*)/Products/GLMISatSS/Level[23]/([^/]*)/([0-9]{8})/(OR_GLM-L[23]-GLMF-M6_G(..)_s(.......)(..).*) FILE -close -edex /awips2/data_store/GOES/\3/\7/GLMISatSS-Stitched/\4 Since you are not receiving data via our IDD, but directly from NOAAPort you can comment out those entries, and uncomment the following line in your pqact.conf.priority which will allow you to ingest the single channel data and 1-min gridded GLM that is now on the SBN: # GOES 16/17 Single Channel (ABI) via NOAAPort/SBN - (not using) #NOTHER ^(TI[RSU]...) (KNES) (..)(..)(..) (...) # FILE -close -edex /awips2/data_store/GOES/(\3:yyyy)(\3:mm)\3/\4/CMI-SBN/\1_\2_\3\4\5_\6_(seq) Note: the 5-min gridded GLM products are still not the SBN. Eventually there will be code (from the NWS/TOWR-S group) that will run locally to create these products. We have removed the SPORT glm-decoder since the gridded GLM data has been baselined into the GOES ingesters. Thanks, Tiffany Meyer AWIPS Lead Software Engineer NSF Unidata If you're interested, please feel free to fill out a survey about the support you receive: https://docs.google.com/forms/d/e/1FAIpQLSeDIkdk8qUMgq8ZdM4jhP-ubJPUOr-mJMQgxInwoAWoV5QcOw/viewform Ticket Details =================== Ticket ID: PYP-441804 Department: Support AWIPS Priority: Normal Status: Open =================== NOTE: All email exchanges with NSF Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.