[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[McIDAS #QLY-545896]: TXT2MD
- Subject: [McIDAS #QLY-545896]: TXT2MD
- Date: Tue, 26 Jul 2016 20:24:40 -0600
Hi Kwan,
re:
> I need to get back to you on TXT2MD again because it seems like upctxt2md
> is not decoding every line in my text file (metar2.txt attached). First, I
> tested using txt2md.
>
> txt2md.k metar2.txt 1000 ISFC MISS=-9999
>
> Now, when I listed the data for VHHH, I got
>
> ID DAY[CYD] HMS[HMS] T[C] PSL[MB]
> ---- --------- --------- --------- ---------
> VHHH 2013314 113000 23.99 1012.88
> VHHH 2013314 120000 23.99 1012.88
> VHHH 2013314 124000 24.99 1012.88
> VHHH 2013314 130000 23.99 1012.88
> VHHH 2013314 134000 23.99 1012.88
> VHHH 2013314 140000 23.99 1012.88
> VHHH 2013314 144000 23.99 1012.88
> VHHH 2013314 150000 23.99 1012.88
> VHHH 2013314 154000 23.99 1012.88
> VHHH 2013314 160000 25.99 1013.89
> VHHH 2013314 164000 25.99 1013.89
> VHHH 2013314 170000 25.99 1013.89
> VHHH 2013314 174000 25.99 1012.88
> VHHH 2013314 180000 25.99 1012.88
> VHHH 2013314 184000 25.99 1012.88
> VHHH 2013314 190000 25.99 1012.88
> VHHH 2013314 194000 25.99 1012.88
> VHHH 2013314 200000 24.99 1012.88
> VHHH 2013314 204000 24.99 1012.88
> VHHH 2013314 210000 24.99 1012.88
> VHHH 2013314 214000 24.99 1012.88
> VHHH 2013314 220000 24.99 1012.88
> VHHH 2013314 224000 24.99 1012.88
> VHHH 2013314 230000 24.99 1013.89
> VHHH 2013314 234000 24.99 1013.89
> *VHHH 2013314 0 24.99 1013.89
> VHHH 2013314 4000 25.99 1014.91
> VHHH 2013314 10000 25.99 1014.91
> VHHH 2013314 14000 25.99 1014.91
> VHHH 2013314 20000 25.99 1014.91
> VHHH 2013314 24000 25.99 1014.91
> VHHH 2013314 30000 25.99 1014.91
> VHHH 2013314 34000 25.99 1013.89
> VHHH 2013314 40000 25.99 1013.89
> VHHH 2013314 44000 25.99 1012.88
> VHHH 2013314 50000 24.99 1011.86
> VHHH 2013314 54000 25.99 1011.86
> VHHH 2013314 60000 26.99 1010.85
> VHHH 2013314 64000 25.99 1010.85
> VHHH 2013314 70000 24.99 1010.85
> VHHH 2013314 74000 25.99 1010.85
> VHHH 2013314 80000 24.99 1010.85
> VHHH 2013314 84000 24.99 1010.85
> VHHH 2013314 90000 24.99 1010.85
> VHHH 2013314 93000 24.99 1011.86
> VHHH 2013314 100000 24.99 1011.86
> VHHH 2013314 104000 24.99 1011.86
> VHHH 2013314 110000 24.99 1012.88
> VHHH 2013314 114000 24.99 1012.88
> Number of matches found = 49
> ptlist.k: Done
>
> which confirms the bug that you indicted before (the date did not advance
> to 2013315 at 00Z as it should (the line marked with a * and below).
>
> Now when I tried using upctxt2md, I got only two line.
>
> mdu.k DEL 1000
> upctxt2md.k metar2.txt 1000 ISFC MISS=-9999
> ptlist.k MYDATA/PTSRCS.1000 FORM=DATA PAR=ID DAY HMS T[C] PSL SEL='ID VHHH'
> NUM=ALL
>
> ID DAY[CYD] HMS[HMS] T[C] PSL[MB]
> ---- --------- --------- --------- ---------
> VHHH 2013314 234000 24.99 1013.89
> VHHH 2013315 114000 24.99 1012.88
> Number of matches found = 2
> ptlist.k: Done
>
> I have absolutely no idea why only these two lines were decoded.
I think that your problem would go away if you separated the two days
of observations into separate source files. Files with days/times
that increment for individual stations seems to be beyond the
capability of both txt2md.k and upctx2md.k. It seems to me that
a simple shell script could be written to easily separate the obs for
different days into different in put files.
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: QLY-545896
Department: Support McIDAS
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.
