mCT scanner

[robbietuk]

This PR adds the mCT scanner geometry to GATE.

Possible issues to assess:

• No unlisting ability (needs STIR mods)

• Crystal overlap due to block geometry
  Oddly low count rate compared with mMR and D690 (my mistake, it is a good count rate)

• Incorporate bed in scanner

• Create two versions of the mMR, one with 8x8 crystals and the other (current) 8x9 crystals. We can keep both. Requires documentation checks.

TODO:
Add correct authorship and copyright.

Additionally, this combines the csorter and digitiser files for the D690 and mMR.

[robbietuk]

Here is a picture of the issue with detector block overlap (I have made it only 1 ring for demonstration)

[robbietuk]

The aforementioned detector overlap has been corrected. This PR is awaiting testing via the unisting of data in STIR, see UCL/STIR#617.

[robbietuk]

What is the span value on the mCT? I need for creating a STIR interfile header template.
From "Physical and clinical performance of the mCT time-of-flight PET/CT scanner" https://iopscience.iop.org/article/10.1088/0031-9155/56/8/004

"Sinograms comprise 400 radial bins, 168 angular bins, 621 total slices, of which 109 direct planes and 512 oblique planes, and 13 TOF bins (312 ps wide)."

Its Max. ring difference acquired is given in the same document as:

"Max. detector ring difference 49 (38)"

not at all confusing

[KrisThielemans]

I think by default they use span=11, mash=2. not sure about TOF mashing. I seem to recall I had a template in the mCT STIR PR?