You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I hooked up the fbar Open-SDFast example to the general simulation analysis driver Dakota, and I did a 512-case Latin Hypercube Sampling of varying all the linkage masses (not the inertias... so there's some weirdness there) and the viscous damping at the crank by +/- 10% uniformly distributed of the nominal values, and I got a bifurcation in the result for going around a second rev in a few cases:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Thought:
Today I hooked up the fbar Open-SDFast example to the general simulation analysis driver Dakota, and I did a 512-case Latin Hypercube Sampling of varying all the linkage masses (not the inertias... so there's some weirdness there) and the viscous damping at the crank by +/- 10% uniformly distributed of the nominal values, and I got a bifurcation in the result for going around a second rev in a few cases:
all_runs_time_history.pdf
Do we want to set up tests that perturb parameters across some ranges for more thorough testing than just single time trace tests?
All reactions