Acknowledgments

Three people have written the code in Visual Dynamics, and others have tested it. Many more gave it ideas, and this page thanks them.

Contributors

Dr. Brandon Zwink started the project and maintains it.

Kevin Cross contributed the sine tracking, which reads a sweep the way a controller's tracking filter does, and thirteen of the readings a test is judged by: the SRS points rule, Q from a peak's half-power width, the shock check, the confidence band on an averaged PSD, the tone read off an ASD, the time statistics, the replication read segment by segment, the classical pulse check, the sweep rate against the modes, the signature comparison, the replication fit, the stroke readout and the dwell.

Matt McDowell made the sparse eigensolution faster: a solve up to a frequency counts the modes below it first and solves once, numpy's and scipy's BLAS thread pools no longer compete while it runs, and the solver checks for converged modes less often.

David Soine tests Visual Dynamics on Windows.

Ideas and inspiration

These people and projects did not write code for Visual Dynamics, but the ideas they offered or showed are in it, and it is better for them.

• sdynpy, the structural dynamics library for Python. Many of the ideas here were first seen in it.
• Rattlesnake, the vibration controller, whose runs this toolset was first built to read.
• Dr. Dan Rohe, for showing what open-source tools for structural dynamics can be.
• Dr. Ryan Schultz, whose implementations of bandwidth averaging, in his own tools and in sdynpy, inspired the bandwidth averaging here.
• Dr. Angela Montoya suggested including the wavelet computation.
• Dr. Chris Beale, for the inspiration behind the report plots.
• Matt McDowell, for the inspiration behind the project tree.

Standing on

• Bendat and Piersol, Random Data. The spectral conventions here follow it, and where two common readings of a term had to be chosen between, theirs was taken.
• The universal file format's dataset 58, a format decades old that still says what a channel is and what it measures.
• sdynpy and Rattlesnake, for showing what these tools should do.

No code from sdynpy, Rattlesnake or any other project is used in Visual Dynamics. Their ideas were studied, and the methods were written here independently.