’lm_to_projdata‘ does not work in the Siemens mMR example

[Lsman0211]

Hi, Thank you for sharing this project!
I encountered the following issue during practical implementation, and I hope you can provide some guidance.
After simulating the Siemens mMR in GATE and acquiring ROOT data, I tried to use the provided 'root_header_template.hroot' and 'STIR_scanner.hs' to run 'lm_to_projdata' to convert the ROOT data into sinograms. During the process, the following error occurred.

`root@sim:/opt/data/private/sim-Brain_Siemmr/PartOutput# lm_to_projdata lm_to_projdata_template.par

WARNING: KeyParser warning: unrecognized keyword: seed

WARNING: KeyParser warning: unrecognized keyword: offset (num of detectors)

INFO: InputStreamFromROOTFile: Processing data with the following event type inclusions:
Unscattered from same eventID: 1
Unscattered from different eventIDs: 1
Scattered from same eventID: 1
Scattered different eventIDs: 1
Warning in TFile::Init: file brain_siemmr.Coincidences.root probably not closed, trying to recover
Info in TFile::Recover: brain_siemmr.Coincidences.root, recovered key TTree:tree at address 6128951616
Warning in TFile::Init: successfully recovered 1 keys

WARNING: CListModeDataROOT: Trying to figure out the scanner geometry from the information given in the ROOT header file.

INFO: CListModeDataROOT: TOF information is missing. Set relevant keywords if you need TOF:
Maximum number of (unmashed) TOF time bins
Size of unmashed TOF time bins (ps)
TOF timing resolution (ps)

INFO: CListModeDataROOT: used ROOT file brain_siemmr.Coincidences.root

INFO: Setting energy window keys as in STIR3.0

WARNING: Scanner::get_scanner_from_name: scanner'' not found

INFO: Interfile warning: I did not recognise the scanner from 'originating_system' (). Hopefully there is enough information present. I will check this now.

WARNING: Scanner: maximum number of timing positions is not yet known. We can only handle non-TOF.

INFO: Interfile parsing ended up with the following scanner:
Scanner parameters:=
Scanner type :=
Number of rings := 64
Number of detectors per ring := 504
Inner ring diameter (cm) := 65.6
Average depth of interaction (cm) := 0.7
Distance between rings (cm) := 0.40625
Default bin size (cm) := 0.208626
View offset (degrees) := 0
Maximum number of non-arc-corrected bins := 344
Default number of arc-corrected bins := 344
Number of blocks per bucket in transaxial direction := 56
Number of blocks per bucket in axial direction := 8
Number of crystals per block in axial direction := 8
Number of crystals per block in transaxial direction := 9
Number of detector layers := 1
Number of crystals per singles unit in axial direction := 8
Number of crystals per singles unit in transaxial direction := 9
Scanner geometry (BlocksOnCylindrical/Cylindrical/Generic) := Cylindrical
End scanner parameters:=

WARNING: LmToProjData: num_events_to_store has been selected. The frame duration in the Interfile header will be incorrect!
LmToProjData NOT Using FRAME_BASED_DT_CORR
lm to projdata parameters :=
input file := root_header_template.hroot
template projdata := STIR_scanner.hs
frame definition file :=
num events to store := -1
output filename prefix := volBrain-siemmr_7e7
bin normalisation type for pre-normalisation := None

bin normalisation type for post-normalisation := None

maximum absolute segment number to process := 5
do pre normalisation := 0
num tof bins in memory := 1
num segments in memory := 11
store prompts := 1
store delayeds := 1
list event coordinates := 0
end :=

Processing time frame 1

*** Break *** segmentation violation
Generating stack trace...
0x000055b3bd596b45 in from lm_to_projdata
0x00007fb4b4c18d90 in from /usr/lib/x86_64-linux-gnu/libc.so.6
0x00007fb4b4c18e40 in __libc_start_main + 0x80 from /usr/lib/x86_64-linux-gnu/libc.so.6
0x000055b3bd59f3e5 in from lm_to_projdata
`
I attempted to set ‘Scanner geometry (BlocksOnCylindrical/Cylindrical/Generic) := BlocksOnCylindrical’, but the error still persists. When running the GE Discovery 690 example, I did not encounter the same issue.Now, I am not sure how to resolve this issue.