We want to simulate a F19- ion going through low-pressure CF4 gas with restG4, but the step seems too large. For instance, I attached a picture including a 25kev original track(the white line), but there are only 8 hits. Then I decrease the MaxStepSize and cut parameters in the restG4 config file(F19-.rml), which doesn’t change the simulation results. At the same time, the simulation of an electron track will effect by changing such parameters.
Thanks a lot!
In which geometry volume those hits are taking place? Could you share your GDML file?
Actually maxTargetStepSize will only affect the sensitive volume (usually the detector active medium). However, right now it is hard-coded inside DetectorConstruction to be using the volume named gasVolume (see image later on). We probably need to change that, but I want to check the source of your problem is coming from there.
Thanks for your reply. Please find attached my gdml files. Since gdml is not authorized name, I added .rml on the end. Here I used PandaX-III Cu vessel geometry, with CF4 mixture gas inside.
So does it means that the mistake may come from the gas itself? Because the electron performance seems correct while the ion track is strange.
Ok, now gdml is also authorised. The geometry file where you define the volumes seems missing.
What is the typical distance between 2 hits? Could you also attach the result from PrintEvent for electron and ion? I believe the ion track is much much shorter than the electron and that’s why visually seems strange?
Thanks for your information. Sorry, I’ve no idea on how to update Rest from master branch to v2.2.11_dev, but I updated restG4/src/PhysicsList.cc to your newest version.
It seems there’s still some problem when simulating ion movement. I attach the log as follows. I guess it’s an error defined by G4SetppingManager.cc but I use /store/bl2/opt/geant4/10.02p01/ which has no source files. Could you please point me out where’s the error probably from?
It is important that we work on the same version of the code, so that I could reproduce your error. I will not be able to help you if you don’t change to v2.2.11_dev.
if you are in the master branch, you may proceed in two different ways.
Option 1. If you do not mind to discard the changes you have locally.
Could you provide also your RML containing TRestG4Metadata, TRestPhysicsList, etc definitions, and all the geometry files you used so that I can reproduce the error?
Sorry, I missed one file, “Geometry_CuVessel.gdml”. By the way, it took me some times to upload it successfully, it seems there’s some bug like that in the image