[gate-users] patch for STIR for recon Gate output

[Kris Thielemans]

Hi Long

> In my understanding, an "Unknown" original system in the 
> interfile will cause STIR
> to guess what kind of scanner it belongs to through its 
> detectors/ring. This is
> what I mean  "auto-detection". Actually, the Unknown_Scanner 
> will be replaced with
> ECAT 962 later. What's more, sometime, a user-defined system 
> may has the same
> detectors/ring as a known scanner. these may cause "dramtic 
> output" as the warning
> message of STIR, and correctness will not be assured.

Alright, you have a point.
We'll put it in.
> > there are other scanner  parameters that we
> > could/should add. These then should all be added to the 
> interfile 4.0
> > proposal of course.
> > 
> 
> That's great! But now, the scanner parameter seems no 
> propriate way to add. At
> least neither of my proposal.
> 

And we should do that now. I really don't like asking the user question
while parsing. Mostly you want to run STIR non-interactively.

> 
> Great, send please. :-) I have read the corresponding code in 
> current release, and
> found that the lmf data can be converted to sets of 
> projection. Am I right?
> 

IF somebody contributes the code to read the LMF format via our
CListMode classes, then all list mode functionality in STIR will work.
And at present that's only lm_to_projdata, but in the not too distant
future it will be ML reconstructino from the list mode data.

> I also want to talk with 
> STIR developers, but
> just can't.
>

Register yourself on the stir-devel mailing list (via the web-site), and
you can.

Kris