Befor we follow this idea any further, T26167 should be solved and performance should be checked again.

Tags/Properties that should be used/filled by the rules can be found

Was fixed "by the way". List entries have an "X" now.

Schould be done after T23808: Add Rule base class for DICOM source imagereferences

OK, then there is still an error with test 3.

@reicht: Thanks
@gaoh : Could you (not of high priority; so within the next month, or at a community day) check if the problem still exists with a actual installer. If you need an installer with DICOM editor, i can provide one.

Hail to the new statistics plugin! One more reason why your epic effort was well invested 😄

@hentsch So does that mean it was false alarm or do I missinterpret something?

Thanks for that. The problem arises from a insufficient implementation of the LabelSetImagIO. It currently ignores the time geometry and additional properties :(.

Just as a remark (but I think an important one).

Oh, uh. One can do it that way, but I am not sure if I would realy like to have each instance of an annotation as an on service in the registry. In other cases (like property aliasis or descriptions) we have one service and you register the specific instances there. But I will open up another tasks for this discussion.

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?

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.

One question: Did I understood it correctly, each annotation is added as a microservice? So when I add two Label annotations, I will have to additional microservice instances registered?

Pushed new branch T25861-MatchPoint_executor_handles_pointSet_and_image_interfaces_incorrect.

With T25861 the executor is refactored and uses node selectors. Other plugin are still open.

No problem.

Thanks for the data. If tested it. The results so far

There seem to be multiple things.

We should verify if the problem still exists with Osirix. DICOM Q/R with wDB was checked 2-3 month ago and was working correctly.

In T25823#172363, @hentsch wrote:

@floca Thanks.
Sadly, it doesn't work yet with the dark theme (and I have no clue about CSS to fix it).
What works is

"<font color=\"red\">red label</font>

In T25437#169775, @steint wrote:

Maybe you can check your plugins which are using the chart widget and report things which won't work as expected.

OK. Thanks.

You can use css syntax.

Pushed new branch T25710-test_fix.