|
MERIS IDL General Purpose Tools |
|
Item #
|
Description of Action to perform or Problem to resolve
|
Priority
|
Comments/Solutions
|
Coding in progress
|
Debugging in progress
|
Validated or Resolved |
|
1
|
Level 0 analysis tool | high |
on the display window materialize each camera w/ a vertical line on the AL profile, from one camera to another the line should be suspended |
|||
|
2
|
Level 1 intermediate file data retrieval tool | mid |
today, only data from a RWMAP file can be retrieved |
|||
|
3
|
Finish the function that should allow to run a neural network directly from IDL on an array of values or on one single point | very low | ||||
|
4
|
develop a function that presents the counts of flags raised on an area specified by its limits (usefull to test the SQADS and generally usefull for the commisioning phase) | done in MV 2.1 | ||||
|
5
|
develop a function that shows the flag positions for any given pixel (... and integrate it within MERISVIEW) | done in MV 2.1 | ||||
|
6
|
the COMPARE functionalities (statistics on L2 intermediate field differences) should be expanded to fields stored in MERIS products (L1 or L2) |
for L2 products add number and % of pixels for which PCD (bad/suspicious/good) is same and mean/stddev/min/max for each PCD class(b/s/g) |
||||
|
7
|
make sure that all products referenced in GET_PRDKEY have an index file (referenced DORIS and RA2 products are missing their index files) | |||||
|
8
|
when using rd_prod it should not be possible to retrieve a MPH or SPH parameter (#0## or #1## keys), it will not produce anything good since these parameters are of ASCII type ... | |||||
|
9
|
develop FUB commisioning tool ... | |||||
|
10
|
develop LISE commisioning tool ... | Fortran based tool | ||||
|
11
|
column power spectrum computation commisioning tool ... | |||||
|
12
|
close to MESCAL calibration commisioning tool ... | |||||
|
13
|
instrument linearity checking commisioning tool ... | |||||
|
14
|
straylight identification commisioning tool ... | AL/AC profiles MV utilities + Line/Column MV ROI should be sufficient | ||||
|
15
|
add CAMERA and BAND (most important) keywords in the RD_PACK function | |||||
|
16
|
any function should be able to work in batch mode ... therefore instead of calling DIALOG_MESSAGE another function should be called that decides to start or not a dialog message box ... this should be decided using a system variable that is set to 0 (no display) by default | |||||
|
17
|
add an interface to RD_LPROD (like the RD_PROD function) to be able to interactively retrieve fields and define sub-sampling and limits | |||||
|
18
|
add an interface to RD_RWMAP (like the RD_PROD function) to be able to interactively retrieve fields and define sub-sampling and limits | |||||
|
19
|
||||||
|
20
|
||||||
|
21
|
||||||
|
22
|
||||||
|
23
|
||||||
|
24
|
||||||
|
25
|
||||||
|
26
|
||||||