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

Tracking Updates #355

Merged
merged 2 commits into from
Jan 16, 2018
Merged

Tracking Updates #355

merged 2 commits into from
Jan 16, 2018

Conversation

wtgee
Copy link
Member

@wtgee wtgee commented Jan 15, 2018

  • Wait for the Dec axis to move before moving RA axis
  • Only update tracking if > 50ms correction
  • Some long line clean up

Note: Most of this update_tracking code should move into the mount
class and accept current_offset_info as a param

Corrects for small adjustments as reported in #351
Relates to #350

* Wait for the Dec axis to move before moving RA axis
* Only update tracking if > 50ms correction
* Some long line clean up

Note: Most of this `update_tracking` code should move into the mount
class and accept `current_offset_info` as a param
@wtgee wtgee requested a review from a team January 15, 2018 21:54
@codecov
Copy link

codecov bot commented Jan 15, 2018

Codecov Report

Merging #355 into develop will increase coverage by 0.14%.
The diff coverage is 37.93%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop     #355      +/-   ##
===========================================
+ Coverage    82.97%   83.11%   +0.14%     
===========================================
  Files           51       51              
  Lines         3441     3452      +11     
  Branches       438      442       +4     
===========================================
+ Hits          2855     2869      +14     
+ Misses         441      432       -9     
- Partials       145      151       +6
Impacted Files Coverage Δ
pocs/observatory.py 83.57% <37.93%> (-1.58%) ⬇️
pocs/state/states/default/pointing.py 87.75% <0%> (ø) ⬆️
pocs/utils/rs232.py 88.49% <0%> (+8.84%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6cf0028...7fd74cd. Read the comment docs.

@@ -148,12 +149,15 @@ def status(self):
status['observation']['field_ha'] = self.observer.target_hour_angle(
t, self.current_observation.field)

evening_astro_time = self.observer.twilight_evening_astronomical(t, which='next')
Copy link
Contributor

Choose a reason for hiding this comment

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

What does next produce if at midnight? Tomorrow night?

Copy link
Member Author

Choose a reason for hiding this comment

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

Correct. The default is nearest, which would go backwards. With next we always get the upcoming.

@@ -316,36 +320,48 @@ def update_tracking(self):
else:
ra_direction = 'east'

Copy link
Contributor

Choose a reason for hiding this comment

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

Could you add some more explanation to the docstring, for those of us who are ignorant of mounts. For example, what does 50 milliseconds measure here? An angle? A time?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, will add.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done. I'm going to merge but let me know if docstring doesn't make sense. I'd like to test these additions on PAN001 tonight.

@wtgee wtgee merged commit d4fc8ed into panoptes:develop Jan 16, 2018
@wtgee wtgee deleted the tracking-adjustments branch January 16, 2018 05:35
This was referenced Jan 18, 2018
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.

2 participants