CTK-Hackfest-Feb-2011 - Revision history

Finetjul: /* Agenda */ Add diner plans

2011-02-14T17:01:42Z

Agenda: Add diner plans

← Older revision		Revision as of 13:01, 14 February 2011
Line 242:		Line 242:
	== Agenda ==		== Agenda ==
	* Sunday		* Sunday
	** 1800: Dinner at Kildare's Irish Pub (Across the street from the hotel)		** 1800: Superbowl: Dinner at Kildare's Irish Pub (Across the street from the hotel)
	*** http://www.kildarespub.com/history.htm		*** http://www.kildarespub.com/history.htm
	* Monday		* Monday
	** 0900 - 1000: Welcome and Project overviews and goals		** 0900 - 1000: Welcome and Project overviews and goals
	** 1000 - 1800: Hacking		** 1000 - 1800: Hacking
			** Diner: Mama Dips (Southern)
	* Tuesday		* Tuesday
	** 0900 - 1800: Hacking		** 0900 - 1800: Hacking
	** 1800: "Pint Night" at Tyler's Bar and Grill		** 1800: "Pint Night" at Tyler's Bar and Grill
			** Diner: Los Potrillos (Mexican)
	* Wednesday		* Wednesday
	** 0900 - 1800: Hacking		** 0900 - 1800: Hacking
			** 21:30: Duke vs. UNC: The Cave (bar & pool)
	* Thursday		* Thursday
	** 0900 - 1800: Hacking		** 0900 - 1800: Hacking
			** Diner: Mediterranean Deli (J2's favorite)
	* Friday		* Friday
	** 0900 - 1200: Project reviews and future plans		** 0900 - 1200: Project reviews and future plans

Pieper: /* End User Functionality */

2011-02-14T12:35:41Z

End User Functionality

← Older revision		Revision as of 08:35, 14 February 2011
Line 193:		Line 193:
	** import dicom files from disk (optionally copy files to library directory)		** import dicom files from disk (optionally copy files to library directory)
	** view local database directory in embedded viewer		** view local database directory in embedded viewer
			** selecting series in tree view populates thumbnails for that series
			** selecting image in tree view displays it in viewer
	* Query/Retrieve		* Query/Retrieve
	** use a query dialog to access remote dicom resources (PACS, scanners, etc)		** use a query dialog to access remote dicom resources (PACS, scanners, etc)

Pieper: /* Major Classes */

2011-02-14T12:33:44Z

Major Classes

← Older revision		Revision as of 08:33, 14 February 2011
Line 164:		Line 164:
	** ctkDICOMThumbnailWidget - for study/series preview		** ctkDICOMThumbnailWidget - for study/series preview
	** ctkDICOMDatasetViewWidget - image display, pan, zoom		** ctkDICOMDatasetViewWidget - image display, pan, zoom

			See the [http://www.commontk.org/docs/html/classes.html CTK doxygen documents] for more information.


	Directory layout used by ctkDICOMDatabase:		Directory layout used by ctkDICOMDatabase:
Line 183:		Line 186:
	(depending on the state of the checkbox when the user selects the Import option in the ctkDICOMViewer).		(depending on the state of the checkbox when the user selects the Import option in the ctkDICOMViewer).
	</pre>		</pre>


	==== End User Functionality ====		==== End User Functionality ====

Pieper: /* Next Steps */

2011-02-14T12:30:58Z

Next Steps

← Older revision		Revision as of 08:30, 14 February 2011
Line 199:		Line 199:

	Major pieces for further work:		Major pieces for further work:
	* Implement the Export and Send features of the ctkDICOM app		* Implement the Export and Send features of the ctkDICOM app (ctkDICOMSend would be a storage SCU and export would be implemented as methods on ctkDICOMDatabase)
			* Add a Listener function (a.k.a. storescp probably as a ctkDICOMStorage class)
	* Test on multiple PACS systems (so far CONQUEST and DCM4CHEE have been used for testing).		* Test on multiple PACS systems (so far CONQUEST and DCM4CHEE have been used for testing).
	* Integrate widgets to invoke DICOM Application Hosting via the ctkDICOM interface		* Integrate widgets to invoke DICOM Application Hosting via the ctkDICOM interface

Pieper: /* Attendees */

2011-02-14T12:28:12Z

Attendees

← Older revision		Revision as of 08:28, 14 February 2011
Line 74:		Line 74:
	\| Nicholas Herlambang		\| Nicholas Herlambang
	\| AZE, Japan		\| AZE, Japan
			\| Yes
			\|-
			\| Dave Partyka
			\| Kitware
	\| Yes		\| Yes
	\|}		\|}

Sascha: /* Accomplishments and Next Steps */

2011-02-14T08:22:34Z

Accomplishments and Next Steps

@@ Line 208: / Line 208: @@
 * Mapped files are used in the host to serve files without copying data between host and application.
 * Interaction with old XIP software done. New XIP with updates from Larry on the way.
 === Documentation and Wiki ===

Pieper at 20:26, 11 February 2011

2011-02-11T20:26:33Z

@@ Line 107: / Line 107: @@
 **** Note that we can jazz up (e.g. use 3D shading, change button shape, color) the standardized icons shown in the profile and still be compliant, as long as the basic icon form (e.g. arrow, double arrow, etc.) is recognizable.
 ** Local DICOM Directory and Database Structure
 * Application Hosting
 ** Hosting Logic
@@ Line 177: / Line 160: @@
 ** ctkDICOMThumbnailWidget - for study/series preview
 ** ctkDICOMDatasetViewWidget - image display, pan, zoom
 ==== End User Functionality ====
 These classes are tied together into the ctkDICOM application that allows the user to do the following:
 * Local Library

Benoit.bleuze: /* Accomplishments and Next Steps */

2011-02-11T20:25:21Z

Accomplishments and Next Steps

← Older revision		Revision as of 16:25, 11 February 2011
Line 199:		Line 199:
	Achievements:		Achievements:
	* Hosted application and hosting system coupled. The application gets a Dicom file from the host and displays a frame.		* Hosted application and hosting system coupled. The application gets a Dicom file from the host and displays a frame.
	* The whole state machine defining authorised and forbidden transitions implemented		* The whole state machine defining authorised and forbidden transitions implemented.
			**Start, suspend, cancel,resume and exit actions supported.
	* Signals emitted for each valid state transition to ease event driven implementation of applications and hosts.		* Signals emitted for each valid state transition to ease event driven implementation of applications and hosts.
	* Mapped files are used in the host to serve files without copying data between host and application.		* Mapped files are used in the host to serve files without copying data between host and application.
			* Interaction with old XIP software done. New XIP with updates from Larry on the way.
	~~Tools:~~
	* ~~The whole reference document is~~ on the ~~wiki~~. ~~References to the doc from the source code (and doxygen) can be easilly done (needs to include images to the wiki, coming)~~

	=== Documentation and Wiki ===		=== Documentation and Wiki ===
Line 212:		Line 211:
	* The CommonTk Wiki contains now more information and first tutorials for the [[Documentation#Plugin_Framework \| Plugin Framework]].		* The CommonTk Wiki contains now more information and first tutorials for the [[Documentation#Plugin_Framework \| Plugin Framework]].
	* Wiki pages containing tutorial code can use an [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi_remote improved MediaWiki extension] for syntax highlighting remote files (and only show certain parts of it).		* Wiki pages containing tutorial code can use an [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi_remote improved MediaWiki extension] for syntax highlighting remote files (and only show certain parts of it).
			* The whole reference document for Dicom Application hosting is on the wiki. References to the doc from the source code (and doxygen) can be easilly done (needs to include images to the wiki, coming). The pdf, the wsdl and other xml files needed for implementation are also on the page.

	== Agenda ==		== Agenda ==

Benoit.bleuze: /* DICOM Application Hosting */

2011-02-11T20:22:34Z

DICOM Application Hosting

← Older revision		Revision as of 16:22, 11 February 2011
Line 197:		Line 197:

	=== DICOM Application Hosting ===		=== DICOM Application Hosting ===
			Achievements:
			* Hosted application and hosting system coupled. The application gets a Dicom file from the host and displays a frame.
			* The whole state machine defining authorised and forbidden transitions implemented
			* Signals emitted for each valid state transition to ease event driven implementation of applications and hosts.
			* Mapped files are used in the host to serve files without copying data between host and application.

			Tools:
			* The whole reference document is on the wiki. References to the doc from the source code (and doxygen) can be easilly done (needs to include images to the wiki, coming)

	=== Documentation and Wiki ===		=== Documentation and Wiki ===

Sascha: /* Accomplishments and Next Steps */

2011-02-11T20:05:47Z

Accomplishments and Next Steps

← Older revision		Revision as of 16:05, 11 February 2011
Line 195:		Line 195:
	* Integrate widgets to invoke DICOM Application Hosting via the ctkDICOM interface		* Integrate widgets to invoke DICOM Application Hosting via the ctkDICOM interface
	* Work with user communities to refine/expand implementation to fit needs of slicer, mitk, maf, gimias, xip, etc...		* Work with user communities to refine/expand implementation to fit needs of slicer, mitk, maf, gimias, xip, etc...

			=== DICOM Application Hosting ===

	=== Documentation and Wiki ===		=== Documentation and Wiki ===
Line 202:		Line 204:
	* The CommonTk Wiki contains now more information and first tutorials for the [[Documentation#Plugin_Framework \| Plugin Framework]].		* The CommonTk Wiki contains now more information and first tutorials for the [[Documentation#Plugin_Framework \| Plugin Framework]].
	* Wiki pages containing tutorial code can use an [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi_remote improved MediaWiki extension] for syntax highlighting remote files (and only show certain parts of it).		* Wiki pages containing tutorial code can use an [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi_remote improved MediaWiki extension] for syntax highlighting remote files (and only show certain parts of it).

	~~=== DICOM Application Hosting ===~~

	== Agenda ==		== Agenda ==