Changes between Version 6 and Version 7 of ticket/370/ticket/370/TicketDetails/OpsReadFromObstore


Ignore:
Timestamp:
Aug 12, 2019 3:17:42 PM (13 days ago)
Author:
Jin Lee
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/370/ticket/370/TicketDetails/OpsReadFromObstore

    v6 v7  
    1515Another way is to let Ops_CreateODB read the obstore and then write out ODB1; then let Ops_ExtractAndProcess read ODB1 and then write back to ODB1. This method should be used as it produces updated ODB1 which can be used by VER. Here's a list of things to keep in mind when running Ops_ExtractAndProcess this way:
    1616
    17    * make sure `maxbatchessubtype` is set to a high enough number to be able to read all the batches in a obstore file
     17   * make sure `maxbatchessubtype` is set to a high enough number to be able to read all the batches in a obstore file. If all the data are not read in then you will see in stdout something like, `More batches of AMSR2 data are available but batch 21 is the Final batch.`
    1818
    1919One difficulty when using the second method is that it's hard to know whether OPS retrieved all the data from an obstore file correctly. To make sure that all data are retrieved use the first method and then put together the app config file using the second method while comparing the log output.