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

Buffer size and data type change during Image Acquisition #444

Open
savassif opened this issue Feb 9, 2024 · 3 comments
Open

Buffer size and data type change during Image Acquisition #444

savassif opened this issue Feb 9, 2024 · 3 comments

Comments

@savassif
Copy link

savassif commented Feb 9, 2024

Describe the Issue
I have been trying to implement a data acquisition pipeline for the SPECIM FX series cameras, using the harvesters API. By utilizing the Matrix Vision GenTL producer, I was able to connect to the camera (FX-17), set parameters like FPS, Exposure, etc and capture one scan.

The expected output for the buffer is 640x224, as the spatial resolution of the camera is 640pixel and the specrtal resolution is 224 bands (which are encoded as columns by the camera). When I try to create a while loop to capture multiple frames, the first 198 frames are captured as expected, and the buffer is of size 640x224 with PixelFormat Mono12Packed. However, after that and for the rest of the loop the buffer size changes to 463x463 and the PixelFormat also changes to Mono8

Sample Code

h = Harvester()
h.add_file(r'C:\Users\savvas\Baluff\bin\x64\mvGenTLProducer.cti')
h.update()

ia = h..create()
ia.start()
for i in range(300):
  with ia.fetch() as buffer:
     print(i, ' : ', buffer)
ia.stop()

Configuration

  • OS: Windows10
  • Python: 3.8
  • Harvester: 1.4.2
  • Camera: SPECIM FX-17
@yaraslau-neolithics
Copy link

yaraslau-neolithics commented Mar 22, 2024

Hello, @savassif. What mvGenTLProducer version are using? I had the same problem with 3.0.0 version. Rollbacked to 2.46.2 and it worked. Try it out as well

upd: 2.50.1 version works as well.

@eli-osherovich
Copy link

Can this explain the behavior?

@jeffwitz
Copy link

Can this explain the behavior?

Yes it is the issue #451 I just raised.

I will try with Stemmer in order to see if it works without licence.

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

No branches or pull requests

4 participants