- User Since
- Aug 1 2016, 12:10 PM (233 w, 3 d)
@kislinsk anyone from the MITK CI team who could take over?
Tue, Jan 19
Changes have landed . @neher could you test again using a nightly build?
Just submitted a Differential
Fri, Jan 15
Thank. New command-line interface looks nice, but the challenge is where to put the credentials, especially if you want to put the script open source like in the Kaapana dockerfiles.
Thu, Jan 14
Dec 2 2020
I contacted dcmqi upstream, thanks @fedorov for the quick reply.
PS: Chrome upload works but data doesn't show up in meta
Nov 30 2020
I tested with the latest develop:
WARNING: SliceThickness is present and is 1. using it! ERROR: JSON parameter file could not be parsed! You can validate the JSON file here: http://qiicr.org/dcmqi/#/validators Exception details (probably not very useful): LargestUInt out of Int range #11.518# ERROR: An error occurred while reading the DICOM Seg file: JSON Exception: file could not be read. #11.520# ERROR: Unknown read error occurred reading /home/nolden/Downloads/Lungs_seg_Left lung_1.dcm
Nov 27 2020
Nov 26 2020
I can confirm this fixes the issue, I can merge it tomorrow
Nov 24 2020
Nov 23 2020
I can confirm this patches fixes the problem. @kislinsk : hotfix oder feature branch?
diff --git a/Rendering/FreeType/vtkFreeTypeTools.cxx b/Rendering/FreeType/vtkFreeTypeTools.cxx index c54289dc60..03b899c4da 100644 --- a/Rendering/FreeType/vtkFreeTypeTools.cxx +++ b/Rendering/FreeType/vtkFreeTypeTools.cxx @@ -378,8 +378,7 @@ FTC_CMapCache* vtkFreeTypeTools::GetCMapCache() }
Nov 17 2020
Oct 20 2020
Ups ;) Replace with - or _?
Oct 19 2020
I was just about to add a note that there is the general question how to handle python in installers. I guess for just having the basic runtime available it would be ok to just load libpython3.so or libpython3.8.so and let the system take the right one from the right path. But on Windows I guess most people don't install Python in system locations. Anyway I think this could be fixed even with the current packaging if we need it for 2020, but I'm just reporting, no pressure from my side ;)
Oct 15 2020
Pushed new branch hotfix/T27887-fix-packaging-with-system-qt.
Oct 9 2020
OpenCV 3.4.11 (https://opencv.org/releases/)
Trivial should be:
PS: as an explanation, one theory is that the install-zip-package still references libraries from the build machine which causes the different behaviour
Sep 25 2020
@schererj we looked at the debug output, thanks. Unfortunately it seems to be complicated ... I would ask you to try another thing:
@kislinsk : I just noticed we had some earlier discussions and there is a branch which fixes two minor issues, not sure if relevant for option (1):
Sep 23 2020
This is resolved, dart client is running on my workstation
Clang 10 on Linux configuration is running now nightly on my desktop machine. "WorkbenchRelease" is green, "All" unfortunately hits an internal clang error . Setting this up on ubuntu would probably solve this, or some update on fedora.
Sep 11 2020
Just checked GDCM 3.0.7 if by chance the issue was fixed there, unfortunately not.
@schererj we just discussed this in the MITK meeting. Could you try something? It would be interesting to compare the outputs of
Since we have this task now I suggest to deactivate them "somewhere globally" and discuss later how to proceed. My guess would be it is quite some effort. Having tests for the generator, packging and the extension mechanism is very important I think, but I'm not sure what the current tests cover and if it's worth to fix.
Jul 30 2020
I'm setting up a clang 10 dart client right now. If that is submitting successfully I would close the task
Jul 29 2020
Jul 28 2020
Jul 27 2020
Jul 20 2020
Jul 16 2020
Added FS-E IT since this is coming from DKFZ radiology
Jul 8 2020
soon'ish == 2 weeks ;)
@norajitr We discussed this today in the MITK 2020 meeting and it stays on the high priority list, no promises regarding a date for a fix but at least some investigation of the underlying cause should happen soon'ish
Jun 19 2020
Jun 17 2020
Jun 15 2020
I am re-opening this since I think this will also become more relevant with the foreseeable use of other REST APIs from MITK , e.g. how did the nvidia segmentation tool resolve this issue for the windows installer? @kislinsk could you comment?
Jun 3 2020
@floca : thanks. Not the whole trick but helped a lot. I will follow up with more geometry questions later ;)
I put a _non-shareable_ dataset in /ad/fs/E132-Projekte/Share/MarcoToMitkTeam .
Jun 2 2020
May 25 2020
May 24 2020
Sorry, did not see your claim, was already working on it. Proposed fix in D308
May 22 2020
Pushed new branch feature/T27438-fix-gcc10-errors.
I changed the superbuild to use ITK 5 with compatibilty and fixed some straightforward issues. This branch can be used for further investigations @floca : some ideas about the geometry issues would be very helpful. The migration guide has an overview on the topic but my experience in that area is limited
Pushed new branch feature/T27437-migrate-to-ITK-5.
Seems the reason this passes on all official clients is Debug vs Release. We currently only test release which ignores asserts. Thus, this should be investigated properly by tracing the problem, Windows and Linux are both affected
May 8 2020
I got some data now which shows a problem with MITK 2018.4 but works with the current master. I don't see though the RWV thing. Can't remember exactly how I investigated this back then. Let's hope the more robust handling of DICOM fixed this as @floca noted , I informed the reporting users that they should comment if this should be investigated again.
I'm currently trying to get access to the relevant data again.
May 7 2020
Does the MITK team have access rights on the NAKO dataset? Then I would suggest an example from there.
May 6 2020
Tests don't fail anymore