Developer Meetings/20170523 - Revision history

JChris.FillionR: /* Conclusion */

2017-05-23T14:36:56Z

Conclusion

JChris.FillionR: /* Conclusion */

2017-05-23T14:36:32Z

Conclusion

JChris.FillionR at 14:29, 23 May 2017

2017-05-23T14:29:27Z

JChris.FillionR at 14:20, 23 May 2017

2017-05-23T14:20:10Z

JChris.FillionR: /* To Discuss */

2017-05-23T13:30:26Z

To Discuss

JChris.FillionR: /* To Discuss */

2017-05-23T13:29:54Z

To Discuss

JChris.FillionR: Created page with "{{mbox | type = style | text = If you would like to list your topic here, create a wiki account and [{{fullurl:{{FULLPAGENAME}}|action=edit}} edit this p..."

2017-05-23T13:29:06Z

Created page with "{{mbox | type = style | text = If you would like to list your topic here, create a wiki account and [{{fullurl:{{FULLPAGENAME}}|action=edit}} edit this p..."

New page

{{mbox
| type = style
| text = If you would like to list your topic here, [[Special:UserLogin|create a wiki account]] and [{{fullurl:{{FULLPAGENAME}}|action=edit}} edit this page]<br>You can join the hangout using http://bit.ly/slicer-hangout-kw.
| image= [[File:smile.png|40px]]
}}
<br>

= Update =
* NA

= To Discuss =
* TBD

= Conclusion =

@@ Line 22: / Line 22: @@
 ** Default behavior: if context is not known. Secondary capture seems to be the only valid approach.
 ** Moving toward consolidating tool around DCMTK
-** David Clunie has implementation in Java. See http://www.dclunie.com/pixelmed/software/webstart/DicomCleanerUsage.html
+** Anonymization: David Clunie has implementation in Java. See http://www.dclunie.com/pixelmed/software/webstart/DicomCleanerUsage.html
 ** [https://github.com/dgobbi/vtk-dicom/ vtk-dicom] from David Gobbi is nice. Issue is that it introduces dependency on VTK for tools that  wouldn't require it (e.g CLI) + VTK doesn't handle orientation (by default) in its core image data structure
 ** DCMTK: currently support only to create secondary capture

@@ Line 22: / Line 22: @@
 ** Default behavior: if context is not known. Secondary capture seems to be the only valid approach.
 ** Moving toward consolidating tool around DCMTK
-** David Clunie has implementation in Java (Steve: see link ?)
+** David Clunie has implementation in Java. See http://www.dclunie.com/pixelmed/software/webstart/DicomCleanerUsage.html
 ** [https://github.com/dgobbi/vtk-dicom/ vtk-dicom] from David Gobbi is nice. Issue is that it introduces dependency on VTK for tools that  wouldn't require it (e.g CLI) + VTK doesn't handle orientation (by default) in its core image data structure
 ** DCMTK: currently support only to create secondary capture

← Older revision		Revision as of 14:29, 23 May 2017
Line 26:		Line 26:
	** DCMTK: currently support only to create secondary capture		** DCMTK: currently support only to create secondary capture
	** DCMQI: support to create seg object		** DCMQI: support to create seg object
		+
		+	* Public repo with collection of DICOM
		+	** During last project week, discussed use of IPFS to store medical test data (DICOM, ...)
		+	** Stored at MIT, Bremen, Standford, ...
		+	** You can contribute without being the central server
		+	** It is easy to start an IPFS server .. but required to throttle the network to avoid full use of network
		+	** IPFS vs WebTorrent:
		+	*** WebTorrent is javascript implementation and require a tab open
		+	*** IPFS: Distributed hash table of encrypted chunk of data

← Older revision		Revision as of 14:20, 23 May 2017
Line 14:		Line 14:

	= Conclusion =		= Conclusion =
		+	* slicer.org on GitHub
		+	** It makes sense to store website on GitHub and have it served from Digital Ocean (or legacy server)
		+	** Waiting final transition to server is done, cronjob
		+
		+	* ITK: What ITK should create ?
		+	** Thin wrapper around DCMTK
		+	** Default behavior: if context is not known. Secondary capture seems to be the only valid approach.
		+	** Moving toward consolidating tool around DCMTK
		+	** David Clunie has implementation in Java (Steve: see link ?)
		+	** [https://github.com/dgobbi/vtk-dicom/ vtk-dicom] from David Gobbi is nice. Issue is that it introduces dependency on VTK for tools that wouldn't require it (e.g CLI) + VTK doesn't handle orientation (by default) in its core image data structure
		+	** DCMTK: currently support only to create secondary capture
		+	** DCMQI: support to create seg object

@@ Line 11: / Line 11: @@
 = To Discuss =
 * Use of GDCM vs DCMTK in Slicer
 = Conclusion =