1) handle input depo management mode and ("fixed", "continuous")
2) delegate to ImpactZipper to actually calculate the waveforms.
A new method replacing his second one (and not covered in this ticket) is needed for this calculation which is faster. It can otherwise reuse the first of the above Ductor functionality. But to do that a component interface needs to be inserted between these two functionalities.
The existing IDepoFramer is a suitable interface.
Unordered steps to fix this bug:
[ ] cut out current implementation of loop over plane and wires into a new DepoZipper which uses ImpactZipper
[ ] add configurable type/name to Ductor so user can specify which IDepoFramer to use
The new faster (for more than about 5000 depos) 2D FFT based "zipper" has been implemented directly in ImpactZipper and placed behind a m_flag variable. This needs to be moved out of this source file.
Ductor currently does really two main things:
1) handle input depo management mode and ("fixed", "continuous")
2) delegate to
ImpactZipper
to actually calculate the waveforms.A new method replacing his second one (and not covered in this ticket) is needed for this calculation which is faster. It can otherwise reuse the first of the above
Ductor
functionality. But to do that a component interface needs to be inserted between these two functionalities.The existing
IDepoFramer
is a suitable interface.Unordered steps to fix this bug:
DepoZipper
which usesImpactZipper
Ductor
so user can specify whichIDepoFramer
to useDuctor
use IDepoFramer