Scheduling RAIN1 Products
The Data Time that you specify when you schedule the product are quantized to the time value in the product configuration for the nearest interval that ends the integration.
For example, if you want to schedule a 60 minute RAIN1 product to integrate the precipitation in the hour from 11:00 to 12:00, set the time to 12:00. If the associated task is running at the end of an hour, the Product Scheduler waits for it to complete, so the task data can be included in the hour's integration.
Use the Skip Time field if you want only the accumulations for specific time intervals. You can set the skip time to any multiple of the accumulation period. For example, if you want a 3-hour integration only for the periods ending at 03:00, 06:00, 09:00, ..., set the Skip Time field to 03:00.
Set the Skip Time field to 01:00 so the RAIN1 product runs every hour. This is recommended because the RAIN1 product for multiple hour accumulations works best if there is a product every hour.
The RAIN1 product must wait for arrival of all the input CAPPIs during the accumulation period.
The trigger is the arrival of a CAPPI that is in the next accumulation period.
There are 2 cases that the product scheduler must handle, that is, the next hour CAPPI either arrives or it does not arrive. Note that in the time-line figures below:
- The horizontal line represents the data time, the time of the start of a volume scan.
- The
Crepresents an input CAPPI product. - The vertical bar represents an the next accumulation period.
Case 1: Normal Case: Next hour CAPPI Arrives
The RAIN1 product is run as soon as a CAPPI from the next accumulation interval arrives.
Case 2: Late Case: Next accumulation Interval CAPPI Does Not Arrive
The RAIN1 product
runs after the Tail and Wait times have elapsed from the
file arrival time of the last input CAPPI.
Tail is the time difference
between the data time of the last CAPPI and the next accumulation
period. The Wait time threshold is configured in IRIS , where you can configure a different value for cases with raingage inputs.
The Wait time threshold is tuned to account for any network delays.
