List view
Currently much of the functionality of this package, especially for the mesh manipulation, rely on an assumed matrix index ordering for spatial dimension and time. To make matters worse, that ordering is not strictly enforced across the package, and sometimes is projected onto the user to know what is what. The `xarray` package (https://xarray.pydata.org) provides a nice, high-level abstract to allow dimensions to be more elegantly referenced by descriptive labels, which would greatly improve readability of the code, and reduce opportunity for user errors. This is a target of future refactoring, but no core functionality is foreseen to change with this infrastructure (except for some API changes for some functions).
No due date•0/1 issues closedGet the thermal simulations up-to-snuff to better match the upgrades to the mechanical sims. This will include: * More Python thermal-specific code (keep weaning away from Matlab) * Thermal examples (none exist right now) * More gracefully functionality for different types of thermal analyses (M-mode, B-mode, etc.) Should build this up in the context of the new JSON probe reading that is on a branch not yet merged into `master`.
No due date•3/7 issues closedconvert to using a standard JSON probe file definition (that will also be used by the ultratrack code)
No due date•2/4 issues closed- No due date•6/9 issues closed
Need more advanced point loads handling, including (1) 3D quiver plots, (2) better multiple vector components, etc.
No due date•0/2 issues closed