Difference between revisions of "Developer Meetings/20121002"
From Slicer Wiki
m (Text replacement - "slicerWiki/index.php" to "wiki") |
|||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 2: | Line 2: | ||
== To discuss == | == To discuss == | ||
| − | + | * Tutorial 9 - Part3 - See http://na-mic.org/Mantis/view.php?id=2587 | |
| + | * Tutorial 13 - see http://www.na-mic.org/Bug/view.php?id=2514 | ||
| + | <!-- | ||
* Create a 'developer sandbox' extension index | * Create a 'developer sandbox' extension index | ||
| + | ** Jc: Provide details regarding the existing extension continuous build system | ||
** Support continuous builds so developers can test | ** Support continuous builds so developers can test | ||
*** cross-platform builds | *** cross-platform builds | ||
| Line 11: | Line 14: | ||
* Support of new data types implemented in extensions | * Support of new data types implemented in extensions | ||
** Andrey: I would like to know how feasible/difficult it is to have a new type of MRML node that will be possible to add as a new item to "Add data"/"Save data" dialog. Is this extensible from an extension? We need to have this capability to provide consistent user experience (this is also Ron's request/strong suggestion for Reporting module) | ** Andrey: I would like to know how feasible/difficult it is to have a new type of MRML node that will be possible to add as a new item to "Add data"/"Save data" dialog. Is this extensible from an extension? We need to have this capability to provide consistent user experience (this is also Ron's request/strong suggestion for Reporting module) | ||
| + | ** Julien: http://wiki.slicer.org/wiki/Documentation/Nightly/Developers/IO | ||
* Greg: Why is Slicer extension documentation hosted on github, instead of slicer.org? | * Greg: Why is Slicer extension documentation hosted on github, instead of slicer.org? | ||
| + | --> | ||
== Conclusion == | == Conclusion == | ||
| + | * Andriy talked about some link error related to ITKv4 | ||
| + | * Talked about Tutorial 6 and the fact ABC extension is not available. Alex will contact Marcel again next week after he is back from Micai. | ||
| + | * Discussed Tutorial 9 with Andriy. | ||
| + | ** We found out that ChangeTracker is failing because IntensityDifferenceMetric failed due to a problem related to libGL. (<code>"usr/lib/nvidia-current/libGL.so.1: undefined symbol: _nv000007gl" error</code>). | ||
| + | *** A message should probably be reported to the user | ||
| + | ** Andriy will look at the crash happening when closing Slicer after using ChangeTracker. | ||
| + | * Discussed issue related to Tutorial 13 | ||
| + | ** Nicole and Julien talked about sceneview issue related to vtkMRMLViewNode | ||
| + | * Update on the factory - Parallel 5 should be installed soon and linux build back :) | ||
| + | * Jc will send an email to each developer having issue to address before October15. | ||
Latest revision as of 17:00, 21 November 2019
Home < Developer Meetings < 20121002Attendees:
To discuss
- Tutorial 9 - Part3 - See http://na-mic.org/Mantis/view.php?id=2587
- Tutorial 13 - see http://www.na-mic.org/Bug/view.php?id=2514
Conclusion
- Andriy talked about some link error related to ITKv4
- Talked about Tutorial 6 and the fact ABC extension is not available. Alex will contact Marcel again next week after he is back from Micai.
- Discussed Tutorial 9 with Andriy.
- We found out that ChangeTracker is failing because IntensityDifferenceMetric failed due to a problem related to libGL. (
"usr/lib/nvidia-current/libGL.so.1: undefined symbol: _nv000007gl" error).- A message should probably be reported to the user
- Andriy will look at the crash happening when closing Slicer after using ChangeTracker.
- We found out that ChangeTracker is failing because IntensityDifferenceMetric failed due to a problem related to libGL. (
- Discussed issue related to Tutorial 13
- Nicole and Julien talked about sceneview issue related to vtkMRMLViewNode
- Update on the factory - Parallel 5 should be installed soon and linux build back :)
- Jc will send an email to each developer having issue to address before October15.
