-
Notifications
You must be signed in to change notification settings - Fork 49
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
Observation current_exp change #668
Conversation
This is now just a count of the `exposure_list`, which means we don't need to do specific bookkeeping. Adds a change to actually reset `exposure_list` when `reset` is called.
…nt_exp-from-list
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look like good changes, but tests seem to be consistently hanging in test_run_complete
(I ran them again to check).
One of those frustrating blocks on |
…nt_exp-from-list
…nt_exp-from-list
This is hanging every time in the |
@@ -157,10 +164,10 @@ def last_exposure(self): | |||
################################################################################################## | |||
|
|||
def reset(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be great if this method were called by __init__
, so that they can't get out of sync.
@@ -127,6 +125,15 @@ def directory(self): | |||
self.field.field_name) | |||
return self._directory | |||
|
|||
@property | |||
def current_exp_num(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if we're currently taking another exposure? Is that counted or not?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This value will go up inside the camera.take_observation
method but before the call to take_exposure
. So yes, the current_exp_num will reflect an image in the process of being taken.
@@ -27,7 +27,6 @@ def on_enter(event_data): | |||
pocs.logger.warning("Problem with imaging: {}".format(e)) | |||
pocs.say("Hmm, I'm not sure what happened with that exposure.") | |||
else: | |||
pocs.observatory.current_observation.current_exp += 1 | |||
pocs.logger.debug('Finished with observing, going to analyze') | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drop the blank line?
…nt_exp-from-list
The hang here is coming from the camera simulator trying to use the same image each time. On my local I now get:
and it loops forever. Will work on getting a fix for it. Will be somewhat related to other camera tests. |
Regarding test_run_complete, I can't help but note the // (double slash) in the paths. Fixing that probably won't help... but might! |
Both you and @AnthonyHorton pointed it out so I would be a fool to ignore fixing it! Edit: #680 |
…nt_exp-from-list
…nt_exp-from-list
…nt_exp-from-list
…nt_exp-from-list
If image upload fails give an error in logs but don't otherwise stop
…nt_exp-from-list
Codecov Report
@@ Coverage Diff @@
## develop #668 +/- ##
===========================================
- Coverage 77.92% 77.69% -0.23%
===========================================
Files 61 61
Lines 5069 5080 +11
Branches 695 697 +2
===========================================
- Hits 3950 3947 -3
- Misses 910 921 +11
- Partials 209 212 +3
Continue to review full report at Codecov.
|
Changed to
current_exp_num
to be more consistent.This is now just a count of the
exposure_list
, which means we don't need to do specific bookkeeping.Adds a change to actually reset
exposure_list
whenreset
is called.