Deleted branch T24716-imageDataItem-limit-expanded.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 10 2020
Deleted branch T24332-update-SimpleITK-and-use-system-python3.
Deleted branch T23343-enable-microservice-based-reading-for-dicom-editor.
Jun 30 2020
A couple of days after writing that, I found the code that is setting the initial state to visible.
In T27389#204198, @Oshio wrote:@kalali Your solution solved the problem. I'd like to point out that SetWidgetPlanesVisibility(true) is already called somewhere inside InitializeMultiWidget(), so just AddPlanesToDataStorage()is enough for rendering the planes.
Jun 20 2020
Thank you for your response and for pointing out the redundancy, I will fix this next week.
@kalali Your solution solved the problem. I'd like to point out that SetWidgetPlanesVisibility(true) is already called somewhere inside InitializeMultiWidget(), so just AddPlanesToDataStorage()is enough for rendering the planes.
Jun 19 2020
I fixed the tutorial accordingly and close this task as resolved. If you still have problems, don't hesitate to reopen this task.
Jun 16 2020
I can reproduce the error. There was a change in the StdMultiWidget so we have to adapt the tutorial. A specific initialization-method was added, so we need to call InitializeMultiWidget before accessing the render windows (which does some things for us so we can remove some lines from the tutorial).
The level window slider was removed from the StdMultiWidget and needs to be added additionally.
May 11 2020
Jan 9 2020
This issue is not wDB related, but MITK related:
Query with CGET activated and then Retrieve:
Retrieve does not work, MTIK directly shows:
Jan 8 2020
This does still not work (Retrieve from wdB fails, when going throw the "Checkliste DICOM Browser".
I have to look into this.
Jun 11 2019
Apr 15 2019
You mean like
-Wno-error=catch-value=
Apr 9 2019
Mar 11 2019
Feb 5 2019
Alright, thanks for your support!
Thanks for that. The problem arises from a insufficient implementation of the LabelSetImagIO. It currently ignores the time geometry and additional properties :(.
Jan 29 2019
Sorry I did not mention this, but I use the multi label segmentation.
In T25939#173903, @full wrote:For the sake of completeness: I did as you suggested and created a segmentation from scratch and exporting it as nrrd. This did not solve the problem.
Then there might be another bug involved. Could you make such a segmentaton (must not be a meaningfull) store it as nrrd and provide the stored NRRD?
Thank you for your extensive response.
The reason is (most certainly, but not verified!), that the nifti segmentations do not store correct timepoints for each frame. If loaded, they will get the default time geometry. (starting with 0 ms and a duration of 1 ms per frame). This is one of the problems I addressed last december with my camic info mail, to make people aware of current problems with using nifti (cf nrrd format) when storing data.
Jan 8 2019
Dec 18 2018
Dec 17 2018
Dec 3 2018
Nov 23 2018
The tutorial ("Welcome screen") has light theme and the old icons. This might be quite confusing for new users.
Nov 21 2018
Nov 20 2018
warnings as errors on by default: New CMake option WARNINGS_NO_ERRORS
Nov 15 2018
Nov 13 2018
Is this really already resolved?
Pushed new branch T25186-version-number-update.
Pushed new branch T25191-v2018.04-beta-DICOMBrowser-ListRequests.
Nov 9 2018
Known Issues:
Under Linux after compiling i have to start the program twice, the first time with --BlueBerry.clean. I use this script to compile and start it faster:
#!/bin/bash
Pushed new branch T25191-v2018.04-beta-FastMargin.
Cherry-picking into beta...
Nov 7 2018
The "Write ...." todos are perfect candidates for off-side parallel tasks for "everyone" to grab.
I just checked again and I was able to open a 2d image and even create a segmentation for it, which is then a 3d image with a single slice.
The branch above is already merged. Closing this one.
Pushed new branch T25193-DCMQI-ON.
Okay, so this sounds to me as if it is nothing MITK specific here. I close this task, please re-open if you disagree.
Wrote an email to @goetzm.
Among other tests, this one is fixed this in the master branch. I cherry-picked most commits from @goetzm into the beta branch and most tests also work in the beta branch now but this single one is still failing randomly.
@goetzm Please help identify the commit in the master that fixes this particular test.
I closed the remaining TODOs because of ordering priorities in MITK tasks. The most important feature here is implemented and in beta branch.
Oct 26 2018
In T25105#167423, @kalali wrote:We do not need to move the whole functionality to the data storage, just the geometry processing part.
What do you exactly mean with geometry processing part? Does "to the storage" mean, into the class or into the file?
Discussed at MITK meeting: workbench should not crash, no matter how we handle 2D segmentations
Pushed new branch T25580-DocumentationFixes-MasterOnly.
Pushed new branch T25580-FixVariousMinorDocumentationIssues.
Oct 25 2018
Oct 24 2018
Oct 23 2018
We do not need to move the whole functionality to the data storage, just the geometry processing part. The rest can be put somewhere else, but https://phabricator.mitk.org/D14 said, It was decided that the status bar should not be responsible for extracting information from an image.
In T25105#167258, @kalali wrote:Would it be reasonable to move the UpdateStatusBar functionality to the data storage as well
No, I don't think so. It is not job of the DataStorage to update the status bar.
Yes, partially. We have no crashes, but
The GetTopLayerNode has been moved to the data storage as FindTopmostVisibleNode.
Would it be reasonable to move the UpdateStatusBar functionality to the data storage as well, as it needs to extract image information from the topmost visible node?
Or is there some other place for this kind of image geometry processing?