2013 Summer Project Week:ProstateBRP - Revision history

Tokuda at 14:58, 21 June 2013

2013-06-21T14:58:44Z

2013-06-21T14:45:39Z

Key Investigators

2013-06-19T20:32:14Z

Protocol Definition

2013-06-19T20:29:11Z

Protocol Definition

2013-06-19T20:28:56Z

Protocol Definition

2013-06-19T04:18:08Z

Key Investigators

2013-06-17T17:33:05Z

Protocol Definition

2013-06-17T17:28:08Z

2013-06-17T17:13:48Z

2013-06-17T17:13:29Z

@@ Line 40: / Line 40: @@
 ***The query ID is used only for queries that requires strict 1-to-1 correspondence between query and reply. For queries that does not require it, we use a device name without ID. For example, querying current position or status does not, because we are always interested in the latest position/device status.
 </div>
 </div>

@@ Line 33: / Line 33: @@
 ***Navigation software can assume that the robot can handle the message exchange protocol only after getting acknowledgement message.
 **Need a message format specialized for for sending command?
-*�**Only missing feature we need is unique ID for query.
+**Only missing feature we need is unique ID for query.
 ***Changing device name is a good solution.
 ***Changing device name is actually ideal solution for Slicer, because when it receives messages with different name, it will create new MRML nodes and can make sure that it will not be overwritten.

@@ Line 45: / Line 45: @@
 ==Protocol Definition==
-[[ProstateBRP_OpenIGTLink_Communication]]
+[[ProstateBRP_OpenIGTLink_Communication_June_2013]]
 NOTE: THIS IS NOT THE FINAL VERSION. THE DEFINITION IS SUBJECT TO CHANGE.

← Older revision		Revision as of 20:28, 19 June 2013
Line 44:		Line 44:

	==Protocol Definition==		==Protocol Definition==
		+
		+	[[ProstateBRP_OpenIGTLink_Communication]]
		+
	NOTE: THIS IS NOT THE FINAL VERSION. THE DEFINITION IS SUBJECT TO CHANGE.		NOTE: THIS IS NOT THE FINAL VERSION. THE DEFINITION IS SUBJECT TO CHANGE.

← Older revision		Revision as of 04:18, 19 June 2013
Line 25:		Line 25:

	<h3>Progress</h3>		<h3>Progress</h3>
		+
		+	*Discussion on June 18
		+	**Greg, Andras, Junichi, Nirav, Csaba, Sebastian
		+	**Integrate the protocol for BRP and Kuka's lightweight robot?
		+	***It's not easy but could do per workphase
		+	***The idea is to define message exchange protocol per workphase. Developer can decide which workhpases is going to be used.
		+	***Navigation software can assume that the robot can handle the message exchange protocol only after getting acknowledgement message.
		+	**Need a message format specialized for for sending command?
		+	�*Only missing feature we need is unique ID for query.
		+	***Changing device name is a good solution.
		+	***Changing device name is actually ideal solution for Slicer, because when it receives messages with different name, it will create new MRML nodes and can make sure that it will not be overwritten.
		+	***Device name with unique query ID should be like: "CMD_12345" where "12345" is the unique query ID. The query ID does not have to be a numerical characters.
		+	***When reply to "CMD_" message, the device name for the reply message should be "ACK_12345"
		+	***The query ID is used only for queries that requires strict 1-to-1 correspondence between query and reply. For queries that does not require it, we use a device name without ID. For example, querying current position or status does not, because we are always interested in the latest position/device status.

	</div>		</div>

@@ Line 30: / Line 30: @@
 ==Protocol Definition==
-(This is not a master copy)
+NOTE: THIS IS NOT THE FINAL VERSION. THE DEFINITION IS SUBJECT TO CHANGE.
 {| border="1" cellpadding="5" cellspacing="0" align="center"
@@ Line 461: / Line 460: @@
 |}
 ==Delivery Mechanism==

@@ Line 5: / Line 5: @@
 ==Key Investigators==
-* WPI: Gregory Fischer
+* WPI: Gregory Fischer, Nirav Patel
 * BWH: Junichi Tokuda, Nobuhiko Hata, Clare Tempany
@@ Line 13: / Line 13: @@
 <h3>Objective</h3>
 *Define and review the clinical workflow
 *Test a new OpenIGTLink-based communication protocol for Slicer-Robot integration.
 </div>