This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Dave, re: > It was working. > One of the things that was the major contributer was the > ADDESITE.TXT file. There was a reference in there to HOST climate = > 10.11.3.65 which it was now 10.11.0.65. That was first problem I figured > out. OK, this makes sense. ADDESITE.TXT (and MCTABLE.TXT files) are used to "cache" dataset_group -> hostname <-> IP information. When IP addresses change for a host included in this(these) file(s), one needs to run DATALOC HOST to force a refresh of the name <-> IP information. re: > Why the change in the directories occured, I know paul ran some .BAT > files which I don't know if that copied default configs over to the other > configs like NEXRADDE.BAT and changed the /home/data/mcidas to become > /data/ldm/mcidas (default) may have done some reconfigurations. The BATCH files included in the McIDAS distribution do not have any actions to overwrite themselves/other BATCH files in the McIDAS distribution. One could include such changes in locally-created BATCH files and/or scripts, but that would have to be well thought out to do (i.e., it wouldn't be that easy). re: > Are there > any .BAT files that may have executed a "factory default" config? No, not by default, that is. re: > Would the best thing to FIX problems here be to re-run the mcxconfig script? That would be the straightforward approach especially if locations of things (e.g., McIDAS-XCD decoded files, etc.) changed. I _really_ don't have any theory how the REDIRECTion backing store file LWPATH could become damaged in the way that it was damaged. The problems I found were references to a directory '/home/data/m' instead of '/home/data/mcidas'. re: GUI not working/coming up This is definitely weird. Both the SSEC GUI and McIDAS MCGUI use the 'mcwish' executable created by the McIDAS build. The version of 'mcwish' that was created by the build on 'climate' appears to be viable: mcidas@climate:~/workdata$ ldd ../bin/mcwish linux-vdso.so.1 => (0x00007fffe8b9c000) libtk8.5.so => /home/mcidas/tcl/lib/libtk8.5.so (0x00007f1f60403000) libtcl8.5.so => /home/mcidas/tcl/lib/libtcl8.5.so (0x00007f1f600f8000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f1f5fdb3000) libgfortran.so.3 => /usr/lib/x86_64-linux-gnu/libgfortran.so.3 (0x00007f1f5fa9c000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1f5f7a0000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f1f5f589000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1f5f1ca000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f1f5efc6000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f1f5eda7000) libquadmath.so.0 => /usr/lib/x86_64-linux-gnu/libquadmath.so.0 (0x00007f1f5eb71000) /lib64/ld-linux-x86-64.so.2 (0x00007f1f60745000) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f1f5e96e000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f1f5e767000) I see no references to missing shared libraries, and it will look for the shared Tcl and Tk libraries in the correct installation location, /home/mcidas/tcl/lib. I will try to run the MCGUI when I get into work. Currently I am at home trying to dig out of the new 1' of snow that fell overnight... > -Dave > > > > > > ============================ > Dave Bukowski -- NREMT-B > BLS Instructor (CPR & AED) > N9KPD > http://davebb.deviantart.com/ > address@hidden > address@hidden > > > address@hidden> wrote: > > > Hi Paul, > > > > re: > > > 1) OK...I think we fixed a few things too...The radar was not working > > > because it searched for the wrong directory. I found that our copy of > > > NEXRADDE.BAT was pointing to the wrong directory. I copied that to > > > NEXRADDE.BAT.OLD and took the old copy from the old server over. Now the > > > data files are where they are supposed to be. > > > > The DSSERVE invocations in files like NEXRADDE.BAT do not become active > > until 'mcidas' makes them active through actions like: > > > > <as 'mcidas'> > > cd $MCDATA > > batch.k NEXRADDE.BAT > > > > Also, if you copied over a file from the old machine, did you put it > > in the MCDATA directory for the user 'mcidas'? This is where > > files that get locally modified should live, not in ~mcidas/data. > > > > re: > > > Does this batch file get > > > replaced with new versions? Should my modifications be named something > > else? > > > > Not in the $MCDATA directory of 'mcidas'. It does get replace by new > > installations/updates if it is in ~mcidas/data. > > > > re: > > > 2) What does XCD.BAT do? I have this > > > mcidas@climate:~/data$ less XCD.BAT > > > REDIRECT ADD *.PRO "#MCDATA > > > REDIRECT ADD *.PTR "#MCDATA > > > > > > REM > > > REM Define needed REDIRECTions > > > REM > > > > > > REDIRECT ADD HRS.SPL "#XCDDATA > > > REDIRECT ADD *.IDX "#XCDDATA > > > REDIRECT ADD *.IDT "#XCDDATA > > > REDIRECT ADD *.XCD "#XCDDATA > > > ... > > > > XCD.BAT sets up McIDAS-XCD processing. > > > > re: > > > when I ran the command by hand, there were no strings defined. On the old > > > servers, it was XCDDATA =: /home/mcidas/data > > > I tried to enter the strings by hand using te.k but it would not let me > > use > > > more than 12 characters. > > > > The invocation from the Linux command line would be: > > > > <as 'mcidas'> > > cd $MCDATA > > te.k XCDDATA \"/home/data/mcidas > > > > re: > > > I was not sure what to do. > > > > I thought that decoding was working correctly on the new climate. > > Are you saying that it wasn't? > > > > re: > > > 3) When I run "mcidasx" I get two windows but do not get the menu. I get > > > > > > Error in startup script: couldn't read file "./tcl/lib/tk8.5/xmfbox.tcl": > > > no such file found.. > > > > > > That is weird. > > > > The error message is, indeed, weird. The Tcl/Tk widgets, etc. should > > get installed in ~mcidas/tcl/... > > > > re: > > > This is what I have so far. > > > > OK. > > > > Dave wrote: > > > > > Paul, as I mentioned on the phone I just installed tcl8.5 and tk8.5. Now > > > if there is a MCIDAS binary that needs to be recompiled then I need to > > know > > > what we are recompiling so I can add it to weather > > > > Tcl/Tk is included as part of the McIDAS distribution. The versions > > of tclsh and mcwish (a McIDAS-modified version of 'wish') get created > > as part of the McIDAS build process. Installations of Tcl/Tk in the > > OS are not needed as they should not be used by the McIDAS GUI/MCGUI > > if the user's environment is setup correctly, and if the McIDAS build > > succeeded with no errors. > > > > Comment: > > > > With three people making modifications, it is hard to know what works > > and what doesn't because of the rapidly moving target that is > > trying to be addressed. > > > > 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: OJB-462098 > > Department: Support ldm-mcidas > > Priority: Normal > > Status: Open > > > > > > 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: OJB-462098 Department: Support ldm-mcidas Priority: Normal Status: Closed