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

20041217: missing line in IMGREMAP MERGEd images (cont.)



>From: McIDAS Help Desk <address@hidden>
>Organization: SSEC
>Keywords: 200412151752.iBFHqalI029160 McIDAS IMGREMAP MERC MERGE

Hi Jay,

re: missing element slice in IMGREMAPed images

>We have had this problem reported in Inquiry 12314.  Dave Santek just
>took a look at it and found the problem.  If you want to try out these
>changes, here they are:
>
>Here are the changes:
>
>jeep(daves): cvs diff imgremap.f
>Index: imgremap.f
>===================================================================
>RCS file: /source-control/mcidas/cmd/imgremap.f,v
>retrieving revision 1.93
>diff -r1.93 imgremap.f
>1282,1285c1282,1285
><          smnline = MAX( smnline, 1)
><          smnelem = MAX( smnelem, 1)
><          smxline = MIN( smxline, save_sdirectory(IMGDIR_LINPOS) )
><          smxelem = MIN( smxelem, save_sdirectory(IMGDIR_ELEPOS) )
>---
> >          smnline = MAX( smnline, 0)
> >          smnelem = MAX( smnelem, 0)
> >          smxline = MIN( smxline, save_sdirectory(IMGDIR_LINPOS)-1 )
> >          smxelem = MIN( smxelem, save_sdirectory(IMGDIR_ELEPOS)-1 )
>1989,1990c1989,1990
><        zl = (zl-slin) * zsincl + 1.0
><        ze = (ze-sele) * zsince + 1.0
>---
> >        zl = (zl-slin) * zsincl
> >        ze = (ze-sele) * zsince

Cool.  I updated the copy of imgremap.pgm in my distribution, rebuilt
the imgremap.k executable under Solaris SPARC using the gcc/g77 compilers,
and reran the BATCH script that showed the problem.  The change looks like
it fixes the missing element problem!

>However, this will be put into testing now, so we aren't sure if this
>change breaks anything else.

Right, I understand.

>Other workarounds we have given out use IMGOPER. I took out the IMGCOPY
>4135 4136 step, and replaced the last IMGREMAP with this IMGOPER:
>
>REM Composite the westernmost GOES-12 piece with the GOES-East remap
>
>IMGOPER MYDATA/IMAGES.4135 MYDATA/IMAGES.4137 MYDATA/IMAGES.4138 FORM=CMIN ZER
> O=DATA SIZE=960 3568
>
>SF 5;ERASE F;IMGDISP MYDATA/IMAGES.4138 MAG=-2 EU=IMAGE;MAP

Thanks for the workaround.  I will pass it along to my user.

>The image will differ a little coverage wise depending if it's a full
>disk or n-hemi, etc.  Rick also mentioned some examples with IMGFILT and
>the discriminate filter if you are interested, and inquiry 12314 has
>another example cutting images up more with IMGCOPY, then using IMGOPER.

OK, thanks for the tips.  I will review 12314 for further info.

>I hope this information helps.  Let us know if you have any further
>questions.

It helped a lot.  Thanks for the quick reply, and thanks to Dave for
the fix!

Cheers,

Tom
--
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.


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.