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

20040315: imgremap still brokwn in McIDAS v. 2003a? (cont.)



>From: Robert Mullenax <address@hidden>
>Organization: NMSU/NSBF
>Keywords: 200403150130.i2F1U8rV014748 McIDAS IMGREMAP

Robert,

re: the error you report seems different than the one reported previously

>You may be right about it being a different error.

OK.  I think it is.  See below.

>I am making a global composite (G-10, G-12, MET, IND, GMS) of the southern
>hemisphere in RECT proj:
>
># Create basemap from Topo files
>imgremap.k TOPO/GLOB MYDATA/IMAGES.1 PRO=RECT SIZE=ALL RES=5
>imgcopy.k MYDATA/IMAGES.1 MYDATA/IMAGES.2 LINELE=1500 0 SIZE=2100 8000
>imgcopy.k MYDATA/IMAGES.2 MYDATA/IMAGES.3 LINELE=0 1685 SIZE=2100 1805
>imgcopy.k MYDATA/IMAGES.2 MYDATA/IMAGES.4 LINELE=0 3490 SIZE=2100 1685
>imgcopy.k MYDATA/IMAGES.2 MYDATA/IMAGES.5 LINELE=0 5172 SIZE=2100 1203
>imgcopy.k MYDATA/IMAGES.2 MYDATA/IMAGES.6 LINELE=0 6373 SIZE=2100 1708
># Remap Imagery onto basemaps
>imgremap.k GWR/GWFDSK04I4 MYDATA/IMAGES.2 DAY=${datej} TIME=02 04
>imgremap.k GER/GEFDSK04I4 MYDATA/IMAGES.3 DAY=${datej} TIME=02 04
>imgremap.k MET/MEGLOB05I MYDATA/IMAGES.4 DAY=${datej} TIME=02:45 03:15
>imgremap.k IND/INDOEXIR MYDATA/IMAGES.5 DAY=${datej} TIME=02:45 03:15
>imgremap.k GPR/GPFDSK04I4 MYDATA/IMAGES.6 DAY=${datej} TIME=03:10 03:40
># Remap imagery into first basemap
>imgremap.k MYDATA/IMAGES.3 MYDATA/IMAGES.2 MERGE=YES SSIZE=ALL
>imgremap.k MYDATA/IMAGES.4 MYDATA/IMAGES.2 MERGE=YES SSIZE=ALL
>imgremap.k MYDATA/IMAGES.5 MYDATA/IMAGES.2 MERGE=YES SSIZE=ALL
>imgremap.k MYDATA/IMAGES.6 MYDATA/IMAGES.2 MERGE=YES SSIZE=ALL
># Give it correct date
>imgcha.k MYDATA/IMAGES.2 CTYPE=BRIT SS=70 BAND=4 TIME=03:00:00 DAY=${datej} ME
> MO
>
>IMGREMAP bombs when I try to do the first merge..G-12 onto the G10 basemap.
>MYDATA/IMAGES.3 merged into MYDATA/IMAGES.2.   The script is running
>fine right now with the 7.8 version.

I put the first parts of your script into a test script here at the UPC
and verified that the problem exists on McIDAS-X v2003b when running on
a Sun Solaris SPARC 5.9 machine for McIDAS built with gcc/g77.  This
told me that we are not looking at a platform-specific problem (had to
check...).

So, I went to the MUG Inquiry Tracking system and looked up problems
with IMGREMAP.  I found one that fits your report:

Inquiry 12313
Summary: IMGREMAP gives "invalid parm - can't get pointer for handle=2" error
when the destination image is a MODIS area.

Given that you are seeing the same problem, I have to conclude that the
problem is not related to the lat,lon navigation of MODIS data alone as
was conjectured in the inquiry interchange:

  ---- 14-NOV-2003 20:09 barryr ------------------------------------------
  *** This is no longer being fixed in #12132.  I'm re-opening this
  inquiry.  Dave says that he thinks part of the bug is in the LALO
  navigation routine, which will probably be very difficult to fix....it
  can't handle the 2 lat/lon navs that IMGREMAP is trying to setup. ***

  See inquiry 12132. The bug in this inquiry is
  being addressed there.

Also, I grabbed the latest version of imgremap.pgm from SSEC and built
it to see if the handle= error has been fixed.  It hasn't, so the
second conjecture in the SSEC inquiry is incorrect as well (sigh).

>It was built using gcc/g77.  I also verified the same bug at Universal
>under Solaris x86 and RH 9.

I verified it on Solaris SPARC using gcc/g77, so this is not a platform
specific bug.

I am now looking through the code to see if I can figure out why the
remapping is being terminated prematurely.  I think I understand where
the problem is happening and why, but I havn't figured out how to
_correctly_ fix the problem.

More later...

>Thanks,

No worries.

Cheers,

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.


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.