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

20040314: imgremap still brokwn in McIDAS v. 2003a?

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

Hi Robert,

>I am trying to use the MERGE=YES option with imgremap under McIDAS 2003a
>(Unidata) under Red Hat 9.  I am getting an error similar to what I saw under 
>the previous versions:
>
>IMGREMAP:   Invalid parm - can't get pointer for handle=3
>IMGREMAP: (handle.c) paramerter ERROR at line 289

I thought that the problem you ran into previously was that the
remapping itself would give blank space in certain circumstances, not
that handle.c would return an error.  Didn't you grab the initial
release of v2003 and _not_ have this problem?  A quick check of the
imgremap.pgm source shows that it has not changed since April of last
year:

C *** $Id: imgremap.f,v 1.80 2003/04/25 02:20:11 barryr Rel $ ***

I just looked at the handle.c code and see that the error comes when
the input handle is greater than the number in the pool.  It is very
strange that this would fail since the handle in question is 3, and I
believe that the pool has 32.  I will check into this later today when
I get the chance.

Can you give me the invocation for which you got this error?  It would
also be useful if I could get the exact dataset elements (images) you
were using when you ran into this problem.

>From address@hidden  Sun Mar 14 18:40:23 2004
>
>BTW I got the imgremap.pgm from McIDAS 7.8, rebuilt imgremap
>and it works fine.  But of course I would rather use the v.2003 as it
>doesn't produce trce files for one thing.

Very strange.  It is almost like an arry has overflowed stepping on
a parameter somewhere.

What is the compilation environment you used to build imgremap.k?
I am assuming gcc/g77, but I want to be sure.

>Thanks,

I will get back to you when I have had a chance to look into this
in more detail.

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.