Bug #1174
Optics tests are slow
Start date:
21 November 2012
Due date:
% Done:
100%
Estimated time:
Workflow:
New Issue
Description
Optics tests are taking too long to run. Email from Peter:
The delay is when the particles are being fired. Sometimes it zips through all 13 test particles in about a second. Sometimes it takes about a second per fired particle. I don't understand why. I could probably bring the time down on one of the classes, but the PolynomialOpticsModel has to create polynomial maps to be tested properly, and the way it does that is to fire test particles as you know. Hmm...I suppose what I could do is put an option to use canned data to build the optics model. It's a bit hacky but it would compensate for the problem. I'd much rather understand why the time it takes to fire particles is so inconsistent.
Updated by Rogers, Chris over 10 years ago
- Category set to Optics
- Assignee set to Lane, Peter
- Priority changed from Normal to Low
- Target version set to Future MAUS release
I put this in an issue tracker, feel free to close it if it's fixed...
Updated by Lane, Peter over 10 years ago
I've changed the code to use RunManyParticles instead of RunParticle. This seems to help since initialization for the run only happens once.
Updated by Rogers, Chris over 9 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
I think this is fixed
Updated by Rajaram, Durga over 9 years ago
- Target version changed from Future MAUS release to MAUS-v0.6.0