Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

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.

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.

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.

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

Resolved, error was in the docker container

Issue in landing page tfda, base pods .

Sounds strange to me.
Is the error still there, if yes can you send me the instance, where this is happening? :)

I like the idea of open sourcing the code and making models available as well. If we can roughly clarify how the workload/hurdles would look like in reality, I can also imagine to back the process. Licensing and publication of trained models arises more often lately, thus any solution here can probably also be fruitful for similar endeavors.

I cannot reproduce the error. When sending the data to an instance the data gets imported. When debugging CTP locally there also seems to be no problem. For me also it looks like the problem is not directly in the CTP but in the java library (dcm4che). Did the files got triggered/send to airflow? Did they get stuck in a quarantine folder of the CTP, and if so in which?

In T27968#220733, @schererj wrote:

This is one of my model DICOMs (not 100% sure if this will reproduce it).
If not I can try to make bigger parts.

Download-link from my instance

Just a remark: The download link does not work for me. I get forbidden access. This is also the case, even if I am logged into the platform. But since there is only one folder in minio I also found it without the link:)

We are going to rewrite the 2-d LabelSetImage mapper and write a 3-d LabelSetImage mapper this year, where this will be addressed. We should at least clean up the duality of the contour properties (binary vs. labelset.contour). We should probably allow to show the contour without any filling and we should clean up the coupling between contours and active label.

This is one of my model DICOMs (not 100% sure if this will reproduce it).
If not I can try to make bigger parts.

Can you send me a dataset to reproduce it? I could try to debug CTP, but it looks like it is not even a problem in CTP but in org.dcm4chri

@kleina can ou review the branch somewhen if the change is OK?