-
Notifications
You must be signed in to change notification settings - Fork 102
-
Notifications
You must be signed in to change notification settings - Fork 102
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
Volume reconstruction using the Epiphan frame grabber #407
Comments
It should be possible. What versions of Plus and Slicer are you using? |
I am using Slicer 4.8.1 and Plus Applications 2.6.0.2017-11-29 (Win32). The plus log doesn't give me any errors, which is why I thought it might just be ignoring it since I am not using an ultrasound device. I have attached the log below. |
Were you able to connect to the server in Slicer? The log doesn't show any connections. |
Yes I was able to, it connects and streams in the whole screen from the frame grabber. |
Is it possible that you uploaded the wrong log file? The log should have a line similar to this to show that Plus was connected to Slicer:
And one similar to this if the StartRecording command was received:
|
Reopen if still persisting. |
I was reading the volume reconstruction page for the PlusServer, and it mentions that it is to reconstruct a 2D ultrasound image to a 3D ultrasound image. I was wondering if it is specific to ultrasound systems. I am using the Epiphan frame grabber on a TEE ultrasound machine and the volume reconstruction isn't working. I am assuming this is due to the requirement of an ultrasound connection, but I was wondering if it is possible to do for the Epiphan device, or if there is any work around. I have attached my config file below in case there is any issues within the file, I have converted it to a txt file so that I am able to upload it here. Any help is appreciated. Thanks!
EpiphanPhilipsTEEVolumeReconstructionandTrackingtxt.txt
The text was updated successfully, but these errors were encountered: