Task Configuration, Scheduling, and Synchronization

Passive IRIS must determine what the active system is doing and then follow along acquiring when data. The TASK Configuration and TSC Monitor menus must be configured for this to work.

Task Configuration

For each task run by the active system, you must configure a corresponding task to run on the passive system. For example, if the active system runs a volume scan, you must configure a corresponding volume scan in the passive system with the same elevation angles.

If the radar trigger is generated externally, you must configure the correct PRF. Note that dual PRF is not supported by passive IRIS when an external trigger is used. If the RVP generates the trigger, you can configure any allowed trigger including dual PRF.

For other signal processing, you can configure any processing option. While passive IRIS must scan the same as the active system, it can use different processing.

Task Scheduler

You must configure the TASK Scheduler with the same tasks that are run by the active system:

The tasks must be in the same order as they are run on the active system unless you are using Status–Slaving.
If your system can run in active or passive mode, set the Active/Passive menu selection at the top of the Task Scheduler to Passive.

Task Scheduler Synchronization (Passive type)

The following table shows how passive IRIS can synchronizes the task that it is running to the active control system.

Using the TSC Editor, you must configure the TSC Monitor with the same tasks that are run by the active system.

Task Schedule Methods
Method	Description	Supported Scans
Multi-Tasking	Passive IRIS tries to run the first task in the schedule. It waits until the PRF and the starting angle match the task configuration and then starts acquiring data for the task. Passive IRIS then waits for the PRF and angle for the 2nd task in the Scheduler and so on. If at any time it notices that the PRF and elevation angle are a better match for the start of a different task, then it interrupts to switch tasks. You may need to adjust the angle tolerances in Setup/ingest to tune the task so that it runs properly. For example, if the angles of the task are close together, the angle tolerance should be smaller than the angle spacing. Also, the antenna may not achieve the desired elevation angle, in which case it is better to modify the task in passive IRIS to match the actual rather than the nominal elevation angles.	Only continuous PPI scans
Single–Tasking	IRIS allows only one task to be scheduled in the task scheduler. IRIS waits until the PRF and the starting angles match the task configuration and then starts acquiring data for the task.	All scans including RHIs.
Status–Slaving	This case requires that a Status product be sent to the passive system. If the active system is another IRIS, the Status product on the active system is generated automatically whenever a task is starts and contains the name of the task that is currently running. When the passive system receives this, it starts (or continues running) the same task. The Status product must be configured to be output automatically over the network to the passive system.	All scans including RHIs.
TS–Playback	Used when trying to synchronize to old time series being played back via the tsarchive utility. Support is required by tsarchive and by the RVP processor. This is a variation of the Multi-Tasking mode. We assume that a single volume scan is being played back. This volume scan may be approximated in IRIS using a single task, multiple tasks, or a hybrid task. IRIS aggressively tries to remain synchronized to the sweeps of the original data. If a sweep ends before the full 360° is complete, IRIS immediately switches to the next to prevent losses at the start. If the sweep is filled before the data is complete, IRIS continues to read rays from the RVP. This is important to make sure that the next sweep does not start with the last few rays of the previous sweep.	Only continuous PPI scans