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/9Support out of source builds2022-03-04T14:45:04+01:00Adrien Mattamatta@lpccaen.in2p3.frSupport out of source builds*Created by: Munken*
Trying to do a out of source build fails with this message:
```
make
[ 1%] Generating NPVDetectorDict.cxx
/bin/sh: 1: ../scripts/build_dict.sh: not found
make[2]: *** [Core/NPVDetectorDict.cxx] Error 127
make[1]: ...*Created by: Munken*
Trying to do a out of source build fails with this message:
```
make
[ 1%] Generating NPVDetectorDict.cxx
/bin/sh: 1: ../scripts/build_dict.sh: not found
make[2]: *** [Core/NPVDetectorDict.cxx] Error 127
make[1]: *** [Core/CMakeFiles/NPCore.dir/all] Error 2
make: *** [all] Error 2
```
Guess the cmake script for making dicts should be modified to use [CMAKE_SOURCE_DIR](https://cmake.org/cmake/help/v3.0/variable/CMAKE_SOURCE_DIR.html)Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://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/49NeutronWall Array problem2020-04-23T13:34:23+02:00Adrien Mattamatta@lpccaen.in2p3.frNeutronWall Array problem*Created by: kkabita*
If Neutronwall Array is used along with any detector configuration (like MUST2), all the branches in the generated root file of the other detectors show empty spectra, while in the absence of NeutronWall all are wo...*Created by: kkabita*
If Neutronwall Array is used along with any detector configuration (like MUST2), all the branches in the generated root file of the other detectors show empty spectra, while in the absence of NeutronWall all are working fine. Is there any specific reason for this occurrence or this might be a bug?
Please suggest how can I use NeutronWall along with other detectors in the set-up.https://gitlab.in2p3.fr/np/nptool/-/issues/10Detector physics classes leaks memory2020-04-23T13:34:16+02:00Adrien Mattamatta@lpccaen.in2p3.frDetector physics classes leaks memory*Created by: Munken*
Most detector physics classes allocate two `XData` with new, but has an empty constructor. *Created by: Munken*
Most detector physics classes allocate two `XData` with new, but has an empty constructor. Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/56GetThetaWorldFrame() doesn't work!!!!2019-01-09T13:54:40+01:00Adrien Mattamatta@lpccaen.in2p3.frGetThetaWorldFrame() doesn't work!!!!*Created by: Elidiano*
@adrien-matta
If I use for drawing simulation results it doesn't work
https://github.com/adrien-matta/nptool/blob/5f3f84792fc0cb154a34e54baa405b486fe06e9d/NPLib/Physics/TReactionConditions.h#L136-L139
(the ...*Created by: Elidiano*
@adrien-matta
If I use for drawing simulation results it doesn't work
https://github.com/adrien-matta/nptool/blob/5f3f84792fc0cb154a34e54baa405b486fe06e9d/NPLib/Physics/TReactionConditions.h#L136-L139
(the values are are distributed in a range like 0-0.3)
on the contrary using the others functions (GetPhiWorldFrame or GetThetaBeamFrame) all work good...
(It is not correlated to the new way to transform the momentum from beam to lab frame)
it works well also drawing the Theta angle using atan(sqrt(fRC_MomentumX^2+fRC_MomentumY^2)/fRC_MomentumZ)https://gitlab.in2p3.fr/np/nptool/-/issues/55Problem with Short-Lifetime Decays2018-12-03T16:18:27+01:00Greg ChristianProblem with Short-Lifetime DecaysI've discovered a problem with the new way that decays are handled in nptool simulations. The mother nucleus for decays with a short lifetime ends up having a kinetic energy that is far below what it should be.
Within the file `Proces...I've discovered a problem with the new way that decays are handled in nptool simulations. The mother nucleus for decays with a short lifetime ends up having a kinetic energy that is far below what it should be.
Within the file `Process/Decay.cc`, we have the following lines:
```
double energy = PrimaryTrack->GetKineticEnergy();
double time = PrimaryTrack->GetGlobalTime();
// Randomize within the step
// Assume energy loss is linear within the step
// Assume no scattering
double rand = G4RandFlat::shoot();
double length = rand*(m_PreviousLength);
energy += (1-rand)*(m_PreviousEnergy-energy);
```
The intent is that the initial kinetic energy for the decay process is chosen randomly from within the step where the decay is supposed to happen. However, this causes a problem for very short lifetime decays, where the decay happens in the first step following the reaction that proceeds the decay.
When this happens, `PreviousEnergy` is equal to zero, and so the generated energy ends up being randomly distributed between 0 and the correct energy.
The easiest way I can think of to fix this is to have a check `if(PreviousEnergy > 0)` before doing the randomization (otherwise just leave `energy = PrimaryTrack->GetKineticEnergy();`). But maybe there is a more robust way, for example checking the step number or something like that.https://gitlab.in2p3.fr/np/nptool/-/issues/4Polish benchmark2018-12-03T15:36:47+01:00Adrien Mattamatta@lpccaen.in2p3.frPolish benchmarkAdd Time and score
Add Time and score
https://gitlab.in2p3.fr/np/nptool/-/issues/7Gaspard and W1 project to new template2018-12-03T15:36:37+01:00Adrien Mattamatta@lpccaen.in2p3.frGaspard and W1 project to new templateGaspard and W1 analysis project should be switch to the new CMake enable compilation with dynamic loading of the libNPanalysis.so library.
Gaspard and W1 analysis project should be switch to the new CMake enable compilation with dynamic loading of the libNPanalysis.so library.
https://gitlab.in2p3.fr/np/nptool/-/issues/23Geometry Definitions2018-12-03T15:36:24+01:00Adrien Mattamatta@lpccaen.in2p3.frGeometry Definitions*Created by: padsley*
This is more of a comment/request than a bug.
How is the geometry defined for detectors? There's the option to set R, theta, phi etc. and a 'Beta' which is probably the orientation of the system. How is this def...*Created by: padsley*
This is more of a comment/request than a bug.
How is the geometry defined for detectors? There's the option to set R, theta, phi etc. and a 'Beta' which is probably the orientation of the system. How is this defined?
It would be good to have this in the guide somewhere.
P.S. I may have just missed this information but I'm in the middle of a nightshift and I have no idea what's happening anymore.https://gitlab.in2p3.fr/np/nptool/-/issues/25Segfaults - currently for information only.2018-12-03T15:36:05+01:00Adrien Mattamatta@lpccaen.in2p3.frSegfaults - currently for information only.*Created by: padsley*
This issue has been created for my own benefit so I have a place to store my thoughts. As you were.
I am currently getting a segmentation violation sometimes.
If I run a calculation with the same inputs, some...*Created by: padsley*
This issue has been created for my own benefit so I have a place to store my thoughts. As you were.
I am currently getting a segmentation violation sometimes.
If I run a calculation with the same inputs, sometimes when I do /run/beamOn N, it crashes.
The culprit is Target::SlowDownBeam, which, when the fault occurs, is doing its first call using G4ParticleDefinition* (this is line 252 in Target.cc where `if(Beam->GetParticleName()=="neutron"` appears.
The failure always comes at the first event which makes me think that something is going wrong in the initialisation.
If I comment out that line (252), then the code fails further down. Yay.
The failure is not consistent - i.e. it doesn't always happen. If I re-run with the same input, things are working fine.Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/39Check geometry followed by reloading geometry followed by check geometry seg ...2018-12-03T15:35:29+01:00Adrien Mattamatta@lpccaen.in2p3.frCheck geometry followed by reloading geometry followed by check geometry seg faul*Created by: robertshearman*
Title explains the problem.
When checking geometry, moving source or detector position in detector config then reloading and checking, a segmentation fault ensues at least on my machine.
This occurs acros...*Created by: robertshearman*
Title explains the problem.
When checking geometry, moving source or detector position in detector config then reloading and checking, a segmentation fault ensues at least on my machine.
This occurs across all detectors, whether there are overlaps or not etc.