Closed yoshinori-0778 closed 1 month ago
I agree with Yoshi that sun-safe criteria are wrongly calculated for this. We have this error everyday recently, so this is relatively urgent. I guess sun-avoidance part is written by @mhasself, could you take a look?
I do not agree that Sun Safety is incorrectly applied here. el=60, az=180 is not safe at local noon (and won't be, for the next few months).
The "sun safe parking" code does not currently permit a change in elevation, for safe parking. That can presumably be added, but we need rules about what el moves are acceptable.
I also acknowledge that the error message could be more helpful -- and explain that the position is only safe until time X, or something ...
Thank you, we missed that.. For now, we will escape to el 50 manually, but we need "sun safe parking" to support the change of elevation.
I got error "ValueError("Sun-safe parking spot not found.")" when I try to produce a schedule that includes only CMB scan. This looks to related observation gap that is written as below. This was an output if we avoid this error by doing comment out of "raise ValueError("Sun-safe parking spot not found.")".
The output above looks fine in terms of the sun-avoidance.
I used latest main branch for both scheduler and scheduler-scripts scheduler: a4173fee02f43316f3036d2aa9380e132ded3a73 scheduler-scripts: a2dd0047f688b76046be6b21d5ed3c47c2c44a02
Used yaml file:
Output