Project

General

Profile

Bug #370

MAUSSteppingAction kills tracks with more than 100k steps

Added by Rogers, Chris almost 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Simulation
Target version:
Start date:
07 March 2011
Due date:
% Done:

100%

Estimated time:
Workflow:

Description

MAUSSteppingAction kills hard coded tracks with more than 100k steps - this is a bug

#1

Updated by Tunnell, Christopher almost 12 years ago

move to datacards?

#2

Updated by Rogers, Chris almost 12 years ago

Sure, probably two datacards - MaxNumberOfSteps (integer, default 100k probably ok) and UseMaxNumberOfSteps (boolean, default true)

#3

Updated by Tunnell, Christopher almost 12 years ago

Or if the number of steps is negative, it runs forever?

#4

Updated by Rogers, Chris almost 12 years ago

Fixed in rogers, will close when I merge - nb I didn't implement the n steps negative, because I think this can cause it to hang...

One could imagine a loop detection algorithm (every 100k steps, see if particle is increasing in distance from some fixed point)

#5

Updated by Tunnell, Christopher almost 12 years ago

So is it an unsigned int then? There should be an error raised in the spill probably, right?

#6

Updated by Rogers, Chris almost 12 years ago

Closed in #457

#7

Updated by Rogers, Chris almost 12 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF