Hi there! 🙂
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 10 2021
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Mar 9 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.
Mar 4 2021
Mar 3 2021
In this case we solved it by upgrading BiocManager. Probably the previous version did not know about the later version of "graph".
graph had only been used for networks, I guess version 1.62 is sufficient
The package "graph" was moved from CRAN to Bioconductor:
https://cran.r-project.org/web/packages/graph/index.html
In T26485#185423, @kalali wrote:Also when changing the interaction mode (PACS <-> MITK) while the segmentation tool (e.g. Add) is active, the changed interaction mode will overwrite the segmentation interaction and the render window changes again while drawing the segmentation.
Mar 2 2021
Since you also mentioned different editors: Not sure if this is also related but one of the terminal outputs of the testers was:
I will go through the source tree and as a rule of thumb I will just add nullptr checks if the render window part is only used for rendering updates and add the OPEN strategy if more is done with the reference and there is not already a nullptr check.
Mar 1 2021
I tested it in debug mode and the fix is pretty simple. The crashes occurs in lines like GetRenderWindowPart()->RequestUpdate() when GetRenderWindowPart() returns a nullptr. I guess there are quite a few unchecked lines like this in MITK.
I got the same result as kislinsk, the crash only occurs when the documentation is open and not in the background
When I reproduced the issue with MatchPoint, it didn't happen when the documentation was in the background (i.e. the documentation is not the active editor). I guess this is a good starting point for debugging.
With the modelfit inspector it most often crashed, if the user clicked on a datanode in the datastorage
Feb 26 2021
Feb 25 2021
Resolved, error was in the docker container
Issue in landing page tfda, base pods .