Open yoshinori-0778 opened 3 months ago
Going to add another example here where SATp1 hit a sun safety error while setting up a Jupiter scan on the simple-sun
branch.
This error: https://site.simonsobs.org/satp1/nextline/db/runs/1321
Can be reproduced with the configuration below (except the offending scan is on line 379 instead of 349, difference just from now passing a state file).
# yaml loads iso format automatically into datetimes
t0: 2024-08-19T20:00:00+00:00
t1: 2024-08-20T20:00:00+00:00
t0_state_file: None
elevation: 60
boresight: 0
az_speed: 0.5
az_accel: 1.0
hwp_dir: True
stow_at_end: False
run_relock: False
cal_targets:
- source: saturn
# boresight: # if not specified, use scan boresight
elevation: 50
focus: 'ws4'
allow_partial: False
- source: jupiter
# boresight: # if not specified, use scan boresight
elevation: 48
focus: 'ws1,ws6'
allow_partial: True
az_branch: 270
- source: jupiter
# boresight: # if not specified, use scan boresight
elevation: 48
focus: 'ws1,ws2'
allow_partial: True
az_branch: 270
The error Katie reports here is actually a problem in the ACU agent. See https://github.com/simonsobs/socs/issues/744.
Yoshi's error still requires investigation.
When I make schedule including jupiter scan, I have an error below.
Scripts I am using are for satp3, but this problem should be common.
az_branch = 270
to calculate azimuth of rising jupiter above 360 deg (E.g., policy.add_cal_target(source=isource, boresight=0, elevation=iel, focus=ifocus, az_branch = 270))