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.
Thanks for the update. We will address your additional open issues on github as well in time. > Thanks for doing that. We've had success on our primary installation and > are proceeding with secondary/ingest installations which include MRMS since > we had to split that off. We did implement a change for MRMS data that now concatenates the files per minute and then a cronjob runs looking for products that haven't updated within a minute or two and then push them to EDEX. This reduces the number of files going through the qpid queue which was previously causing a bottleneck. I also updated the grid properties in /awips2/edex/etc/ingestGrib.sh > A cursory look-through leads us to believe that GOES-17 Mesoscale sectors > don't work correctly when coming from NOAAPort. This has happened in the > EDEX 18.2.1-x installations and I believe I've brought this up before but > I'll make a PR this time. Are there specific products for GOES-17 Mesoscale sectors that aren't displaying in CAVE? I don't believe we have run into this issue at all. Thanks, Tiffany Meyer AWIPS Lead Software Engineer UCAR-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: SGX-641557 Department: Support AWIPS Priority: Normal Status: Open =================== NOTE: All email exchanges with 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.