Project

General

Profile

Bug #1303

Poor Default Beam Settings

Added by Lane, Peter almost 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Simulation
Target version:
Start date:
03 July 2013
Due date:
% Done:

100%

Estimated time:
Workflow:
New Issue

Description

I think this goes hand in hand with the ongoing geometry efforts, but Chris wanted me to file a bug report...

The current default beam settings are incompatible with the default Test.dat geometry. The beam diverges too fast to hit the lH2 box.

The beam starts in the middle of TOF1 for Stage1.dat through Stage3.dat. It appears that the beam defaults were intended for this since the transverse mode is "constance_solenoid" and the beam traverses the elements it actually passes through well.

For stage4.dat and above the beam diverges and terminates (the maximum_number_of_steps value of 10000 is insufficient) before reaching any geometry elements.

Presumably the geometries should all start at the same place since the Beamline.dat element is identical. It should then be possible to configure the beam to enter at the same point in any of the stages.

#1

Updated by Rogers, Chris almost 11 years ago

  • Target version set to Future MAUS release

Mapping default beam settings to this configuration or that configuration is hard and not supported. User has to do this.

maximum_number_of_steps should be large enough not to cause problems. This has been increased to 500000.

#2

Updated by Rogers, Chris almost 11 years ago

  • Category changed from common_py to Simulation
  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Fixed in r960

#3

Updated by Rajaram, Durga almost 11 years ago

  • Target version changed from Future MAUS release to MAUS-v0.6.0

Also available in: Atom PDF