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.
Hi Gerry, re: > More to the point, it's not writing anything in the subdir where I *think* > l2assemble.py is trying to write to. Nothing in there. > > Tabs are in the correct positions; I've rechecked it. Here's my entry: > ### > ### NEW NEXRAD2 processing... We'll move it to its rightful place after > testing > ### > NEXRAD2 > ^L2-BZIP2/(....)/([0-9][0-9][0-9][0-9][0-1][0-9][0-3][0-9])([0-2][0-9][0-5][0-9][0-9][0-9])/([0-9]*)/[0-9]*/(S|I|E) > PIPE -metadata /usr/local/ldm/scripts/l2assemble.py -g -t 960 > /work/LDM/radar/level2 -f raw --threads 20 > ### > > The File Model data messages are writing out OK, as near as I can tell. Hmm... It may well be the case that l2assemble.py needs to find ldm.py but that ldm-alchemy file has not been copied to the same directory in which you put l2assemble.py. I suggest this because this is what I ran into when trying to run goes-restitch.py (which I modified) on a clean installation. I believe that you can check to see if a missing ldm.py file is the cause by trying to invoke l2assemble.py by hand. Please let me know if this helps! Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: CIX-410192 Department: Support IDD Priority: Normal Status: Closed =================== 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.