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

[McIDAS #VTQ-561942]: issue with latest MODIS AEROSOL HDF products on our old mcidas 2009q server



Hi Tyn,

re:
> Thanks for looking into this!

No worries.

re:
> There appear to be multiple trce files:
> 
> MODXADIR   PRODUCT NAME=/home/mcidas/data/modis/products/MXD06/MOD06_L2
> MODXADIR    Num_Band=55 5000m=48 1000m=7 250m=0
> MODXADIR   cdate: A2007065, image_cyd 2007065, image_iyd 107065
> MODXADIR   image_hms: char=1000 int=100000
> MODXADIR   READ the LATITUDE field
> MODXADIR      lines= 408  elems= 270
> MODXADIR      Center = 50.578655
> MODXADIR   READ the LATITUDE field
> MODXADIR      lines= 408  elems= 270
> MODXADIR      Center = -16.842318
> No images satisfy the selection criteria

First, this does not look like it should be from the 'mod4aget' server
(note the MODXADIR label which should indicate that the message
was written by the 'modxaget' server).

There should only be one 'trce' file written to by an ADDE
server.  Where this file should/will be located will depend on
how the ~/.mcenv file is configured in the account that is fulfilling
the ADDE requests.  The typical setup is for 'trce' to be written
to the ~/mcidas/data directory.

re:
> tail /home/mcidas/mcidas/data/trce
> 
> 
> MODSADIR   file 338 = 
> /home/mcidas/data/modis/products/MXD02/MOD021KM.A2007181.1115.005.2007183053349.hdf
> MODSADIR   Looking for ALL bands
> MODSADIR   bPos: 339, ePos: 1
> MODSADIR   value for AUX flag: 1
> MODSADIR   BEFORE  MAIN LOOP --- bpos=339 epos=1 ipos=-1
> MODSADIR   cdate: A2007181, image_cyd 2007181, image_iyd 107181
> MODSADIR   image_hms 111500
> MODSADIR   START: FAILED for 
> /home/mcidas/data/modis/products/MXD02/MOD021KM.A2007181.1115.005.2007183053349.hdf
> MODSADIR   cdate: A2007181, image_cyd 2007181, image_iyd 107181
> MODSADIR   image_hms 111000
> MODSADIR   READ the LATITUDE field
> MODSADIR      lines= 406  elems= 271
> MODSADIR      Center = 64.424690
> MODSADIR   READ the LATITUDE field
> MODSADIR      lines= 406  elems= 271
> MODSADIR      Center = -6.671602
> MODSADIR   Dir Size = 64  Num Cards = 174
> MODSADIR   Send Byte Total = 14180
> MODSADIR   exit
> 

This looks like it is from the 'modsadir' server.  But, the START: Failed 
message
would appear to be the place to start for this server transaction.

re:
> tail /home/mcidas/trce

Why there would be a 'trce' file in the /home/mcidas directory is
a mystery to me.

Questions:

- what are the time stamps on the two (or more) 'trce' files that you
  found?

- have you looked into why I am not able/allowed to SSH to your machine?

  Getting on the machine would make the troubleshooting go much faster.

  If getting on the machine is not possible, could you put a couple of
  representative HDF files somewhere where I could grab them so I could
  do my investigations in my McIDAS development environment?

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: VTQ-561942
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.