Hi Heather,
Sorry for the slow reply. I had too many things going on this past weekend
to get to your inquiry.
re:
> Sorry to keep bothering you, but after countless tries and unsuccessful
> internet searches I am at a loss on this one ...
>
> I am still working with my CO2 data, and am trying to put several images
> together using imgoper. However, my resultant image will only show
> brightness temperatures! If I specify a product, all I am getting are
> values of 255. I have attached the 4 files I am trying to put together,
> I put them in a dataset called CO2REMAP/CTP. Here are the commands I
> am using:
>
> This command gives me the image with ONLY brightness temps:
> imgoper.k CO2REMAP/CTP.1 CO2REMAP/CTP.2 CO2REMAP/CTP.3 CO2REMAP/CTP.4 CO2RE
> MAP/CTP.5 SIZE=ALL FORM=CMIN MISS=NONE
Hmm... I would say that this gives only brightnesses. The funny thing though is
if you compare the headers of any one of the input files with the header of
the output created by IMGOPER, it looks like the PROD calibration should have
been copied into the output but isn't. For instance:
LWU LIST AREA2000 0 256
0. 0 4 HEX: 0 4 ASCII:
2. 181 113309 HEX: B5 1BA9D ASCII:
4. 194600 9761 HEX: 2F828 2621 ASCII: ( !&
6. 9401 0 HEX: 24B9 0 ASCII: $
8. 480 1200 HEX: 1E0 4B0 ASCII:
...
192. 1146049104 950 HEX: 444F5250 3B6 ASCII: PROD
194. 150 76 HEX: 96 4C ASCII: L
196. 255 538993261 HEX: FF 2020626D ASCII: mb
198. 1 99999 HEX: 1 1869F ASCII:
200. 1347376195 950 HEX: 504F5443 3B6 ASCII: CTOP
202. 150 76 HEX: 96 4C ASCII: L
204. 255 538993261 HEX: FF 2020626D ASCII: mb
206. 1 99999 HEX: 1 1869F ASCII:
208. 1413762115 245 HEX: 54444C43 F5 ASCII: CLDT
210. 320 75 HEX: 140 4B ASCII: @ K
212. 1 1265067364 HEX: 1 4B676564 ASCII: degK
214. 1 99999 HEX: 1 1869F ASCII:
LWU LIST AREA2004 0 256
0. 0 4 HEX: 0 4 ASCII:
2. 185 113309 HEX: B9 1BA9D ASCII:
4. 202400 9761 HEX: 316A0 2621 ASCII: !&
6. 9401 0 HEX: 24B9 0 ASCII: $
8. 480 1200 HEX: 1E0 4B0 ASCII:
...
192. 1146049104 0 HEX: 444F5250 0 ASCII: PROD
194. 255 0 HEX: FF 0 ASCII:
196. 255 0 HEX: FF 0 ASCII:
198. 0 0 HEX: 0 0 ASCII:
As you can see, the PROD calibration after the IMGOPER is a linear
mapping of counts to brightness.
re:
> This command gives me the image with temps of 255:
> imgoper.k CO2REMAP/CTP.1 CO2REMAP/CTP.2 CO2REMAP/CTP.3 CO2REMAP/CTP.4
> CO2REMAP/CTP.5 UNIT=PROD BAND=1 SIZE=ALL FORM=CMIN MISS=NONE
>
> I used UNIT=PROD, because that is the command that I used to imgcopy
> one remap file to the netcdf file. I have tried different UNIT= values
> like CLDT, but I am still getting garbage.
This gives exact same output for me as the first IMGOPER invocation:
LWU LIST AREA2004 0 256
0. 0 4 HEX: 0 4 ASCII:
2. 185 113309 HEX: B9 1BA9D ASCII:
4. 202400 9761 HEX: 316A0 2621 ASCII: !&
6. 9401 0 HEX: 24B9 0 ASCII: $
8. 480 1200 HEX: 1E0 4B0 ASCII:
...
192. 1146049104 0 HEX: 444F5250 0 ASCII: PROD
194. 255 0 HEX: FF 0 ASCII:
196. 255 0 HEX: FF 0 ASCII:
That the two invocations give the same result is expected as the default
would be to use the first calibration. That the calibration is different
is unexpected for me, but I may be expecting more than I should.
Keep reading, more at bottom...
re:
> I just realized that I did not attach my remapped files.
Thanks for sending these along, they helped me immensely!
So, here is the other bit:
What to do? Use the PRDUTIL utility to add/modify calibration to the
AREA file created by the IMGOPER invocation. Here is what I just
tried:
DSSERVE ADD CO2REMAP AREA 2000 2010 "CO2 REMAP FROM NORTHRUP GRUMMAN
IMGOPER CO2REMAP/CTP.1 CO2REMAP/CTP.2 CO2REMAP/CTP.3 CO2REMAP/CTP.4
CO2REMAP/CTP.5 UNIT=PROD BAND=1 SIZE=ALL FORM=CMIN MISS=NONE
PRDUTIL ADD CO2REMAP/CTP.5 1 PROD 950 150 76 255 mb 1 99999
After running PRDUTIL, the PROD calibration block in the image created
by IMGOPER matches the PROD calibration blocks in the input images:
PRDUTIL ADD CO2REMAP/CTP.5 1 PROD 950 150 76 255 mb 1 99999
Image file directory listing for:CO2REMAP/CTP
Pos Satellite/ Date Time Center Res (km) Image_Size
sensor Lat Lon Lat Lon
--- ------------- ------------ -------- ---- ---- ----- ----- ------------
5 G-15 SND 5 NOV 13309 20:24:00 31 104
Band: 1 No Information Available 14.01 12.02 480 x 1200
proj: 0 created: 2013329 230004 memo:
type:PRD cal type:BRIT
offsets: data= 1280 navigation= 256 calibration= 768 auxiliary= 0
doc length: 0 cal length: 0 lev length: 0 PREFIX= 0
valcod: 0 zcor: 0 avg-smp: N
lcor: 9761 ecor: 9401 bytes per pixel: 1 ss:185
Resolution Factors (base=1): Line= 13.0 Element= 13.0
IMGLIST: done
Current Calibration Block Segments In File:
Output Input
Product Product Brit Brit
Num Type low high low high Units Scale Missing Val
--- ---- -------- -------- ----- ----- ----- ----- -----------
1: PROD 950 150 76 255 mb 1 99999
LWU LIST AREA2004 0 256
0. 0 4 HEX: 0 4 ASCII:
2. 185 113309 HEX: B9 1BA9D ASCII:
4. 202400 9761 HEX: 316A0 2621 ASCII: !&
6. 9401 0 HEX: 24B9 0 ASCII: $
8. 480 1200 HEX: 1E0 4B0 ASCII:
...
192. 1146049104 950 HEX: 444F5250 3B6 ASCII: PROD
194. 150 76 HEX: 96 4C ASCII: L
196. 255 538993261 HEX: FF 2020626D ASCII: mb
198. 1 99999 HEX: 1 1869F ASCII:
In a like manner, you can add the CTOP and CLDT calibrations to the
image created by IMGOPER:
PRDUTIL ADD CO2REMAP/CTP.5 2 CTOP 950 150 76 255 mb 1 99999
PRDUTIL ADD CO2REMAP/CTP.5 3 CLDT 245 320 75 1 degK 1 99999
Cheers,
Tom
--
****************************************************************************
Unidata User Support UCAR Unidata Program
(303) 497-8642 P.O. Box 3000
address@hidden Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage http://www.unidata.ucar.edu
****************************************************************************
Ticket Details
===================
Ticket ID: QMH-464866
Department: Support McIDAS
Priority: Normal
Status: Closed
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.