A molecular simulation can look plausible frame by frame and still fail to answer the question you care about. One common reason is that a part of the model is being moved on a timescale that is too fast for the behavior you want to study. If a gripper misses its target, for example, the result may reflect the imposed motion—not simply the gripper’s design.
SAMSON’s Simulate animation performs multiple simulation steps at each frame. It can also be combined with animations that control atom positions, which makes it possible to run constrained simulations. That combination is useful, but it makes the order of the animations important: the motion that sets up the simulation and the simulation itself need to be arranged deliberately.
Start by checking the timescale
A useful first check is to estimate how quickly the driven part of your model moves. In the documented nano-gripper example, the actuated part moves 1.7 nm in 2.5 ps. Dividing distance by time gives a speed of 0.68 nm/ps, or 680 m/s. In that example, the part moves down too quickly and the gripper fails to grasp the cylinder.
This calculation does not tell you by itself what motion is appropriate for every model. It does give you a concrete quantity to inspect instead of relying only on how the animation looks. A movement that appears gradual across a few frames can correspond to a very short physical interval. Before interpreting a failed interaction, check the displacement and time interval associated with the imposed motion.
Put the simulation in the right place
The Animator executes animations from top to bottom. As a result, place Simulate after the animations that generate the starting positions for the simulation. If the order is not what you intended, the simulation may run at a different point in the animation sequence than you expect.
To add the animation, double-click Simulate in the Animation panel of the Animator. Its keyframe is placed at the current frame, and you can move the keyframe if needed. It is worth checking both the animation order and the keyframe location before running the sequence, particularly when several animations contribute to the motion.
Make the setup easier to inspect
- Identify the moving part. Note which atoms or component are being repositioned by another animation.
- Estimate its displacement over time. Use the distance moved and the interval to calculate an approximate speed. This helps distinguish a visual impression from the actual rate of motion.
- Check the Animator order. Confirm that the animations producing the starting positions appear before Simulate.
- Inspect the simulation settings. In the Inspector for the Simulate animation, you can change the number of steps per frame and the step size for the simulator’s state updater.
- Review the resulting trajectory. The Record path animation can save the trajectory generated by the simulation. The path can also be used with Play path or Play reverse path.
Changing the number of steps per frame or the step size changes the simulator’s update settings; it does not, by itself, establish that a chosen imposed motion is physically appropriate. Treat these settings and the movement timescale as separate things to check. If a driven component moves too quickly for the question you are asking, revisit the motion and evaluate the simulation again rather than treating a failed grasp as a definitive test of the design.
This simple diagnostic is useful whenever a simulation combines externally controlled positions with molecular dynamics: check what is being moved, how fast it is moved, and when the simulation runs. For details on adding and configuring the animation, see the Simulate animation documentation.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
