iMSTK issueshttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues2019-07-28T15:57:44-04:00https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/81Offset initialization for virtual-coupling object2019-07-28T15:57:44-04:00Nicholas MilefOffset initialization for virtual-coupling objectIn VirtualCouplingObject.cpp:
* virtualCoupling->initOffsets() &
* updateFromDevice() {computeTrackingData(p, r)}
* It will give wrong coordinates if mesh is loaded and then relocated/reoriented. The virtualCoupling->initOffsets() is c...In VirtualCouplingObject.cpp:
* virtualCoupling->initOffsets() &
* updateFromDevice() {computeTrackingData(p, r)}
* It will give wrong coordinates if mesh is loaded and then relocated/reoriented. The virtualCoupling->initOffsets() is called when simulation mode starts. All translation/rotation made will be treated as offset, which is not always the case.
* Considering set two different offset? One for tool-mesh offset, one for mesh offset to its original position.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/82Leap Motion Integration2018-09-17T11:17:12-04:00Nicholas MilefLeap Motion Integration* Involves GPU skinning
* This needs to get done (not just for fun :smile: )* Involves GPU skinning
* This needs to get done (not just for fun :smile: )Nicholas MilefNicholas Milefhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/83Debug visualization2018-11-10T19:30:30-05:00Nicholas MilefDebug visualizationDebug visualization could help debug various algorithms during the development process
* Vector visualization: Easy printout and visualization of vectors(in 3D scene and its magnitude vs. time in a 2D plot)
* On-the-fly visualization...Debug visualization could help debug various algorithms during the development process
* Vector visualization: Easy printout and visualization of vectors(in 3D scene and its magnitude vs. time in a 2D plot)
* On-the-fly visualization of a given type of primitives (Points, line segments, triangles). These primitives are expected to change at every simulation time stephttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/84Add imstkCollidingObject2019-03-19T15:51:27-04:00Nicholas MilefAdd imstkCollidingObject* Member variable m_collidingGeometry in both imstkSceneObject and imstkCollidingObject?
* imstkCollidingObject actually don’t add new stuff on top of imstkSceneObject.* Member variable m_collidingGeometry in both imstkSceneObject and imstkCollidingObject?
* imstkCollidingObject actually don’t add new stuff on top of imstkSceneObject.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/85Create documentation guidelines2019-03-07T12:51:06-05:00Nicholas MilefCreate documentation guidelinesWhat should be the rules for documenting the source code with Doxygen? Is there a certain template we should follow? I want to start documenting some functions before I forget how they work :wink:.What should be the rules for documenting the source code with Doxygen? Is there a certain template we should follow? I want to start documenting some functions before I forget how they work :wink:.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/86VegaFEM CMake file not being found2019-03-19T15:51:27-04:00trudiQVegaFEM CMake file not being foundI switched to ssh (from http) to clone the repo, and that cleared up many of the issues downloading the dependent repositories. However, I have one dependency that is failing (VegaFEM):
```
17> CMake Error at CMakeLists.txt:130 (find_p...I switched to ssh (from http) to clone the repo, and that cleared up many of the issues downloading the dependent repositories. However, I have one dependency that is failing (VegaFEM):
```
17> CMake Error at CMakeLists.txt:130 (find_package):
17> Could not find a package configuration file provided by "VegaFEM" with any
17> of the following names:
17>
17> VegaFEMConfig.cmake
17> vegafem-config.cmake
17>
17> Add the installation prefix of "VegaFEM" to CMAKE_PREFIX_PATH or set
17> "VegaFEM_DIR" to a directory containing one of the above files. If
17> "VegaFEM" provides a separate development package or SDK, be sure it has
17> been installed.
17>
17>
17> -- Configuring incomplete, errors occurred!
17> See also "C:/Projects/iMSTK/build/Innerbuild/CMakeFiles/CMakeOutput.log".
17>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5): error MSB6006: "cmd.exe" exited with code 1.
```Alexis GiraultAlexis Giraulthttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/87iMSTK interface for 3D collisions2019-03-19T15:51:27-04:00trudiQiMSTK interface for 3D collisionsI think we should have an interface for 3D collisions libraries so that you can switch between them depending on your needs. For example, being able to switch from PhysX to Newton or vice-versa would be a useful feature.I think we should have an interface for 3D collisions libraries so that you can switch between them depending on your needs. For example, being able to switch from PhysX to Newton or vice-versa would be a useful feature.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/88Add virtual coupling for rigid-rigid contacts2019-03-19T15:51:27-04:00Sreekanth ArikatlaAdd virtual coupling for rigid-rigid contactsvirtual coupling represents a rigid object being controlled by the user into visual and haptic representations (connected by mass-spring-damper) thereby simulating non-penetration and proper force feedback.virtual coupling represents a rigid object being controlled by the user into visual and haptic representations (connected by mass-spring-damper) thereby simulating non-penetration and proper force feedback.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/89Implement LCP collision response2019-07-28T15:57:48-04:00Sreekanth ArikatlaImplement LCP collision responseLinear complementarity problem (LCP) based response to resolve contactsLinear complementarity problem (LCP) based response to resolve contactshttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/90Implement linear projection constraints2019-03-19T15:51:27-04:00Sreekanth ArikatlaImplement linear projection constraintsLinear projection constraints [1] for rigid-soft interactions, picking and general Dirichlet B.C.
Reference:
1. http://dl.acm.org/citation.cfm?id=2542348Linear projection constraints [1] for rigid-soft interactions, picking and general Dirichlet B.C.
Reference:
1. http://dl.acm.org/citation.cfm?id=2542348https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/91Add rigid body dynamics capability2019-03-19T15:51:27-04:00Sreekanth ArikatlaAdd rigid body dynamics capabilityAdd rigid body dynamics capability either through native implementation or by incorporating a library
One option: http://www.ode.org/Add rigid body dynamics capability either through native implementation or by incorporating a library
One option: http://www.ode.org/https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/92Add support for 1-D elastic structures2018-09-15T12:24:20-04:00Sreekanth ArikatlaAdd support for 1-D elastic structuresAdd support for 1-D elastic structures. One use case is the suture thread simulation. This could be done using mass-spring with bending stiffnessAdd support for 1-D elastic structures. One use case is the suture thread simulation. This could be done using mass-spring with bending stiffnesshttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/93Extend existing PBD formulation to include fluid simulation2019-03-19T15:51:27-04:00Sreekanth ArikatlaExtend existing PBD formulation to include fluid simulationReference:
1. http://mmacklin.com/pbf_sig_preprint.pdf
!190 Reference:
1. http://mmacklin.com/pbf_sig_preprint.pdf
!190 Rachel ClippRachel Clipphttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/94Add support for VEGA's precomputed models for deformation mechanics2019-07-28T15:57:51-04:00Sreekanth ArikatlaAdd support for VEGA's precomputed models for deformation mechanicsVEGA has support for model order reduction based deformation models that needs to be interfaced with iMSTKVEGA has support for model order reduction based deformation models that needs to be interfaced with iMSTKhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/95Add frictional mechanical models2019-07-28T15:57:54-04:00Sreekanth ArikatlaAdd frictional mechanical modelsReferences:
1. IPC based friction modeling: http://www.sciencedirect.com/science/article/pii/S1524070315000491
2. Friction cone based friction modeling: http://www.gmrv.es/Publications/2009/OTSG09/OTSG09.pdfReferences:
1. IPC based friction modeling: http://www.sciencedirect.com/science/article/pii/S1524070315000491
2. Friction cone based friction modeling: http://www.gmrv.es/Publications/2009/OTSG09/OTSG09.pdfhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/96Make sure modules shut down properly2017-07-03T15:39:10-04:00Nicholas MilefMake sure modules shut down properlyRight now, it doesn't look like modules are shutting down properly. This means that there's a potential to lose work done in a module right now since the module gets shut down by the OS if the main thread closes first.
Edit: Looks lik...Right now, it doesn't look like modules are shutting down properly. This means that there's a potential to lose work done in a module right now since the module gets shut down by the OS if the main thread closes first.
Edit: Looks like I made a mistake debugging.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/97Program shuts down immediately after starts2017-07-03T15:39:10-04:00trudiQProgram shuts down immediately after startsHi @alexis-girault
after pulled the latest code (commit: Merge branch 'fix_multiple_omnis' into 'master') from master, i got this issue.. attached pls find the log file.[simulation.g3log.20161013-105851.log](/uploads/9d9c8ecfbb8d4771bbc...Hi @alexis-girault
after pulled the latest code (commit: Merge branch 'fix_multiple_omnis' into 'master') from master, i got this issue.. attached pls find the log file.[simulation.g3log.20161013-105851.log](/uploads/9d9c8ecfbb8d4771bbcb22f53855740a/simulation.g3log.20161013-105851.log)https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/98Input file format for vegaFEM2017-07-03T15:39:10-04:00mohitTyagiInput file format for vegaFEM1. what are the file formats which handles all the inputs in a single file, such as mesh and material (mechanical) properties ? .veg is one such.
2. is a file converter required ?1. what are the file formats which handles all the inputs in a single file, such as mesh and material (mechanical) properties ? .veg is one such.
2. is a file converter required ?https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/99Refactor controller/virtualobject class2017-07-03T15:39:10-04:00Alexis GiraultRefactor controller/virtualobject classRight now we have two different kind of controllers:
- `CameraController`, subclassing `TrackingController`, which can be setup from the `Camera` class and control the camera
- `VirtualCouplingObject, subclassing `TrackingController` a...Right now we have two different kind of controllers:
- `CameraController`, subclassing `TrackingController`, which can be setup from the `Camera` class and control the camera
- `VirtualCouplingObject, subclassing `TrackingController` as well as `CollidingObject`, which can control its own geometry
My suggestion would be to get rid of `VirtualCouplingObject` to instead have:
- `SceneObjectController`, subclassing `TrackingController`, which can be setup from the `SceneObject` class and control the object geometry
Thoughts? @HongLi @trudiQ @sreekanth-arikatla ?Alexis GiraultAlexis Giraulthttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/100Place resources for examples online2017-07-03T15:39:10-04:00Sreekanth ArikatlaPlace resources for examples online* The resources (mesh files, texture files, shaders etc.) can be placed online to facilitate easy download
* They can be downloaded automatically through a Cmake script that is part of the example* The resources (mesh files, texture files, shaders etc.) can be placed online to facilitate easy download
* They can be downloaded automatically through a Cmake script that is part of the exampleRelease 1.0.0