Skip to content
Educational Vibration programs. Intended for undergraduate and early graduate students.
Python Makefile
Branch: master
Clone or download

readme.rst

The Engineering Vibration Toolbox for Python

https://badge.fury.io/py/vibration-toolbox.png/ https://travis-ci.org/vibrationtoolbox/vibration_toolbox.svg?branch=master PyPi Download stats

Joseph C. Slater and Raphael Timbó

Welcome to the Vibration Toolbox. This Python version is a completely new design build for modern education. This is an educational set of codes intended primarily for demonstration of vibration analysis and phenomenon. You may find them useful for application, but that isn't the intent of this toolbox. If you have professional-level needs please contact the authors.

Full documentation is available, but please excuse that it is still under development. Such documentation has never existed for the other ports of the toolbox so this is taking some time. We don't need feedback at this time, but we will take assistance in improving documentation and code. Please clone the repository and support use by submitting pull requests fixing typos and clarifying documentation.

Try now!

You won't get everything, but you can try parts of the toolbox immediately on and tutorial on mybinder.org, right in your browser window.

Installation

If you aren't familiar at all with Python, please see Installing Python.

Installation is made easy with pip (or pip3), with releases as we have time while we try to create a full first release. Much of it works already, but we certainly need issue reports (on github).

To install type:

pip install --user vibration_toolbox

at your command prompt (not the python prompt) where --user isn't necessary if you are using a locally installed version of Python such as Anaconda.

To run, I recommend you open a Jupyter notebook by using jupyter notebook at your command prompt/terminal prompt/Anaconda prompt and then type:

import vibration_toolbox as vtb

For examples, see the JupyterNotebooks folder. Some of these have interactive capabilities that are only apparent when you run them yourself instead of just looking at them on GitHub. Unfortunately our organization of these still leaves a little to be desired. Help accepted!

Installation of current code/contributing

The usage documentation is far behind the current code, while the reference is way ahead of the released code due to the autodoc capability of Sphinx. Especially as of 2017, the code is still in rapid development. So is the documentation. Releases to pypi.

If you wish to install the current version of the software, and especially contribute, please follow the instructions in Contributing.rst

That should be it. Please note issues on the issues tab on GitHub.

You can’t perform that action at this time.