Noticed in the past that some fits throw exceptions with non-bracketed minima because a trial trajectory starts swimming away from some hit. Tried swimming backward from initial position and then initial step more likely to start toward the hits. This was not a panacea.
NOTES
working in /local/swim_quick on roentgen
damn: no push_front member function in vector
kludge: swim back and put farthest back point as first point on trajectory
original version:
MyTrajectory::doca: bad initialization of doca search: 0 1 1574 10.96 11.2782 68.0906
==========fit error = 1===========
= at event 25
MyTrajectory::doca: bad initialization of doca search: 0 1 1027 7.39348 7.70726 60.046
==========fit error = 1===========
= at event 32
MyTrajectory::doca: bad initialization of doca search: 0 1 2000 10.96 11.2014 14.775
==========fit error = 1===========
= at event 66
MyTrajectory::doca: bad initialization of doca search: 0 672 673 34.4129 6.08385 5.9746
==========fit error = 1===========
= at event 70
swim_back version, single swim back point:
MyTrajectory::doca: bad initialization of doca search: 0 1 303 18.093 18.7091 58.895
==========fit error = 1===========
= at event 57
MyTrajectory::doca: bad initialization of doca search: 0 1 548 27.948 28.7997 35.4432
==========fit error = 1===========
= at event 70
MyTrajectory::doca: bad initialization of doca search: 0 1 648 26.6388 28.9513 66.7086
==========fit error = 1===========
= at event 90
Note that all of these are tough changes, e. g. event 70, which is in both configurations:

event 70, gives exception with non-bracketed minimum with or without swim-back method for trajectory
This test version was checked into branches/src/programs/Analysis/plugins/trkfitterLSLM-swim-back-quick-and-dirty .