Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix positioner angle range checks. #267

Merged
merged 2 commits into from May 8, 2020
Merged

Fix positioner angle range checks. #267

merged 2 commits into from May 8, 2020

Conversation

tskisner
Copy link
Member

@tskisner tskisner commented May 7, 2020

This work:

  • Handles the case of arbitrary positioner theta / phi
    offsets and min / max.

  • Adds a unit test which attempts to move every positioner
    to a circle of spots halfway from the center to the patrol
    radius. It also verifies intended failure in the case of
    restricted phi range.

Attached are plots of "unreachable targets" computed by taking uniform random RA / DEC points with a density of 50K per sq. deg. and computing the targets available for each positioner. Then these available targets were removed from the input sample and the remaining targets were plotted. Starting with the old legacy focalplane model (with equal 3mm arm lengths) you can see good coverage across the patrol radius. With the more realistic focalplane, you can see some unreachable targets near the center of each positioner and more around the edge of the patrol radius due to varying arm lengths. The final plot shows the commissioning focalplane with restricted phi range. Compare these plots to the ones in #266.

Note to @Srheft and @djschlegel , the current master branch did NOT apply the phi angle restriction correctly, which means that previous runs did not limit the phi range properly. This likely explains why you were assigning targets that were then rejected by the online system. This is now fixed, as you can see in the plots.

unreachable_2012-06-01
unreachable_2020-01-01
unreachable_2020-04-01

Closes #266.

This work:

  - Handles the case of arbitrary positioner theta / phi
    offsets and min / max.

  - Adds a unit test which attempts to move every positioner
    to a circle of spots halfway from the center to the patrol
    radius.  It also verifies intended failure in the case of
    restricted phi range.
@tskisner tskisner requested review from sbailey and forero May 7, 2020 21:14
@tskisner tskisner self-assigned this May 7, 2020
@Srheft
Copy link
Contributor

Srheft commented May 7, 2020

@tskisner wow! I'm going to compare the new run of the same observed tiles with the the ones passed to ICS on the nights of 14th and 15th and see if we can spot the rejected cases in difference between these two runs. Thanks much!

@michaelJwilson
Copy link
Contributor

Given that some of the online ics feedback was lost, is it possible to rerun the assignments and deduce what fibers should have been reported? Or is this not relevant / the case anymore.

Copy link
Contributor

@sbailey sbailey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, though I haven't checked in detail (mainly trusting the new unit test and plots Ted put in the PR). Double checks from others actually running the code would be welcome.

@forero
Copy link
Member

forero commented May 8, 2020

I am running the code. Just give me one more hour to inspect the results.

@tskisner
Copy link
Member Author

tskisner commented May 8, 2020

@forero , of course, no problem.

Copy link
Member

@forero forero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I ran some tests on the DR8 data I have been using so far. Everything looks great.

@tskisner
Copy link
Member Author

tskisner commented May 8, 2020

Ok, I'll update the changelog and then merge.

@tskisner tskisner merged commit e58fbe9 into master May 8, 2020
@tskisner tskisner deleted the issue_266 branch May 8, 2020 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect effective positioner angles
5 participants