How to automate actions after waiting for K2 to converge for sequential input changes

Hello world,

this is perhaps a broad question, but nonetheless I'd be extremely grateful of any help or pointers.

For an arbitrarily slow/big K2 simulation with some variable input parameter (see file attached), I'd like to automate a downstream action (in my case: push a button and store some data) when, and only when, K2 has successfully converged. Once the convergence and action have been completed, I'd like to tell the input variable to change.

As the power of K2 grows, so too does its potential for producing valuable analytical results. I'm basically trying to find a way to control the simulation and export results for routine (and big) calculations.

In appreciation,

Greg

Attachments:

waitforconvergence.png, 454 KB
slow simulation with result logging.gh, 18 KB

Replies to This Discussion

Permalink Reply by Anders Holden Deleuran on December 21, 2015 at 3:22am

The attached seems to work in the context of your definition. Although updating/changing goal values probably will not work with scripted goals though (at least not just yet :)

Attachments:

151221_slowsimulationwithresultlogging_UsingCustomSolver.gh, 21 KB

Permalink Reply by Gregory Quinn on January 15, 2016 at 3:20am

Hello!

So I've been able to make some decent progress with the file that Anders shared last.

I now have a pretty cool and versatile custom script which I wanted to share with the community - I'm sure others will be able to benefit from what's in here. I'm quite pleased with it! Here's a brief description:

For a K2 simulation, this solver iterates to a solution for a given VSum threshold and subiteration count.
Once converged, downstream results are logged and an upstream input slider is automatically updated to progress one increment (e.g. a subsequent load case) and the routine repeats.
This facilitates autonomous simulation and result logging using K2, which I think is pretty awesome!

Anders Holden and Max Marschall did all the hard work. I just had the idea and glued it together.

Regards,

Greg

Attachments:

160115_Autonomous K2 simulation with result logging.gh, 18 KB

Permalink Reply by Gregory Quinn on January 15, 2016 at 6:25am

Interestingly, the custom script can't seem to accept the FloorPlane goal. Object reference issues (?). See attached.

As far as I can tell, it doesn't have an issue with the other goals, just FloorPlane.

Any ideas anyone?

Regards,

Greg

Attachments:

Permalink Reply by Gregory Quinn on January 18, 2016 at 9:46am

Since custom goals are not compatible with a custom K2 solver, an alternative to check whether K2 is still solving would be to passively read downstream output, as per the attached example.

This method works and is not sensitive to wider custom scripting issues. Thanks again to Anders for the heads up.

Attachments: