kill calc

[uomou]

I wonder if there is a way to stop the calculation proces. Say you have a full sheet with nested parts, sometimes it takes like 10 minutes until the calculation is doen. You spot a mistake while bb is calculating, and I cannot aboard the calculation.

Thanks for help

Alex

[JensDyvik]

I am not sure. Sometime hitting the escape button can stop a calculation process sooner in grasshopper. Have you done any research on generally stopping a calculation process in grasshopper?

[uomou]

hitting escape doesent do much, but I just found this:

The new component Data Dam is pretty useful for keeping large definitions under control. A few Data Dam at key locations can turn a potentially BSODing large calculation into several smaller managable ones, and for calculations that does not change often you can have the data buffered at the dam (by disabling the stuff before it) to save CPU time. I'm liking this component a lot atm

[JensDyvik]

My experience with the data dam component is that it is a bit finicky. I am also worried that the user interface will become more complicated to learn and use if you have to toggle a data dam component or more.

Maybe the best solution for now is to speed up general calculation time?

[mikeFandA]

If you´re open to other plugins you could look at human, it has various interface components that help with this kind of thing. Another option is to setup up a small scripting component to do the same as data dam but using a button press, then locate the buttons for the various stages with a note to say apply changes to path, to block, to material etc. I haven't dipped into the structure of your code for quite a while but it's possible that you could split each function into several nodes that are calculated separately before the final calculation (if you haven't already done so), with some previews at each stages to verify correct data entry or results to keep things user friendly and avoid heavy calculations for now reason.

Michael Arnett

BArch MArch

Coordinador de Robotica y Diseño Digital

Universidad Autonoma de Chile

Sede Temuco

+56 45 2895298

Avda. Rudecindo Ortega 01302, Temuco

On Mon, 29 Nov 2021 at 11:23, Jens Dyvik @.***> wrote:

My experience with the data dam component is that it is a bit finicky. I am also worried that the user interface will become more complicated to learn and use if you have to toggle a data dam component or more.

Maybe the best solution for now is to speed up general calculation time?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/fellesverkstedet/Bark-beetle-parametric-toolpaths/issues/81#issuecomment-981681870, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGFQFYNCT36SDQKIF543CHTUOOEHRANCNFSM5IVQH55Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.