[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20010810: what to do when two acars files come in with the same file name

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.

  • Subject: 20010810: what to do when two acars files come in with the same file name
  • Date: Fri, 10 Aug 2001 16:38:02 -0600
>From: Celia Chen <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200108102057.f7AKvv106520

>Dear Support,
>
>I just noticed that when two ACARS files with the same file name (they use
>time for file name) come in, LDM files them into one file. How can I
>file them into separate files ? - They come from different aircraft.
>
>It looks like the data are not being decoded properly when that happens.  
>How can I decode both files when they come in with the same file name?
>
>Thanks in advance.
>
>Celia
>
>


Celia,

I have not seen files with same names/different data, such as below:

Aug 10 22:29:37 notifyme[8811]: NOTIFYME(motherlode): OK
Aug 10 22:29:37 notifyme[8811]:   542460 20010810200032.359    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222000.*
Aug 10 22:29:38 notifyme[8811]:   527044 20010810201043.505    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222010.*
Aug 10 22:29:39 notifyme[8811]:   533112 20010810202024.976    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222020.*
Aug 10 22:29:40 notifyme[8811]:   528028 20010810203047.409    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222030.*
Aug 10 22:29:40 notifyme[8811]:   502280 20010810204030.116    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222040.*
Aug 10 22:29:43 notifyme[8811]:   521960 20010810210027.504    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222100.*
Aug 10 22:29:43 notifyme[8811]:   523436 20010810211032.365    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222110.*
Aug 10 22:29:44 notifyme[8811]:   520484 20010810212028.065    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222120.*
Aug 10 22:29:44 notifyme[8811]:   498672 20010810213034.139    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222130.*
Aug 10 22:29:45 notifyme[8811]:   481944 20010810214041.468    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222140.*
Aug 10 22:29:46 notifyme[8811]:   472104 20010810215042.810    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222150.*
Aug 10 22:29:47 notifyme[8811]:   514416 20010810220045.487    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222200.*
Aug 10 22:29:47 notifyme[8811]:   514088 20010810221042.672    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222210.*
Aug 10 22:29:48 notifyme[8811]:   522616 20010810222032.385    PCWS 000  
FSL.NetCDF.ACARS.QC.20012222220.*

If you can provide an example, I might be able to better unerstand your problem.

If you have to file 2 files with the same name, perhaps you can use the time 
templates
within pqact.conf to generate a unique file name based on system time, eg append
the FSL file name with: _%Y%m%d%H%M.%S.

Then, down to 1000th of a second, you should have unique file names.


Steve Chiswell
Unidata User Support