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

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



>From: Unidata Support <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200403150130.i2F1U8rV014748 McIDAS IMGREMAP

Hi Robert,

I filed an inquiry on the IMGREMAP problems you are seeing and got
a quick response back from Rick Kohrs (after I made the exact data
you are using available through ADDE).  Rick replicated the problem
and is initiating a new inquiry.  He also developed a simple
workaround:

  Hi Tom,
  
  I was able to reproduce your error even with the most recent version of 
  CVS.  I tried your last IMGREMAP command and omitted the SSIZE=ALL and 
  the command finished successfully. I'll write this up as a new inquiry.  
  If Dave thinks it is related to inquiry 12313, I'll close the new 
  inquiry and transfer the information.
  
  Rick

I rolled the copy of imgremap.pgm back to the one in the v2003
distribution and rebuilt its executable.  I then ran the sequence of
IMGREMAP commands that you provided leaving off the SSIZE= keyword and
it worked without any problems.  So, the fix is simply to leave off
the SSIZE= keyword on IMGREMAPs that are MERGEing into an existing
image.  Go figure...

Anyway, this is being written up as a bug that needs fixing.

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.

>From address@hidden  Tue Mar 16 19:42:09 2004

Thanks as always for your help.   I use SSIZE=ALL as it seemed it
didn't always work right without it.    I will remake the V2003 binary
and change the script.

I also have a weird ADDE issue that I will send in a separate e-mail.

Thanks,
Robert


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.