<div>2008/2/5, Jasmine Schirmer <<a href="mailto:jasmine.schirmer@tum.de">jasmine.schirmer@tum.de</a>>:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Dear Gate users and developers, At the end of last year, we reported strange behaviour in the energy spectra of singles and coincidences when using the newest version of Gate (3.1.2). Since then, we have recently received a cluster system in our lab and would like to install Gate on this new system. Has the problem with Gate 3.1.2 been identified and solved? Thanks in advance, Jasmine Schirmer and Irene Torres</blockquote><div> Hi all, Sorry but I was very busy since the beginning of the year ... The problem in energy spectra has been identified but not solved ... because everything demonstrates that the different behaviours between Gate versions are coming from the different Geant4 releases. It is not a problem of coding, and nothing has changed between Gate versions concerning the detection and the transportation, we just use the same Geant4 utilities, but them, they are always changing. Our cluster has encountered some problems but it will be soon functional. So I will install Gate3.0.0 with Geant4.9.0 and Gate3.1.2 with Geant4.8.0.p01 and run the same tests. I think that it will definitively answer the question. And concerning the intersector coincidences problem, I progressed since our cluster was sick ! But it seems to be the same problem: coming from Geant4 versions ... News are coming soon ! And to answer your question Irene and Jasmine, I think you may install the last Gate version because all strange behaviours appear between Gate3.0.0 and Gate3.1.0, and in 3.0.0 there are no Cluster Tools also (if you plan to use its). Moreover it depends on what you want to do in your applications but the differences in energy spectra should not be harmful and the intersector coincidences either (because I think those problems are only related to crystal scattering and crystalSD behaviour), and moreover I think that you will not use intersector coincidences for imaging :-) Cheers, Simon </div></div>