-
Notifications
You must be signed in to change notification settings - Fork 105
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
Adaptation to parameter changes in PlusServer #121
Comments
2012-08-31 12:06 2012-08-31 12:23 If these attributes are not given, we can give a warning, and just send the any of the given ImageToProbe transforms for backwards compatibility. (In old config files, only one is given anyways.) 2012-08-31 12:49 I would suggest to use a different image stream for each depth (or any other configuration setting), because it is very hard (if not impossible) to synchronize multiple pipelines where information can abruptly change at anytime (you cannot interpolate between abrupt changes, so an infinitely small time difference can cause a large position change, etc.). We need to have a "master" configuration file anyway, so we can just as well (and for simplicity we should) store all information related to a procedure in one XML file. So, the proposed implementation:
2012-08-31 12:52
2012-08-31 12:59 Instead of changing the transform repository we can just let the switcher update the transform names. The switcher can easily do that by creating an alias in the transform repo: AxialPlaneToAxialPlaneDepth40=[identity]. 2012-08-31 13:14 2012-08-31 14:09 2013-06-05 14:00 2013-06-05 14:01 2013-06-05 14:24 2013-06-05 14:33 2013-06-05 14:48 2013-06-05 15:00 2013-06-05 17:01 2013-06-11 15:17 2013-06-18 14:39 adding reply status reporting in igt messages fixing crash in plus server 2013-06-18 17:02 2013-06-18 19:09 2013-06-24 15:04 2013-06-24 15:36 2013-06-24 16:00 2013-06-24 21:43 2013-06-27 13:09 2013-06-28 14:14 2013-06-28 14:22 2013-06-28 14:27 2013-06-28 14:50 2013-06-28 14:51 2013-06-28 14:56 2013-06-28 15:09 2013-06-28 15:29 2013-10-27 16:06 2013-10-28 08:52 |
@Sunderlandkyl @adamrankin Now that there is the Get/Set USImagingParameters framework, would it be possible to also add in support for changing imaging depth and other fields that include pixel spacing information since that would also be changing? I didn't know if what was discussed a long time ago in this thread was still relevant or if a new approach for imaging depth had been determined. Changing imaging depth quickly during simple live streaming would be very helpful, instead of having to stop the server and then restart with a different configuration file. Of course, I would never use it to change imaging depth during the middle of a recording, but I would change it prior to beginning various recordings. Update: I see that there is a Update2: I guess using |
See also #168 |
There are two options:
|
The depth is frequently changed during US-guided interventions. Since we have different ImageToProbe matrices for each depth, stored in different config files, the PlusServer should be restarted now at each change in depth. This takes unacceptably long time during interventions.
A possible solution: ImageToProbe matrices could be stored for every possible depth in one config file. PlusServer could always apply the one for the actual depth parameter.
Migrated from https://app.assembla.com/spaces/plus/tickets/582/details
The text was updated successfully, but these errors were encountered: