Steve Pieper

Now that we are moving to discourse and github, markdown is becoming the common syntax. I feel like using rst for one specific task and markdown everywhere else is going...

> if not initialized by the user explicitly in a longitudinal tracking situation, TrackingUID will be different even if the structure is the same I'd say this is appropriate -...

I'd actually leave this open - the underlying issue isn't fixed yet.

FYI - the dcmqi extension is also broken, and that breaks quantitative reporting: http://slicer.cdash.org/viewBuildError.php?buildid=1843321

Sound good - I hope there's an easy fix for the extension. The build errors are all about things like `CERR` and `COUT` not being defined. e.g. `D:\D\P\S-0-E-b\DCMQI\libsrc\TID1500Reader.cpp(21): error C2065:...

If you take this conversation off the public ticket please report back what you decide - it sounds like an important use case and I look forward to seeing the...

I don't think it would be a problem to have a 2D image with identity geometry at the ITK level. Putting the segmentation back into DICOM will require some knowledge...

From the Slicer point of view we tend to insist that images are positioned in patient space, but if you load a single slice 2D image it is just in...

Related to this, I followed the example from the Archive.zip files to implement a javascript structured report demo. https://github.com/pieper/dcmjs/commit/cb2846a29e208e8fc1325a636146e156e739d212

The live (prototype) demo is here: https://pieper.github.io/dcmjs/examples/linearMeasurements/index.html