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

Camera IO update #165

Merged
merged 8 commits into from
Oct 9, 2024
Merged

Conversation

braden6521
Copy link
Collaborator

  • Fixed ImageAcquisition class to work with new generation of Basler cameras.
  • Updated documentation in existing examples
  • Created new examples.

@braden6521 braden6521 added the bug Something isn't working label Aug 29, 2024
@braden6521 braden6521 self-assigned this Aug 29, 2024
Copy link
Collaborator

@e10harvey e10harvey left a comment

Choose a reason for hiding this comment

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

@braden6521: Please add some documentation for the hard coded values. Also, where are the tests for ImAgeAcquisition_DCAM_mono?

@@ -104,7 +110,9 @@ def instance_matches(self, possible_matches: list[ImageAcquisitionAbstract]) ->
def get_frame(self) -> np.ndarray:
# Start frame capture
self.cap.StartGrabbingMax(1)
grabResult = self.cap.RetrieveResult(5000, pylon.TimeoutHandling_ThrowException)
grabResult = self.cap.RetrieveResult(
int(self.cap.ExposureTimeRaw.Max / 1000 * 1.5), pylon.TimeoutHandling_ThrowException
Copy link
Collaborator

Choose a reason for hiding this comment

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

Please add quick documentation for 1000 * 1.5

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good call, it's documented now.

@braden6521
Copy link
Collaborator Author

@e10harvey, this is another tricky case in terms of unit testing we don't have a good solution for. To test this piece of code, we need a camera and network card physically connected to the computer. In fact, we have no tests for: ImageAcquisition_DCAM_color, ImageAcquisition_DCAM_mono, or ImageAcquisition_MSMF because these all require hardware present. These classes (in addition to all GUIs) are not tested currently.

Our solution up to this point has been to have a test for ImageAcquisitionAbstract (in ocmmon/lib/camera/test). Any suggestions are welcome.

@e10harvey
Copy link
Collaborator

@e10harvey, this is another tricky case in terms of unit testing we don't have a good solution for. To test this piece of code, we need a camera and network card physically connected to the computer. In fact, we have no tests for: ImageAcquisition_DCAM_color, ImageAcquisition_DCAM_mono, or ImageAcquisition_MSMF because these all require hardware present. These classes (in addition to all GUIs) are not tested currently.

Our solution up to this point has been to have a test for ImageAcquisitionAbstract (in ocmmon/lib/camera/test). Any suggestions are welcome.

Ok, let's get this merged. We can setup a machine with the physical hardware needed to test this. I filed: #174

@e10harvey e10harvey merged commit 90d7e13 into sandialabs:develop Oct 9, 2024
4 checks passed
@braden6521 braden6521 deleted the camera_io_update branch December 6, 2024 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants