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

20051128: some AREA file not being updated (cont.)



>From: Myron Kowalski <address@hidden>
>Organization: Moravian
>Keywords: 200511281523.jASFNF7s008982 ldm-mcidas McIDAS

Hi Myron,

>Since I sent the e-mail, I've dug around and found that the LWPATH.NAM
>file had the wrong storage bin listed. I change where the files go a
>year ago from /app/data to /mcidasdata/mcidas. I thought I caught all
>the conf files. So far, 17 of the 137 files have updated thenselves.

OK.  During the change, you would have had to copy/move the McIDAS
files ROUTE.SYS and SYSKEY.TAB from the old location to the new and
make sure that they are readable and writable by the user running your
LDM.  If you did not do this and later remembered that you should have
AND copied the versions from the McIDAS directories (SYSKEY.TAB in
~mcidas/data and ROUTE.SYS in ~mcidas/workdata), you would end up
turning off filing/creation of certain image products.  This coupled
with copying the old AREA files to the new output directory could be
the reason that you see some AREA files being updated and others not
being updated.

>I've upgraded ldm a year ago, but mcidas is old.

OK.

>Unfortunately, I need
>mcidas to work for a class tomorrow. But, I don't need the new version
>yet, just an updated data files. Any way to get the files faster?

If I knew what images were not being updated, I could better answer
this.

>You need to be on catwoman to make any changes to /mcidasdata/mcidas. To
>get to catwoman you need to go through batboat.cs.moravian.edu

OK.

>Which e-mail is your private account?

address@hidden

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.