Algodoo

Before I attempt to help you on this scene, you need to respond to scripting help needed.

See response scene.

What was done:
  Turn off clouds.
  Turn off gravity.
  Read entire article.
  Set motorTorque for all axles to +inf.
  Add mechanism to pull lowest link.
  Select all links and turn off all collision layers.
  Set bendConstant for thinner sections to 10.
  Set sim.frequency to 240.
  Set air multiplyer to 100 (for damping).
  Add code to puller hinge to track force and deflection.
  Add display box to show force and deflection.
  Add circle to track force and deflection.
  Add plot to track circle.
  
What still needs to be done:
  Tune each of the (3) mechanisms individually by adjusting the bendConstants so that the force deflection curves look like those in the research article.
  Modify the bendConstants in the assembly to the tuned values from the previous step.

Steps are listed below. Report any steps you don't understand. Anyone who understands that step can respond.

What was done:
  1. Turn off clouds.
  2. Turn off gravity.
  3. Read entire article.
  4. Set motorTorque for all axles to +inf.
  5. Add mechanism to pull lowest link.
  6. Select all links and turn off all collision layers.
  7. Set bendConstant for thinner sections to 10.
  8. Set sim.frequency to 240.
  9. Set air multiplyer to 100 (for damping).
  10. Add code to puller hinge to track force and deflection.
  11. Add display box to show force and deflection.
  12. Add circle to track force and deflection.
  13. Add plot to track circle.

What still needs to be done:
  14. Tune each of the (3) mechanisms individually by adjusting the bendConstants so that the force deflection curves look like those in the research article.
  15. Modify the bendConstants in the assembly to the tuned values from the previous step.

I now see that you beat me to answer the request. I missed this because no comment or response to original scene.

Thanks Xray. That helps a lot.

The forces that you cite in the comment above I will assume are correct for that scene, but the scene does not match the behavior of the mechanism in the video. I suspect you understand how the real mechanism is supposed to work as well or better than anybody else here. You may be able to get the scene to work correctly by adjusting bend constants. You (or somebody else) may be able to adjust the bend constants for each part of the assembly by multiplying all the bend constants for that component by the same value. Whoever gets the mechanism to work like the one in the video can post it as a response to ploters scene.

My point was that I'm stuck and willing to accept help from anyone. The last upload is my best shot, but I'm not sure that it functions the same as the one in the video.

Density doesn't matter since gravity is off. The components are frictionless. The elastic properties are shown in the force deflection curves in the paper. I added scenes that display the force deflection curves for the present system as a response to this scene. Modify bend constants to tweak the curves. You are running out of excuses (other than the "trial and error" thing).

Q: Are all those functions intrinsic to Algodoo.
A: No, none are.

Q: Are they ones that either you created or got from some other source (AI maybe?).
A: I asked AI to generate string functions similar to Python.

ploters,
Thanks for the clarification.

Xray,
Thanks.

Q: how do i delete a comment?
A: You don't. Xray might if he feels like it.

Note that the appendix to the article has much more detail on the construction and force-displacement curves for each component.

Thanks for the feedback. Now at 240 Hz.

Xray,

Q: What did you do differently for this YouTube video to display correctly?
A: I changed the video. The original video had a "-" in the url. I thought the "-" might have been tripping up Algobox, so I changed the video.

Ploters,

Thanks.

Nice work.

AI is overcomplicated because it has extra code to show or handle the indexing error source. My recollection was that the AI code ran without error. Once you locate the source of the error, you can modify your original code. What happened when you ran the AI code?

Upon subroutine ignition, the fan's rotational permissivity is nullified via a pre-emptive deenergization cascade. When the photonic emitter interfaces with the chromo-reactive conduit (blueBar), a positive spin-state is induced through laser-initiated flux realignment. The motor's post-cyclonic behavior is then synchronized with the fanMotorIsOn flag using a bidirectional magneto-throttle handshake. For inverse polarity disengagement, consult the auxiliary onNotHitByLaser protocol, which leverages beam absence detection via retrograde luminance attenuation.

I only know of (2) things that God mode does. Only God knows the other things.
No penetration minimizes penetration of one body into another. It comes in handy when dimensional accuracy counts.

Within the cerulean containment matrix, the update vector initiates a conditional runtime oscillation check. If the photonic quantifier exceeds the calibrated refLaserCount threshold and the impact resonance (_hit) is active, a deactivation cascade is triggered via the _onNotHitByLaser subroutine, employing a reverse-phase beam nullifier. Initialization protocols reset the refCount to zero, ensuring temporal coherence. Upon laser impact, the fanMotorIsOn flag is re-energized through quantum beam imprinting, while the motor's postStep logic aligns rotational torque with the fanMotorIsOn state using a dual-phase autobrake inverter. For optimal modularity, encapsulate the laser emitter and reactive box into a phunlet-class component and deploy via scene importation protocols.

Good work. I rated it highly to get it into highlighted scenes.

Nice work.