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

[McIDAS #LLN-564004]: GOES-16 data and McIDAS



Hi Heather,

re:
> We have the latest version of Unidata Mcidas 2016.  Should we be able to
> look at GOES-R imagery with this version of McIDAS?

Yes, but there have been a number of changes to the ADDE server for the
GOES-R imagery that are not available in the Unidata v2016a release.

re:
> I am following this tutorial:
> 
> https://www.ssec.wisc.edu/mcidas/mug_meeting2016/training/McIDAS_ABI_Tutorial.pdf
> 
> And am unable to do an imglist on my data after adding it with dsserve as
> described in the tutorial.
> 
> address@hidden PDA]$ dsserve.k ADD ABI/FD ABIN TYPE=IMAGE 
> DIRFILE="$PWD/OR_ABI-L1b-RadF-M3C08_G16_s20172552345356_e20172552356123_c20172552356171.nc"
> 
> Group/Descriptor         Type  Format & Range     RT Comment
> ------------------------ ----- ------------------ -- --------------------
> ABI/FD                   IMAGE ABIN
> DIRFILE=/data/archive/PDA/OR_ABI-L1b-RadF-M3C08_G16_
> s20172552345356_e20172552356123_c20172552356171.nc
> dsserve.k: done
> 
> address@hidden PDA]$ imglist.k ABI/FD.ALL
> Image file directory listing for:ABI/FD
> imglist.k: done?
> 
> Thanks!  Any advice you can offer would be appreciated!

I just setup an ADDE dataset pointing at an ABI Channel 1 Full Disk image
file created by CSPP GEO on our GOES-16 ingest downlink, and I had no
problems listing/displaying the data in Unidata McIDAS-X v2016a:

DSSERVE LIST RTGOESR

Group/Descriptor         Type  Format & Range     RT Comment
------------------------ ----- ------------------ -- --------------------
RTGOESR/FDC01            IMAGE ABIN                  GOES-16 Channel 1 from GRB
                               
DIRFILE=/home/mcidas/workdata/GOES16/GRBFD/*C01*.nc
DSSERVE: done

IMGLIST RTGOESR/FDC01 FORM=ALL
Image file directory listing for:RTGOESR/FDC01
 Pos Satellite/         Date       Time      Center      Res (km)   Image_Size
     sensor                                 Lat  Lon    Lat   Lon
 --- -------------  ------------  --------  ---- ----  ----- ----- ------------
   1  G-16 IMG      17 APR 17107  16:30:38     0   89
   Band: 1    0.47 um VIS aerosol-over-land             1.00  1.00 10848 x10848
     proj:    0 created: 2017107 163038  memo: GOES-R Full Disk
     type:ABIN     cal type:RAW
     offsets:  data=    1280 navigation=  256 calibration=  768 auxiliary=    0
     doc length:   0   cal length:   0   lev length:   0 PREFIX=   0
     valcod:          0 zcor:  0 avg-smp: A
     lcor:    1  ecor:     1  bytes per pixel: 2  ss:186
     Resolution Factors (base=1):   Line=    2.0   Element=    2.0
IMGLIST: done

My test demonstrates that v2016a should be able to serve the data (but newer
versions of McIDAS-X will needed to serve the data correctly).   The only
thing I can think of is that there is something wrong with the file you have.

What is the output of:

imglist.k ABI/FD.ALL FORM=ALL DEV=CCC


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: LLN-564004
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.



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.