nptool issueshttps://gitlab.in2p3.fr/np/nptool/-/issues2023-08-23T16:16:31+02:00https://gitlab.in2p3.fr/np/nptool/-/issues/70Event generator file for 7Be breakup (resonant or two step breakup process)2023-08-23T16:16:31+02:00Subhankar MaityEvent generator file for 7Be breakup (resonant or two step breakup process)Hi,
I am carrying out the resonant breakup of 7Be on 12C target using the reaction :
7Be + 12C -> 3He + 4He + 12C at E = 35 MeV
Could you please check if the event generator file is correct or not ? I have attached the even...Hi,
I am carrying out the resonant breakup of 7Be on 12C target using the reaction :
7Be + 12C -> 3He + 4He + 12C at E = 35 MeV
Could you please check if the event generator file is correct or not ? I have attached the event generator file for the above reaction. Please reply at your earliest convenience.
[7Be_breakup.reaction](/uploads/11fa2a3017db7568b96d48bfc6cd1bcf/7Be_breakup.reaction)Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/69Orientation issue of scintillator detector in NPTool wizard2023-06-12T11:27:07+02:00Subhankar MaityOrientation issue of scintillator detector in NPTool wizardHi!
[SAND.detector](/uploads/af8ffa2612cfb39804f2ac56f93a0136/SAND.detector)
![Screenshot_SAND_NPTool](/uploads/11bf759aaee77e4e54163c1254c00d24/Screenshot_SAND_NPTool.png)
We have been carrying out the simulation of 9Li(gamma, n)8Li. W...Hi!
[SAND.detector](/uploads/af8ffa2612cfb39804f2ac56f93a0136/SAND.detector)
![Screenshot_SAND_NPTool](/uploads/11bf759aaee77e4e54163c1254c00d24/Screenshot_SAND_NPTool.png)
We have been carrying out the simulation of 9Li(gamma, n)8Li. We’ve created a new detector (default cube scintillation detector) using the NPTool wizard to detect neutrons. However, there is an orientation issue of the detector as it looks like it has only one vector to determine its position. The issue is clearly visible when we make an array of the detector. Is there an easy way to add more position vectors so that I can control its orientation completely?
The following files are attached :
1. Detector file (SAND array)
2. Screenshot of the array from NPTool GUI
Thank youhttps://gitlab.in2p3.fr/np/nptool/-/issues/68fDetected_Angle_Theta inconsistency in Simulated file2022-03-04T15:02:14+01:00Subhankar MaityfDetected_Angle_Theta inconsistency in Simulated fileHi
I am trying to simulate the deuteron target breakup using the event generator “Be_PhaseSpace.reaction” which you provided last time. But the hurdle I am facing is with the theta angles of protons detected in W1 and SSSD (ΔE-E config...Hi
I am trying to simulate the deuteron target breakup using the event generator “Be_PhaseSpace.reaction” which you provided last time. But the hurdle I am facing is with the theta angles of protons detected in W1 and SSSD (ΔE-E config). I used Annular S1 (8 – 25 degrees) at front angular region and W1 and SSSD (ΔE-E config) in angular region 40 – 80 degrees.
I have attached the event generator file, detector configuration file.
When we plot W1 back strip numbers vs detected theta we get a plot that is inconsistent with our detector configuration, i.e the detected angle should be in 40 – 80 deg range whereas we see the values below 30 degrees also. The plot is attached.
Please have a look. What could be the reason for the inconsistency?
Thank you very much.
Subhankar[Be_PhaseSpace.reaction](/uploads/b1e571c1ddc807efe780913c1980bcc4/Be_PhaseSpace.reaction)[S1_W1_SSSDconfig.detector](/uploads/d9c1ad10b195f4daf282a4f70e4690dd/S1_W1_SSSDconfig.detector)![Back_Strip_vs_theta.svg](/uploads/e32eb7d3b5277943a5f86d9b027cdc36/Back_Strip_vs_theta.svg)https://gitlab.in2p3.fr/np/nptool/-/issues/67Event generator file for deuteron target breakup2022-02-24T14:09:52+01:00Subhankar MaityEvent generator file for deuteron target breakupI am trying to simulate the target break up of deuteron using the reaction :
7Be + d -> (p + n) + 7Be for E(7Be) = 35 MeV
Could you please check if the event generator file is correct or not ? I have attached the event generator file f...I am trying to simulate the target break up of deuteron using the reaction :
7Be + d -> (p + n) + 7Be for E(7Be) = 35 MeV
Could you please check if the event generator file is correct or not ? I have attached the event generator file for the above reaction.
[deuteron_breakup.reaction](/uploads/18b0ee799bfb4ff1193a6f46ca4045fd/deuteron_breakup.reaction)https://gitlab.in2p3.fr/np/nptool/-/issues/66Unable to install NPTool in Ubuntu 20.042022-02-23T12:10:40+01:00Subhankar MaityUnable to install NPTool in Ubuntu 20.04Hi,
I am trying to install NPTool in Ubuntu 20.04 LTS operating system but I am getting some cmake errors. The ROOT version is 6.24.06 and Geant4 version is 4.10.07.p03. I have attached the screenshot of the error and the cmake output l...Hi,
I am trying to install NPTool in Ubuntu 20.04 LTS operating system but I am getting some cmake errors. The ROOT version is 6.24.06 and Geant4 version is 4.10.07.p03. I have attached the screenshot of the error and the cmake output logfile.
Please have a look. Any help is greatly appreciated.
![Screenshot_from_2022-02-23_14-43-07](/uploads/cd24fba399fed8d2bb736e3b858f9013/Screenshot_from_2022-02-23_14-43-07.png)
[CMakeOutput.log](/uploads/631ce4ede645ccf2a4465760b1c49bde/CMakeOutput.log)https://gitlab.in2p3.fr/np/nptool/-/issues/65Errors during compilation, due to C++ standard ?2021-06-09T17:18:57+02:00MehdiErrors during compilation, due to C++ standard ?Hi
**I'm using ubuntu 20.04. I compiled from source latest ROOT version and it was done (by default) with C++14 standard, so I forced compilation with C++14 also for GEANT4. How I can check/change the C++ standard used for nptool compil...Hi
**I'm using ubuntu 20.04. I compiled from source latest ROOT version and it was done (by default) with C++14 standard, so I forced compilation with C++14 also for GEANT4. How I can check/change the C++ standard used for nptool compilation ? here are the arguments I used :**
sudo cmake -Dgdml=ON -Dminuit2=ON -DCMAKE_INSTALL_PREFIX=/home/dz/products/ROOT6.24.00/ /home/dz/products/root-6.24.00/
sudo cmake -DCMAKE_INSTALL_PREFIX=../GEANT4.10.07.p01 -DGEANT4_BUILD_MULTITHREADED=ON -DGEANT4_INSTALL_DATA=ON -DGEANT4_USE_QT=ON -DGEANT4_USE_RAYTRACER_X11=OFF -DGEANT4_USE_OPENGL_X11=ON -DGEANT4_USE_GDML=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DGEANT4_USE_XM=OFF -DGEANT4_ENABLE_TESTING=OFF -DGEANT4_BUILD_CXXSTD=14 -DGEANT4_USE_RAYTRACER_X11=OFF -DGEANT4_USE_SYSTEM_CLHEP=OFF -DGEANT4_USE_SYSTEM_ZLIB=OFF ../geant4.10.07.p01
**When I execute "make -j8 install" I get these errors :**
\[ 0%\] Building CXX object Core/CMakeFiles/NPCore.dir/NPRandom.cxx.o In file included from /home/dz/products/ROOT6.24.00/include/TString.h:29, from /home/dz/products/ROOT6.24.00/include/TNamed.h:26, from /home/dz/products/ROOT6.24.00/include/TRandom.h:25, from /home/dz/products/ROOT6.24.00/include/TRandom1.h:25, from /home/dz/products/nptool/NPLib/Core/NPRandom.h:29, from /home/dz/products/nptool/NPLib/Core/NPRandom.cxx:22: /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:32:37: error: ‘experimental’ in namespace ‘std’ does not name a type 32 | using basic_string_view = ::std::experimental::basic_string_view<_CharT,_Traits>; | ^\~\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:35:12: error: ‘basic_string_view’ does not name a type 35 | typedef basic_string_view string_view; | ^\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:36:12: error: ‘basic_string_view’ does not name a type 36 | typedef basic_string_view<char16_t> u16string_view; | ^\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:37:12: error: ‘basic_string_view’ does not name a type 37 | typedef basic_string_view<char32_t> u32string_view; | ^\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:38:12: error: ‘basic_string_view’ does not name a type 38 | typedef basic_string_view<wchar_t> wstring_view; | ^\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:48:28: error: ‘string_view’ is not a member of ‘std’ 48 | inline double stod(std::string_view str, size_t *pos) | ^\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:48:28: note: ‘std::string_view’ is only available from C++17 onwards /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:48:52: error: expected primary-expression before ‘*’ token 48 | inline double stod(std::string_view str, size_t \*pos) | ^ /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:48:53: error: ‘pos’ was not declared in this scope; did you mean ‘pow’? 48 | inline double stod(std::string_view str, size_t \*pos) | ^\~\~ | pow /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:48:56: error: expression list treated as compound expression in initializer \[-fpermissive\] 48 | inline double stod(std::string_view str, size_t \*pos) | ^ /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:65:56: error: ‘std::string_view’ has not been declared 65 | inline std::string &operator+=(std::string &left, std::string_view right) | ^\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx: In function ‘std::string& std::__ROOT::operator+=(std::string&, int)’: /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:67:29: error: request for member ‘data’ in ‘right’, which is of non-class type ‘int’ 67 | return left.append(right.data(), right.size()); | ^\~\~\~ /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:67:43: error: request for member ‘size’ in ‘right’, which is of non-class type ‘int’ 67 | return left.append(right.data(), right.size()); | ^\~\~\~ /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx: At global scope: /home/dz/products/ROOT6.24.00/include/ROOT/RStringView.hxx:84:17: error: expected type-specifier 84 | operator std::string_view() const { return std::string_view(fData,fLength); } | ^\~\~ In file included from /home/dz/products/ROOT6.24.00/include/TNamed.h:26, from /home/dz/products/ROOT6.24.00/include/TRandom.h:25, from /home/dz/products/ROOT6.24.00/include/TRandom1.h:25, from /home/dz/products/nptool/NPLib/Core/NPRandom.h:29, from /home/dz/products/nptool/NPLib/Core/NPRandom.cxx:22: /home/dz/products/ROOT6.24.00/include/TString.h:115:13: error: expected type-specifier 115 | operator std::string_view() const { return std::string_view(Data(),fExtent); } | ^\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:280:32: error: ‘string_view’ in namespace ‘std’ does not name a type 280 | explicit TString(const std::string_view &sub); | ^\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:280:27: note: ‘std::string_view’ is only available from C++17 onwards 280 | explicit TString(const std::string_view &sub); | ^\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:317:37: error: ‘string_view’ in namespace ‘std’ does not name a type 317 | TString &operator=(const std::string_view &s); | ^\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:317:32: note: ‘std::string_view’ is only available from C++17 onwards 317 | TString &operator=(const std::string_view &s); | ^\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:444:9: error: ‘string_view’ in namespace ‘std’ does not name a type 444 | std::string_view View() const { return std::string_view(GetPointer(),Length()); } | ^\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:444:4: note: ‘std::string_view’ is only available from C++17 onwards 444 | std::string_view View() const { return std::string_view(GetPointer(),Length()); } | ^\~\~ In file included from /home/dz/products/ROOT6.24.00/include/TNamed.h:26, from /home/dz/products/ROOT6.24.00/include/TRandom.h:25, from /home/dz/products/ROOT6.24.00/include/TRandom1.h:25, from /home/dz/products/nptool/NPLib/Core/NPRandom.h:29, from /home/dz/products/nptool/NPLib/Core/NPRandom.cxx:22: /home/dz/products/ROOT6.24.00/include/TString.h:839:53: error: ‘string_view’ in namespace ‘std’ does not name a type 839 | inline Bool_t operator==(const char \*s1, const std::string_view &s2) | ^\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:839:48: note: ‘std::string_view’ is only available from C++17 onwards 839 | inline Bool_t operator==(const char *s1, const std::string_view &s2) | ^\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:839:15: error: ‘Bool_t operator==(const char*, const int&)’ must have an argument of class or enumerated type 839 | inline Bool_t operator==(const char \*s1, const std::string_view &s2) | ^\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:844:37: error: ‘string_view’ in namespace ‘std’ does not name a type 844 | inline Bool_t operator==(const std::string_view &s1, const char *s2) | ^\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:844:32: note: ‘std::string_view’ is only available from C++17 onwards 844 | inline Bool_t operator==(const std::string_view &s1, const char s2) | ^\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:844:15: error: ‘Bool_t operator==(const int&, const char)’ must have an argument of class or enumerated type 844 | inline Bool_t operator==(const std::string_view &s1, const char s2) | ^\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:857:37: error: ‘string_view’ in namespace ‘std’ does not name a type 857 | std::string printValue(const std::string_view val); | ^\~\~\~\~\~\~\~\~\~\~ /home/dz/products/ROOT6.24.00/include/TString.h:857:32: note: ‘std::string_view’ is only available from C++17 onwards 857 | std::string printValue(const std::string_view* val); | ^\~\~ make\[2\]: \*\*\* \[Core/CMakeFiles/NPCore.dir/build.make:88: Core/CMakeFiles/NPCore.dir/NPRandom.cxx.o\] Error 1 make\[1\]: \*\*\* \[CMakeFiles/Makefile2:3746: Core/CMakeFiles/NPCore.dir/all\] Error 2 make: \*\*\* \[Makefile:130: all\] Error 2
**Tell me if you need more informations on my system!**
**Regards**
**Mehdi**Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/64MUST2 Thresholds (and resolutions) in npsimulation2020-11-30T00:24:59+01:00Mhd MoukaddamMUST2 Thresholds (and resolutions) in npsimulationIs there a reason why we fix the thresholds and the resolutions of the detectors in MUST2?
Suggestion:
We can read the same MUST2 Config file to load the E-thresholds and use them in the simulation, this is important for efficiency calc...Is there a reason why we fix the thresholds and the resolutions of the detectors in MUST2?
Suggestion:
We can read the same MUST2 Config file to load the E-thresholds and use them in the simulation, this is important for efficiency calculations post experiment. Same can be said about the resolutions, new tokens (transparent for the analysis.cxx) can be added to the Config file to give the user more control on the E/T resolutions and avoid potential tampering with the source code.Mhd MoukaddamMhd Moukaddamhttps://gitlab.in2p3.fr/np/nptool/-/issues/63Simulation is stuck at "starting run 1"2020-11-18T10:29:15+01:00Sk Mustak AliSimulation is stuck at "starting run 1"Hi,
I am trying to simulate 7Be + d -> p + 8Be -> p + (p + 7Li) using a 7Be beam of 35 MeV. However, the simulation is getting stuck at "starting run 1" even if I try to run it for a single event.
I have attached the event generator f...Hi,
I am trying to simulate 7Be + d -> p + 8Be -> p + (p + 7Li) using a 7Be beam of 35 MeV. However, the simulation is getting stuck at "starting run 1" even if I try to run it for a single event.
I have attached the event generator file and the screenshot of the terminal after running the simulation. Any help or suggestion is highly appreciated.
[7Bed7Li.reaction](/uploads/463973258f6d204a75eca55e7ad49598/7Bed7Li.reaction)
![Screenshot_from_2020-11-12_19-21-34](/uploads/a83ad00eb57947b22e251d1c11db6a81/Screenshot_from_2020-11-12_19-21-34.png)https://gitlab.in2p3.fr/np/nptool/-/issues/62Event generator file for 9B decay2020-10-20T11:41:04+02:00Sk Mustak AliEvent generator file for 9B decayHi,
I need help regarding writing the event generator file for the reaction :
7Be + d -> 9B* -> 8Be* + p -> a + a + p
I could not find a sample input file in NPTool to simulate this type of 3 body decay via a compound nucleus formation.Hi,
I need help regarding writing the event generator file for the reaction :
7Be + d -> 9B* -> 8Be* + p -> a + a + p
I could not find a sample input file in NPTool to simulate this type of 3 body decay via a compound nucleus formation.Pierre MorfouacePierre Morfouacehttps://gitlab.in2p3.fr/np/nptool/-/issues/61Not writing dEdX table for fragment in batch mode2020-10-19T11:45:04+02:00flavignyNot writing dEdX table for fragment in batch modeWe realised that the dEdX tables for particles produced in a Reaction (2-body or QFS) are not written when running the simulation in batch mode. This is not the case with an interactive GUI session.
Maybe the EndOfRunAction() in which th...We realised that the dEdX tables for particles produced in a Reaction (2-body or QFS) are not written when running the simulation in batch mode. This is not the case with an interactive GUI session.
Maybe the EndOfRunAction() in which these tables are written is not called in batch mode....https://gitlab.in2p3.fr/np/nptool/-/issues/34npanalysis - selecting a portion of useful data in the output tree2017-05-24T16:59:09+02:00Adrien Mattamatta@lpccaen.in2p3.frnpanalysis - selecting a portion of useful data in the output tree*Created by: moukaddam*
Is there a way to store only a portion of the analysed tree?
The point is to optimise the time spent at during the preliminary analysis.
In the npanalysis.cxx the portion where we fill the tree follows the...*Created by: moukaddam*
Is there a way to store only a portion of the analysed tree?
The point is to optimise the time spent at during the preliminary analysis.
In the npanalysis.cxx the portion where we fill the tree follows the 'Building of a physical event" without any check from the user:
`for (unsigned int i = 0 ; i < nentries; i++) {
// Get the raw Data
Chain -> GetEntry(i);
// Build the current event
myDetector->BuildPhysicalEvent();
// Fill the tree
tree->Fill();
etc...
} `
One way to do what is suggested is to redefine BuildPhysicalEvent() with a return value, that can be used as a condition to Fill the tree or to skip this step.
(Cc @ryanwilkinson)
https://gitlab.in2p3.fr/np/nptool/-/issues/41File "DetectorManager.h" missing2017-08-21T12:08:41+02:00Adrien Mattamatta@lpccaen.in2p3.frFile "DetectorManager.h" missing*Created by: mustak21*
Hi,
I tried performing analysis using the W1 detector. On giving the `make -j4` command I am getting the following errors:
> In file included from /home/geant4/nptool/Projects/W1/Analysis.cxx:1:0:
/home/geant...*Created by: mustak21*
Hi,
I tried performing analysis using the W1 detector. On giving the `make -j4` command I am getting the following errors:
> In file included from /home/geant4/nptool/Projects/W1/Analysis.cxx:1:0:
/home/geant4/nptool/Projects/W1/Analysis.h:9:29: fatal error: DetectorManager.h: No such file or directory
#include "DetectorManager.h"
^
compilation terminated.
make[2]: *** [CMakeFiles/NPAnalysis.dir/Analysis.cxx.o] Error 1
make[1]: *** [CMakeFiles/NPAnalysis.dir/all] Error 2
make: *** [all] Error 2
https://gitlab.in2p3.fr/np/nptool/-/issues/40nptool-wizard and NPVSpectra.h2017-09-29T13:49:18+02:00Adrien Mattamatta@lpccaen.in2p3.frnptool-wizard and NPVSpectra.h*Created by: robertshearman*
When creating a new detector, currently the make fails due to the GetHisto and GetCanvas functions derived from NPVSpectra.h.
The GetHisto function is commented in $NPL/core/NPVSpectra.h and the GetCanvas...*Created by: robertshearman*
When creating a new detector, currently the make fails due to the GetHisto and GetCanvas functions derived from NPVSpectra.h.
The GetHisto function is commented in $NPL/core/NPVSpectra.h and the GetCanvas function is missing. (line 66).
in $NPL/Include/NPVSpectra.h these functions are present and uncommented.
Un-commenting and adding in core allows for compilation, however I do not know if this is wanted/recommended and I haven't tested these functions.
It should be noted that some detectors in the repo have simply commented out these functions.
https://gitlab.in2p3.fr/np/nptool/-/issues/36checking nptool version2017-06-06T11:18:33+02:00Adrien Mattamatta@lpccaen.in2p3.frchecking nptool version*Created by: mustak21*
How to check which version of NPTOOL I am using ? *Created by: mustak21*
How to check which version of NPTOOL I am using ? https://gitlab.in2p3.fr/np/nptool/-/issues/44Error in accessing branch W1 of simulated root file.2017-07-18T17:10:33+02:00Adrien Mattamatta@lpccaen.in2p3.frError in accessing branch W1 of simulated root file.*Created by: mustak21*
Hi,
I have the root file generated after simulation of a reaction. The branches are the various detectors namely AnnularS1,W1,SSSD etc. I wrote a macro which needs to access the leaves of the branch of W1. Howe...*Created by: mustak21*
Hi,
I have the root file generated after simulation of a reaction. The branches are the various detectors namely AnnularS1,W1,SSSD etc. I wrote a macro which needs to access the leaves of the branch of W1. However on executing the macro I am getting the error
```
> use of undeclared identifier 'W1'
t0->SetBranchAddress("W1",&W1);
```
So where is the variable W1 defined ?
I am attaching the macro .
[W1_theta.pdf](https://github.com/adrien-matta/nptool/files/1155073/W1_theta.pdf)
https://gitlab.in2p3.fr/np/nptool/-/issues/26Randomizing channels prior to calibration2017-05-15T10:36:33+02:00Adrien Mattamatta@lpccaen.in2p3.frRandomizing channels prior to calibration*Created by: moukaddam*
@adrien-matta I was wondering why raw data values are not systematically randomised prior to calibration.
is there any good reason for that?*Created by: moukaddam*
@adrien-matta I was wondering why raw data values are not systematically randomised prior to calibration.
is there any good reason for that?https://gitlab.in2p3.fr/np/nptool/-/issues/43Simulating Coincidence Sources2017-08-21T12:05:55+02:00Greg ChristianSimulating Coincidence SourcesI would like to simulate emission of multiple particles of the same type and different (but specific) energies from a source. For example, something like coincident 1173 keV and 1333 keV gamma-rays from 56Co.
Is there any way to do th...I would like to simulate emission of multiple particles of the same type and different (but specific) energies from a source. For example, something like coincident 1173 keV and 1333 keV gamma-rays from 56Co.
Is there any way to do this that is already implemented in nptool? I couldn't find anything either in the documentation or by looking through the code. `EventGeneratorIsotropic` can do similar things, for example emit multiple particles in the same event, but they have to have the same energy or have random energies picked from the same range.
This is quite an easy feature to add, and in fact I've already done so in my version of the code. I did this by modifying `EventGeneratorIsotropic` such that all of the parameters related to particle emission are stored in vectors, which are looped over and the final particle is added to the `ParticleStack`. Different particles are specified in the configuration file, by adding a new `Isotropic` block.
I can check these changes in, of course, but before doing do, I wanted to make sure that 1) there isn't already the same feature available in nptool; and 2) that the way I have done things won't conflict with the intended way of using ``EventGeneratorIsotropic`.https://gitlab.in2p3.fr/np/nptool/-/issues/21nptool-wizard token problem2016-12-16T15:59:31+01:00Adrien Mattamatta@lpccaen.in2p3.frnptool-wizard token problem*Created by: gizmo404*
When you run nptool-wizard it sets "pipo" as the token for detectors in the input file rather than the name you gave your detector.*Created by: gizmo404*
When you run nptool-wizard it sets "pipo" as the token for detectors in the input file rather than the name you gave your detector.https://gitlab.in2p3.fr/np/nptool/-/issues/24Compilation Problems2017-02-09T17:40:52+01:00Adrien Mattamatta@lpccaen.in2p3.frCompilation Problems*Created by: padsley*
I'm struggling with this a bit...
I'm trying to recompile nptool as I've been making changes to the two-body reaction code to make it better for use with the SplitPole+silicon Orsay work.
NPLib compiles witho...*Created by: padsley*
I'm struggling with this a bit...
I'm trying to recompile nptool as I've been making changes to the two-body reaction code to make it better for use with the SplitPole+silicon Orsay work.
NPLib compiles without a problem (if I limit the compilation to W1 and SplitPole because that's all that I want).
However, NPSimulation is throwing this:
```
[ 2%] Building CXX object Scorers/CMakeFiles/NPSScorers.dir/SiliconScorers.cc.o
In file included from /home/padsley/codes/nptoolNew/NPSimulation/Scorers/SiliconScorers.cc:22:0:
/home/padsley/codes/nptoolNew/NPSimulation/Scorers/SiliconScorers.hh:29:21: fatal error: NPImage.h: No such file or directory
compilation terminated.
Scorers/CMakeFiles/NPSScorers.dir/build.make:86: recipe for target 'Scorers/CMakeFiles/NPSScorers.dir/SiliconScorers.cc.o' failed
make[2]: *** [Scorers/CMakeFiles/NPSScorers.dir/SiliconScorers.cc.o] Error 1
CMakeFiles/Makefile2:346: recipe for target 'Scorers/CMakeFiles/NPSScorers.dir/all' failed
make[1]: *** [Scorers/CMakeFiles/NPSScorers.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
```
Now, this is occurring because the compiler can't find the header "NPImage.h" which is in `/home/padsley/codes/nptoolNew/NPLib/Core`.
I am sourcing `nptool.sh` in my .bashrc, and `nps`, `npl` and `npa` all give the expected behaviour.
I can get around this problem by manually setting e.g. C_INCLUDE_PATH in the system but this seems unsatisfactory.
To be honest, I can't work out what this isn't working. I tried checking out a new version of the repo to test it on my machine but I get the same problem. Is it a task for the user to set the include paths or has something gone wrong?https://gitlab.in2p3.fr/np/nptool/-/issues/27Issue in NPSimulation/Scorers/SiliconScorers.cc and .hh2017-03-28T16:50:34+02:00Adrien Mattamatta@lpccaen.in2p3.frIssue in NPSimulation/Scorers/SiliconScorers.cc and .hh*Created by: malabi*
An issue was recently reported to me regarding this scorer while used for a gamma-ray detection system, as it returned a wrong strip id assignment and wrong strip multiplicity.
The origin of this problem turne...*Created by: malabi*
An issue was recently reported to me regarding this scorer while used for a gamma-ray detection system, as it returned a wrong strip id assignment and wrong strip multiplicity.
The origin of this problem turned out to be the variable m_Index that is declared as a G4int in the header file but, as used in the cc file (line showed below), can take very large values.
m_Index = aStep->GetTrack()->GetTrackID() + m_DetectorNumber * 1e3 + m_StripLengthNumber * 1e6 + m_StripWidthNumber * 1e9;
The solution is to declare m_Index as a long integer with: int long or G4long.