Use this project to tag tasks and other stuff that should be discussed in the weekly MITK meeting.
Hi there! 🙂
Mon, May 25
I know how to fix the obvious problem. But I want to discuss if this is the complete fix or only curing the symptoms,
Sun, May 24
But we should also discuss if we should have such an unsave construct in the class. I would judge it as premature optimization. The savest way is to over a getter that always casts the BaseData::Geometry to plane geometry and skip the unmanaed member completly. Was there an known issue, explicit plan why the current pattern was chosen?
Sat, May 23
Fri, May 22
Thu, May 21
Wed, May 20
Wed, May 13
We need specific information of the test failures and if they are the same thing.
Sun, May 10
Fri, May 8
Curently you can workarround by moving the control point (e,g, for size) to the other side, so that it does not hit the boundary.
Thu, May 7
Tue, May 5
Mon, May 4
Thu, Apr 30
Diffusion still shows this:
Apr 27 2020
Strong agree on dicombrowser and avoiding the term editor ...
Apr 26 2020
I would use org.mitk.gui.qt.dicombrowser and not *editor. The name does refere to the plugin and not to views, editors, preference pages ... that may be in the plugin.
Second, I think *editor would confuse the people. It is technically the correct term but for the user it implies something that it does not do!
Apr 24 2020
Interim results of the discussion:
- It is a topic
- But it is to larga to discuss it in one metting. We should find dedicated slots for discussion or task owner how drives it.
- We should focus all design/rework considerations to the central data elements, namely:
- BaseData and derived classes (and maybe agregated sub components)
- BaseProperty and derived classes
- And we should split the discussion between A1 and A2 (divide and conquere). I would start with A2.
- Regarding A1, it is also an option to think about which event (bus) mechanism is the best to use. (It must not be the build-in itk option; nevertheless there should be good options to don't use what is already there.)
Apr 23 2020
Apr 22 2020
One reason to integrate modelfit and perfusion into the normal workbench would be that it will probably receive an increased amount of attention via OSIPI over the next two years.