>From: "James D. Marco" <address@hidden> >Organization: Cornell >Keywords: 200102071732.f17HW4L24435 McIDAS-X batch Jdm, >Thanks, got the Topo stuff straightened out. Two different >batch.k files, I recompiled the one in McIDAS and restarted >the LDM...end of problem. Sounds good. >On RH 6.2 Linux > > OK. New/old problem: > The FOUS14 and other model data are not being generated. >Log entries seem OK. The decoders seem to be running as per normal, >one for each type of data. This occurred in July when I upgraded, soo >I am missing something. The Unidata McIDAS distribution is sent out with grid decoding turned off by default. The reason for this is that a LOT of sites simply don't have the disk space to decode the gridded data. The fact that your dmgrid.k is apparently running suggests a different problem, however. Your XCD_START.LOG file looks normal. A listing of process IDs says that grid decoding should proceed: >ldm 10745 10743 0 11:23 ? 00:00:00 startxcd.k >ldm 10787 10745 0 11:23 ? 00:00:00 startxcd.k >ldm 10788 10787 0 11:23 ? 00:00:03 DMSFC >ldm 10789 10787 0 11:23 ? 00:00:00 DMRAOB >ldm 10793 10787 0 11:23 ? 00:00:01 DMSYN >ldm 10794 10787 0 11:23 ? 00:00:01 DMMISC >ldm 10795 10787 1 11:23 ? 00:00:16 DMGRID >ldm 10827 10747 0 11:23 ? 00:00:00 /home/mcidas/bin/ingebin.k HRS >ldm 10835 10827 0 11:23 ? 00:00:01 /home/mcidas/bin/ingebin.k HRS >ldm 11242 10747 0 11:40 ? 00:00:00 /home/mcidas/bin/ingetext.k DDS >ldm 11243 10747 0 11:40 ? 00:00:00 /home/mcidas/bin/ingetext.k DDS >ldm 11258 11243 0 11:40 ? 00:00:00 /home/mcidas/bin/ingetext.k DDS >ldm 11259 11242 0 11:40 ? 00:00:00 /home/mcidas/bin/ingetext.k DDS But there is a problem on your system. There should only be one pair of ingetext.k processes (one is the parent of the other); you have two. The first thing we need to do is find out why you have two pairs. Can you supply all of the xcd_run related entries in your LDM pqact.conf file? >Sooo, it looks OK to me, so far. Yes, the grid setup looks OK. >I tracked the HRS.SPL file and it appears to be updating as expected. OK, this shows that the LDM has write permission in the directory into which GRID files will be created. What are the REDIRECTions for GRID* on this system: REDIRECT LIST >In the McIDAS session the DMGRID is reported active. Right. >No data available in the McIDAS sessions!??? Did you do a simple Unix 'ls' in the directory in which GRID files are supposed to be created? If no, it may be that the files are being created, but the users' sessions do not have REDIRECTions that point to the files if not going through the remote ADDE server. If users sessions do go through the remote ADDE server, it might be the case that the ADDE access to the files is incorrect. Was this working previously? >I'm not sure what needs to be fixed. Any thoughts? Not right off. I am willing to get on and poke around if you like. In order to test things out, I would need logins as 'mcidas', 'ldm', and one of the users that is seeing the problem. >Soundings/Skew-T/Hodographs: >Soundings/Hodographs do not work under RH 6.2. They appear to be available >under RH 7.0. Look real good. The difference here could be that the session you are running under RH 7 is accessing the RTPTSRC dataset as LOCAL-DATA, and the RH 6.2 sessions are going through a remote ADDE server setup (i.e., the DATALOC for RTPTSRC for those sessions are _not_ LOCAL-DATA). This would be consistent with what I have found in the UNCA, NIU, and Unidata installations. >For RH6.2 it appears to be a date related problem, perhaps a library problem. >In one case today (Feb 9, 2001), The Day offered under the selection menu, >normally written on the button face, was Feb, 10 2001! Now, this _is_ weird! >I had to test this anyway, so I thought I'd send the data along. I appreciate the input! Now I am even more eager to get on one of the systems so I can really see what is happening. Thanks in advance. 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.