Revision as of 17:56, 29 March 2011

Home < Projects:ARRA:SlicerEM:AtlasCreator:Groupwise

Integration of Groupwise Registration in the AtlasCreator

Step1 (until 04/01/11):
- Daniel will get the code from Jeremy and dump it into our atlascreator/commandline directory
- Daniel will compile the code under slicer - should you run into problems Jeremy is going to work on figuring them out with / for Daniel . If the code needs changes, Jeremy is responsible for implementing them
  - Daniel waits for the GIT repository from Jeremy
    - Then, run some tests provided by Jeremy
- If Congeal doesn't compile cross platform then we could use the Slicer extension system as a backup
Step 2 (until 04/01/11):
- Daniel will write a wrapper to create Congeal config files by specifying command line arguments
  - Jeremy and Daniel will communicate if the "wrapper" fits Congeal's config needs and test the config files
- File formats:
  - Congeal supports NIfTI-1 file format
  - Slicer does too :)
Step 3 (until 04/06/11):
- Daniel will modify the atlas creator so that he can access the wrapper
Step 4 (until 08/04/11):
- Daniel creates an advanced tab in our tool that makes some of the key parameter visible to user and modify the docu accordingly
- Jeremy will give us a link or modify our wiki page with respect to the meaning of specific parameters , ....
Step 5:
- Be happy

For all:
For Kilian:
- How does this effort coordinate with the integration of PCA? Which one has higher priority? (Daniel)
  - PCA will sit on top of this. This effort is an alternative to the registration stage. (Daniel after talking to Kilian)
For Jeremy:
- ~~Please send the code after you are done cleaning up (Daniel)~~
For Daniel:

@@ Line 26: / Line 26: @@
 == Questions ==
 * For all:
-** should the wrapper in Step 2/3 be a simple bash script (downside might be no platform independency) or an executable (Daniel)
-*** If an executable, should it be written using the Slicer Execution Model which generates a GUI automatically? This GUI would be separate from our AtlasCreator module and would list all parameters.
-**** Link to the Slicer Execution Model: http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation
-**** If not, there will be only limited parameters exposed in the AtlasCreator GUI's advanced panel
 * For Kilian:
 ** How does this effort coordinate with the integration of PCA? Which one has higher priority? (Daniel)
 *** PCA will sit on top of this. This effort is an alternative to the registration stage. (Daniel after talking to Kilian)
 * For Jeremy:
-** Please send the code after you are done cleaning up (Daniel)
+** <strike>Please send the code after you are done cleaning up (Daniel)</strike>
 * For Daniel: