Support the Jupyter notebook of rotator duty cycle. The template is Rotator_NightObserving.ipynb. The plan is:

The execution of these tests will be done via a Jupyter notebook using our pointing component and scheduler.

Test 1 – Extreme conditions

Summary:
The idea of this test is to check different rapidly cycling the Rotator between “fast-tracking”, “slow-tracking”, tracking at different directions with big slews and small slews in between. These are conditions that will seldom occur during a regular observing night but are conditions we expect the rotator to be able to handle seamlessly.

Execution:

Start with rotator position in 0.

Track target with starting Rotator position -80 deg with velocity +0.01 deg/s for 30s.
Final position: ~ -79.5 deg (assumes ~0.2 deg of “tracking” during the time it takes to slew from 0 to -80).

Track target with starting Rotator position -80 deg with velocity +0.02 deg/s for 30s
Final position: ~ -79.4 deg (assuming slewing from -79.4 deg to -80 deg takes negligible amount of time).

Track target with starting Rotator position -80 deg with velocity -0.02 deg/s for 30s
Final position: ~-80.6 deg.

Track target with starting Rotator position -80 deg with velocity -0.01 deg/s for 30s
Final position: ~-80.3 deg.

Track target with starting Rotator position +80 deg with velocity +0.01 deg/s for 30s
Final position: ~+80.7 deg (assumes ~0.4 deg of “tracking” during the time it takes to slew from ~-80.3 to +80).

Track target with starting Rotator position +80 deg with velocity +0.02 deg/s for 30s
Final position: ~+80.6 deg.

Track target with starting Rotator position +80 deg with velocity -0.02 deg/s for 30s
Final position: ~+79.4 deg.
Track target with starting Rotator position +80 deg with velocity -0.01 deg/s for 30s
Final position: ~+ 79.7 deg.

Test 2 – Emulate filter change, tracking target with zero velocity between two targets.

Summary:
There are some conditions we expect to be able to track a target through the sky while not rotating. These will happen while doing filter changes and also during some mount tracking tests we may perform during commissioning. At the very least, the rotator must be able to track a non-moving target for 2 minutes without interruption, which is the approximate time it takes to perform a filter change.

Execution:

Start with rotator position in zero.

Track target with starting Rotator position -45 deg with velocity +0.02 deg/s for 30s
Final position: ~-44.2 deg (assumes ~0.2 deg of “tracking” during the time it takes to slew from 0 to -45, note the tracking speed here is twice the one used on the 0 to 80 degrees above, which is why the buffer is similar).

Track position 0 with velocity 0 for 2 minutes.

Track target with starting Rotator position +45 deg with velocity -0.02 deg/s for 30s.
Final position: ~+44.2 deg (again, assumes ~0.2 deg of “tracking” during the time it takes to slew from 0 to +45).

Test 3 – Execute a 2-8 hours regular observing campaign.

Summary:
Most of the time during operations the scheduler will be imaging a pack of the sky trying to keep the rotator close to a certain position. Basically we can assume it is going to “slew” the rotator to a certain position and, from there on, track and unwind the rotator constantly for hours on end. From the rotator perspective, this can be seen as something like:

Start with rotator position in zero.

Repeat 240 times (around 2 hours):
Track target with starting Rotator position around -0.3 deg and tracking velocity +0.01deg/s for 30s.