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

[McIDAS #YBA-424649]: mcidas question

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.

  • Subject: [McIDAS #YBA-424649]: mcidas question
  • Date: Wed, 23 May 2012 12:18:18 -0600
Hi Randy,

re:
> I am using our version of REMAP2 on different machines.
> 
> 1) machine1:
> 
> Linux fsoc3.it-protect.com 2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:52:25 EST 
> 2011 x86_64 x86_64 x86_64 GNU/Linux
> [sleet@fsoc3 tmp]$ cat /etc/*-release
> CentOS release 5.5 (Final)
> 
> REMAP2 runs fine, output looks like,
> 
> [sleet@fsoc3 tmp]$ imglist.k RJA/TMP.8 FORM=EXP
> Image file directory listing for:RJA/TMP
> Pos Satellite/         Date       Time      Center      Res (km)   Image_Size
> sensor                                 Lat  Lon    Lat   Lon
> --- -------------  ------------  --------  ---- ----  ----- ----- ------------
> 8  G-15 IMG      23 MAY 12144  02:00:00    22  156
> Band: 1    0.62 um VIS Cloud and Surface Features    1.00  0.92   334 x  112
> Band: 2    3.9 um IR Low Cloud/Fog,Fire Detection    1.00  0.92   334 x  112
> Band: 3    6.5 um IR Mid-level Water Vapor           1.00  0.92   334 x  112
> Band: 4    10.7 um IR Surface/Cloud-top Temp         1.00  0.92   334 x  112
> Band: 6    13.3 um IR CO2, Cloud Heights             1.00  0.92   334 x  112
> proj:    0 created: 2012144 174449  memo: RT GVAR
> type:GVAR     cal type:RAW
> offsets:  data=    3328 navigation=  256 calibration= 2816 auxiliary=    0
> doc length:   0   cal length:   0   lev length:   8 PREFIX=   8
> valcod:          0 zcor:  0 avg-smp: N
> start yyddd: 2012144  start time: 20020  start scan:  311
> lcor:    1  ecor:     1  bytes per pixel: 2  ss:184
> Resolution Factors (base=1):   Line=    1.0   Element=    1.0
> imglist.k: done
> 
> 
> 2) machine 2:
> sleet@tornado:~/mcidas/bin$ uname -a
> SunOS tornado 5.11 snv_111b i86pc i386 i86pc Solaris
> sleet@tornado:~/mcidas/bin$ uname -r
> 5.11
> 
> REMAP2 appears to run fine but output looks like,
> 
> sleet@tornado:/data/tmp$ imglist.k TORNADO/RJA.8 FORM=EXP
> Image file directory listing for:TORNADO/RJA
> Pos Satellite/         Date       Time      Center      Res (km)   Image_Size
> sensor                                 Lat  Lon    Lat   Lon
> --- -------------  ------------  --------  ---- ----  ----- ----- ------------
> 8  G-15 IMG      23 MAY 12144  02:00:00    23    0
> Band: 1    0.62 um VIS Cloud and Surface Features                 334 x  112
> Band: 2    3.9 um IR Low Cloud/Fog,Fire Detection                 334 x  112
> Band: 3    6.5 um IR Mid-level Water Vapor                        334 x  112
> Band: 4    10.7 um IR Surface/Cloud-top Temp                      334 x  112
> Band: 6    13.3 um IR CO2, Cloud Heights                          334 x  112
> proj:    0 created: 2012144 175351  memo: RT GVAR
> type:GVAR     cal type:RAW
> offsets:  data=    3328 navigation=  256 calibration= 2816 auxiliary=    0
> doc length:   0   cal length:   0   lev length:   8 PREFIX=   8
> valcod:          0 zcor:  0 avg-smp: N
> start yyddd: 2012144  start time: 20020  start scan:  311
> lcor:    1  ecor:     1  bytes per pixel: 2  ss:184
> Resolution Factors (base=1):   Line=    1.0   Element=    1.0
> imglist.k: done
> 
> 
> NOTE the center LON is 0 and the Res(km) column is now blank.

I see this, yes.

re:
> Using same version of mcidas  mcidas2009i
> Code is of coursed recompiled on the SunOS 5.11 machine.
> 
> any ideas?

My first guess is that the difference reflects a difference in the
executables on the two systems: the CentOS 5.5 system will have 64-bit
executables, and I _guess_ that the Solaris 5.11 system has 32-bit
executables (the default build on Solaris is typically 32-bit even
though the machine and OS are 64-bit).

My second guess (that is associated with the first) is that there is
a coding bug that is making itself seen on the Solaris system, but
not on the CentOS system.  I have run into this kind of thing many,
many times with McIDAS-X.

Request:

- can you make the AREA files that are the result of the two different
  REMAP2 invocations available so I can take a look?

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: YBA-424649
Department: Support McIDAS
Priority: Normal
Status: Closed