Hi Eric,
no problem - the calculations seem to be *correct* which is the major
hurdle ;-) As I posted, scipy.signal.convole seems a lot faster, and is
probably a good way to do it. The test also revealed that the TDR response
was being re-calculated whenever a marker was moved, which, as it turns
out, was completely unnecessary. So that won't be the case for the next
release :-)
Thanks for your efforts,
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Sun, 27 Oct 2019 at 13:05, <ericm@...> wrote:
Hi Rune,
I am sorry to hear that the convolve math caused so much delay and that I
didn't notice it. Not sure how to measure this. Running python 3.7.4 under
OSX does not seam to have a lot of delay. Could there be a difference in
python versions? Another member also mentioned in a PM to me that he
experienced higher CPU load.
Fortunately Oristo was able to help us out!
I will try to write down the theoretical background of these routines as
to explain the physical background.
Regards,
Eric
