[gate-users] Image Reconstruction of Gate output

[Mutanga Theodore]

Hi Kris ,
these are the outputs from running FBP3DRP in debug mode

(gdb) r FBP3DRP.par
Starting program: /afs/hpc2n.umu.se/home/m/muathe02/bin/FBP3DRP FBP3DRP.par

WARNING: Scanner GE Discovery ST: transaxial bucket info is not set

WARNING: Scanner GE Discovery ST: axial bucket info is not set

Program received signal SIGSEGV, Segmentation fault.
0x00000000004342de in
stir::BackProjectorByBinUsingInterpolation::actual_back_project ()

(gdb) info stack
#0  0x00000000004342de in
stir::BackProjectorByBinUsingInterpolation::actual_back_project ()
#1  0x0000000000512ec8 in stir::BackProjectorByBin::back_project ()
#2  0x0000000000512cf8 in stir::BackProjectorByBin::back_project ()
#3  0x00000000005298a6 in stir::FBP2DReconstruction::reconstruct ()
#4  0x000000000048dd72 in
stir::FBP3DRPReconstruction::do_2D_reconstruction ()
#5  0x000000000048d4f2 in stir::FBP3DRPReconstruction::reconstruct ()
#6  0x0000000000514178 in stir::Reconstruction::reconstruct ()
#7  0x000000000048d109 in stir::FBP3DRPReconstruction::reconstruct ()
#8  0x00000000004069eb in main ()
(gdb)

Could you get a clue about the problem from these lines ?

This one is from running sensitivity in the same data:

m191:/scratch/muathe02/Gate_Reconstruction> gdb sensitivity
GNU gdb 6.1-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-linux"...Using host libthread_db
library "/lib/libthread_db.so.1".

(gdb) r OSMAPOSL_osem_with_interfiltering.par
Starting program: /afs/hpc2n.umu.se/home/m/muathe02/bin/sensitivity
OSMAPOSL_osem_with_interfiltering.par

WARNING: Scanner GE Discovery ST: transaxial bucket info is not set

WARNING: Scanner GE Discovery ST: axial bucket info is not set
Get attenuation image from which file (0 = 0's): 0
Get normalisation factors from which file (1 = 1's):1
Starting to process segment 0 (and symmetry related segments)
End-planes of segment 0 will be zeroed

Program received signal SIGSEGV, Segmentation fault.
0x000000000045f7b2 in
stir::BackProjectorByBinUsingInterpolation::actual_back_project ()
(gdb) where
#0  0x000000000045f7b2 in
stir::BackProjectorByBinUsingInterpolation::actual_back_project ()
#1  0x0000000000514608 in stir::BackProjectorByBin::back_project ()
#2  0x0000000000514438 in stir::BackProjectorByBin::back_project ()
#3  0x00000000004b988e in stir::RPC_process_related_viewgrams_sensitivity ()
#4  0x0000000000479900 in stir::distributable_computation ()
#5  0x00000000004b9142 in stir::distributable_compute_sensitivity_image ()
#6  0x0000000000405b78 in stir::compute_sensitivity_image ()
#7  0x0000000000406807 in stir::do_sensitivity ()
#8  0x0000000000408855 in main ()

Hope you can make out something, Im completely lost here.


Also I cheked the projection data segment by segment and it matched with
what I have in the projections.hs header.

The segments run from

 -7  , -6  ,-5   ,...  0  ..., 6 ,  7
 (6)  (12)  (18)      (47)    (12) (6)

The numbers in brackets are the slices.

Hope this gives some more information about my setup.

Cheers
Theo






> Hi Theo
>>
>> I don't know if this is more a STIR issue but it concerns
>> reconstruction from GATE cylindrical PET system using the
>> codes from Sadek.
>>
>
> Well, it's a STIR issue, but on GATE data...
>
>> I have modified the codes replacing DLS things with DST
>> things and then I used creat_projdata template to generate a
>> header file. Using manip_prodata, I can view the sinograms,
>> but when I try to use any of the reconstruction tools, (FBP2D
>> , FBP3DRP , OSMAPSL ) I get a segmentation fault, can you
>> help me trace the source of the problem ?
>>
>
> That shouldn't happen obviously, even with crappy data. However, I have
> no clue where/why it happens with the info you give me. You will have to
> build the debug version of STIR and run it one of the tools in debug
> mode to at least see where it crashes. This goes as follows:
>
> gdb /whereever/it/is/FBP2D
> gdb> cd /wherever/the/data/is
> gdb> r myparameterfile
> (wait till segmentation fault)
> gdb> info stack
> (some more gdb commands)
> gdb> quit
>
> Ideally you then have a look at the value of some of the variables (use
> "p variablename"), maybe after moving up the call-stack ("up").
>
> However, before you go that way, try
> - list_projdata_info to see if you and STIR agree on what the data
> siezes etc are.
> - use display_projdata (or manip_projdata) to look at all segments (not
> just a few).
>
> Good luck!
>
> Kris
>
> _______________________________________________
> gate-users mailing list
> gate-users at lphe1pet1.epfl.ch
> http://lphe1pet1.epfl.ch/mailman/listinfo/gate-users
>