ID: | 4244 |
From: | Evan Foss <ev...@gmail.com> |
Date: | Sun, 5 Jul 2020 12:20:15 -0400 |
Subject: | Re: [pcb-rnd] bugreport: mesh |
in-reply-to: | 4243 from ge...@igor2.repo.hu |
replies: | 4245 from N <ni...@gmail.com> |
On Sun, Jul 5, 2020 at 1:25 AM <gedau@igor2.repo.hu> wrote: > > > > On Sun, 5 Jul 2020, Evan Foss wrote: > > >Ok. If since it's a missing feature I suggest another one. At the very > >least there should be a warning in the log window that lets the user > > I disagree. We don't warn for copper text, and our arc handling is > not very clever either. These are called known limitations. Well once more users show up we will see which opinion is right. I had assumed the meshers algorithm started by placing lines on the ports and then worked out how to handle the copper edges. > I know you bumped into one specific limitation with your current example > so you may feel it's the important one. But in reality users won't know > the internals so they will do random things and will bump into random > _other_ limitations as well. Yea I have more examples I haven't committed yet. I am writing up a guide to debugging simulations for another video. I realized from talking to other wannabe users on twitter that the amount of text in there (probably because of the runtime log) put people off trying it. > Instead of trying to warn for each, we should just fix them - when we get > there. Until that, users shall know the whole thing is not a generic > "simulate anything for me" but a dirty hack to simulate a narrow set of > things. > > Not only the mesher, the whole current setup. > > Instead of spending time on trying to enumerate all possible ways it can > go wrong and fill up the code with warnings about them, I rather spend my > time on a more generic fix (which is really the tinyopenems workflow > effort). > > >know when the mesh lines don't land on the port. I have done a few > >examples and I am doing more. Meshing with real life traces is harder > >than the polygons of the scale in the filter I started with. I can > >tell from testing that the active port causes no excitation if it > >doesn't get all 3 lines. > > As I said, it's on the TODO. I will handle it when I get there. It's > in the queue, please be patient. No rush. I was mostly just concerned about more stuff being built on top of what I thought was a bug. > Regards, > > Igor2 > > -- https://github.com/evanfoss -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2 mQENBFYy4RYBCAC183JomLtbdAlcKiaPDoVHq52LDmVmH75aiEc69m7YxDt54/ai VtYCAobbGVIyn3Hlz3uhF6LnPl/6Lm1VdnCfpwu3KQhCO6ds10ow2C30X4ohCqOd hCVg5C+ILmQkEffFrFODy3ji+PYTF4pADvHCWsTMv0hf0llwFOJsBCK6cl02IffE JPqy4PjM1nZ9HpzT84JBaG/4OGvTZ8SQ2yFUl265jagvygPTf88H1xpZHH1r8dB1 stjUHLmPH8AOyDgKxFchgGeDc3p/vJtgDDIXAFfDXG0NSRovLmtaQdGxe47Zf/go bXiEM7YL2WqQe5zfEA919JxkEwlDKYniOSVzABEBAAG0N0V2YW4gRm9zcyAoVGhp cyBpcyBteSBwdWJsaWMga2V5LikgPGV2YW5mb3NzQGdtYWlsLmNvbT6JATkEEwEC ACMFAlYy4RYCGwMHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRCIpQTcE8nN bbBaCACAm8pU5lG1ev2Fsw68Axtcl57SJrYieqX96c3YuYH9JpqMqJRnd9nDKw9X tQuvuH7tUk0VbOaDqReOYJVI/4c5wb9AaOFp6K2DUcupq6XhgXpvz3HzoPwjAdIj XuQzdRUx5+innTJrSkGuBYW/CZ2zqEx4xfLlq4rO0hoTUMR8QVp2cCrkw6BT0m86 APIw/ZnjoxM8IEzr7MxfRIg3qpzrZk28rmhx+k78Jyk61UhwcCPGIm/pjUopTwYJ 3YBdRB2cYD2aN7A1JVf5cRmSQYooHBGpH0kYvomGk97PKqypVuJ7OpG9xM58wUcC qUVt9hKlePLzP8csYjt8onqI7qIIuQENBFYy4RYBCADlH8spG3WkCx62vB5mr5Z0 SCDd/RcyA4A5y5EOj5KurQkrSWpgi9Ho1yKruMJ6blQR2qkc66KqH9pnXDm/ZI1M K/wdW3ngETxBmXoozzFMT89aEWIVR5/PFodWK1elekE9iJxACuR98Zg2QttTD3x8 A9w8VEyMLOXcDTrPFpHegMKswFBg5iuMulAdXAoGejWTI3n+qKFpabHm2Lfs6wjk 5rjucpTdeFK6UeWF1xAvNxXibuu5BlGwv53930qIXRwO/Gn2Rh5DXWxKU2fEIme/ xgQQmIsDeUoWbfybdjw/x7Q0LW4mINiLDQcGHHRQKFIxbAJCT3USPLGh5xwE9/Er ABEBAAGJAR8EGAECAAkFAlYy4RYCGwwACgkQiKUE3BPJzW0uYAf9Hf30n8tM3mR2 Zo6ESE0ivgdgjaJtAWrBUx7JzAzPjBnBOlNnu5Y9lVEqetvUPH6e3PvaHYUuaUU8 0HwxuKBW9nUprgV6uIu1DZmlcp+SxpbuCy7RDpNocRLNWWFMaYYzznmTgfnTgD4D gCq8Mf1mcfrluTkOAo+QNqbMfl1GISClopRqxVuAo59ewgMnFujwgd8w12BwWl24 CzqOs5HqcUslePj+LzcjSNgVCklYwKl+0dsb/fctMOCtHodwqm2CBJ+zydvNmYkD fxda/J91Z1xrah5ec++FL0L4vs+jCiIWJeupJFKlr1hCMZiiGH7W554loK5l4jv3 EY347EidAw== =Ta4p -----END PGP PUBLIC KEY BLOCK-----
Reply subtree:
4244 Re: [pcb-rnd] bugreport: mesh from Evan Foss <ev...@gmail.com>
4245 Re: [pcb-rnd] bugreport: mesh from N <ni...@gmail.com>
4249 Re: [pcb-rnd] bugreport: mesh from ge...@igor2.repo.hu