Custom Query (419 matches)


Show under each result:

Results (121 - 123 of 419)

Ticket Resolution Summary Owner Reporter
#167 fixed Hardcoded default bands in bil.hdr mggr mark1

Default bands in the bil.hdr are hard coded such that they always assume the full range of bands is used. This causes errors in ENVI when it tries to load the bil file.

#168 fixed Overflow handling in azspec mggr mggr

[Issue began 5/June/2008, split out from #133 18/June.]

While fixing the FODIS processing (#133), Bill noticed that the overflow value he was looking for was 4096 but should actually have been 4095. In fixing this, he has unearthed a large number of overflows in captured Eagle and Hawk imagery.

In Hawk, which shifts the whole frame out of the CCD at once, these overflows will only affect the data at the bandpixel that has overflowed. The only fix required is to mark the bad pixels and to provide info to the flight crew to allow them to set camera values appropriately.

In Eagle, the CCD shifts the image out a line at a time, which means light continues to accumulate during the shifting procedure. This additional light is removed by "frame smear correction", where a proportion of the light is removed from each pixel, accumulating as the shifts progress through the frame (begins at the red end of the spectrum and proceeds to the blue end). However, if a pixel overflows, it is no longer possible to estimate the proportion of light to remove from the next pixel (as it will be unmeasured due to pixel saturation).

#171 fixed Support: 25/Jun/2008, Thomas Ruhtz, NL08/01 mggr mggr

Contacted via Peter Purcell. Thomas would like some raw data for quick feedback on the EUCAARI flights in order to assist with VOCALS preparations.

Hi Peter,

Hugh did agree to work together on the Vocals and eucaari data analysis and I
will ask him further if he agrees to our participation during the campaign.
We are going to write a proposal and would like to include some data of the
eucaari campaign. The proposal will focus on the analysis of remote sensing
data and aerosol and cloud products. We can put in some funding of our
participation at Vocals if Hugh agrees on that.

I did discuss with Phil during the campaign the possibity to get the raw data
on a harddisk and it should be the easiest way to have a quick look at the
data for our proposal. The linux quick look tool would help a lot as well. I
only have some older software of the Aisa system and dont know if it works
with the Eagle/Hawk data. Later on if the prosessing is finished at PML we
can discuss the processing of the data in more detail. I think this will be
the case during JRA4 anyway. Who is the contact point at PML for the data
processing or whom should I contact in case of questions regarding the
procedures, calibration coefficients etc.

Thanks a lot

Note: See TracQuery for help on using queries.