|
ocssw
V2022
|
Typedefs | |
| using | Center = =====================LUN 800620 has been identified by SDST as the LUN to use for the metadata value "ProcessingCenter", which is to be read from the PCF file. Set this value to the location the data is processed, e.g. 800620|ProcessingCenter|MODAPS e.) Use the makefile to create the executable "MOD_PR02.exe". Optionally, remove old object files and executables:make clean -f MOD_PR02.mk Compile and link:make -f MOD_PR02.mk f.) Running the code:The name of the PCF file must be defined by the environment variable:PGS_PC_INFO_FILE Enter the command:MOD_PR02.exe 4. ENVIRONMENT VARIABLE:PGSINC defines directory for SDP toolkit headers HDFINC defines directory for HDF headers HDFEOS_INC defines directory for HDF-EOS headers CFLAGS defines compiler flags CC defines the C compiler PGSLIB defines directory for SDP toolkit library HDFLIB defines directory for HDF library HDFEOS_LIB defines directory for HDFEOS library HDF5INC defines directory for HDF5 headers HDF5LIB defines directory for HDF5 library SZIPHOME defines directory for SZIP compression library BRAND defines the operating system 5. MAPI:No M-API used. 6. HDF:HDF version 4.2r10 and HDF-EOS version 2.19 7. SDP TOOLKIT:SDP-Toolkit versions 5.2.19 8. This code was developed on the MCST computer server "luna", OS Linux version 3.10.0-514.6.1.el7.x86_64, 16 Intel(R) Xeon(R) CPU E7330 @ 2.40GHz gcc version 4.8.5 20150623(Red Hat 4.8.5-11) 9. ANCILLARY DATA:This code uses no ancillary data. 10.MODIS INPUT PRODUCTS:Three L1A(MOD_PR01) files, one Geolocation(MOD_PR03) file. See "MOD_PR02_pr.txt" for more details. 11.OTHER INPUTS:Three lookup table files(MOD02_Emissive_LUTs.hdf, MOD02_Reflective_ LUTs.hdf, and MOD02_QA_LUTs.hdf). See "MOD_PR02_pr.txt" for more details. 12.MODIS OUTPUT PRODUCTS:Four L1B(MOD_PR02) files(MOD021KM, MOD02HKM, MOD02QKM, and MOD02OBC). 13.PROBLEMS:None. 14.DELIVERY SIZE:Total size of untarred delivery is approximately 3535 MB. See PACKINGLIST for the information of files delivered. 15.OUTPUT FILE SIZE:Total size of expected output files(203 scans) is approximately 1838 MB. The stack size required is approximately 68 MB. 16.TESTS PERFORMED:The code has been tested with MODIS data collected on the Terra satellite which was processed by PGE01 at the Goddard DAAC. It runs to completion, producing the 4 L1B output files, and the outputs look reasonable. 17.EXIT CODES:0:normal end |
Variables | |
| README for MOD_PR02(TERRA) Version to | disable |
| README for MOD_PR02(TERRA) Version to set to For disabling creating and output data sets when in night | mode |
| README for MOD_PR02(TERRA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file | appropriately |
| README for MOD_PR02(TERRA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file LUN identifies the platform(Terra or Aqua). The value defined after the last "|" defines the satellite. For Terra | AM1M =Terra |
| README for MOD_PR02(TERRA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file LUN identifies the platform(Terra or Aqua). The value defined after the last "|" defines the satellite. For Terra | PM1M |
| README for MOD_PR02(TERRA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file LUN identifies the platform(Terra or Aqua). The value defined after the last "|" defines the satellite. For Terra set the value of ReprocessingActual to processed | once |
| README for MOD_PR02(TERRA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file LUN identifies the platform(Terra or Aqua). The value defined after the last "|" defines the satellite. For Terra set the value of ReprocessingActual to processed otherwise set to Near Real Time for NRT processing Set the value of ReprocessingPlanned to further update is anticipated Processing | Environment |
| __pad0__ | |
Typedef Documentation
◆ Center
| using Center = ===================== LUN 800620 has been identified by SDST as the LUN to use for the metadata value "ProcessingCenter", which is to be read from the PCF file. Set this value to the location the data is processed, e.g. 800620|ProcessingCenter|MODAPS e.) Use the makefile to create the executable "MOD_PR02.exe". Optionally, remove old object files and executables: make clean -f MOD_PR02.mk Compile and link: make -f MOD_PR02.mk f.) Running the code: The name of the PCF file must be defined by the environment variable: PGS_PC_INFO_FILE Enter the command: MOD_PR02.exe 4. ENVIRONMENT VARIABLE: PGSINC defines directory for SDP toolkit headers HDFINC defines directory for HDF headers HDFEOS_INC defines directory for HDF-EOS headers CFLAGS defines compiler flags CC defines the C compiler PGSLIB defines directory for SDP toolkit library HDFLIB defines directory for HDF library HDFEOS_LIB defines directory for HDFEOS library HDF5INC defines directory for HDF5 headers HDF5LIB defines directory for HDF5 library SZIPHOME defines directory for SZIP compression library BRAND defines the operating system 5. MAPI: No M-API used. 6. HDF: HDF version 4.2r10 and HDF-EOS version 2.19 7. SDP TOOLKIT: SDP-Toolkit versions 5.2.19 8. This code was developed on the MCST computer server "luna", OS Linux version 3.10.0-514.6.1.el7.x86_64, 16 Intel(R) Xeon(R) CPU E7330 @ 2.40GHz gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) 9. ANCILLARY DATA: This code uses no ancillary data. 10.MODIS INPUT PRODUCTS: Three L1A (MOD_PR01) files, one Geolocation (MOD_PR03) file. See "MOD_PR02_pr.txt" for more details. 11.OTHER INPUTS: Three lookup table files (MOD02_Emissive_LUTs.hdf, MOD02_Reflective_ LUTs.hdf, and MOD02_QA_LUTs.hdf). See "MOD_PR02_pr.txt" for more details. 12.MODIS OUTPUT PRODUCTS: Four L1B (MOD_PR02) files (MOD021KM, MOD02HKM, MOD02QKM, and MOD02OBC). 13.PROBLEMS: None. 14.DELIVERY SIZE: Total size of untarred delivery is approximately 3535 MB. See PACKINGLIST for the information of files delivered. 15.OUTPUT FILE SIZE: Total size of expected output files (203 scans) is approximately 1838 MB. The stack size required is approximately 68 MB. 16.TESTS PERFORMED: The code has been tested with MODIS data collected on the Terra satellite which was processed by PGE01 at the Goddard DAAC. It runs to completion, producing the 4 L1B output files, and the outputs look reasonable. 17.EXIT CODES: 0: normal end |
Definition at line 236 of file README.txt.
Variable Documentation
◆ __pad0__
| __pad0__ |
Definition at line 237 of file README.txt.
◆ AM1M
| README for MOD_PR02 (TERRA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file LUN identifies the platform (Terra or Aqua). The value defined after the last "|" defines the satellite. For Terra AM1M =Terra |
Definition at line 111 of file README.txt.
◆ appropriately
| README for MOD_PR02 (TERRA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file appropriately |
Definition at line 107 of file README.txt.
◆ disable
◆ Environment
| README for MOD_PR02 (TERRA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file LUN identifies the platform (Terra or Aqua). The value defined after the last "|" defines the satellite. For Terra set the value of ReprocessingActual to processed otherwise set to Near Real Time for NRT processing Set the value of ReprocessingPlanned to further update is anticipated Processing Environment |
Initial value:
======================
permissible, the SDP Toolkit issues error messages when it cannot find
the variable)
Definition at line 130 of file README.txt.
◆ mode
| README for MOD_PR02 (TERRA) Version to set to For disabling creating and output data sets when in night mode |
Definition at line 96 of file README.txt.
◆ once
| README for MOD_PR02 (TERRA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file LUN identifies the platform (Terra or Aqua). The value defined after the last "|" defines the satellite. For Terra set the value of ReprocessingActual to processed once |
Definition at line 126 of file README.txt.
◆ PM1M
| README for MOD_PR02 (TERRA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file LUN identifies the platform (Terra or Aqua). The value defined after the last "|" defines the satellite. For Terra PM1M |
Initial value:
the PCF.
Reprocessing Notes
==================
800605|ReprocessingActual|processed once
For forward processing
Definition at line 111 of file README.txt.
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 as required for compatibility with version of the SDP toolkit Corrected test output file names to end in per delivery and then split off a new MYD_PR03 pcf file for Aqua Added AssociatedPlatformInstrumentSensor to the inventory metadata in MOD01 mcf and MOD03 mcf Created new versions named MYD01 mcf and MYD03 where AssociatedPlatformShortName is rather than Terra The program itself has been changed to read the Satellite Instrument LUN
Definition: HISTORY.txt:441
a context in which it is NOT documented to do so subscript which cannot be easily calculated when extracting TONS attitude data from the Terra L0 files Corrected several defects in extraction of entrained ephemeris and and as HDF file for both the L1A and Geolocation enabling retrieval of South Polar DEM data Resolved Bug by changing to opent the geolocation file only after a successful read of the L1A metadata
Definition: HISTORY.txt:73
README for MOD_PR02AQUA(AQUA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file LUN identifies the platform(Terra or Aqua). The value defined after the last "|" defines the satellite. For Aqua AM1M
Definition: README.txt:111
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
HDF4 data type of the output SDS Default is DFNT_FLOAT32 Common types used are
Definition: HOWTO_Add_a_product.txt:67
this program makes no use of any feature of the SDP Toolkit that could generate such a then geolocation is calculated at that and then aggregated up to Resolved feature request Bug by adding three new int8 SDSs for each high resolution offsets between the high resolution geolocation and a bi linear interpolation extrapolation of the positions This can be used to reconstruct the high resolution geolocation Resolved Bug by delaying cumulation of gflags until after validation of derived products Resolved Bug by setting Latitude and Longitude to the correct fill resolving to support Near Real Time because they may be unnecessary if use of entrained ephemeris and attitude data is turned resolving bug report Corrected to filter out Aqua attitude records with missing status helping resolve bug MOD_PR03 will still correctly write scan and pixel data that does not depend upon the start thereby resolving MODur00108 Changed header guard macro names to avoid reserved name resolving MODur00104 Maneuver list file for Terra satellite was updated to include data from Jecue DuChateu Maneuver list files for both Terra and Aqua were updated to include two maneuvers from recent IOT weekly reports The limits for Z component of angular momentum was and to set the fourth GEO scan quality flag for a scan depending upon whether or not it occurred during one of them Added _FillValue attributes to many and changed the fill value for the sector start times from resolving MODur00072 Writes boundingcoordinate metadata to L1A archived metadata For PERCENT *ECS change to treat as
Definition: HISTORY.txt:297
this program makes no use of any feature of the SDP Toolkit that could generate such a then geolocation is calculated at that and then aggregated up to Resolved feature request Bug by adding three new int8 SDSs for each high resolution offsets between the high resolution geolocation and a bi linear interpolation extrapolation of the positions This can be used to reconstruct the high resolution geolocation Resolved Bug by delaying cumulation of gflags until after validation of derived products Resolved Bug by setting Latitude and Longitude to the correct fill resolving to support Near Real Time because they may be unnecessary if use of entrained ephemeris and attitude data is turned resolving bug report Corrected to filter out Aqua attitude records with missing status helping resolve bug MOD_PR03 will still correctly write scan and pixel data that does not depend upon the start thereby resolving MODur00108 Changed header guard macro names to avoid reserved name resolving MODur00104 Maneuver list file for Terra satellite was updated to include data from Jecue DuChateu Maneuver list files for both Terra and Aqua were updated to include two maneuvers from recent IOT weekly reports The limits for Z component of angular momentum was and to set the fourth GEO scan quality flag for a scan depending upon whether or not it occurred during one of them Added _FillValue attributes to many and changed the fill value for the sector start times from resolving MODur00072 Writes boundingcoordinate metadata to L1A archived metadata For PERCENT *ECS change to treat rather resolving GSFcd01518 Added a LogReport Changed to create the Average Temperatures vdata even if the number of scans is
Definition: HISTORY.txt:301
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
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 used
Definition: HISTORY.txt:408
a context in which it is NOT documented to do so subscript which cannot be easily calculated when extracting TONS attitude data from the Terra L0 files Corrected several defects in extraction of entrained ephemeris and and as HDF file for both the L1A and Geolocation enabling retrieval of South Polar DEM data Resolved Bug by changing to opent the geolocation file only after a successful read of the L1A and also by checking for fatal errors from not restoring C5 and to report how many of those high resolution values were water in the new WaterPresent SDS Added valid_range attribute to Land SeaMask Changed to bilinearly interpolate the geoid_height to remove artifacts at one degree lines Made corrections to const qualification of pointers allowed by new version of M API library Removed casts that are no longer for same not the geoid Corrected off by one error in calculation of high resolution offsets Corrected parsing of maneuver list configuration parameter Corrected to set Height SDS to fill values when geolocation when for elevation and land water through the PCF
Definition: HISTORY.txt:127
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 as required for compatibility with version of the SDP toolkit Corrected test output file names to end in per delivery and then split off a new MYD_PR03 pcf file for Aqua Added AssociatedPlatformInstrumentSensor to the inventory metadata in MOD01 mcf and MOD03 mcf Created new versions named MYD01 mcf and MYD03 where AssociatedPlatformShortName is Aqua
Definition: HISTORY.txt:439
README for MOD_PR03(V6.1.0) 2. POINTS OF CONTACT it can be either SDP Toolkit or MODIS Packet for Terra input files The orbit validation configuration because the validation criteria it uses are too strict for the low precision estimation methods we use in that mode The PGEVersion configuration or PM1M for Aqua data The ProcessingEnvironment configuration as executed in the processing environment The that would be reprocessed once and further update anticipated
Definition: README.txt:134
README for MOD_PR02(TERRA) Version to set to For disabling creating and output data sets when in night use the following files and set their names in the PCF file LUN identifies the platform(Terra or Aqua). The value defined after the last "|" defines the satellite. For Terra set the value of ReprocessingActual to processed once
Definition: README.txt:126
this program makes no use of any feature of the SDP Toolkit that could generate such a then geolocation is calculated at that and then aggregated up to Resolved feature request Bug by adding three new int8 SDSs for each high resolution offsets between the high resolution geolocation and a bi linear interpolation extrapolation of the positions This can be used to reconstruct the high resolution geolocation Resolved Bug by delaying cumulation of gflags until after validation of derived products Resolved Bug by setting Latitude and Longitude to the correct fill resolving to support Near Real Time because they may be unnecessary if use of entrained ephemeris and attitude data is turned resolving bug report Corrected to filter out Aqua attitude records with missing status helping resolve bug MOD_PR03 will still correctly write scan and pixel data that does not depend upon the start thereby resolving MODur00108 Changed header guard macro names to avoid reserved name resolving MODur00104 Maneuver list file for Terra satellite was updated to include data from Jecue DuChateu Maneuver list files for both Terra and Aqua were updated to include two maneuvers from recent IOT weekly reports The limits for Z component of angular momentum was and to set the fourth GEO scan quality flag for a scan depending upon whether or not it occurred during one of them Added _FillValue attributes to many and changed the fill value for the sector start times from to
Definition: HISTORY.txt:295
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 fields
Definition: HISTORY.txt:400
HISTORY txt for MOD_PR01(step one of PGE01) History follows the following convention needed due to new Aqua MCF
Definition: HISTORY.txt:150
===========================================================================V5.0.48(Terra) 03/20/2015 Changes shown below are differences from MOD_PR02 V5.0.46(Terra)============================================================================Changes noted for V6.1.20(Terra) below were also instituted for this version.============================================================================V6.1.20(Terra) 03/12/2015 Changes shown below are differences from MOD_PR02 V6.1.18(Terra)============================================================================Changes from v6.1.18 which may affect scientific output:A situation can occur in which a scan which contains sector rotated data has a telemetry value indicating the completeness of the sector rotation. This issue is caused by the timing of the instrument command to perform the sector rotation and the recording of the telemetry point that reports the status of sector rotation. In this case a scan is considered valid by L1B and pass through the calibration - reporting extremely high radiances. Operationally the TEB calibration uses a 40 scan average coefficient, so the 20 scans(one mirror side) after the sector rotation are contaminated with anomalously high radiance values. A similar timing issue appeared before the sector rotation was fixed in V6.1.2. Our analysis indicates the ‘SET_FR_ENC_DELTA’ telemetry correlates well with the sector rotation encoder position. The use of this telemetry point to determine scans that are sector rotated should fix the anomaly occured before and after the sector rotation(usually due to the lunar roll maneuver). The fix related to the sector rotation in V6.1.2 is removed in this version.============================================================================V6.1.18(Terra) 10/01/2014 Changes shown below are differences from MOD_PR02 V6.1.16(Terra)============================================================================Added doi attributes to NRT(Near-Real-Time) product.============================================================================V6.1.16(Terra) 01/27/2014 Changes shown below are differences from MOD_PR02 V6.1.14(Terra)============================================================================Migrate to SDP Toolkit 5.2.17============================================================================V6.1.14(Terra) 06/26/2012 Changes shown below are differences from MOD_PR02 V6.1.12(Terra)============================================================================Added the doi metadata to L1B product============================================================================V6.1.12(Terra) 04/25/2011 Changes shown below are differences from MOD_PR02 V6.1.8(Terra)============================================================================1. The algorithm to calculate uncertainties for reflective solar bands(RSB) is updated. The current uncertainty in L1B code includes 9 terms from prelaunch analysis. The new algorithm regroups them with the new added contributions into 5 terms:u1:the common term(AOI and time independent) and
Definition: HISTORY.txt:126
README for MOD_PR03(V6.1.0) 2. POINTS OF CONTACT it can be either SDP Toolkit or MODIS Packet for Terra input files The orbit validation configuration because the validation criteria it uses are too strict for the low precision estimation methods we use in that mode The PGEVersion configuration or PM1M for Aqua data The ProcessingEnvironment configuration as executed in the processing environment The ReprocessingActual(LUN 800600) and ReprocessingPlanned(LUN 800605) should be set to the values that should appear in the corresponding ECS metadata items of the same name. Typically
HISTORY txt for MOD_PR01(step one of PGE01) History follows the following convention needed due to new Aqua ReprocessingActual and the expected LUT revision number from PCF Changed to use PGE version for ProductionHistory Added Archive including ProcessingEnvironment Corrected handling of bad to resovle GSFcd02514 Changed to check staged LUT revision number versus the expected LUT revision number from thereby resolving defect report MODxl02056 This change also avoids the memory access violation reported in MODur00039 Changed the way output arrays were initialized with fill values
Definition: HISTORY.txt:162
Definition: names.f90:1
this program makes no use of any feature of the SDP Toolkit that could generate such a then geolocation is calculated at that and then aggregated up to Resolved feature request Bug by adding three new int8 SDSs for each high resolution offsets between the high resolution geolocation and a bi linear interpolation extrapolation of the positions This can be used to reconstruct the high resolution geolocation Resolved Bug by delaying cumulation of gflags until after validation of derived products Resolved Bug by setting Latitude and Longitude to the correct fill resolving to support Near Real Time because they may be unnecessary if use of entrained ephemeris and attitude data is turned resolving bug report Corrected to filter out Aqua attitude records with missing status helping resolve bug MOD_PR03 will still correctly write scan and pixel data that does not depend upon the start time
Definition: HISTORY.txt:248
PGE01 indicating that PGE02 PGE01 V6 for and PGE01 V2 for MOD03 were used to produce the granule By convention adopted in all MODIS Terra PGE02 code versions are even(e.g. 4.2.0, 5.6.8) and all MODIS/Aqua PGE02 code versions are odd(e.g. 4.2.1
README for MOD_PR03(V6.1.0) 2. POINTS OF CONTACT it can be either SDP Toolkit or MODIS Packet for Terra input files The orbit validation configuration because the validation criteria it uses are too strict for the low precision estimation methods we use in that mode The PGEVersion configuration or PM1M for Aqua data The ProcessingEnvironment configuration as executed in the processing environment The that would be reprocessed once and further update respectively In LANCE MODIS processing
Definition: README.txt:135
