@JimCarruthers wrote:
I'm working on converting a VBscript into Python, to learn Python and hopefully leverage some RhinoCommon stuff to speed it up. The script is for fitting (very specific) curves to other curves, using a brute force randomly-try-anything-then-check-accuracy approach. I've left the VBscript version to run for a day, churning through millions of possibilities, only interacting with the document to draw in a new best-fit when found. The Python version right now doesn't even draw every best-fit, just after completing a set of options, so I kinda presumed that even if it was still mostly using rhinoscript functions it would be faster, but it behaves kinda weird.
Less than a minute into running the script Rhino stops displaying the debugging messages I'm printing to the command line and becomes unresponsive, to the point where if(as I would do with the VBScript version) I can't open up a second session of the same file. Eventually it finishes running the script and spits out the rest of the command line messages and all the output at once, which is obviously not how it's set up to work. Is there something known about quirks of this stuff that might explain that?
Posts: 7
Participants: 4