20040316: IMGREMAP fails with handle=3 error (cont.)

>From: McIDAS Help Desk <address@hidden>
>Organization: SSEC/MUG
>Keywords: 200403150130.i2F1U8rV014748 McIDAS IMGREMAP

Hi Rick,

>Since all of your commands listed deal with LINELE values, I'm having a 
>hard time guessing what domains are being used.

I'm sorry, I should have realized that this would be the case last
night.  Please read on...

>You do mention that you 
>are trying to make a SH mosaic, so I tried to recreate the same type of 
>situation and found that the latest CVS build of imgremap.k works on 
>linux.  I started with the topo image that is supplied with xrd (which I 
>have in A/A.8800)
>
>IMGCOPY A/A.8800 A/A.8000 STYPE=VISR LINE=1080 1 1080 4320
>IMGCOPY A/A.8800 A/A.8001 STYPE=VISR LINE=1080 1 1080 4320
>IMGREMAP EASTL/FD A/A.8000 BAND=4 TIME=11:45
>IMGREMAP WESTL/FD A/A.8001 BAND=4 TIME=12:00
>IMGREMAP A/A.8000 A/A.8001 MERGE=YES
>
>Does this seem like a similar scenario?  Please let me know.

Try the following:

Create a BATCH file with the following contents:

REM Set pointers to needed datasets
DATALOC ADD TOPO ADDE.UCAR.EDU
DATALOC ADD TEST ADDE.UCAR.EDU

REM Create basemap from Topo files
IMGREMAP TOPO/GLOB A/A.1 PRO=RECT SIZE=ALL RES=5
IMGCOPY A/A.1 A/A.2 LINELE=1500 0 SIZE=2100 8000
IMGCOPY A/A.2 A/A.3 LINELE=0 1685 SIZE=2100 1805

REM Remap Imagery onto basemaps
IMGREMAP TEST/GWFDSK04I4 A/A.2 DAY=2004076 TIME=11 12
IMGREMAP TEST/GEFDSK04I4 A/A.3 DAY=2004076 TIME=11 12

REM Remap imagery into first basemap
IMGREMAP A/A.3 A/A.2 MERGE=YES SSIZE=ALL DEV=CCC

REM Give it correct date
IMGCHA A/A.2 CTYPE=BRIT SS=70 BAND=4 TIME=11:45:00 DAY=2004076


I just ran this from a McIDAS-X v2003 session using IMGREMAP v1.86
(not released yet, but available in the CVS) and got:

 ...
IMGREMAP* invalid parm - can't get pointer for handle=3
IMGREMAP* (handle.c): parameter ERROR at line 293
IMGREMAP: Failed to remap the image
IMGREMAP* ERROR --- domap= -1
IMGREMAP failed, RC=1

>Since there are a lot of other changes in the latest CVS, I'll be hard 
>pressed to single out the correct module. We are planning on send out a 
>FASTRACK soon and I can check this version.

I will be very interested to see if this works with all of the
other changes in the SSEC FasTrack.  Please let me know.

Thanks in advance...

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.