![]() ![]() ![]() ![]() But since I don't want to work for 30 years on just that one area it's not really feasible for me to make a complete new fillet engine myself, it's something that I need to license from an existing library. I can fix some individual bugs in the current filleter, and in fact I did fix a couple of them near the end of v4 (at a time cost of several weeks of focused work for each one). That's something that takes a long sustained effort like 30 man years of effort before it's very good. A strong fillet engine isn't made by executing a single algorithm well, it's done by recognizing and handling a large number of special cases and corner configurations. Hi Mauro, well for filleting it's a difficult case.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |