dynamic relaxation node about dynamo HOT 8 CLOSED

Works now. I've got it more stable with shorter spring rest length, tighter steps and more dampening. In example below there are 10 points laid out along x-axis every 100 feet. Spring rest length is 1 foot. You can see the contraction in the screenshot below. You can see from the forces in the m_Velocity field and the delta between m_oldPosition and m_Position that the point is moving to the left. What i'm not sure, because the dynamics are not working yet is how well the dampening works over time and does acceleration stay under control or not.

Regarding dynamics - I'm still experimenting with timers and having trouble having the stopwatch trigger an update when the interval is hit. I have recreated the old dynTimer and am using a stopwatch but the only way I can hit KeepTime() is in the Evaluate loop for dynTimer. I want to send a pulse downstream every time the stopwatch hits a specified interval in milliseconds. I feel a mental block coming on here - I need some Stephen magic or at least a hint from Stephen or Ian.

Todo on the dynDynamicRelaxation:

• parse input point and curve lists, convert to particles and springs. Right now it just uses a stub setup method in the constructor
• Make the output points and curves be handled non-destructively, this will speed things up a lot
• Manage changes to input lists (add,remove,change)
• Expose stepsize as an input port.
• Coloring of springs would fun but adding OSTs is a PIA in revit, maybe use AVF instead.

from dynamo.

need to expose Gravity vector and Wind vec as inputs to node

from dynamo.

"Timer" node has been implemented as "Evaluation Interval" node

from dynamo.

Does the evaluation interval exist any more?

from dynamo.

Hi erik @ekatzenstein, the evaluation interval node did not make the transition to 7.x but @Steell @ikeough and @lukechurch have a new timer design for a number of needs here.

from dynamo.

Thanks Matt, was there meant to be a link at the end of your post? Seems to
be missing.

On Wednesday, November 19, 2014, Matt Jezyk [email protected]
wrote:

Hi erik @ekatzenstein https://github.com/ekatzenstein, the evaluation
interval node did not make the transition to 7.x but @Steell
https://github.com/Steell @ikeough https://github.com/ikeough and
@lukechurch https://github.com/lukechurch have a new timer design for a
number of needs here.

—
Reply to this email directly or view it on GitHub
#45 (comment).

from dynamo.

Nope, just wanted to say we have people working on this now

-matt

On Nov 19, 2014, at 10:26 PM, ekatzenstein [email protected] wrote:

Thanks Matt, was there meant to be a link at the end of your post? Seems to
be missing.

On Wednesday, November 19, 2014, Matt Jezyk [email protected]
wrote:

Hi erik @ekatzenstein https://github.com/ekatzenstein, the evaluation
interval node did not make the transition to 7.x but @Steell
https://github.com/Steell @ikeough https://github.com/ikeough and
@lukechurch https://github.com/lukechurch have a new timer design for a
number of needs here.

—
Reply to this email directly or view it on GitHub
#45 (comment).

—
Reply to this email directly or view it on GitHub.

from dynamo.

Ok great. Looking forward to the next release.

On Wednesday, November 19, 2014, Matt Jezyk [email protected]
wrote:

Nope, just wanted to say we have people working on this now

-matt

On Nov 19, 2014, at 10:26 PM, ekatzenstein <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

Thanks Matt, was there meant to be a link at the end of your post? Seems
to
be missing.

On Wednesday, November 19, 2014, Matt Jezyk <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');>
wrote:

Hi erik @ekatzenstein https://github.com/ekatzenstein, the
evaluation
interval node did not make the transition to 7.x but @Steell
https://github.com/Steell @ikeough https://github.com/ikeough and
@lukechurch https://github.com/lukechurch have a new timer design
for a
number of needs here.

—
Reply to this email directly or view it on GitHub
#45 (comment).

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#45 (comment).

from dynamo.