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.
Kirk, > My environment is RedHat Linux 3. > [ldm@gpsldm /]# uname -a > Linux gpsldm.fsl.noaa.gov 2.4.21-53.EL #1 Wed Nov 14 04:02:23 EST 2007 > i686 i686 i386 GNU/Linux > > The expressions work as expected: > > [ldm@gpsldm /]# /home/ldm/ldm-6.3.0/bin/regex -s > 'SA39_UNKNOWN_SA39_1472-5-43200.BNX' > '^(S[A-Z][0-9][0-9]\_[0-9][0-9][0-9][0-9][0-9]\_S[A-Z][0-9][0-9]\_[0-9][0-9][0-9][0-9]-[0-9]-[0-9][0-9][0-9][0-9][0-9])(\.BNX)' > no match > [ldm@gpsldm /]# /home/ldm/ldm-6.3.0/bin/regex -s > 'SC04_17314_SC04_1471-4.BNX' > '^(S[A-Z][0-9][0-9]\_[0-9][0-9][0-9][0-9][0-9]\_S[A-Z][0-9][0-9]\_[0-9][0-9][0-9][0-9]-[0-9]-[0-9][0-9][0-9][0-9][0-9])(\.BNX)' > no match > > After a bit more study I realized that these unexpected file names > appear in ldmd.log, but the files are not written to disk. This is what > I want to happen. So, the pattern match is working. > > Therefore, my immediate problem is solved. But, I am still curious as > to why these unexpected file names appear in the log. What, exactly, are the log messages in which those products appear? > Thanks for your help. > > --Kirk > > ***************************************** > * Kirk L. Holub * > * NOAA Earth System Research Laboratory * > * 325 Broadway * > * Bldg 33/2B143/x6642 * > * Boulder, CO 80305-3328 * > * * > * Global Systems Division * > * Forecast Applications Branch * > * * > * 303-497-6642 (W) 303-748-7262 (FAX) * > * 303-748-6390 (Cell) * > ***************************************** Regards, Steve Emmerson Ticket Details =================== Ticket ID: OIF-246882 Department: Support LDM Priority: Normal Status: On Hold