|
ocssw
V2022
|
/gfs-oceanweb/web/ocssw/ocssw_src/src/l1bgen_modist/error_messages.txt File Reference
Functions | |
| MOD_PR02 Error Meanings and Operator specific error codes that may be generated by the general meaning of these error codes and | operator actions to take if one these is encountered. MCST points of contact are:Xu Geng 301-867-2057 xu.geng @ssaihq.com James Kuyper 301-867-2064 James.R.Kuyper @nasa.gov=============================================================================="SUCCESS" ERROR CODES:==============================================================================MODIS_S_OK - OK (do nothing) |
Variables | |
| MOD_PR02 Error | Codes |
| MOD_PR02 Error Meanings and Operator | Actions |
| MOD_PR02 Error Meanings and Operator specific error codes that may be generated by | MOD_PR02 |
| MOD_PR02 Error Meanings and Operator specific error codes that may be generated by the general meaning of these error codes and probably from the MOD01 | granule |
Function Documentation
◆ operator actions to take if one these is encountered. MCST points of contact are:Xu Geng 301-867-2057 xu.geng @ssaihq.com James Kuyper 301-867-2064 James.R.Kuyper @nasa.gov=============================================================================="SUCCESS" ERROR CODES:==============================================================================MODIS_S_OK - OK()
| MOD_PR02 Error Meanings and Operator specific error codes that may be generated by the general meaning of these error codes and operator actions to take if one these is encountered. MCST points of contact are:Xu Geng 301-867-2057 xu.geng @ssaihq.com James Kuyper 301-867-2064 James.R.Kuyper @nasa.gov=============================================================================="SUCCESS" ERROR CODES:==============================================================================MODIS_S_OK - OK | ( | do | nothing | ) |
Variable Documentation
◆ Actions
| MOD_PR02 Error Meanings and Operator specific error codes that may be generated by the general meaning of these error codes and probably from the MOD01 was found to be out of the valid range but Level processing can continue Operator an algorithm problem or a code defect Operator Actions |
Initial value:
Definition at line 3 of file error_messages.txt.
◆ Codes
Definition at line 2 of file error_messages.txt.
◆ granule
| MOD_PR02 Error Meanings and Operator specific error codes that may be generated by the general meaning of these error codes and probably from the MOD01 granule |
Definition at line 36 of file error_messages.txt.
◆ MOD_PR02
Definition at line 6 of file error_messages.txt.
u5 which has been done in the LOCALGRANULEID metadata should have an extension NRT It is requested to identify the NRT production Changes from v6 which may affect scientific the sector rotation may actually occur during one of the scans earlier than the one where it is first reported As a the b1 values are about the LOCALGRANULEID metadata should have an extension NRT It is requested to identify the NRT to fill pixels affected by dead subframes with a special value Output the metadata of noisy and dead subframe Dead Subframe EV and Detector Quality Flag2 Removed the function call of Fill_Dead_Detector_SI to stop interpolating SI values for dead but also for all downstream products for science test only Changes from v5 which will affect scientific to conform to MODIS requirements Removed the Mixed option from the ScanType in the code because the L1A Scan Type is never Mixed Changed for ANSI C compliance and comments to better document the fact that when the HDF_EOS metadata is stricly the and products are off by and in the track respectively Corrected some misspelling of RCS swir_oob_sending_detector to the Reflective LUTs to enable the SWIR OOB correction detector so that if any of the sending detectors becomes noisy or non near by good detectors from the same sending band can be specified as the substitute in the new look up table Code change for adding an additional dimension of mirror side to the Band_21_b1 LUT to separate the coefficient of the two mirror sides for just like other thermal emissive so that the L1B code can calibrate Band scan to scan with mirror side dependency which leads better calibration result Changes which do not affect scientific when the EV data are not provided in this Crosstalk Correction will not be performed to the Band calibration data Changes which do not affect scientific and BB_500m in L1A Logic was added to turn off the or to spatial aggregation processes and the EV_250m_Aggr1km_RefSB and EV_500m_Aggr1km_RefSB fields were set to fill values when SDSs EV_250m and EV_500m are absent in L1A file Logic was added to skip the processing and turn off the output of the L1B QKM and HKM EV data when EV_250m and EV_500m are absent from L1A In this the new process avoids accessing and reading the and L1A EV skips and writing to the L1B and EV omits reading and subsampling SDSs from geolocation file and writing them to the L1B and omits writing metadata to L1B and EV and skips closing the L1A and L1B EV and SDSs Logic was added to turn off the L1B OBC output when the high resolution OBC SDSs are absent from L1A This is accomplished by skipping the openning of
Definition: HISTORY.txt:352
no change in intended resolving MODur00064 Corrected handling of bad ephemeris attitude resolving resolving GSFcd00179 Corrected handling of fill values for[Sensor|Solar][Zenith|Azimuth] resolving MODxl01751 Changed to validate LUT version against a value retrieved from the resolving MODxl02056 Changed to calculate Solar Diffuser angles without adjustment for estimated post launch changes in the MODIS orientation relative to incidentally resolving defects MODxl01766 Also resolves MODxl01947 Changed to ignore fill values in SCI_ABNORM and SCI_STATE rather than treating them as resolving MODxl01780 Changed to use spacecraft ancillary data to recognise when the mirror encoder data is being set by side A or side B and to change calculations accordingly This removes the need for seperate LUTs for Side A and Side B data it makes the new LUTs incompatible with older versions of the and vice versa Also resolves MODxl01685 A more robust GRing algorithm is being which will create a non default GRing anytime there s even a single geolocated pixel in a granule Removed obsolete messages from seed file
Definition: HISTORY.txt:413
