Steve Pieper

No, we were testing the ctk code directly. On Nov 8, 2013 11:12 AM, "Jean-Christophe Fillion-Robin" < [email protected]> wrote: > Could it be related to qSlicerCoreApplication.cxx#L171-172https://github.com/Slicer/Slicer/blob/5b46fd1aa2189acc9915029caeacc274f68cdbdd/Base/QTCore/qSlicerCoreApplication.cxx#L171-172? > > — >...

Hmm, since the cited paper didn't explicitly test the arrow the way it's used currently in Slicer I don't see how it can be cited as a justification for changing...

Moving it to the right side would make it a more explicit change from the current convention and hopefully less confusing to users as a result.

My general preference would be to have the core reader code only handle completely standard dicom so that it is readable and maintainable. Any special code to handle malformed or...

@hjmjohnson could you have a look at this? It fixes https://github.com/InsightSoftwareConsortium/ITK/issues/4108

Thanks for the review @jhlegarreta - I had tried to add just the one function but it looks like my checkout was against an older target. I'll fix it.

> it should be done in GDCM or documented that the changes have to be re-applied after every GDCM update. Very good point! I wasn't sure how ITK interacts with...

This has been fixed already: https://github.com/AIM-Harvard/pyradiomics/pull/857

It's not uncommon for multimodality datasets to define segmentations in different sampling grids from any particular image. It would be great for itkwidgets to handle this situation or at least...

> Different sampling grids between the intensity and label image are already supported. This is handled via ITK-Wasm during render. Great! Then maybe the issue is with the package being...