-
Notifications
You must be signed in to change notification settings - Fork 103
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
Problem: fCal calibration using Clarius (temporal calibration crashes) #850
Comments
Can you provide more information?
|
Thank you in advance. Regards |
The issue seems to be with the connection to the Clarius device itself. I'll see if I can track down the one of the probes in our lab. |
Thank you |
Previously the Clarius cast device acquired images in BGRA32 format. Images are now acquired grayscale by default, however RGB24 images can be acquired by setting ImageType="RGB_COLOR" (for use in color Doppler). Also fixed an error message if the destructor was called without device initialization. Re #850
@joaolgfonseca I've made the Clarius images grayscale by default and fixed an issue so that fCal won't crash even if it is streaming color images. It should be available in the nightly package tomorrow. |
Previously the Clarius cast device acquired images in BGRA32 format. Images are now acquired grayscale by default, however RGB24 images can be acquired by setting ImageType="RGB_COLOR" (for use in color Doppler). Also fixed an error message if the destructor was called without device initialization. Re #850
Dear all,
I am interested in using fCal app to calibrate the Clarius ultrasound probe with a tracker device.
I was able to initialize the configuration file with fCal app, however when I tried to get access to "temporal calibration" fCal crashes (i.e., this happened immediately when I clicked in the tab). Sometimes, a memory error appeared, mentioning that it was unable to write. I tried several times and changed several settings in the configuration file without success.
Have you ever got this problem?
Best regards,
João Fonseca
The text was updated successfully, but these errors were encountered: