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 Dave, So, I've been on twister for quite awhile this afternoon, and I am sorry to say that I have not been able to figure out what the problem with running PIPE actions is :-( I do have some observations that I want to get down "on paper" before I forget them: - I rebuilt LDM-6.13.4 from source just to make sure that there were no weird things during the build This didn't help. - I dropped back to using the old LDM installation, LDM-6.12.6, and this also did not result in PIPE actions working (!?) - I noted that the PATH in scope for 'ldm' had GEMPAK directories before system ones, and this resulted in the GEMPAK 'ps' command being used instead of the system /bin/ps when doing things like 'ps -u ldm' I changed the order of the 'path' definition in your ~ldm/.login file. - I noted that you are defining LD_LIBRARY_PATH in ~ldm/.login and that you put the /usr/local/miniconda/lib first Since I think that this is a bad idea, I redefined LD_LIBRARY_PATH in ~ldm/.login and put /usr/local/miniconda/lib last. I also removed the non-existent /usr/lib/64 part of the definition. - I tried changing a number of things in the 'dcmetr' action in ~ldm/etc/pqact.gempak, but nothing I tried got things working - by poking around, I found that the CONDUIT STUDIOFILE action in ~ldm/etc/pqact.conf is (or, at least, seems to be) working correctly - I noted that GEMPAK decoding seems to have stopped back in mid-June Does this jibe with your view of things? I wrote up a note to bring Steve Emmerson up to date on what I found on twister and asked him to login to take a look. Sorry that I couldn't figure this one out! Hopefully, Steve will be able to figure out what is going on!! 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: FPM-496740 Department: Support LDM 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.