Dear Paola,
thanks for your message. I’ll try to use the work-around you suggest.
Btw, in the past I tried to use STUPRF.f to access this process (since manual says this is called also when muons are put on the stack), however I was not able to “catch” muons for gamma->mu+ mu- (while I got muons from pi decay). Now I understand this “special” process is handled by stupre.f, and that makes sense, since it is the “analogous” of gamma->e+ e-. I suggest to upload the manual for this.
Thanks,
Bests,
Andrea
> On Aug 24, 2018, at 15:08, paola sala <paola.sala_at_cern.ch> wrote:
>
> Dear Andrea
> you are perfectly right. USDRAW is not called after photomuon production.
> This will be corrected in a next respin.
> In the meanwhile, aI can suggest a workaround:
> - The user routine stupre.f is called after photomuon production, as well as after any other electromagnetic interaction.
> - the flag LPAIRP, available in stupre through (EVTFLG), is .true. for muon pair production AND..for standard pair production
> - however, in case of muon pair pair production no electrons/photons are produced, thus stupre.f is called with NPEMF=NPSTRT (no variation in the EMF particle stack). This condition can be used to select muon pair production.
> - the produced muons are stored directly on the main FLUKA stack. To access them, include (FLKSTK) in stupre.f and check the last two particle, those corresponding to index NPFLKA and NPFLKA-1. Meaning of the variables is in the comments in the $FLUPRO/flukapro/(FLKSTK) file.
> - the parent photon quantities are available in common EMFSTK (already included) at position NPSTRT
>
> Please feel free to contact me if you need help
> Paola
>
>
> On 08/20/2018 04:33 PM, Andrea Celentano wrote:
>> Dear Fluka community,
>> I come back to this message, since I think there may be an issue with the process gamma -> mu+ mu- being “recognized” in mgdraw.f, entry USDRAW.
>>
>> I want to underline that the process itself, as implemented in FLUKA, works correctly, also regarding the corresponding bias. In particular, I did a comparison between a fluka-based and a Geant4-based simulation, with an 11-GeV electron beam impinging on a thick aluminum target, scoring the number of muons exiting from the target, as a function of their energy, and I got an excellent agreement. The process gamma-> mu+ mu- was turned on in G4 by hand.
>>
>> I am now trying to identify each produced muon, both by the decay of a pion/kaon, by the gamma-> mu+ mu- process, or by other more rare processes. For each produced muon, I write to an output file the energy, the direction, and the production vertex, together with the processID that produced it, and the mother particle ID and energy.
>>
>> The code mgdraw.f code I am using is the following (entry USDRAW)
>>
>> if ((JTRACK.ne.10).and.(JTRACK.ne.11)) then
>> do ip=1,np
>> if ((KPART(IP).eq.10).or.(KPART(IP).eq.11)) then
>> CALL eventcreate(NCASE,1,KPART(IP),TKI(IP),
>> & CXR(IP),CYR(IP),CZR(IP),XSCO,YSCO,ZSCO,WEI(IP),WTRACK)
>> CALL vertexsave(JTRACK,ICODE,ETRACK,XSCO,YSCO,ZSCO)
>> CALL eventsave
>> end if
>> end do
>> end if
>>
>> In particular, I am checking every interaction, looking for secondaries. If any secondary is a muon, I write it to my file trough the “eventcreate - vertexsave - eventsave” routines. The first “IF” is used to exclude processes where the impinging particle is a muon, such as mu N -> mu N X, i.e. inelastic (or elastic) interaction of the muon itself.
>>
>> In my output file, I see many events, all of them with ICODE=102 (particle decay secondaries), and none with ICODE corresponding to gamma -> mu+ mu- (should be 104, pair production, according to the message by Stefan Rosler).
>>
>> I tried to remove the first IF statement, and I saw in the output some events with ICODE=104, associated only to mu -> mu e+ e- (radiative pair production by muon), some with ICODE=103, associated to mu->mu e- (delta ray), and with ICODE=105, associated to mu -> mu gamma (muon bremmstrahlung).
>> However, still I did not saw any event with ICODE=104, where the primary particle is a photon.
>>
>> In other words, I think that this process, even if properly implemented in Fluka, does not get “exported” to mgdraw.f, entry USDRAW.
>> Is this possible? (I see that this process is a particular one, to be explicitly activated through the PHOTONUC card, SDUM=MUMUPAIR - maybe the issue is related to this?)
>>
>> Thanks,
>> Bests,
>> Andrea
>>
>>
>>> On Jun 21, 2017, at 12:06, Andrea Celentano <andrea.celentano_at_ge.infn.it> wrote:
>>>
>>> Dear fluka community,
>>> I have a question regarding the process gamma -> mu+ mu-.
>>>
>>> In my simulation, I explicitly activated it trough the card:
>>>
>>> PHOTONUC 1111. 0.0005 BLCKHOLE _at_LASTMAT MUMUPAIR
>>>
>>> (I am using a strong bias for it)
>>>
>>> When such a process happens, which of the flags reported in (EVTFLG) is switched on?
>>>
>>> The question arises from the fact that I'd like to modify the stuprf.f function in order to save, for muons, the mother particle and the process id that produced it.
>>>
>>> I already verified that my code works properly when the muon is produced by the decay of another particle (usually pions), or due to the inelastic interaction of another muon with a nucleus. However, I can't find the flag for the aforementioned process.
>>>
>>> For completeness, I attach to this email the stuprf.f code I am using
>>>
>>> Bests
>>>
>>> Andrea Celentano
>>> <stuprf.f>
>
>
__________________________________________________________________________
You can manage unsubscription from this mailing list at
https://www.fluka.org/fluka.php?id=acc_info
- application/pkcs7-signature attachment: smime.p7s
Received on Fri Aug 24 2018 - 17:37:17 CEST