Feature #847
Control room - beam envelope tool
100%
Description
We need a simple tool to operate in the control room that will extrapolate beam matrices through the geometry and show calculated linear beam optics output (emittance, twiss parameters, envelopes, energy loss) as a function of z.
Files
Updated by Rogers, Chris over 11 years ago
Proposed GUI attached...
Updated by Rogers, Chris almost 10 years ago
I made a prototype wrapper for the ROOT gui system that handles layout based on a configuration (json) file. Added half a GUI as part of the set up process.
Probably got 12 good hours working on this during the CM.
Updated by Rogers, Chris almost 10 years ago
Another 16 hours or so - have a functional prototype that makes some plots. Have dialogues for selecting beam and for manipulating magnet currents, plus an embedded canvas that holds plots of propagated beam envelope variables. Working on the plotting dialogue, and haven't started any tests or documentation at all...
Still to do then:
Plotting dialogue (8 hours)6 hoursBackend mod - field element aperture (8 hours)4 hoursBackend mod - propagate reference particle (for mean energy etc) (8 hours)4 hoursTests of the ROOT GUI wrapper stuff (8 hours)4 hoursTests of the actual logic (8 hours)8 hoursDocument,pylint and prettification (8 hours)2 hours- (pylint was done with everything else)
So looks like I will overrun the 56 hour estimate for effort required by ~ 30 %. Let's wait and see.
Updated by Rogers, Chris almost 10 years ago
Additionally:
- Reasonable geometry set up
Bug fix - ROOT TGTextEntry is throwin segv if I update it by hand (not if I update it automatically)Exception handler(5 hours)
Updated by Rogers, Chris almost 10 years ago
I think that this is reasonably complete now.
The outstanding issue is a reasonable geometry description. I think this is predicated on Ryan finishing what he is up to, so I won't press it now.
Updated by Rogers, Chris almost 10 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
Merged to trunk as r1014 - another hour spent mucking about with the test server brings the total time spent up to
12 + 16 + (6 + 4 + 4 + 4 + 8 + 2) + 5 + 1 = 62 hours
Next steps on this:- Get a clean geometry description
- Sit with some operations or analysis people in the MLCR and get a new set of requirements
It won't happen any time soon I suspect.
Updated by Rajaram, Durga over 9 years ago
- Target version changed from Future MAUS release to MAUS-v0.7.4