nptool issueshttps://gitlab.in2p3.fr/np/nptool/-/issues2020-04-23T13:34:23+02:00https://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/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/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/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/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/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.
https://gitlab.in2p3.fr/np/nptool/-/issues/42a simple Foil class2017-08-21T12:08:16+02:00Adrien Mattamatta@lpccaen.in2p3.fra simple Foil class*Created by: moukaddam*
With Sharc experiments (also potentially with Spice) we use passive foils as ion catchers or screens, mostly made of aluminum but could also be of other materials, . I didn't find one so I made it using nptool-wi...*Created by: moukaddam*
With Sharc experiments (also potentially with Spice) we use passive foils as ion catchers or screens, mostly made of aluminum but could also be of other materials, . I didn't find one so I made it using nptool-wizard.
Due to the "passive" purpose of this object, the spectra class was deleted since they are likely not to be used. I can also turn off the "sensitivity" but I figured out it might be useful in the future.
@adrien-matta Let me know what you think about that, and whether you think it's worth it to add back the Histogram class.
This class can also be used in a plunger set-up.
Here's the possible configs:
------------------------------------
Foil
POS = 0 0 250 mm
Shape= Square
Height= 40 mm
Width= 40 mm
Thickness= 10 micrometer
Material= Al
%%%%%%%%%%%
Foil
R= 350 mm
THETA= 90 deg
PHI= 63 deg
Shape= Cylindrical
Radius= 30 mm
Thickness= 2 mm
Material= Cu
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.https://gitlab.in2p3.fr/np/nptool/-/issues/37Segmentation violation error while doing simulation.2017-06-07T10:43:43+02:00Adrien Mattamatta@lpccaen.in2p3.frSegmentation violation error while doing simulation.*Created by: mustak21*
Hi,
While doing the simulation of 7Be(d,t)6Be->alpha+p+p I am facing the following errors. I am attaching the input reaction file as well as the error file. Please have a look.
[7Be(d,t) error.docx](ht...*Created by: mustak21*
Hi,
While doing the simulation of 7Be(d,t)6Be->alpha+p+p I am facing the following errors. I am attaching the input reaction file as well as the error file. Please have a look.
[7Be(d,t) error.docx](https://github.com/adrien-matta/nptool/files/1054415/7Be.d.t.error.docx)
[7Bedt_reaction.docx](https://github.com/adrien-matta/nptool/files/1054417/7Bedt_reaction.docx)
https://gitlab.in2p3.fr/np/nptool/-/issues/47Limiting the range of events for npanalysis2017-11-02T10:06:54+01:00Greg ChristianLimiting the range of events for npanalysisCurrently you can specify the `-L <arg>` flag to `npanalysis` to limit the range of analyzed events from 0 -> `<arg>`. I am interested in also being able to specify the _starting_ event too, i.e. allowing the analysis to start with some...Currently you can specify the `-L <arg>` flag to `npanalysis` to limit the range of analyzed events from 0 -> `<arg>`. I am interested in also being able to specify the _starting_ event too, i.e. allowing the analysis to start with some event other than event zero.
I've made a simple change to the `NPOptionManager` code (and `npanalysis.cxx`) adding a `-F` flag that specifies the beginning of the event loop (default is zero). Using this, the analysis goes from F -> F+L (with a check to not go past the end of the chain). This should fully maintain backward compatibility.
Before pushing I wanted to make sure it's an acceptable change to make, since it modifies the core parts of the package. Any thoughts?
I also changed the event loop variable to `unsigned long`, to minimize the chance that it overflows. It was `unsigned int` before, which is 32 bit on most systems (~4e9 event maximum), but could conceivably be 16 bit (~65k maximum).
Here's the relevant changes in case anyone wants to inspect.
```
unsigned long first_entry = myOptionManager->GetFirstEntryToAnalyse(); // defaults to zero
unsigned long nentries = Chain->GetEntries();
if(nentries> myOptionManager->GetNumberOfEntryToAnalyse() && myOptionManager->GetNumberOfEntryToAnalyse()>0)
nentries = myOptionManager->GetNumberOfEntryToAnalyse() ;
if(nentries + first_entry > Chain->GetEntries()) {nentries = first_entry+Chain->GetEntries();}
```
(event loop):
```
for (unsigned long i = first_entry ; i < nentries + first_entry; i++) {
```https://gitlab.in2p3.fr/np/nptool/-/issues/45Rectangular beam profile2017-09-29T13:37:56+02:00Adrien Mattamatta@lpccaen.in2p3.frRectangular beam profile*Created by: moukaddam*
Salut,
Often in _in-beam_ fragmentation experiments the beam profile looks more like a rectangular profile with gaussian borders (see image). If we normally have the data we can use the ProfilePath option to r...*Created by: moukaddam*
Salut,
Often in _in-beam_ fragmentation experiments the beam profile looks more like a rectangular profile with gaussian borders (see image). If we normally have the data we can use the ProfilePath option to reproduce a very realistic beam profile. However, if one wants to replecate in a simple way the profile from an image of the beam it might be useful to have a "rectangular" distribution for X an Y, this will only move the centroid of the beam within a rectangle centered at the beam position. If you think that's interesting for the collaboration I can push in my changes. The same thing could be said about the beam energy, it would be nice to have the option of uniform distribution arounf the beam energy in addition to the gaussian.
![image](https://user-images.githubusercontent.com/5272621/30969444-4ef54bd8-a45a-11e7-8e03-2412417905f9.png)
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/54Solid angle corresponding to each pixel.2018-11-30T11:11:39+01:00Adrien Mattamatta@lpccaen.in2p3.frSolid angle corresponding to each pixel.*Created by: mustak21*
Hi,
I am using 16x16 W1 detectors in my detector set up and I would like to calculate the solid angle subtended by each pixel of my individual telescopes. I need some guidance regarding which files I need to edit...*Created by: mustak21*
Hi,
I am using 16x16 W1 detectors in my detector set up and I would like to calculate the solid angle subtended by each pixel of my individual telescopes. I need some guidance regarding which files I need to edit and modify in order to get the solid angles.https://gitlab.in2p3.fr/np/nptool/-/issues/38Different nature of deltaE-E plots for same simulations in two different NPTO...2018-12-03T15:34:01+01:00Adrien Mattamatta@lpccaen.in2p3.frDifferent nature of deltaE-E plots for same simulations in two different NPTOOL installed system.*Created by: mustak21*
Hi,
This is quite a strange problem that we are facing. We have NPTOOL installed in two of our pcs both having CentOS 7 and ROOT 6. When we simulate the reaction 7Be(d,p)8Be->alpha+alpha for same values of all pa...*Created by: mustak21*
Hi,
This is quite a strange problem that we are facing. We have NPTOOL installed in two of our pcs both having CentOS 7 and ROOT 6. When we simulate the reaction 7Be(d,p)8Be->alpha+alpha for same values of all parameters concerned and then plot the delta E-E curves(for annular detectors) in these two different pcs the plots observed are not identical but has some prominent differences! In one of the plots (named npt1)the proton band observed has many discontinuous small gaps alongwith the expected alpha band however the other plot (named npt2) the proton band is continuous alongwith the alpha band but there is another band above the alpha one which is unexpected!
What could be the possible reasons for such discrepancy?
[npt1.pdf](https://github.com/adrien-matta/nptool/files/1063915/npt1.pdf)
[npt2.pdf](https://github.com/adrien-matta/nptool/files/1063917/npt2.pdf)
https://gitlab.in2p3.fr/np/nptool/-/issues/35'make' failed in project2017-11-09T12:10:21+01:00Adrien Mattamatta@lpccaen.in2p3.fr'make' failed in project*Created by: kkabita*
I have written a new project similar to Example1 in the folder /nptool/Projects containing
Analysis.h
Analysis.cxx
CMakeLists.txt
RunToTreat.txt
cmake ./ is executed but
"make" generates a lot of errors.
...*Created by: kkabita*
I have written a new project similar to Example1 in the folder /nptool/Projects containing
Analysis.h
Analysis.cxx
CMakeLists.txt
RunToTreat.txt
cmake ./ is executed but
"make" generates a lot of errors.
_make[2]: *** [CMakeFiles/NPAnalysis.dir/Analysis.cxx.o] Error 1
make[1]: *** [CMakeFiles/NPAnalysis.dir/all] Error 2
make: *** [all] Error 2_
[error.docx](https://github.com/adrien-matta/nptool/files/1025156/error.docx)
https://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/1Example CATS2015-12-17T14:29:02+01:00Adrien Mattamatta@lpccaen.in2p3.frExample CATSdo an example for CATS:
- with real data (mask)
- with simu : not simulated so not needed.
do an example for CATS:
- with real data (mask)
- with simu : not simulated so not needed.
https://gitlab.in2p3.fr/np/nptool/-/issues/3Nptool wizard2016-01-08T14:57:52+01:00Adrien Mattamatta@lpccaen.in2p3.frNptool wizardFinish and polish
Finish and polish
Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/2Modification to the package structure2016-01-06T17:21:26+01:00Adrien Mattamatta@lpccaen.in2p3.frModification to the package structureRecover the doc
Recover read me folder
Put the detectors in a common folder for npl and nps
Check clean in project
Recover the doc
Recover read me folder
Put the detectors in a common folder for npl and nps
Check clean in project
Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/5Input file appear twice in the output file2016-03-23T12:48:48+01:00Adrien Mattamatta@lpccaen.in2p3.frInput file appear twice in the output fileKey are written twice
Key are written twice
Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/6W1 Simulation Crash2016-10-10T21:49:58+02:00Adrien Mattamatta@lpccaen.in2p3.frW1 Simulation Crash*Created by: padsley*
I'm adding this mainly so that I have a reference for myself. Sorry for clogging up your inboxes.
I'm trying to use the W1s using npsimulation, mainly to check to see whether my calculated W1 positions for n-si-90...*Created by: padsley*
I'm adding this mainly so that I have a reference for myself. Sorry for clogging up your inboxes.
I'm trying to use the W1s using npsimulation, mainly to check to see whether my calculated W1 positions for n-si-90 are correct.
Running the command:
`npsimulation -D W1nsi90.detector -E alpha.source -O SPcoincW1_19F_test`
where W1nsi90.detector is my modified input file (as I hate to break the original one), then I get this output:
```
/////////////////////////////////////////
//// Adding Detector W1
///
W1 element found:
Theta: 113
Phi: 0
R: 110
Beta: 0 0 0
///
W1 element found:
Theta: 113
Phi: 0
R: 150
Beta: 0 0 0
///
W1 element found:
Theta: 156
Phi: 0
R: 150
Beta: 0 0 0
///
W1 element found:
Theta: 156
Phi: 0
R: 150
Beta: 0 0 0
///
W1 element found:
Theta: -135
Phi: 0
R: 150
Beta: 0 0 0
///
W1 element found:
Theta: -135
Phi: 0
R: 150
Beta: 0 0 0
/////////////////////////////////////////
L226test
L231test
L233test
L231test
*** Break *** segmentation violation
```
where the cout statements are shown below...
```
else{
std::stringstream oss(LineBuffer);
std::string token;
oss >> token ;
NPS::VDetector* detector = theFactory->Construct(token);
if(detector!=NULL && check.find(token)==check.end()){
cout << "/////////////////////////////////////////" << endl;
cout << "//// Adding Detector " << token << endl;
detector->ReadConfiguration(Path);
cout << "/////////////////////////////////////////" << endl;
// Add array to the VDetector Vector
AddDetector(detector);
check.insert(token);cout << "L226test" << endl;
}
else{
if(detector!=NULL)
{
cout << "L231test" << endl;
delete detector;
cout << "L233test" << endl;
}
}
}
}
cout << "L234test" << endl;
ConfigFile.close();
cout << "\033[0m" ;
```
Stack trace is:
```
===========================================================
#5 0x00007f4f0753ec78 in main_arena () from /lib/x86_64-linux-gnu/libc.so.6
#6 0x00007f4ef822cbe0 in W1::~W1() () from /home/padsley/codes/nptool/NPSimulation/lib/libNPSW1.so
#7 0x00007f4ef822ccd9 in W1::~W1() () from /home/padsley/codes/nptool/NPSimulation/lib/libNPSW1.so
#8 0x00007f4f0a1a8809 in DetectorConstruction::ReadConfigurationFile() () from /home/padsley/codes/nptool/NPSimulation/lib/libNPSCore.so
#9 0x00007f4f0875da2c in G4RunManager::InitializeGeometry (this=0x25e5320) at /home/padsley/codes/geant4/geant4.10.02.p02/source/run/src/G4RunManager.cc:581
#10 0x00007f4f0875db21 in G4RunManager::Initialize (this=0x25e5320) at /home/padsley/codes/geant4/geant4.10.02.p02/source/run/src/G4RunManager.cc:565
#11 0x0000000000404628 in main ()
===========================================================
```
I think that this suggests that the code is trying to delete something that it can't at `delete detector;`.
Not sure what that is at the moment, though.
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/8Unit in input files2016-12-09T09:10:18+01:00Adrien Mattamatta@lpccaen.in2p3.frUnit in input files*Created by: Munken*
This is something you need!
Feel free to use this implementation:
https://git.kern.phys.au.dk/ausa/ausalib/blob/master/include/ausa/parser/UnitParser.h
https://git.kern.phys.au.dk/ausa/ausalib/blob/master/sou...*Created by: Munken*
This is something you need!
Feel free to use this implementation:
https://git.kern.phys.au.dk/ausa/ausalib/blob/master/include/ausa/parser/UnitParser.h
https://git.kern.phys.au.dk/ausa/ausalib/blob/master/source/parser/UnitParser.cppAdrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://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/11Adding detector part 2 - FillRawSpectra and FillPreTreatedSpectra broken2016-11-30T11:38:00+01:00Adrien Mattamatta@lpccaen.in2p3.frAdding detector part 2 - FillRawSpectra and FillPreTreatedSpectra broken*Created by: Munken*
The examples for these two sections calls `GetE_StripNbr()` which is missing an index.*Created by: Munken*
The examples for these two sections calls `GetE_StripNbr()` which is missing an index.https://gitlab.in2p3.fr/np/nptool/-/issues/12File causes npsim to stall2016-12-09T09:08:44+01:00Adrien Mattamatta@lpccaen.in2p3.frFile causes npsim to stall*Created by: Munken*
This one works:
[gdecay_working.txt](https://github.com/adrien-matta/nptool/files/624024/gdecay_working.txt)
This one causes npsimulation to stall:
[gdecay.txt](https://github.com/adrien-matta/nptool/files/6240...*Created by: Munken*
This one works:
[gdecay_working.txt](https://github.com/adrien-matta/nptool/files/624024/gdecay_working.txt)
This one causes npsimulation to stall:
[gdecay.txt](https://github.com/adrien-matta/nptool/files/624026/gdecay.txt)
It gives this warning:
```
-----------------------------------------------------------
-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomSolids1002
issued by : G4Box::DistanceToOut(p,v,..)
Undefined side for valid surface normal to solid.
Position:
p.x() = -0.2173821947071701 mm
p.y() = 13.14089812809774 mm
p.z() = 0.4972360623902874 mm
Direction:
v.x() = -nan
v.y() = -nan
v.z() = -nan
Proposed distance :
snxt = 9e+99 mm
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------
```Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/14No white space after CrossSectionPath make npsimulator stall2016-12-09T09:08:01+01:00Adrien Mattamatta@lpccaen.in2p3.frNo white space after CrossSectionPath make npsimulator stall*Created by: Munken*
This reaction will make `npsimulator` stall
```
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%% Reaction file for 15O(6Li,d)19Ne reaction %%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%...*Created by: Munken*
This reaction will make `npsimulator` stall
```
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%% Reaction file for 15O(6Li,d)19Ne reaction %%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Beam
Particle= 15O
Energy= 65
SigmaEnergy= 0
SigmaThetaX= 0
SigmaPhiY= 0
SigmaX= 0
SigmaY= 0
MeanThetaX= 0
MeanPhiY= 0
MeanX= 0
MeanY= 0
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
TwoBodyReaction
Beam= 15O
Target= 6Li
Light= d
Heavy= 19Ne
ExcitationEnergyLight= 0.0
ExcitationEnergyHeavy= 5
CrossSectionPath=11Li(d,3He)10He.txt CS10He
ShootLight= 1
ShootHeavy= 0
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
GammaDecay 19Ne
Cascade
BranchingRatio= 30
Energies= 0.1
DifferentialCrossSection= 11Li(d,3He)10He.txt Gamma9He
Cascade
BranchingRatio= 70
Energies= 0.05 0.5
```
if run like this
```
npsimulation -D MUGAST_Agata.detector -E Projects/15O6Li_d19Ne.reaction
```
Adding a space after `CrossSectionPath` fixes it. Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/15Cascade branching ratio sum > 100 causes undefined behavior2016-12-09T09:08:18+01:00Adrien Mattamatta@lpccaen.in2p3.frCascade branching ratio sum > 100 causes undefined behavior*Created by: Munken*
Reaction file
```
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%% Reaction file for 15O(6Li,d)19Ne reaction %%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Be...*Created by: Munken*
Reaction file
```
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%% Reaction file for 15O(6Li,d)19Ne reaction %%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Beam
Particle= 15O
Energy= 65
SigmaEnergy= 0
SigmaThetaX= 0
SigmaPhiY= 0
SigmaX= 0
SigmaY= 0
MeanThetaX= 0
MeanPhiY= 0
MeanX= 0
MeanY= 0
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
TwoBodyReaction
Beam= 15O
Target= 6Li
Light= d
Heavy= 19Ne
ExcitationEnergyLight= 0.0
ExcitationEnergyHeavy= 4.0329
CrossSectionPath= flat.txt CS10He
ShootLight= 1
ShootHeavy= 0
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
GammaDecay 19Ne
Cascade
BranchingRatio= 50
Energies= 0.1
DifferentialCrossSection= flat.txt Gamma9He
Cascade
BranchingRatio= 70
Energies= 0.05 0.5
```
yields
```
*** Error in `npsimulation': malloc(): smallbin double linked list corrupted: 0x0000000002bdf450 ***
Aborted (core dumped)
```
Changing the upper branching ratio to 40 just causes it to stall.
Summing to < 100 seems to work fine. Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/16Cannot find batch file should give error2016-12-05T13:05:39+01:00Adrien Mattamatta@lpccaen.in2p3.frCannot find batch file should give error*Created by: Munken*
*Created by: Munken*
https://gitlab.in2p3.fr/np/nptool/-/issues/17Reaction file crashes MUGAST analysis2017-02-03T10:16:23+01:00Adrien Mattamatta@lpccaen.in2p3.frReaction file crashes MUGAST analysis*Created by: Munken*
```
npsimulation -D MUGAST_Agata.detector -E 15O6Li_d19Ne.reaction
```
and then
```
npanalysis --last-sim
```
crashes with this
[15O6Li_d19Ne.txt](https://github.com/adrien-matta/nptool/files/624294...*Created by: Munken*
```
npsimulation -D MUGAST_Agata.detector -E 15O6Li_d19Ne.reaction
```
and then
```
npanalysis --last-sim
```
crashes with this
[15O6Li_d19Ne.txt](https://github.com/adrien-matta/nptool/files/624294/15O6Li_d19Ne.txt)
Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/18ROOT5 / ROOT6 compatibility2016-12-05T12:47:49+01:00Adrien Mattamatta@lpccaen.in2p3.frROOT5 / ROOT6 compatibility*Created by: moukaddam*
The TSpectrum has changed the type of the returned position. See https://root.cern.ch/phpBB3/viewtopic.php?t=20802 for more details
in file /NPLib/Calibration/NPSiliconCalibrator.cxx the type of xpeaks must be...*Created by: moukaddam*
The TSpectrum has changed the type of the returned position. See https://root.cern.ch/phpBB3/viewtopic.php?t=20802 for more details
in file /NPLib/Calibration/NPSiliconCalibrator.cxx the type of xpeaks must be changed if ROOT6 is in use:
ROOT5 compatible: Float_t* xpeaks =(Float_t*) sp->GetPositionX();
ROOT6 compatible: Double_t* xpeaks =(Double_t*) sp->GetPositionX();https://gitlab.in2p3.fr/np/nptool/-/issues/20SiliconCalibrator leaks memory2016-12-05T13:14:04+01:00Adrien Mattamatta@lpccaen.in2p3.frSiliconCalibrator leaks memory*Created by: Munken*
In `FitSpectrum` SiliconCalibrator creates a new `TSpectrum` with no deletion. See [here](https://github.com/adrien-matta/nptool/blob/NPTool.2.dev/NPLib/Calibration/NPSiliconCalibrator.cxx#L220) not sure if this is ...*Created by: Munken*
In `FitSpectrum` SiliconCalibrator creates a new `TSpectrum` with no deletion. See [here](https://github.com/adrien-matta/nptool/blob/NPTool.2.dev/NPLib/Calibration/NPSiliconCalibrator.cxx#L220) not sure if this is intentional due to ROOT funkiness or a bug?
https://gitlab.in2p3.fr/np/nptool/-/issues/22nptool not compatible with Geant4 10.32016-12-19T14:05:31+01:00Adrien Mattamatta@lpccaen.in2p3.frnptool not compatible with Geant4 10.3The scorer hit map now use a G4StatDouble instead of G4double, and hence cannot be cast to a double*. This make our scorer facility incompatible at the moment with Geant4 10.3.The scorer hit map now use a G4StatDouble instead of G4double, and hence cannot be cast to a double*. This make our scorer facility incompatible at the moment with Geant4 10.3.Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://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/32Energy loss in annularS12017-05-16T17:04:26+02:00Adrien Mattamatta@lpccaen.in2p3.frEnergy loss in annularS1*Created by: mustak21*
Hi,
Using a proton source of 40MeV I took annularS1,W1 and SSSD detectors each of thickness 500um.Although the energy deposited by the incoming protons on the W1 and SSSD detectors matches the values of energy lo...*Created by: mustak21*
Hi,
Using a proton source of 40MeV I took annularS1,W1 and SSSD detectors each of thickness 500um.Although the energy deposited by the incoming protons on the W1 and SSSD detectors matches the values of energy loss as calculated by LISE++ but for annularS1 the value of energy deposited differs a lot.
![annulars1](https://cloud.githubusercontent.com/assets/25579005/26098940/e89050b8-3a46-11e7-8360-7d5e73bbfabc.jpg)
![sssd](https://cloud.githubusercontent.com/assets/25579005/26098981/05d27b6a-3a47-11e7-9777-67724bc11851.jpg)
![w1](https://cloud.githubusercontent.com/assets/25579005/26098989/0c919490-3a47-11e7-9209-59c6005db940.jpg)
I checked the annularS1.hh file but couldn't identify the reason why the thickness appears to get doubled.https://gitlab.in2p3.fr/np/nptool/-/issues/51Vaccum in Simulation2018-02-01T10:28:29+01:00Adrien Mattamatta@lpccaen.in2p3.frVaccum in Simulation*Created by: moukaddam*
Is there an easy way define the Vacuum from the .detector file?
I think the default pressure is not vacuum, for efficiency calculations I have changed the alpha energy and got different results hinting to this...*Created by: moukaddam*
Is there an easy way define the Vacuum from the .detector file?
I think the default pressure is not vacuum, for efficiency calculations I have changed the alpha energy and got different results hinting to this. https://gitlab.in2p3.fr/np/nptool/-/issues/28Analysis of Simulated root file2017-04-28T12:42:05+02:00Adrien Mattamatta@lpccaen.in2p3.frAnalysis of Simulated root file*Created by: mustak21*
The root file, generated after simulation, has such a structure that its leaves (the parameters holding the data) cannot be accessed through the “Tree Viewer”of ROOT. Since I am new to both ROOT and C++, so buildi...*Created by: mustak21*
The root file, generated after simulation, has such a structure that its leaves (the parameters holding the data) cannot be accessed through the “Tree Viewer”of ROOT. Since I am new to both ROOT and C++, so building a macro totally on my own in a short time seems a difficult task. It would be very helpful if I could get the guidance for building a general macro for analysis.
However, if the tree structure could be controlled and formed in a way to make the leaves accessible in Tree Viewer, that would also be a great help.
https://gitlab.in2p3.fr/np/nptool/-/issues/48Problem in NPTool installation2017-12-04T13:33:43+01:00Adrien Mattamatta@lpccaen.in2p3.frProblem in NPTool installation*Created by: mustak21*
Hi,
I have successfully installed ROOT v6.10/06 and GEANT4.10.01.p02 in macOS X Yosemite 10.10.5
However while giving the command `cmake ./` in NPLib while installing NPTool I am getting the following error:
...*Created by: mustak21*
Hi,
I have successfully installed ROOT v6.10/06 and GEANT4.10.01.p02 in macOS X Yosemite 10.10.5
However while giving the command `cmake ./` in NPLib while installing NPTool I am getting the following error:
Dhrubas-MacBook-Pro:NPLib dhruba$ cmake ./
Looking for Root:
**Root /bin/sh: /Users/dhruba/root/bin/root-config: No such file or directory found**
Building all detectors
– Configuring done
– Generating done
– Build files have been written to: /Users/dhruba/nptool/NPLib
https://gitlab.in2p3.fr/np/nptool/-/issues/53Using EventGeneratorParticleDecay2018-08-21T09:42:43+02:00Adrien Mattamatta@lpccaen.in2p3.frUsing EventGeneratorParticleDecay*Created by: zhangningtao*
I am trying to use both TwoBodyReaction and ParticleDecay for simulation. But the "ParticleDecay" doesn't work, not shooting any decays. I checked the codes (latest version) and found that class EventGenerator...*Created by: zhangningtao*
I am trying to use both TwoBodyReaction and ParticleDecay for simulation. But the "ParticleDecay" doesn't work, not shooting any decays. I checked the codes (latest version) and found that class EventGeneratorParticleDecay was not registered in the PrimaryGeneratorAction. It seemed that function codes related to secondary particle emission were moved to G4FastSimulationManagerProcess. For example, BeamReaction has been registered in PhysicsList. Is this true?
Could you experts give me some ideas how to make EventGeneratorParticleDecay working? I mean decay particles emitted from the same vertex with TwoBodyReaction.https://gitlab.in2p3.fr/np/nptool/-/issues/30Empty root file generated on analysis2017-04-28T21:14:04+02:00Adrien Mattamatta@lpccaen.in2p3.frEmpty root file generated on analysis*Created by: kkabita*
I have a source run file. I am using the following command in NPTOOL to analyse the root file, the path to the root file is mentioned in "RunToTreat.txt".
npanalysis - D geometry _ filename . detector
...*Created by: kkabita*
I have a source run file. I am using the following command in NPTOOL to analyse the root file, the path to the root file is mentioned in "RunToTreat.txt".
npanalysis - D geometry _ filename . detector
- R runstotreatreat _ filename . txt
- O output _ rootfilename
This gives an empty root file in the nptool/Outputs/Analysis Folder. What can be the reasons of getting an empty root file? Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/52Major bug, fixed2018-05-16T10:52:24+02:00Adrien Mattamatta@lpccaen.in2p3.frMajor bug, fixed*Created by: moukaddam*
The bug affected mainly simulations using a thick target (here it's ~25.6um) inducing large energy loss of the beam. Before the fix, the energy loss of the beam particle in the target was overestimated for intera...*Created by: moukaddam*
The bug affected mainly simulations using a thick target (here it's ~25.6um) inducing large energy loss of the beam. Before the fix, the energy loss of the beam particle in the target was overestimated for interactions taking place close to the upstream target surface. The opposite was true for interactions downstream. Problem spotted in NPS/Core/Target.cxx, below some typical values and their fix.
=============== Example
Target Z: 0 mm
halfTargetThickness: 12.3 micrometer
(below in micrometer)
test case 1:
Generated Interaction Z: -8.1
Calculated depth : -20.4 --> This should be 12.3-8.1 = 4.2
test case 2:
Generated Interaction Z: +9.8
Calculated depth : -2.5 --> This should be 12.3+9.8 = 23.1
Result on a test case:
The peaks shown corresponds to the g.s in different angular bin. Data are simulated for 60Fe(d,p) reaction. Left panel before fix, right panel after.
![60fe_before_after_bugfix_2](https://user-images.githubusercontent.com/5272621/39209857-f1606cac-47fe-11e8-8ca8-7501d302a0f0.png)https://gitlab.in2p3.fr/np/nptool/-/issues/33Is multiple exit channels of a reaction allowed?2017-05-24T16:46:17+02:00Adrien Mattamatta@lpccaen.in2p3.frIs multiple exit channels of a reaction allowed?*Created by: mustak21*
Hi,
I just wanted to know if it is allowed to edit the reaction file of a reaction such that there are multiple exit channels or does a single reaction can have only one exit channel?*Created by: mustak21*
Hi,
I just wanted to know if it is allowed to edit the reaction file of a reaction such that there are multiple exit channels or does a single reaction can have only one exit channel?https://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/31Update an already installed NPTOOL2017-12-01T13:18:15+01:00Adrien Mattamatta@lpccaen.in2p3.frUpdate an already installed NPTOOL*Created by: kkabita*
I have NPTOOL installed on the mac OS - Yosemite and I am using geant4 10.01.02. While running some simulation, I came across errors which imply missing of files, e.g. NPInputParser.h .
A complete set of commands...*Created by: kkabita*
I have NPTOOL installed on the mac OS - Yosemite and I am using geant4 10.01.02. While running some simulation, I came across errors which imply missing of files, e.g. NPInputParser.h .
A complete set of commands for **updating** would be very helpful.
Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.frhttps://gitlab.in2p3.fr/np/nptool/-/issues/46Possible bug in beam stack, quick check2018-05-16T10:55:09+02:00Adrien Mattamatta@lpccaen.in2p3.frPossible bug in beam stack, quick check*Created by: moukaddam*
In the case of the **beam**, the corresponding "Particle" class object members are set differently:
1- Particle::m_ThetaCM is indeed the initial energy before entering the target
2- Particle::m_T is the final...*Created by: moukaddam*
In the case of the **beam**, the corresponding "Particle" class object members are set differently:
1- Particle::m_ThetaCM is indeed the initial energy before entering the target
2- Particle::m_T is the final energy just before interaction in the target
However I have found the following snippet the ParticleStack Class
```
void ParticleStack::AddBeamParticleToStack(Particle& particle){
// If the particle is the first one to be added, then the IC are cleared
if(m_First)
m_InitialConditions->Clear();
m_ParticleStack.push_back(particle);
// Incident beam parameter
m_InitialConditions-> SetIncidentParticleName (particle.GetParticleDefinition()->GetParticleName());
//m_InitialConditions-> SetIncidentInitialKineticEnergy (particle. GetParticleThetaCM());
m_InitialConditions-> SetIncidentInitialKineticEnergy (particle. GetParticleKineticEnergy());
```
Hence, if I want to fix the code above I would use:
```
void ParticleStack::AddBeamParticleToStack(Particle& particle){
(...)
// Incident beam parameter
(idem)
m_InitialConditions-> SetIncidentInitialKineticEnergy (particle. GetParticleThetaCM()); //<<<<<<
(idem)
```
Is this done on purpose?
This is now fixed and pushed, please advise in case I need to retract
https://gitlab.in2p3.fr/np/nptool/-/issues/50Excitation-Energy Randomisation and Event Rate dropping2018-11-30T11:14:30+01:00Adrien Mattamatta@lpccaen.in2p3.frExcitation-Energy Randomisation and Event Rate dropping*Created by: padsley*
When I try to run NPTool using a histogram for excitation energy, I find that it tends to run very slowly, and gets slower in contrast to the very similar code for the random angle generation.
Has anyone else se...*Created by: padsley*
When I try to run NPTool using a histogram for excitation energy, I find that it tends to run very slowly, and gets slower in contrast to the very similar code for the random angle generation.
Has anyone else seen this happening with NPTOOL or another GEANT4 simulation? I'm presently running valgrind to try to work out if and when a memory leak is occurring but there's nothing obvious leaping out at me at the moment.
So... my query is: "Has anyone else seen this behaviour?" If you haven't ever tried using an Ex histogram input rather than one set value for Ex in the input file, could you try and let me know if it's got this same behaviour of the event rate dropping fairly quickly?
Thanks.https://gitlab.in2p3.fr/np/nptool/-/issues/29Low Gain Energies in GeTAMU2017-04-15T03:41:19+02:00Adrien Mattamatta@lpccaen.in2p3.frLow Gain Energies in GeTAMU*Created by: moukaddam*
@adrien-matta: @shuyaota is requesting to include High and Low-Gain energies simultaneously in GeTamuPhysics class. His argument is that Low- and High-Gain are equally important in 2 experiments of our campaign.
...*Created by: moukaddam*
@adrien-matta: @shuyaota is requesting to include High and Low-Gain energies simultaneously in GeTamuPhysics class. His argument is that Low- and High-Gain are equally important in 2 experiments of our campaign.
For now I have included distinct vectors in the GeTamuData class, i.e. by using the midas2nptool un-packer one can specify if he wants to read the Low-Gain channels (and the High-Gain) simultaneously from Midas, and store them in there specific vectors (parallel to the High-Gain ones). From thereon, the user can choose to call the Low- or the High-Gain in the Physics class. Obviously, the fact that the user have to manually choose the function names in not practical, especially when another collaborator updates the code. In contrast, the downside of adding another set of physics data for the Low-Gain (in parallel to the High-Gain ones) is that the Physics Class will loose its generic design.
Suggestion:
I can reconfigure the Physics class by adding an argument in the constructor of getamu (by default it will to use the High-Gain). The argument can go in the GeTamuData getter functions and can decide which Getter to use (High or Low). The same argument can be used upload the calibration tokens specific for the gain used. In this case the physics class is essentially the same, ant he user can call either gains from the project analysis.cxx
@adrien-matta What's your suggestion on that.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/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/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/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/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/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/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/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/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/71Energy correlation issue of breakup fragments of a projectile nucleus using n...2024-02-01T13:37:04+01:00Subhankar MaityEnergy correlation issue of breakup fragments of a projectile nucleus using nptoolHi Adrien! Hope you are doing well.
I am carrying out the resonant breakup of 7Be on the 12C target i.e 7Be + 12C -> 3He + 4He + 12C at E = 35 MeV using the two step breakup reaction file. I am using a detector setup consisting of five...Hi Adrien! Hope you are doing well.
I am carrying out the resonant breakup of 7Be on the 12C target i.e 7Be + 12C -> 3He + 4He + 12C at E = 35 MeV using the two step breakup reaction file. I am using a detector setup consisting of five DSSDs in a pentagon geometry backed by unsegmented pads (SSSDs). But I am again facing a strange issue with SSSDs in NPTool while doing the coincidence measurements of breakup fragments. We can expect a negative correlation between the energies of the breakup fragments according to the conservation of energy. But I am getting a positive slope when I plot the energies of the two fragments. I looked into this issue and found out that probably SSSDs are causing the problem. Just to verify quickly, I replaced the SSSDs with W1s of similar configuration (thickness, segmentation etc.). And I got a satisfactory output in the energy correlation plot.
Could you please comment on this issue? Is there any way to fix this strange problem with SSSDs so that I can exactly imitate our experimental detector setup in simulation ? Please reply at your earliest convenience. Thank you in advance.Adrien Mattamatta@lpccaen.in2p3.frAdrien Mattamatta@lpccaen.in2p3.fr