2013 Summer Project Week:CLI Improvements - Revision history

Grundlett: Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

2017-07-10T17:36:58Z

Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

Lasso at 14:44, 24 June 2013

2013-06-24T14:44:32Z

Lasso at 14:11, 21 June 2013

2013-06-21T14:11:32Z

Lasso at 14:08, 21 June 2013

2013-06-21T14:08:55Z

Hans.meine: /* Key Investigators */

2013-06-17T19:52:26Z

Key Investigators

Lasso at 17:10, 12 June 2013

2013-06-12T17:10:42Z

Lasso at 17:08, 12 June 2013

2013-06-12T17:08:24Z

Pinter: Page created

2013-06-05T19:12:04Z

Page created

New page

__NOTOC__
<gallery>
Image:PW-MIT2013.png|[[2013_Summer_Project_Week#Projects|Projects List]]
</gallery>

==Key Investigators==
* Queen's: Csaba Pinter, Andras Lasso
* Kitware: Jean-Cristophe Fillion-Robin
* Isomics: Steve Pieper
*?

<div style="margin: 20px;">
<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Objective</h3>
Enhance the CLI interface to accommodate new needs:
* Add logic to put the output under the same hierarchy as the input (like in the case of Transforms)
* Hidden parameter containing the related nodes (CLI doesn't know about the whole scene)
* Extend XML syntax to specify roles

</div>

<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Approach, Plan</h3>

The approach is to enhance the CLI interface to accommodate new needs, related to processing nodes in a hierarchy, and to nodes having attributes.

The plan for the project week is to discuss the options and the best approach, and possibly start implementing.

</div>

<div style="width: 40%; float: left;">

<h3>Progress</h3>

*TODO: Discussion about the CLI interface improvements

</div>
</div>

==Delivery Mechanism==

This work will be delivered to the NA-MIC Kit as an enhancement in the CLI interface.

==References==
* Relevant ticket in the SlicerRT system: [https://www.assembla.com/spaces/slicerrt/tickets/165#/activity/ticket: #165]

@@ Line 55: / Line 55: @@
 ==References==
 * Relevant ticket in the SlicerRT system: [https://www.assembla.com/spaces/slicerrt/tickets/165#/activity/ticket: #165]
-* http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation
+* https://www.slicer.org/wiki/Slicer3:Execution_Model_Documentation

@@ Line 43: / Line 43: @@
 *** Time sequences (managed by hierarchies): node should be put back into the same timestep as the referenced node
 *** There should be a way for CLIs that are aware of hierarchies to override the default behavior and have access to information stored in the hierarchy (e.g., allow to retrieve th timestamps stored in the time hierarchy and allow the module to put the result into any timestamp)
 ** Potential solution: put the output node in the same location as the referenced node comes from, in all node hierarchies; pass the hierarchy information to the CLI module => how to implement?

← Older revision		Revision as of 17:10, 12 June 2013
Line 46:		Line 46:
	==References==		==References==
	* Relevant ticket in the SlicerRT system: [https://www.assembla.com/spaces/slicerrt/tickets/165#/activity/ticket: #165]		* Relevant ticket in the SlicerRT system: [https://www.assembla.com/spaces/slicerrt/tickets/165#/activity/ticket: #165]
		+	* http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation

@@ Line 9: / Line 9: @@
 * Isomics: Steve Pieper
 * MEVIS: Hans Meine
 <div style="margin: 20px;">

@@ Line 36: / Line 36: @@
 <h3>Progress</h3>
-*TODO: Discussion about the CLI interface improvements
+* Discussed about potential approaches for generalization of the "Reference" concept in CLIs
 </div>

@@ Line 8: / Line 8: @@
 * Kitware: Jean-Cristophe Fillion-Robin
 * Isomics: Steve Pieper
 *?

@@ Line 5: / Line 5: @@
 ==Key Investigators==
-* Queen's: Csaba Pinter, Andras Lasso
+* Queen's: Andras Lasso, Csaba Pinter
 * Kitware: Jean-Cristophe Fillion-Robin
 * Isomics: Steve Pieper