muon DIS and inactivateMuonProcesses

[ThomasRuf]

It was found out that when running DIS simulations for SND@LHC, the outgoing muons do not make any hits in the detector. This is due to setting the inactivateMuonProcesses for DIS, which inactivates muIoni. The original reason for this setting has to do with DIS procedure: the incoming muon is cloned flying backward to make a signal in the SBT in case the DIS happens at the inner wall of the vacuum tank. However, it also made unwanted interactions in GEANT4 at other places. For this reason, some of the muon processes were switched of. I thought this was tested with FairShip, and everything worked as foreseen. Could somebody please check if muons from DIS are still making signals?

[olantwin]

@maksymovchynnikov didn't you signals from the incoming muons in the veto systems?

[maksymovchynnikov]

Yes, I had the same problem because of the option.

…

On Thu, Apr 20, 2023, 1:42 PM Oliver Lantwin ***@***.***> wrote: @maksymovchynnikov <https://github.com/maksymovchynnikov> didn't you signals from the incoming muons in the veto systems? — Reply to this email directly, view it on GitHub <#431 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2TG5N2WQ2VP3ETL55DOVGTXCEOIZANCNFSM6AAAAAAXFJZNX4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[olantwin]

Could it be that we need to at least activate muIoni to have energy deposits in the veto detectors?

Alternatively, we could reactivate all, and the unphysical interactions deposits need to be ignored during the analysis.

Relevant commits: 8a9a67e, 479e8df, 1b68df0

[maksymovchynnikov]

Pair production and bremsstrahlung may also be important.

…

On Tue, Apr 25, 2023, 10:45 AM Oliver Lantwin ***@***.***> wrote: Could it be that we need to at least activate muIoni to have energy deposits in the veto detectors? Alternatively, we could reactivate all, and the unphysical interactions deposits need to be ignored during the analysis. Relevant commits: 8a9a67e <8a9a67e>, 479e8df <479e8df>, 1b68df0 <1b68df0> — Reply to this email directly, view it on GitHub <#431 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2TG5N6CTKGY2MQLNWHNJ73XC6FJTANCNFSM6AAAAAAXFJZNX4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ThomasRuf]

In principle, for the outgoing muon, we want to have all processes. For the backward running muon, we don't want to have anything except of muIoni, the rest would violate the arrow of time. But I don't know how to achieve this. Except of creating a new particle which has all properties of a muon but makes only muIoni. So, activating all processes and ignoring any hits made by daughter particles created by MCTrack[2] might be the best solution. Only use hits directly made by this muon.

[anupama-reghunath]

this would be resolved with the new muon DIS implementation. @olantwin