You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During I&T, we noticed that there is not enough information writes out to the log and had hard time to debug for DSWx-S1 job submission.
Describe the feature request
We want to add following information to the logs for RTC query/download jobs to trigger DSWx-S1 sciflo jobs.
For a given query, what inputs were seen. We have this in GRQ, but I think having that in the logs would also be useful, especially if it’s easily searchable.
E.g. for the FWD queries, this would show the inputs with revision IDs in the query window.
For a given query, which TileSets were considered (based on the inputs seen from the previous point)
Also list out which TileSets were triggered for PGE jobs, along with the reason (e.g. 100% of bursts found, or X% bursts found, and we reached the wait time threshold)
Also list out which TileSets were NOT triggered for PGE jobs, along with the reason
Reasons would include things like: “only x% bursts found (less than the X% threshold)“, or “x% of bursts found (surpassing X% threshold, but <100%), but waiting n more hours (out of N)“, etc.
The text was updated successfully, but these errors were encountered:
Checked for duplicates
Yes - I've already checked
Alternatives considered
No - I haven't considered
Related problems
During I&T, we noticed that there is not enough information writes out to the log and had hard time to debug for DSWx-S1 job submission.
Describe the feature request
We want to add following information to the logs for RTC query/download jobs to trigger DSWx-S1 sciflo jobs.
E.g. for the FWD queries, this would show the inputs with revision IDs in the query window.
Also list out which TileSets were triggered for PGE jobs, along with the reason (e.g. 100% of bursts found, or X% bursts found, and we reached the wait time threshold)
Also list out which TileSets were NOT triggered for PGE jobs, along with the reason
Reasons would include things like: “only x% bursts found (less than the X% threshold)“, or “x% of bursts found (surpassing X% threshold, but <100%), but waiting n more hours (out of N)“, etc.
The text was updated successfully, but these errors were encountered: