On 03.08.23 17:28, [email protected] wrote:
I implemented that algorithm (without any pre-computation in source) and
I'm quite optimistic. Benchmark results (on mobile i7-3610QM) are:
- 4R E12 - about 3ms
- 4R E24 - about 12ms
- 4R E96 - about 150ms
- 4R E192 - about 500ms
Obviously PC HW improved as this is much faster to what I tested a few
years ago. E24 was already prepared and I failed there with a progress
bar. The screen was only updated after calculation finished.
Therefore I dropped E24 and above. If you take the practical component
tolarances in account, there is hardly any use for further values
between E96.
Best
Jan
--
You received this message because you are subscribed to the Google Groups "KiCad
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/kicad.org/d/msgid/devlist/faeeada0-c160-7592-888b-435c2dc16a46%40veith.net.
