NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Greg, First, did you download the pre-release Unidata McIDAS-X/-XCD distribution (mcidasx2017.tar.gz) from our anonymous FTP server? If yes, I will remove it. re: > I'm having trouble getting any output out of the glmlist command. > Here's several things I've tried: > > [gstoss@typhoon]: glmlist.k > PTLIST: Failed to generate file mask list > /h/eol/gstoss/mcidas/data > [gstoss@typhoon]: glmlist.k DAT=ALL > ^C/h/eol/gstoss/mcidas/data > [gstoss@typhoon]: glmlist.k DAT=ALL DAY=IMA > glmlist.k: No Day/Time for image frame = 1 > /h/eol/gstoss/mcidas/data > [gstoss@typhoon]: glmlist.k CO DAT=ALL > ^C/h/eol/gstoss/mcidas/data > [gstoss@typhoon]: glmlist.k CO DAT=ALL TYPE=GROUP > ^C/h/eol/gstoss/mcidas/data > [gstoss@typhoon]: glmlist.k CO DAT=ALL TYPE=GROUP TIME=0 1 > > All the Ctrl-Cs are me killing the process after several minutes with no > response. Can you give me any advice on what I'm doing wrong? I'll try, but I have to admit that I have little to no experience with the GLM data. Since I need to rectify this situation, I will try and figure things out as we go along... re: > I've copied > the GLM.CORE file to my personal ~/mcidas/data/GLM.USER and have changed > the group and descriptors to point to what you set up. Can I assume that you: - replaced all occurrences of EAST with RTGOESR? - replaced all occurrences of GLM-EVENT, GLM-GROUP and GLM-FLASH with GLMEVENT, GLMGROUP and GLMFLASH, respectively? Results of my tests: I copied GLM.CORE to $MCDATA/GLM.USER in my 'mcidas' environment, and pointed at RTGOESR on atm.ucar.edu and then ran GLMLIST with good results: DATALOC ADD RTGOESR atm.ucar.edu GLMLIST DEV=TNN GLMLIST.OUT less $MCDATA/GLMLIST.OUT DAY TIME LAT[DEG] LON[DEG] IDN ENGY AREA FLSH --------- --------- --------- --------- ------------ --------- --------- --------- 2018205 185220 53.1113 86.4613 588365120 28 183 11588 2018205 185220 53.1336 86.4680 588365120 32 183 11588 2018205 185220 53.1231 86.4649 588365120 28 183 11588 2018205 185220 53.1377 86.4691 588365120 28 183 11588 2018205 185220 53.1928 86.4857 588365120 6 92 11588 2018205 185220 34.8846 111.1743 588365120 3 71 11584 2018205 185220 34.8821 111.1366 588365120 12 142 11584 2018205 185220 34.8847 111.1744 588365120 4 71 11584 2018205 185220 34.8846 111.1744 588365120 4 71 11584 2018205 185220 34.8846 111.1744 588365120 4 71 11584 2018205 185220 34.8821 111.1365 588365120 19 142 11584 2018205 185220 34.8847 111.1744 588365184 5 71 11584 2018205 185220 33.0372 81.2261 588365184 10 203 11591 2018205 185220 33.0324 81.2288 588365184 19 270 11591 ... 2018205 185620 27.0822 90.3000 588406016 20 208 16053 2018205 185620 27.0869 90.2767 588406016 2 69 16053 2018205 185620 27.0874 90.2948 588406016 7 138 16053 2018205 185620 27.0875 90.3004 588406016 5 138 16053 Number of matches found = 24110 I then tried to do the same as 'yoksas' while logged in on typhoon.eol.ucar.edu and I got the same results when accessing RTGOESR from atm.ucar.edu, but nothing when I tried accessing RTGOESR from typhoon.eol.ucar.edu. This tells me that the ADDE setup on typhoon is no longer valid for some reason. I then looked at the ADDE dataset definitions in the 'mcidas' account on typhoon (in the file ~mcidas/workdata/RESOLV.SRV) and was reminded that the GRB ABI and GLM files used to be located in the /data/output/GRB-R directory. I don't see anything in this directory on typhoon now: ls -alt /data/output/GRB-R total 5120 drwxrwxr-x 3 mcidas 1001 24 Jun 11 19:48 . drwxr-xr-x 2 mcidas 1001 5382144 Jun 11 19:47 tmp drwxr-xr-x 8 mcidas 1001 106 Dec 1 2017 .. So, the questions to you are: - are you still ingesting GRB products on typhoon.eol.ucar.edu? - if yes, where are they being written on disk? If typhoon is still ingesting GRB products but they are being written in a location other than /data/output/GRB-R, I will need to update the ADDE dataset definitions to point at the correct directory. 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: CXJ-584047 Department: Support McIDAS Priority: Normal Status: Closed =================== 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.