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

20001026: McIDAS SCHEMA regristration; use of TXT2MD (cont.)



>From:  Xu Li <address@hidden>
>Organization:  UMD
>Keywords:  200010262140.e9QLe8411152 McIDAS SCHE LSCHE TXT2MD

Xu,

Sorry I couldn't get to this sooner, but I am putting on a McIDAS workshop
at the moment.  Also, you are likely to get much faster response to
questions when you send your email to Unidata User Support
(address@hidden).  There is more than one person reading the
Support mail box, so questions get answered faster.

>Thanks a lot for your reply to my question on schema registration. It
>helps a lot.

You are welcome.

>Now, the schema registration seems OK from the following:
>============================
>lsche.k CTYP
>
>NAME: CTYP  VERSION:  2  DATE: 2000300  TEXTID: "CLOUD MASK AND TYPE
>----        -------
>   DEFAULT NUMBER OF ROWS:   72                        INTEGER ID: 0
>                     COLS: 3600                   MISSING DATA VALUE:
>-2139062144
>   REPEAT GROUP:  NUMBER OF REPETITIONS:   1
>                      STARTING POSITION:   6
>                                   SIZE:   8
>   NUMBER OF KEYS IN ROW HEADER:     2
>                     COL HEADER:     3   STARTING AT POSITION   3
>                    DATA RECORD:     8   STARTING AT POSITION   6
>                                  ----
>                                    13 TOTAL
>
>        KEY  SCALE UNIT     KEY  SCALE UNIT     KEY  SCALE UNIT
>        ---- ----- ----     ---- ----- ----     ---- ----- ----
>        DATE   0            TIME   0            ALON   0
>        ALAT   0            IDN    0            SFTP   0
>        RD01   0            RD02   0            RD03   0
>        RD04   0            RD05   0            MASK   0
>        TYPE   0
>lsche.k: DONE
>=========================

This looks good.

>What I did is to copy the file SCHEMA from the directory
>(/usr/mcidas/data for my case)
>where the McIDAS was installed to my ~mcidas/data directory.
>
>Is this resonable?

Yes, this is totally reasonable.  Your McIDAS-X sessions should use this
copy of SCHEMA instead of the one in the ~mcidas/data directory if your
Unix MCPATH environment variable has been set so that your mcidas/data
directory comes before /usr/mcidas/data.

>But when I tried to convert a text file to MD file, it failed like this:
>
>(I have added the MD data set by DSSERVE ADD ....)
>=============================
>
>txt2md.k txt.dat 100 CTYP
> TXT2MD -- BEGIN
>txt2md.k: OVERSIZE ROW WITH NC= 6000
>txt2md.k: MAXIMUM ALLOWABLE IS  3500
>================================

This must have come after running for awhile.  Your schema list above
shows that you set the maximum number of rows to be 3600.  I believe
that there may still be a 3500 column limit in McIDAS MD files, but
I will have to check.  The error message you sent appears to say that
your text data file had enough entry for 6000 rows.  Is this true?

>My schema CTYP:
>
>=====================
>"CTYP (JSP) 0001 SCHEMA -- Cloud Screening SCHEMA
>"        NAME VSN DATE  ID "TEXTID
>"        ---- --- ----- -- -------
>  SCHEMA CTYP  2 00300 0 "CLOUD MASK AND TYPE
>
>  ROWS 72             "Number of ROWS
>
>  DATE                "YEAR AND JULIAN DAY (CCYYDDD)
>  TIME                "NOMINAL TIME (HH0000)
>
> COLUMNS 3600         "Maximum number of COLUMNS
>
>  ALON                    "RANGE (-180 => +180) POSITIVE WEST
>  ALAT                    "RANGE (-90 => +90) POSITIVE NORTH
>  IDN                     "Satellite ID
>
>  DATA
>
>  SFTP                    "Surface type (0=sea, 1=land)
>  RD01                    " CH-1 reflectance
>  RD02                    " CH-2 3.9 um Brightness temperature
>  RD03                    " CH-3 6.7 um Brightness temperature
>  RD04                    " CH-4 10.7 um Brightness temperature
>  RD05                    " CH-5 12.0 um Brightness temperature
>  MASK                    " Cloud MASK (0,1,2,3,4)
>  TYPE                    " Cloud TYPE (0,1,2,3,4,5)
>ENDSCHEMA
>
>=================

This matches the LSCHE listing you included above.

>The beginning of txt.dat file:
>
>=================
>   DATE   TIME    ALON    ALAT IDN SFTP RD01 RD02 RD03 RD04 RD05 MASK TYPE
>1996093 151514  148.03   54.31 8 0   3.30 250.20 226.40 248.60 247.30 1 1
>1996093 151514  140.56   53.37 8 0   6.20 258.90 227.80 249.40 248.90 1 1
>1996093 151514  136.91   52.93 8 0   5.60 266.80 229.60 263.40 260.20 4 2
>1996093 151514  134.11   52.59 8 0   5.40 270.60 231.50 267.20 264.00 3 5
>1996093 151514  131.76   52.32 8 0   8.70 272.00 231.80 266.00 263.50 0 0
>1996093 151514  129.70   52.08 8 0  12.80 266.00 232.60 256.50 256.10 3 2
>1996093 151514  127.84   51.87 8 1  13.30 265.10 233.70 254.20 253.00 3 3
>1996093 151514  126.13   51.69 8 1  11.90 262.70 234.80 248.20 246.70 3 5
>1996093 151514  124.54   51.52 8 1  14.70 267.20 235.10 258.50 258.40 1 1
>1996093 151514  123.05   51.36 8 1   6.20 267.20 232.90 265.40 264.90 0 0
>1996093 151514   69.51   24.97 8 0   5.20 293.70   0.00 287.30 283.30 4 5
>
>=========================
>
>What's the problem?

How many lines are there in your data file?

>BTW, McIDAS was installed on my workstation. I am using it as a user
>(mcuser) on my DEC workstation.

OK.

>Thanks!
>
>Looking forward to hearing from you?

Again, sorry to have taken so long to reply.  Preparations for the workshop
totally consumed me as we were fighting hardware problems right up until
Sunday night at 9 pm.

Tom
--
+-----------------------------------------------------------------------------+
* Tom Yoksas                                             UCAR Unidata Program *
* (303) 497-8642 (last resort)                                  P.O. Box 3000 *
* address@hidden                                   Boulder, CO 80307 *
* Unidata WWW Service                             http://www.unidata.ucar.edu/*
+-----------------------------------------------------------------------------+


pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy