Project Events Description - Revision history

Tkapur at 14:54, 15 June 2016

2016-06-15T14:54:21Z

Tkapur at 23:50, 6 May 2016

2016-05-06T23:50:31Z

Tkapur at 18:44, 21 November 2014

2014-11-21T18:44:20Z

Tkapur at 15:33, 9 December 2012

2012-12-09T15:33:44Z

Marianna at 15:41, 24 October 2008

2008-10-24T15:41:51Z

Marianna at 15:40, 24 October 2008

2008-10-24T15:40:56Z

Marianna at 15:40, 24 October 2008

2008-10-24T15:40:03Z

Tkapur at 16:56, 8 May 2008

2008-05-08T16:56:00Z

Tkapur at 20:58, 28 November 2007

2007-11-28T20:58:52Z

Tkapur: New page: NA-MIC Project Week is a hands on activity -- programming using the NA-MIC Kit, algorithm design, and clinical application -- that has become one of the major events in the ...

2007-11-28T20:58:17Z

New page: NA-MIC Project Week is a hands on activity -- programming using the NA-MIC Kit, algorithm design, and clinical application -- that has become one of the major events in the ...

New page

NA-MIC Project Week is a hands on activity -- programming using the [[NA-MIC-Kit|NA-MIC Kit]], algorithm design, and clinical application -- that has become one of the major events in the NA-MIC calendar. It is held in the summer at MIT, typically the last week of June, and a shorter version is held in Salt Lake City in the winter, typically the second week of January.
The main goal of these events if to move forward the deliverables of NA-MIC. NA-MIC participants, as well as active and potential collaborators are typical attendees at these events. These events are setup to maximize informal interaction between participants.

Active preparation begins 6-8 weeks prior to the meeting, when a kick-off teleconference is hosted by the NA-MIC Engineering, Dissemination, and Leadership teams, the primary hosts of this event. Invitations to this call are sent to all na-mic members, past attendees of the event, as well as any parties who have expressed an interest in working with NA-MIC. The main goal of the kick-off call is to get an idea of which groups/projects will be active at the upcoming event, and to ensure that there is sufficient NA-MIC coverage for all. Subsequent teleconferences allow the hosts to finalize the project teams, consolidate any common components, and identify topics that should be discussed in breakout sessions. In the final days leading upto the meeting, all project teams are asked to fill in a templated page on this wiki that describes the objectives and plan of their projects.

The event itself starts off with a short presentation by each project team, driven using their previously created description, and allows all participants to be acquainted with others who are doing similar work. In the rest of the week, about half the time is spent in breakout discussions on topics of common interest of subsets of the attendees, and the other half is spent in project teams, doing hands-on programming, algorithm design, or clinical application of NA-MIC kit tools. The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in NA-MIC kit software, algorithms, and clinical. To facilitate this work, a large room is setup with several tables, with internet and power access, and each team gathers on a table with their individual laptops, connects to the internet to download their software and data, and is able to work on their projects. On the last day of the event, a closing presentation session is held in which each project team presents a summary of what they accomplished during the week.

@@ Line 1: / Line 1: @@
 Founded in 2005, the National Alliance for Medical Image Computing (NAMIC), was chartered with building a computational infrastructure to support biomedical research as part of the NIH funded [http://www.ncbcs.org/ NCBC] program. The work of this alliance has resulted in important progress in algorithmic research, an open source medical image computing platform [http://www.slicer.org 3D Slicer], built  using [http://www.vtk.org VTK], [http://www.itk.org ITK], [http://www.cmake.org CMake], and [http://www.cdash.org CDash], and the creation of a community of algorithm researchers, biomedical scientists and software engineers who are committed to open science. This community meets twice a year in an event called Project Week.
-[[Engineering:Programming_Events|Project Week]] is a semi-annual event which draws 80-120 researchers. As of August 2014, it is a MICCAI endorsed event. The participants work collaboratively on open-science solutions for problems that lie on the interfaces of the fields of computer science, mechanical engineering, biomedical engineering, and medicine. In contrast to conventional conferences and workshops the primary focus of the Project Weeks is to make progress in projects (as opposed to reporting about progress). The objective of the Project Weeks is to provide a venue for this community of medical open source software creators. Project Weeks are open to all, are publicly advertised, and are funded through fees paid by the attendees. Participants are encouraged to stay for the entire event.
+[[Engineering:Programming_Events|Project Week]], led by [https://www.spl.harvard.edu/pages/People/tkapur Tina Kapur, PhD], is a semi-annual event which draws 80-120 researchers. As of August 2014, it is a MICCAI endorsed event. The participants work collaboratively on open-science solutions for problems that lie on the interfaces of the fields of computer science, mechanical engineering, biomedical engineering, and medicine. In contrast to conventional conferences and workshops the primary focus of the Project Weeks is to make progress in projects (as opposed to reporting about progress). The objective of the Project Weeks is to provide a venue for this community of medical open source software creators. Project Weeks are open to all, are publicly advertised, and are funded through fees paid by the attendees. Participants are encouraged to stay for the entire event.
 Project Week activities: Everyone shows up with a project. Some people are working on the platform. Some people are developing algorithms. Some people are applying the tools to their research problems. We begin the week by introducing projects and connecting teams. We end the week by reporting progress. In addition to the ongoing working sessions, breakout sessions are organized ad-hoc on a variety of special topics. These topics include: discussions of software architecture, presentations of new features and approaches and topics such as Image-Guided Therapy.
@@ Line 7: / Line 7: @@
 Several funded projects use the Project Week as a place to convene and collaborate. These include [http://nac.spl.harvard.edu/ NAC], [http://www.ncigt.org/ NCIGT], [http://qiicr.org/ QIICR], and [http://ocairo.technainstitute.com/open-source-software-platforms-and-databases-for-the-adaptive-process/ OCAIRO].  As of 2015, the summer event is held in the second half of June in conjunction with the [http://www.cars-int.org/ CARS conference], and the winter event in the first half of January at MIT.
-A summary of all past NA-MIC Project Events is available [[Project_Events#Past|here]].
+A summary of all past NA-MIC Project Events is available [[Project_Events|here]].
    Back to [[Project_Events|Project Events]]

@@ Line 5: / Line 5: @@
 Project Week activities: Everyone shows up with a project. Some people are working on the platform. Some people are developing algorithms. Some people are applying the tools to their research problems. We begin the week by introducing projects and connecting teams. We end the week by reporting progress. In addition to the ongoing working sessions, breakout sessions are organized ad-hoc on a variety of special topics. These topics include: discussions of software architecture, presentations of new features and approaches and topics such as Image-Guided Therapy.
-Several funded projects use the Project Week as a place to convene and collaborate. These include [http://nac.spl.harvard.edu/ NAC], [http://www.ncigt.org/ NCIGT], [http://qiicr.org/ QIICR], and [http://ocairo.technainstitute.com/open-source-software-platforms-and-databases-for-the-adaptive-process/ OCAIRO]. The next events in this ongoing series will occur in [http://wiki.na-mic.org/Wiki/index.php/2015_Winter_Project_Week Salt Lake City, Utah in January of 2015], followed by one in Boston, MA in June of 2015.
+Several funded projects use the Project Week as a place to convene and collaborate. These include [http://nac.spl.harvard.edu/ NAC], [http://www.ncigt.org/ NCIGT], [http://qiicr.org/ QIICR], and [http://ocairo.technainstitute.com/open-source-software-platforms-and-databases-for-the-adaptive-process/ OCAIRO].  As of 2015, the summer event is held in the second half of June in conjunction with the [http://www.cars-int.org/ CARS conference], and the winter event in the first half of January at MIT.
 A summary of all past NA-MIC Project Events is available [[Project_Events#Past|here]].

@@ Line 1: / Line 1: @@
-Project Week is a hands on activity -- programming using the open source [[NA-MIC-Kit|NA-MIC Kit]], algorithm design, and clinical application -- that has become one of the major events in the NA-MIC, NCIGT, and NAC calendars. It is held in the summer at MIT, typically the last week of June, and a shorter version is held in Salt Lake City in the winter, typically the second week of January.
+Founded in 2005, the National Alliance for Medical Image Computing (NAMIC), was chartered with building a computational infrastructure to support biomedical research as part of the NIH funded [http://www.ncbcs.org/ NCBC] program. The work of this alliance has resulted in important progress in algorithmic research, an open source medical image computing platform [http://www.slicer.org 3D Slicer], built  using [http://www.vtk.org VTK], [http://www.itk.org ITK], [http://www.cmake.org CMake], and [http://www.cdash.org CDash], and the creation of a community of algorithm researchers, biomedical scientists and software engineers who are committed to open science. This community meets twice a year in an event called Project Week.
-Active preparation begins 6-8 weeks prior to the meeting, when a kick-off teleconference is hosted by the NA-MIC Engineering, Dissemination, and Leadership teams, the primary hosts of this event.  Invitations to this call are sent to all na-mic members, past attendees of the event, as well as any parties who have expressed an interest in working with NA-MIC. The main goal of the kick-off call is to get an idea of which groups/projects will be active at the upcoming event, and to ensure that there is sufficient NA-MIC coverage for all. Subsequent teleconferences allow the hosts to finalize the project teams, consolidate any common components, and identify topics that should be discussed in breakout sessions. In the final days leading upto the meeting, all project teams are asked to fill in a template page on this wiki that describes the objectives and plan of their projects.
+[[Engineering:Programming_Events|Project Week]] is a semi-annual event which draws 80-120 researchers. As of August 2014, it is a MICCAI endorsed event. The participants work collaboratively on open-science solutions for problems that lie on the interfaces of the fields of computer science, mechanical engineering, biomedical engineering, and medicine. In contrast to conventional conferences and workshops the primary focus of the Project Weeks is to make progress in projects (as opposed to reporting about progress). The objective of the Project Weeks is to provide a venue for this community of medical open source software creators. Project Weeks are open to all, are publicly advertised, and are funded through fees paid by the attendees. Participants are encouraged to stay for the entire event.
-The event itself starts off with a short presentation by each project team, driven using their previously created description, and allows all participants to be acquainted with others who are doing similar work. In the rest of the week, about half the time is spent in breakout discussions on topics of common interest of subsets of the attendees, and the other half is spent in project teams, doing hands-on programming, algorithm design, or clinical application of NA-MIC kit tools.  The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in NA-MIC kit software, algorithms, and clinical.  To facilitate this work, a large room is setup with several tables, with internet and power access, and each team gathers on a table with their individual laptops, connects to the internet to download their software and data, and is able to work on their projects.  On the last day of the event, a closing presentation session is held in which each project team presents a summary of what they accomplished during the week.
+Project Week activities: Everyone shows up with a project. Some people are working on the platform. Some people are developing algorithms. Some people are applying the tools to their research problems. We begin the week by introducing projects and connecting teams. We end the week by reporting progress. In addition to the ongoing working sessions, breakout sessions are organized ad-hoc on a variety of special topics. These topics include: discussions of software architecture, presentations of new features and approaches and topics such as Image-Guided Therapy.
 A summary of all past NA-MIC Project Events is available [[Project_Events#Past|here]].

← Older revision		Revision as of 15:33, 9 December 2012
Line 1:		Line 1:
−	~~NA-MIC~~ Project Week is a hands on activity -- programming using the [[NA-MIC-Kit\|NA-MIC Kit]], algorithm design, and clinical application -- that has become one of the major events in the NA-MIC ~~calendar~~. It is held in the summer at MIT, typically the last week of June, and a shorter version is held in Salt Lake City in the winter, typically the second week of January.	+	Project Week is a hands on activity -- programming using the open source [[NA-MIC-Kit\|NA-MIC Kit]], algorithm design, and clinical application -- that has become one of the major events in the NA-MIC, NCIGT, and NAC calendars. It is held in the summer at MIT, typically the last week of June, and a shorter version is held in Salt Lake City in the winter, typically the second week of January.
	The main goal of these events if to move forward the deliverables of NA-MIC. NA-MIC participants, as well as active and potential collaborators are typical attendees at these events. These events are setup to maximize informal interaction between participants.		The main goal of these events if to move forward the deliverables of NA-MIC. NA-MIC participants, as well as active and potential collaborators are typical attendees at these events. These events are setup to maximize informal interaction between participants.

← Older revision		Revision as of 15:40, 24 October 2008
Line 9:		Line 9:


−	Back to [[Project_Events]]	+	Back to [[Project_Events\|Project Events]]

@@ Line 2: / Line 2: @@
 The main goal of these events if to move forward the deliverables of NA-MIC. NA-MIC participants, as well as active and potential collaborators are typical attendees at these events. These events are setup to maximize informal interaction between participants.
-Active preparation begins 6-8 weeks prior to the meeting, when a kick-off teleconference is hosted by the NA-MIC Engineering, Dissemination, and Leadership teams, the primary hosts of this event.  Invitations to this call are sent to all na-mic members, past attendees of the event, as well as any parties who have expressed an interest in working with NA-MIC. The main goal of the kick-off call is to get an idea of which groups/projects will be active at the upcoming event, and to ensure that there is sufficient NA-MIC coverage for all. Subsequent teleconferences allow the hosts to finalize the project teams, consolidate any common components, and identify topics that should be discussed in breakout sessions. In the final days leading upto the meeting, all project teams are asked to fill in a templated page on this wiki that describes the objectives and plan of their projects.
+Active preparation begins 6-8 weeks prior to the meeting, when a kick-off teleconference is hosted by the NA-MIC Engineering, Dissemination, and Leadership teams, the primary hosts of this event.  Invitations to this call are sent to all na-mic members, past attendees of the event, as well as any parties who have expressed an interest in working with NA-MIC. The main goal of the kick-off call is to get an idea of which groups/projects will be active at the upcoming event, and to ensure that there is sufficient NA-MIC coverage for all. Subsequent teleconferences allow the hosts to finalize the project teams, consolidate any common components, and identify topics that should be discussed in breakout sessions. In the final days leading upto the meeting, all project teams are asked to fill in a template page on this wiki that describes the objectives and plan of their projects.
 The event itself starts off with a short presentation by each project team, driven using their previously created description, and allows all participants to be acquainted with others who are doing similar work. In the rest of the week, about half the time is spent in breakout discussions on topics of common interest of subsets of the attendees, and the other half is spent in project teams, doing hands-on programming, algorithm design, or clinical application of NA-MIC kit tools.  The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in NA-MIC kit software, algorithms, and clinical.  To facilitate this work, a large room is setup with several tables, with internet and power access, and each team gathers on a table with their individual laptops, connects to the internet to download their software and data, and is able to work on their projects.  On the last day of the event, a closing presentation session is held in which each project team presents a summary of what they accomplished during the week.

← Older revision		Revision as of 16:56, 8 May 2008
Line 5:		Line 5:

	The event itself starts off with a short presentation by each project team, driven using their previously created description, and allows all participants to be acquainted with others who are doing similar work. In the rest of the week, about half the time is spent in breakout discussions on topics of common interest of subsets of the attendees, and the other half is spent in project teams, doing hands-on programming, algorithm design, or clinical application of NA-MIC kit tools. The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in NA-MIC kit software, algorithms, and clinical. To facilitate this work, a large room is setup with several tables, with internet and power access, and each team gathers on a table with their individual laptops, connects to the internet to download their software and data, and is able to work on their projects. On the last day of the event, a closing presentation session is held in which each project team presents a summary of what they accomplished during the week.		The event itself starts off with a short presentation by each project team, driven using their previously created description, and allows all participants to be acquainted with others who are doing similar work. In the rest of the week, about half the time is spent in breakout discussions on topics of common interest of subsets of the attendees, and the other half is spent in project teams, doing hands-on programming, algorithm design, or clinical application of NA-MIC kit tools. The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in NA-MIC kit software, algorithms, and clinical. To facilitate this work, a large room is setup with several tables, with internet and power access, and each team gathers on a table with their individual laptops, connects to the internet to download their software and data, and is able to work on their projects. On the last day of the event, a closing presentation session is held in which each project team presents a summary of what they accomplished during the week.
		+
		+	A summary of all past NA-MIC Project Events is available [[Project_Events\|here]].
		+

	Back to [[Project_Events]]		Back to [[Project_Events]]

← Older revision		Revision as of 20:58, 28 November 2007
Line 5:		Line 5:

	The event itself starts off with a short presentation by each project team, driven using their previously created description, and allows all participants to be acquainted with others who are doing similar work. In the rest of the week, about half the time is spent in breakout discussions on topics of common interest of subsets of the attendees, and the other half is spent in project teams, doing hands-on programming, algorithm design, or clinical application of NA-MIC kit tools. The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in NA-MIC kit software, algorithms, and clinical. To facilitate this work, a large room is setup with several tables, with internet and power access, and each team gathers on a table with their individual laptops, connects to the internet to download their software and data, and is able to work on their projects. On the last day of the event, a closing presentation session is held in which each project team presents a summary of what they accomplished during the week.		The event itself starts off with a short presentation by each project team, driven using their previously created description, and allows all participants to be acquainted with others who are doing similar work. In the rest of the week, about half the time is spent in breakout discussions on topics of common interest of subsets of the attendees, and the other half is spent in project teams, doing hands-on programming, algorithm design, or clinical application of NA-MIC kit tools. The hands-on activities are done in 10-20 small teams of size 3-5, each with a mix of experts in NA-MIC kit software, algorithms, and clinical. To facilitate this work, a large room is setup with several tables, with internet and power access, and each team gathers on a table with their individual laptops, connects to the internet to download their software and data, and is able to work on their projects. On the last day of the event, a closing presentation session is held in which each project team presents a summary of what they accomplished during the week.
		+
		+	Back to [[Project_Events]]