2017 Winter Project Week/SlicerShape - Revision history

Bpaniagua: /* Key Investigators */

2017-01-21T19:08:00Z

Key Investigators

Jfishbaugh at 15:34, 13 January 2017

2017-01-13T15:34:43Z

Prisgdd at 15:22, 13 January 2017

2017-01-13T15:22:01Z

Bpaniagua: /* Project Description */

2017-01-13T13:59:00Z

Project Description

Bpaniagua at 13:56, 13 January 2017

2017-01-13T13:56:47Z

Jfishbaugh at 02:11, 13 January 2017

2017-01-13T02:11:15Z

Bpaniagua at 17:23, 12 January 2017

2017-01-12T17:23:31Z

Bpaniagua: /* Breakout session notes */

2017-01-11T16:57:23Z

Breakout session notes

Bpaniagua at 02:59, 11 January 2017

2017-01-11T02:59:44Z

Bpaniagua: /* Key Investigators */

2017-01-11T02:56:31Z

Key Investigators

@@ Line 17: / Line 17: @@
 * James Fishbaugh (NYU)
 * Priscille de Dumast (UofM)
 ==Project Description==

@@ Line 80: / Line 80: @@
 *** Girder has ways to submit jobs and save outputs into it  (Breakout session tomorrow)
 ==Background and References==
 <!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->

@@ Line 6: / Line 6: @@
 File:SlicerSALT_Dashboards.png
 File:Shape_regression_slicer.png
 <!-- Use the "Upload file" link on the left and then add a line to this list like "File:MyAlgorithmScreenshot.png" -->
 </gallery>

@@ Line 45: / Line 45: @@
 ** James
 ** Priscille
 |}

@@ Line 36: / Line 36: @@
+|
 <!-- Progress and Next steps bullet points (fill out at the end of project week) -->
-* Dashboard created.
+* Got started with setting up the testing infrastructure
 |}
 ==Breakout session notes==
@@ Line 47: / Line 52: @@
 * Slicer.org bridging with all Slicer customizations available
 ** We will need to change infrastructure of slicer.org to acknowledge all the different customized versions of the program. Bea will give this a go.
-** Tutorials, forums, mailinlists should be included there.
+** Tutorials, forums, mailing lists should be included there.
 * Architectural design decisions
@@ Line 69: / Line 74: @@
 *** Ron Kikinis' input is that Slicer is not really designed for not interactive things, but you can have non-interactive mode and run things
 *** Girder has ways to submit jobs and save outputs into it  (Breakout session tomorrow)

← Older revision		Revision as of 16:57, 11 January 2017
Line 43:		Line 43:
	==Breakout session notes==		==Breakout session notes==
	[https://docs.google.com/presentation/d/1CbddFklbMS-96CF0XJMZCA9o0MwXh2neo6fc-C6Ia7E/edit?usp=sharing Slides]		[https://docs.google.com/presentation/d/1CbddFklbMS-96CF0XJMZCA9o0MwXh2neo6fc-C6Ia7E/edit?usp=sharing Slides]
		+
		+	==Breakout session notes==
		+	[https://docs.google.com/presentation/d/1CbddFklbMS-96CF0XJMZCA9o0MwXh2neo6fc-C6Ia7E/edit?usp=sharing Slides]
		+
		+	* Slicer.org bridging with all Slicer customizations available
		+	** We will need to change infrastructure of slicer.org to acknowledge all the different customized versions of the program. Bea will give this a go.
		+	** Tutorials, forums, mailinlists should be included there.
		+
		+	* Architectural design decisions
		+	** Improving support for vtkMRMLModelNode.
		+	*** Visualization - Color maps, Surface pre-processing algorithms
		+	*** Support for 4D support - Sequences
		+	** New vtkMRML*Node classes
		+	** S-reps
		+
		+	* Improving user experience
		+	** Providing a lot of feedback to the user
		+	*** Quality of inputs and outputs
		+	*** Speed, computation time
		+	**** Obtain some sort of benchmarks of computational performance based on the OS requirements. kwsyslibrary can provide information of the program running. Another idea is to run a small subset of the batch processing and provide some information of how much did it take and how much the rest of the computation is going to take.
		+	**** The user's frustration comes from the unexpected time delay when you run a method (expecting 1 min, waiting 1 h) Slicer has progress bars (Andras Lasso) is saying progress bar have phases and we should use it. They have a preview for parameter tuning and then they run the long method (preview on small data)
		+	**** Running in separate process is good because you can kill the process anytime
		+
		+	* Thinking about the specific needs of the user base of slicerSALT
		+	** These methods take a lot of time to compute and usually involve a batch process
		+	*** Greg Sharp SlicerRT has a stand-alone tool that submits and logs jobs into Slicer
		+	*** Ron Kikinis' input is that Slicer is not really designed for not interactive things, but you can have non-interactive mode and run things
		+	*** Girder has ways to submit jobs and save outputs into it (Breakout session tomorrow)

← Older revision		Revision as of 02:59, 11 January 2017
Line 40:		Line 40:
	==Background and References==		==Background and References==
	<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->		<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->
		+
		+	==Breakout session notes==
		+	[https://docs.google.com/presentation/d/1CbddFklbMS-96CF0XJMZCA9o0MwXh2neo6fc-C6Ia7E/edit?usp=sharing Slides]

@@ Line 13: / Line 13: @@
 * Johan Andruejol (Kitware, Inc.)
 * JC Fillon-Robin (Kitware, Inc.)
 ==Project Description==