Start and stop volume reconstruction from the Slicelet

[tdowrick]

In GitLab by @AnastasisGeorgoulas on Feb 26, 2019, 15:18

The Slicelet should have a button that instructs the PLUS Server to start recording US images in order to do a volume reconstruction. Pressing it again should stop the recording, and retrieve the constructed volume.

This would involve:

• [x] Adding a button to the GUI layout
• [x] Figuring out how to send PLUS instructions to start/stop (this may be useful)
• [ ] Adding the button logic and the connection to the PLUS Server

[tdowrick]

In GitLab by @AnastasisGeorgoulas on Feb 26, 2019, 15:31

assigned to @AnastasisGeorgoulas

[tdowrick]

In GitLab by @AnastasisGeorgoulas on Mar 4, 2019, 09:47

mentioned in merge request !6

[tdowrick]

In GitLab by @DavidPerez-Suarez on Mar 18, 2019, 10:21

marked the task Adding a button to the GUI layout as completed

[tdowrick]

In GitLab by @DavidPerez-Suarez on Mar 18, 2019, 10:21

marked the task Figuring out how to send PLUS instructions to start/stop (this may be useful) as completed

[tdowrick]

In GitLab by @DavidPerez-Suarez on Mar 18, 2019, 10:30

• Possibly adding quick/detailed recording buttons, but we don't know whether that's the best way for the reconstruction
• Temporal calibration could be ok if using PLUS to calibrate. Right now the pyIGTLink sends "now" as the time it gets the image. There will be a delay, from the acquisition.

[tdowrick]

In GitLab by @AnastasisGeorgoulas on Apr 11, 2019, 14:35

The volume containing the live reconstruction results is called _1, _2 by default. This should be changed to something more meaningful, although it is not clear exactly how to control this. In both the PLUS config and the code for sending the reconstruction command, we specify the device name from which the reconstructed volume is sent. I had assumed that the name of the volume would match that, but it seems that is not the case. Instead, we can try the following:

1. Don't the volume automatically on completion of the reconstruction
2. Save the volume to a file at completion instead
3. Load the volume into Slicer from the file (presumably we can choose the volume name at this point)

[tdowrick]

In GitLab by @ThomasDowrick on May 15, 2019, 15:12

Going to close this, as we have implemented this by including the 'standard' Slicer GUI elements for reconstruction in the slicelet.

[tdowrick]

In GitLab by @ThomasDowrick on May 15, 2019, 15:12

closed