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, Interesting, sorry you're having problems. What happens if you try to run: /awips2/ldm/etc/goes-restitch.py -h as the ldm user? Ryan > Hi Ryan, > > > I recently came across your python module to stitch GOES-16/17 tiles > together. > > > Since it requires Python 3.6, I opted to use Anaconda3 for a closed > environment and included the shebang for this env at the top of the > goes-restitching.py file. > > > I am running into a permission issue when using the ldm with the scrip > below. I am a bit lost since the python script has the same ownership and > mods as the LDM. Any ideas? > > > Mar 6 11:08:09 localhost journal: pqact[18303] ERROR: Child 18414 exited > with status 1 > Mar 6 11:08:09 localhost journal: pqact[18415] ERROR: Permission denied > Mar 6 11:08:09 localhost journal: pqact[18415] ERROR: [filel.c:1552] > Couldn't execute decoder "/awips2/ldm/etc/goes-restitch.py" > Mar 6 11:08:09 localhost journal: pqact[18415] NOTE: Exiting > Mar 6 11:08:09 localhost journal: pqact[18415] NOTE: Deleting shared > segment. > Mar 6 11:08:09 localhost journal: pqact[18303] ERROR: pbuf_flush(): fd=6: > Broken pipe > Mar 6 11:08:09 localhost journal: pqact[18303] ERROR: Deleting failed PIPE > entry: pid=18415, cmd="-metadata /awips2/ldm/etc/goes-restitch.py -v -d > /awips2/data_store/goes16 -t 120 -l /home/awips/Desktop/TIRW04.log TIRW04 > KNES" Ticket Details =================== Ticket ID: VUP-539476 Department: Support Python Priority: Low 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.