We commented out the entire if-else clause for the RT data and it seems to do what it is supposed to do, even without the special conditions. Need to check that in more detail.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 10 2021
Pushed new branch to rMITK MITK: bugfix/T28455-rt-struct-3d-visibility.
Jun 8 2021
Jun 7 2021
Jun 4 2021
Jun 2 2021
Discussed it in the MITK meeting:
May 10 2021
I narrowed it down.
If you load a RTStruct via DICOMBrwoser, the node has a special "visible" property for stdmulti.widget3 (the 3D view). You can enable/disbale it via the Properties plugin. #Workaround :-P
Ok, we tested it on several machines and it is as described above: After loading via DICOM Browser we can confirm the issue.
Apr 22 2021
Apr 21 2021
Your argument makes sense to me. I did not have a specific order in mind when implementing it, so I do not have any counterargument here.
Forgot something and didn't request review correctly. I will open this one agian.
Apr 20 2021
Apr 19 2021
Apr 15 2021
I updated the draft in the branch directly (same file).
Apr 9 2021
Apr 7 2021
I agree with the raised point. I checked the classes again and do not see a valid reason behind the blackbox_func call. I will fix this.
Sorry, I was on vacation.
Mar 10 2021
Mar 8 2021
Mar 5 2021
The auto wrapping functionality for MPISolverWrapper looks correct and straightforward to me. A check for function type is already included in the HyppopySolver.
I agree. As we already said, we have to work on the mpiplayground anyways and convert it into a propper mpi_example. I will spawn a task for that and include your suggestion there.
Feb 11 2021
@kleina I think you should move the mpi playground stuff away from the top level. Examples would be better suited. Don't you think?
That makes a lot of sense. I personally like the idea of a "optional dependency" better. I will have a look.