20050607: Surface MD file is not generated in a RedHat Linux system (cont.)

>From: Eirh-Yu Hsie <address@hidden>
>Organization: CU/CIRES
>Keywords: 200506032148.j53LmYZu017997 McIDAS-XCD configuration
   
Hi Hsie,

re: The question now is who made the modifications I reference above (I suspect
that it was Owen Cooper, but I don't know for sure).  The next question
is if modifying the ISFC schema (file ~mcidas/linux/workdata/DCISFC) to
support 15000 stations and using the modified XCDDEC.BAT and ISFCDEC.CFG
files would result in XCD being able to correctly decode surface data.

>Thank you for your help. At one stage, Owen needed to geneater MD file 
>with more than 7000 columns.  We modified the following 3 files:
>
>(1) txt2md.pgm - change MAXCOL from 7000 to 15000
>(2) XCDDEC.BAT - change "BILDTEXT INIT SAOMETAR.RAP SAOMETAR.RAT 7000 4 
>C4 36 1 80 SAOMETAR X 48" from 7000 to 15000
>(3)ISFCDEC.CFG - change NCOLS from 7000 to 15000

Yes, this is what I found out after poking around.

>How these can mess up surface MD file decoding?

Apparently, the MD file schema in SCHEMA must match the settings in
ISFCDEC.CFG ** OR ** the setting in the BILDTEXT line of XCDDEC.BAT
must match the settings in SCHEMA.  I first discovered the change
to XCDDEC.BAT; changed it back; deleted SAOMETAR.RAP; and reran XCDDEC.BAT.
This did not result in the flile SAOMETAR.RAT being created, so decoding
would not proceed.  It was only after I modified ISFCDEC.CFG and stopped
and restarted DMSFC that decoding began.

So, I am not sure of exactly what can be changed to increase the
number of stations decoded.  My observations were:

- with both XCDDEC.BAT and ISFCDEC.CFG modified you were not decoding
  anything

- with XCDDEC.BAT changed back to its original state and SAOMETAR.RAP
  recreated from the BILDTEXT line, no decoding was occurring

- with XCDDEC.BAT and ISFCDEC.BAT changed back to their original states
  and SAOMETAR.RAP recreated from the BILDTEXT line decoding would proceed

Cheers,

Tom
--
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.