API reference¶
Generated from the code on every build — every signature, every attribute and every description here is the one the interpreter sees. The hand-written guides, which explain why, are under Guides.
visualdynamics.core¶
Geometry, the data arrays, shapes and the analyses over them — the whole toolset without a window. The guide's The objects is the map: every kind, what it stores, and what can be done with it; the pages below hold the signatures.
authoraveragingchannel_tablecompliancecorrelatedatadetectentitiesfemfiltersgeometrykurtosismatchesmergemodal_fitoctavephotosreplicationreportrigidshapesshockssinesrstablestransformtruncateunit_choicesvalidatewavelet
visualdynamics.io¶
Nearly everything the package reads it also writes — one module per format, and a round trip that is tested rather than assumed.
adfexcelexodusexportersfemapnastrannativephoto_filespunchrattlesnakerattlesnake_specificationreport_templatesdynpy_datasdynpy_npzsdynpy_shapessep005sniffingstepstlthreemfunv
visualdynamics.plot¶
One renderer for the app and for scripting, so a plot drawn from a script is the plot the window draws.
visualdynamics.viz¶
Geometry, deflection and picking, over shared VTK buffers.
visualdynamics.report¶
Blocks bound to project objects, rendered to one self-contained page.
visualdynamics.demo¶
The quadcopter and the plate the fixtures, the examples and the website are built from.
visualdynamics.gui¶
The window and its panes. Nothing here is needed to use the toolset from a script, and no Qt is imported outside it.
app_iconauthor_panelaveraging_panelconsoledisclaimerdrawer_tabeditorsfilter_panelglyphsiconsmain_windowobject_tablesoctave_panelpanesproject_treerecord_gridreport_editorrigid_panelsettings_panelshock_panelstage_dragtablestoolbarstruncate_panelwavelet_panelwindows
visualdynamics¶
What import visualdynamics puts in front of you.