Summary
Design an ancillary file that allows the L3e processor to force recreation of L3e even if L3d hasn't changed
Requirements
Although this probably won't be a direct trigger for the GLOWS L3b-L3e processing (which are triggered daily), it should still be defined as an input in the dependency file.
Notionally I can see this is a simple list of products and what to reprocess -- for e, I think we want to support either CR or repointing? If we support b, c, d reprocessing in this approach, specify CR for b and c, and of course it's whole file for d.
l3e_survival-probability-lo repoint00245,repoint00246,cr02310
l3c_sw-profile cr02311
l3d_solar-hist
What I can't figure is how to make sure this only goes once. Two immediate options come to mind:
- Check the ingestion time of the ancillary file. Do the reprocessing if and only if this is less than 24 hours in the past
- Put an "expires" timestamp at the top of the ancillary file. Do the reprocessing if and only if current time is before the expiration
Notionally I'm thinking this is a file that we upload when we want to reprocess and it sits there forever until the next needed reprocessing, at which point we upload it with a new version. I don't think the start date makes much sense on this file, we could just choose something arbitrary.
Related tickets
#30, #43, #135
Summary
Design an ancillary file that allows the L3e processor to force recreation of L3e even if L3d hasn't changed
Requirements
Although this probably won't be a direct trigger for the GLOWS L3b-L3e processing (which are triggered daily), it should still be defined as an input in the dependency file.
Notionally I can see this is a simple list of products and what to reprocess -- for e, I think we want to support either CR or repointing? If we support b, c, d reprocessing in this approach, specify CR for b and c, and of course it's whole file for d.
What I can't figure is how to make sure this only goes once. Two immediate options come to mind:
Notionally I'm thinking this is a file that we upload when we want to reprocess and it sits there forever until the next needed reprocessing, at which point we upload it with a new version. I don't think the start date makes much sense on this file, we could just choose something arbitrary.
Related tickets
#30, #43, #135