Difference between revisions of "Projects:ARRA:SlicerEM:AtlasCreator:Groupwise"
From NAMIC Wiki
| (2 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
== Action Plan == | == Action Plan == | ||
* Step1 (until 04/01/11): | * Step1 (until 04/01/11): | ||
| − | ** Daniel will get the code from Jeremy and dump it into our atlascreator/commandline directory | + | ** <strike>Daniel will get the code from Jeremy and dump it into our atlascreator/commandline directory</strike> |
| − | ** 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 | + | ** <strike>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</strike> |
| − | *** Daniel waits for the GIT repository from Jeremy | + | *** <strike>Daniel waits for the GIT repository from Jeremy</strike> |
**** Then, run some tests provided by 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 | ** If Congeal doesn't compile cross platform then we could use the Slicer extension system as a backup | ||
* Step 2 (until 04/01/11): | * Step 2 (until 04/01/11): | ||
| − | ** Daniel will write a wrapper to create Congeal config files by specifying command line arguments | + | ** <strike>Daniel will write a wrapper to create Congeal config files by specifying command line arguments </strike> |
| − | *** Jeremy and Daniel will communicate if the "wrapper" fits Congeal's config needs and test the config files | + | *** <strike>Jeremy and Daniel will communicate if the "wrapper" fits Congeal's config needs and test the config files</strike> |
** File formats: | ** File formats: | ||
*** Congeal supports NIfTI-1 file format | *** Congeal supports NIfTI-1 file format | ||
| Line 26: | Line 26: | ||
== Questions == | == Questions == | ||
* For all: | * For all: | ||
| − | |||
| − | |||
| − | |||
| − | |||
* For Kilian: | * For Kilian: | ||
** How does this effort coordinate with the integration of PCA? Which one has higher priority? (Daniel) | ** 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) | *** PCA will sit on top of this. This effort is an alternative to the registration stage. (Daniel after talking to Kilian) | ||
* For Jeremy: | * 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: | * For Daniel: | ||
Latest revision as of 20:58, 13 April 2011
Home < Projects:ARRA:SlicerEM:AtlasCreator:GroupwiseBack to AtlasCreator..
Integration of Groupwise Registration in the AtlasCreator
Action Plan
- Step1 (until 04/01/11):
Daniel will get the code from Jeremy and dump it into our atlascreator/commandline directoryDaniel 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 themDaniel 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 argumentsJeremy 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
Questions
- 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)
- How does this effort coordinate with the integration of PCA? Which one has higher priority? (Daniel)
- For Jeremy:
Please send the code after you are done cleaning up (Daniel)
- For Daniel:
