sherpa is hosted by Hepforge, IPPP Durham
close Warning: Can't synchronize with repository "(default)" (/hepforge/svn/sherpa does not appear to be a Subversion repository.). Look in the Trac log for more information.

Opened 13 years ago

Last modified 12 years ago

#203 closed defect

Limitations of PARTICLE_CONTAINER — at Initial Version

Reported by: Frank Siegert Owned by: support@sherpa-mc.de
Priority: minor Milestone: rel-1.4.0
Component: Unknown Version: 0.trunk
Keywords: Cc:

Description

The keyword 'PARTICLE_CONTAINER' allows to define custom particle containers, which is useful to simplify process listings. In some cases though, these containers will show unexpected behaviour compared to using their contents directly.

Example Run.dat without using the containers integrates fine:

(run){
  BEAM_1=2212
  BEAM_2=2212
  BEAM_ENERGY_1=3500
  BEAM_ENERGY_2=3500

  MASSIVE[5]=1
}(run)

(processes){
  Process 93 93 -> 5 -5
  End process;
}(processes)

(selector){
  METS sqr(20.0/E_CMS)
}(selector)

Example Run.dat with containers integrates to nan:

(run){
  BEAM_1=2212
  BEAM_2=2212
  BEAM_ENERGY_1=3500
  BEAM_ENERGY_2=3500

  MASSIVE[5]=1
  PARTICLE_CONTAINER 905 bottoms 5 -5
}(run)

(processes){
  Process 93 93 -> 905 905
  End process;
}(processes)

(selector){
  METS sqr(20.0/E_CMS)
}(selector)

I thought the METS jet finder is applied on the single process level, so I don't quite understand why this makes a difference here.

Change History (0)

Note: See TracTickets for help on using tickets.