Difference between revisions of "Engineering:TCON 2013"
Line 4: | Line 4: | ||
==2013-10-17== | ==2013-10-17== | ||
− | Attendees: Jim, Steve, Dirk, Tina, Ron | + | Attendees: Jim, Steve, Dirk, Tina, Ron, Nicole |
*Albert's problem | *Albert's problem |
Revision as of 19:22, 17 October 2013
Home < Engineering:TCON 2013Back to TCON:Main, Events
Contents
- 1 2013-10-17
- 2 2013-10-03
- 3 2013-09-26
- 4 2013-09-19
- 5 2013-09-12
- 6 2013-09-05
- 7 2013-08-29
- 8 2013-08-22
- 9 2013-08-15
- 10 2013-08-08
- 11 2013-07-18
- 12 2013-07-11
- 13 2013-07-04
- 14 2013-06-27
- 15 2013-06-20
- 16 2013-06-13
- 17 2013-06-07
- 18 2013-05-30
- 19 2013-05-23
- 20 2013-05-16
- 21 2013-05-02
- 22 2013-4-25
- 23 2013-04-18
- 24 2013-04-11
- 25 2013-04-04
- 26 2013-3-28
- 27 2013-3-21
- 28 2013-3-14
- 29 2013-3-7
- 30 2013-2-28
- 31 2013-2-21
- 32 2013-2-14
- 33 2013-2-7
- 34 2013-1-31
- 35 2013-01-24
- 36 2013-01-17
- 37 2013-01-10
- 38 2013-01-03
2013-10-17
Attendees: Jim, Steve, Dirk, Tina, Ron, Nicole
- Albert's problem
2013-10-03
Attendees: Jim, JC, Nicole, Tina
Agenda:
- Testing
Notes:
- Don't check in a test that will fail for more than 24 hours
- Nicole: will check in a test showing failing behaviour but not failing the test via ctest
- JC script for patch release is ready, fixing last few tests
- Winter project week is set, start thinking of projects in mid to late October
2013-09-26
Attendees: Jim, Dave, Nicole, JC
Notes:
- update from JC on the release
- Jim, JC and Nicole discussed layout changes and attendant bugs
2013-09-19
Attendees: Tina, Nicole, JC
Agenda:
- From Nicole: Adding a MRML scene flag for when changing the layout
- see back trace here in comment 9733: Bug 1690. Need to be able to know in my displayble manager that the layout is in the process of changing so as not to try and set renderers on widgets (active camera may also not be set)
- name? LayoutChangeState, LayoutChangeEvent?
- for which Slicer release? Bug 1690 probably won't get closed without this change and will need to be retargeted
- Slicer 4.3.1 release on Monday
Notes:
- Nicole will post a topic to github and send the url for feedback
2013-09-12
Attendees: Jim, Ayesha, Nicole, Tina, JC
Agenda:
- Slicer 4.3.1 release
Notes:
- Tina announced we will have a project week at MIT next summer, Jun 23-27
- Jim talked about redoing the process read node data method
- MRML node changes to support creating default display and storage nodes
- to let extensions define new nodes and have them get passed to CLIs
- Nicole will test once it's ready for review
2013-09-05
Attendees: Jim, Nicole, JC, Tina
Agenda:
- Slicer 4.3 release
- Roadmap
- SVN branch was made this afternoon
2013-08-29
Attendees: Jim, Steve, Nicole, Sunil, JC
Agenda:
- Slicer 4.3 release
Notes:
- talked about the light box bug, Jim says cross hair displayable manager is good as a base
- Nicole to change Markups documentation xml file to take out a layer of nesting, JC can extend the wiki settings after the release
- talked about the dti analysis bug, Steve can reproduce now and will try to fix
- ITK tag has been updated
2013-08-22
Attendees: Steve, Nicole, JC, Dave
Agenda:
- Slicer 4.3 release
2013-08-15
Attendees: Steve, Nicole, Ayesha, Ron, Tina, JC
Agenda:
- Slicer 4.3 release
2013-08-08
Attendees: Ron, Nicole, Jim, Tina
2013-07-18
Attendees: Ron, Nicole, Steve, Jim, Tina, JC
Agenda:
- Slicer 4.3 release Road map
2013-07-11
Attendees: Nicole, Dave, Steve, Tina
- visualization of pediatric cardiac patients using 3d slicer has been underway at Children's (a brief tutorial was provided to them a few years ago and it turns out that they have been using it extensively. They are preparing an educational website for clinicians, which will be launched this year.)
2013-07-04
No mtg
2013-06-27
Attendees: Ron, Steve, Nicole, Dave, Tina
- Summary stats from project week: http://wiki.na-mic.org/Wiki/index.php/2013_Summer_Project_Week#Summary
2013-06-20
Project Week!
2013-06-13
Attendees: Tina, Nicole, Sneha, Steve, JC, Dave
Agenda:
2013-06-07
Attendees: Hans Meine, Steve, Jim, Ayesha, Tina, Dirk
- Hans Meine project
2013-05-30
Attendees: Ayesha, Lilla, Steve, Tina, Nicole, Dirk, JC, Matt Tosch
- Project Week
- Lilla Zollei
- Hans Meine
2013-05-23
Attendees: Jim, Tina, Nicole, Jason (UCSF), Beck (USCF), Aiyesha, Tamas, Dave, JC, Adriana (Univ of Mexico)
Agenda:
- Project Week
- HD projects added
- UCSF team will not be able to join this project week, but SLC possible
- U of Mexico team will complete their project pages and join next call
2013-05-16
Attendees: Jim, Steve, Tina, Nicole, JC, Aiyesha, Josh, Dirk, Jack
Agenda:
2013-05-02
Attendees: Jim, Nicole, Aiyesha, Dave
Agenda:
Meeting Notes:
- Jim and Nicole discussed qMRMLNodeComboBoxes, events, and mrml updates on entering modules
- workaround: disable widget until ready to update from MRML. Look into blockSignals.
- discussed Dave's project and storing/distributing large data for extensions
2013-4-25
Attendees:
Agenda:
- Project Week Kickoff: list projects
Meeting Notes:
2013-04-18
Attendees: Jim, Steve, Nicole, Tina, Andriy, Aiyesha, JC
Agenda:
- Project Week
- Virtual functional pointer tables
See: Hans's test example
Meeting Notes:
2013-04-11
Attendees: Jim, JC, Hans, Nicole, Brad
Meeting notes:
- BRAINS and EMSegment
- Building on Mac
- Project Week: filling in the page
2013-04-04
Attendees: Jim, Nicole, JC, Ayesha
2013-3-28
Attendees: Jim, Steve, Nicole, JC, Ayesha
Agenda:
- Project Week Kickoff:List engineering projects
Meeting Notes:
- discussed general outlines of engineering projects:
- Annotations rewrite
- Brain atlas optimisations (Marianna to do a demo)
- Provenance
- Patient hierarchies
- Sample data - content addressable data, in external data processing in Slicer, cmake file for external data, when write test can decorate the data file name with macro keywords saying it's external
- Next slicer release?
- post namic submission late May
- itkv4 version - use for project week development, not ready for users though
- need to go through the targetted bugs to decide what goes in the next release
- Slicer prereqs
- qt(? or cmake?) version - no time to update it now
- VS2010: cmake-ified python testing, delayed by the double convert and dcmtk build problems, but should be done by project week
2013-3-21
No call today. Several participants in DC. Please join next tcon to kickoff engineering project discussion for project week.
2013-3-14
Attendees: Steve, Ron, Tina, Nicole, Ayesha,
Agenda:
- CHECK YOUR EMAIL (SLICER-DEVELOPERS, NAMIC-ENG) FOR NEW TCON NUMBER
- OpenSSL status update
- Reorg menus in Slicer - deferred to when JC is on the call
- india update (nicole)
- Training Events http://wiki.na-mic.org/Wiki/index.php/Training:Events_Timeline
- Project Week kickoff in two weeks with engineering projects.
2013-3-7
Attendees: Jim, Steve, Tina, Aisha
Agenda:
- CHECK YOUR EMAIL (NAMIC-ENG) FOR NEW TCON NUMBER
2013-2-28
Attendees: Jim, Steve, Tina, Hans, JC, Sunil, Dave
Agenda:
2013-2-21
Attendees: Jim, Steve, Tina, Hans, JC, Sunil, Dave
Agenda:
2013-2-14
Attendees: Nicole, Sunil, Tina, Jim, JC, Ron, Dave,
Agenda:
- utility python script to parse a file to make MRML file for modelmaker - where is the best place to put it (Nicole)
2013-2-7
Attendees: Nicole, Sunil, Tina, Steve, Andriy
Agenda:
- (Ann will review progress report materials with core/site PIs offline)
2013-1-31
Attendees: Jim, Steve, Nicole, Tina, Sunil, Ruiy, Stephen
Agenda:
- Python external libraries discussion (Ron, Steve, JC, Sunil)
- SSL, setuptools, etc.
- Bug report: http://na-mic.org/Bug/view.php?id=2352
- In the next TCON, Ann will review draft of engineering core progress report. All site PIs should plan to attend.
Extending Slicer with more python packages
Different approaches
Multiple and non-exclusive approach can be considered.
- (1) Bundling of package within Slicer installed (i.e. NUMPY)
If the package require compilation steps and is recognized of general interest, it probably make sens to bundle it within Slicer.
- (2) Installation of additional python packages from an *installed* Slicer
Few cases should be considered here:
a) *NO* compilation - *NO* libraries - It means the user does *NOT* have to install any compiler to be able to install the package. It is basically a pure python implementation.
b) *NO* compilation - *WITH* dependencies/libraries - It means the user does *NOT* have to install any compiler *BUT* have to install some external library to be able to install/use the package. This could reveal to be challenging for some user, especially to get the PATH, ... right.
c) *WITH* compilation - *NO* libraries - On unix like system, it is generally easier to install compiler but if we consider that most of our user works on windows, we should probably not require them to install Visual Studio to be able to install a python package ...
- (3) Installation of additional python packages from a *built* Slicer
The researched having a lot of experience in development usually have a build tree of Slicer and know enough to be able to tinker and install things.
Runtime installation
In the python ecosystem, the usage of a tool named pip became the standard regarding installation of additional module and packages. There are currently around 27500 packages available on the Python Package Index. See http://pypi.python.org/pypi
Most of these packages are served from server using https
protocol. To support such protocol, we would have to include the OpenSSL library.
Integrating OpenSSL into Slicer
Considering the license of OpenSSL (BSD style) is compatible with the Slicer one, there should not be any problem distributing it within Slicer. That said, is still presents few challenges.
Build system integration
- Download of the binaries on windows
- Build or download of binaries on macosx/linux
- As part of this integration, integrating a CMake'ified version of python would also make sens.
Some work and testing would be required to make sure everything works as expected.
Legal mention on the download page
We would have to probably have some mention on our page. That said, I found an article mentioning that it should now be fine to distribute strong cryptographic algorithm library within open-source project:
- http://www.theregister.co.uk/2011/01/07/open_source_crypto_curbs/
- https://www.federalregister.gov/articles/2011/01/07/2010-32803/publicly-available-mass-market-encryption-software-and-other-specified-publicly-available-encryption
Certificate Authority
To ensure Slicer is authenticated, we would have to create appropriate certificate and bundle them within Slicer. Some testing/research is required to exactly find out what need to be done. There is also probably a (not ideal) way of ignoring CA ...
2013-01-24
Attendees: Jim, Ron, Nicole, Sunil, JC, Steve
Agenda:
- ITK v4
- ssl issues with python
Minutes:
- ITK v4
- JC found the problem with dcmtk
- Xnat folks need to install some python package => Need openssl to pip install most of the package
- What is the legal aspect of having openssl bundled ?
- OpenSSL is build by CMake folks on all platform ... it could be re-used
- Difference between ITK 3.20.0 and ITK 3.20.1. See https://github.com/Kitware/ITK/compare/v3.20.0...v3.20.1
- Talked about Stan langage. See http://mc-stan.org/
2013-01-17
Attendees: Ron, Steve, Tina, Nicole, JC, Sunil, Dave, Jim
- Project week results review: http://wiki.na-mic.org/Wiki/index.php/2013_Winter_Project_Week
Agenda:
2013-01-10
No call due to 2013_Winter_Project_Week
2013-01-03
Attendees: Jim, Steve, Stephen, Nicole, Tina,
Agenda:
- Project week: http://wiki.na-mic.org/Wiki/index.php/2013_Winter_Project_Week
- Engineering core presentation: http://wiki.na-mic.org/Wiki/index.php/AHM2013-Engineering_Updates