iMSTK issueshttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues2021-07-06T22:15:17-04:00https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/242Update doc with right version of cmake2021-07-06T22:15:17-04:00Sreekanth ArikatlaUpdate doc with right version of cmakehttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/241superbuild fails at physx external project2020-03-13T09:43:39-04:00Sreekanth Arikatlasuperbuild fails at physx external projecthttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/240Timeout in external data download2020-02-24T14:29:34-05:00Sreekanth ArikatlaTimeout in external data downloadThe volume rendering data set fails to download as it times out even after setting no limits on timeThe volume rendering data set fails to download as it times out even after setting no limits on timehttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/239Using system builds of dependencies fails2020-07-31T13:04:54-04:00Sreekanth ArikatlaUsing system builds of dependencies failshttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/238Remove cyclic dependencies2020-07-31T11:23:15-04:00Sreekanth ArikatlaRemove cyclic dependencies[click here to visualize](https://dreampuf.github.io/GraphvizOnline/#digraph%20imstkDependency%0A%7B%0Astyle%3Dfilled%3B%0Acolor%3Dlightgrey%3B%0Anode%20%5Bstyle%3Dfilled%2Ccolor%3Dcornflowerblue%5D%3B%0Aedge%5Barrowhead%3Dvee%2C%20arrow...[click here to visualize](https://dreampuf.github.io/GraphvizOnline/#digraph%20imstkDependency%0A%7B%0Astyle%3Dfilled%3B%0Acolor%3Dlightgrey%3B%0Anode%20%5Bstyle%3Dfilled%2Ccolor%3Dcornflowerblue%5D%3B%0Aedge%5Barrowhead%3Dvee%2C%20arrowtail%3Dinv%2C%20arrowsize%3D.7%2C%20color%3Dgrey20%5D%0ACollision%20-%3E%20Datastructures%20%20%20%20%0ACollision%20-%3E%20Geometry%0ACollision%20-%3E%20SceneElements%0ACollision%20-%3E%20DynamicalModels%0A%0AAnimation%20-%3E%20Core%0AAnimation%20-%3E%20Geometry%0AAnimation%20-%3E%20SceneElements%0A%0ASimulationManager%20-%3E%20Rendering%0A%0AMaterials%20-%3E%20Core%0A%0AGeometry%20-%3E%20Core%0AGeometry%20-%3E%20Materials%0A%0ADevices%20-%3E%20Core%0A%0AScene%20-%3E%20Core%0AScene%20-%3E%20SceneElements%0AScene%20-%3E%20DynamicalModels%0AScene%20-%3E%20Collision%0A%0AConstraints%20-%3E%20Core%0AConstraints%20-%3E%20Geometry%0A%0ADynamicalModels%20-%3E%20Core%0ADynamicalModels%20-%3E%20Datastructures%0ADynamicalModels%20-%3E%20Geometry%0ADynamicalModels%20-%3E%20Constraints%0ADynamicalModels%20-%3E%20Solvers%20%5Bcolor%3Dred%5D%0A%0ARendering%20-%3E%20Scene%0ARendering%20-%3E%20Animation%0A%0ASceneElements%20-%3E%20Core%0ASceneElements%20-%3E%20Geometry%0ASceneElements%20-%3E%20Constraints%0ASceneElements%20-%3E%20Devices%0ASceneElements%20-%3E%20DataStructures%0ASceneElements%20-%3E%20DynamicalModels%20%20%5Bcolor%3Dred%5D%20%20%20%0A%0ASolvers%20-%3E%20Core%0ASolvers%20-%3E%20Datastructures%0ASolvers%20-%3E%20Constraints%0ASolvers%20-%3E%20SceneElements%20%5Bcolor%3Dred%5D%0A%0ADatastructures%20-%3E%20Core%0ADatastructures%20-%3E%20Materials%0ADatastructures%20-%3E%20Geometry%0A%0AGUIOverlay%20-%3E%20Core%0A%0AapiUtilities%20-%3E%20Core%0AapiUtilities%20-%3E%20SimulationManager%0AapiUtilities%20-%3E%20Scene%0A%7D)
```
digraph imstkDependency
{
style=filled;
color=lightgrey;
node [style=filled,color=cornflowerblue];
edge[arrowhead=vee, arrowtail=inv, arrowsize=.7, color=grey20]
Collision -> Datastructures
Collision -> Geometry
Collision -> SceneElements
Collision -> DynamicalModels
Animation -> Core
Animation -> Geometry
Animation -> SceneElements
SimulationManager -> Rendering
Materials -> Core
Geometry -> Core
Geometry -> Materials
Devices -> Core
Scene -> Core
Scene -> SceneElements
Scene -> DynamicalModels
Scene -> Collision
Constraints -> Core
Constraints -> Geometry
DynamicalModels -> Core
DynamicalModels -> Datastructures
DynamicalModels -> Geometry
DynamicalModels -> Constraints
DynamicalModels -> Solvers [color=red]
Rendering -> Scene
Rendering -> Animation
SceneElements -> Core
SceneElements -> Geometry
SceneElements -> Constraints
SceneElements -> Devices
SceneElements -> DataStructures
SceneElements -> DynamicalModels [color=red]
Solvers -> Core
Solvers -> Datastructures
Solvers -> Constraints
Solvers -> SceneElements [color=red]
Datastructures -> Core
Datastructures -> Materials
Datastructures -> Geometry
GUIOverlay -> Core
apiUtilities -> Core
apiUtilities -> SimulationManager
apiUtilities -> Scene
}
```https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/237Simulation Can't Start Without a Scene2020-06-02T18:47:28-04:00Andrew WilsonSimulation Can't Start Without a SceneThe simulation manager's initial scene name is "" which it will try to look up in a map and break. The simulation manager should be able to start without a scene.The simulation manager's initial scene name is "" which it will try to look up in a map and break. The simulation manager should be able to start without a scene.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/236Replace PointSet Glyph3D with vtkOpenGLGlyph3DMapper for hardware instancing2021-01-08T17:22:16-05:00Sreekanth ArikatlaReplace PointSet Glyph3D with vtkOpenGLGlyph3DMapper for hardware instancingreported by @andrew.wilsonreported by @andrew.wilsonhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/235Resetting PBD Examples on Debug build Breaks2020-07-31T13:03:15-04:00Andrew WilsonResetting PBD Examples on Debug build BreaksOnly happens with PBD Examples.Only happens with PBD Examples.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/234where is the xPBD branch?2019-12-20T16:20:58-05:00swqwhere is the xPBD branch?https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/233nothing display in the window2019-10-23T02:27:45-04:00Wu Bonothing display in the windowHi
I am new to the excellent toolkit. I downloaded the source code and compiled it successfully. However, I got nothing displayed on the window when I tried the example. Here I run Example-PBDFluids, but I only got this ![Screenshot_201...Hi
I am new to the excellent toolkit. I downloaded the source code and compiled it successfully. However, I got nothing displayed on the window when I tried the example. Here I run Example-PBDFluids, but I only got this ![Screenshot_2019-09-27_18-17-32](/uploads/91f12a536277e0309c51adf7fa5ec16f/Screenshot_2019-09-27_18-17-32.png)
and there is no info about where the problem is. I tried to run the program in different path, but no good.
anyone run into same problem? is there any advices?
thanks in advancehttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/232Group multiple projects into folders in msvc2019-08-03T18:26:15-04:00Sreekanth ArikatlaGroup multiple projects into folders in msvchttps://stackoverflow.com/questions/41078807/cmake-and-visualstudio-group-files-in-solution-explorerhttps://stackoverflow.com/questions/41078807/cmake-and-visualstudio-group-files-in-solution-explorerhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/231Improve Parallel SpinLock Efficiency2021-06-01T12:50:54-04:00Nghia TruongImprove Parallel SpinLock EfficiencyRead: https://geidav.wordpress.com/2016/03/23/test-and-set-spinlocks/
![Capture](/uploads/406a4c763ccea6a52403a66c51d7d30e/Capture.PNG)
The current spinlock in iMSTK is TasSpinLock. The bets spinlock implementation (from the link above...Read: https://geidav.wordpress.com/2016/03/23/test-and-set-spinlocks/
![Capture](/uploads/406a4c763ccea6a52403a66c51d7d30e/Capture.PNG)
The current spinlock in iMSTK is TasSpinLock. The bets spinlock implementation (from the link above and from the benchmark) is ExpBoRelaxTTasSpinLock. However, it need to be compiled under MSVC 2015 and up.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/230Remove cyclic dependencies in imstk libraries2019-09-07T19:22:39-04:00Sreekanth ArikatlaRemove cyclic dependencies in imstk libraries![graphviz](/uploads/ad7946f7c08d8bed1c2c800721085f3b/graphviz.png)![graphviz](/uploads/ad7946f7c08d8bed1c2c800721085f3b/graphviz.png)https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/229Unit tests for narrow-phase collision detections2019-07-28T16:21:22-04:00Nghia TruongUnit tests for narrow-phase collision detectionsThe new implemented NarrowPhaseCD (narrow-phase collision detection) does not have unit tests!The new implemented NarrowPhaseCD (narrow-phase collision detection) does not have unit tests!https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/228PBD constraints are shared pointers, and they are re-created at every time step2020-04-29T13:49:08-04:00Nghia TruongPBD constraints are shared pointers, and they are re-created at every time stepPBD constraints are shared pointers, and they are re-created at every time step. This is very costly.PBD constraints are shared pointers, and they are re-created at every time step. This is very costly.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/227Follow-up from "ENH: Vulkan display modes"2019-07-05T14:27:32-04:00Sreekanth ArikatlaFollow-up from "ENH: Vulkan display modes"The following discussion from !335 should be addressed:
- [x] @sreekanth-arikatla started a [discussion](https://gitlab.kitware.com/iMSTK/iMSTK/merge_requests/335#note_590381): (+2 comments)
> @NickMilef, Can process all the optio...The following discussion from !335 should be addressed:
- [x] @sreekanth-arikatla started a [discussion](https://gitlab.kitware.com/iMSTK/iMSTK/merge_requests/335#note_590381): (+2 comments)
> @NickMilef, Can process all the options here? Meaning if any mode is not supported log a warning and default to nearest available mode.
>
> `enum DisplayMode
> {
> SURFACE,
> WIREFRAME,
> POINTS,
> WIREFRAME_SURFACE
> };`https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/226Vulkan missing POINTS and SURFACE_WIREFRAME display modes2019-07-05T12:38:51-04:00Nicholas MilefVulkan missing POINTS and SURFACE_WIREFRAME display modesNicholas MilefNicholas Milefhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/225Vulkan validation fails2021-06-01T16:50:57-04:00Nghia TruongVulkan validation failsMy computer cannot run the examples with Vulkan backend. Vulkan Info app crashes immediately without any error message. The GPU is GTX 1080 Ti. Here is the log from examples:
```
Starting viewer
Vulkan Renderer Information:
Enabled ext...My computer cannot run the examples with Vulkan backend. Vulkan Info app crashes immediately without any error message. The GPU is GTX 1080 Ti. Here is the log from examples:
```
Starting viewer
Vulkan Renderer Information:
Enabled extension: VK_KHR_surface
Enabled extension: VK_KHR_win32_surface
Enabled extension: VK_EXT_debug_report
Validation: [ VUID-VkDeviceQueueCreateInfo-queueFamilyIndex-00381 ] Object: 0x20034e37ee0 (Type = 2) | vkCreateDevice: pCreateInfo->pQueueCreateInfos[0].queueFamilyIndex (= 0) is not less than any previously obtained pQueueFamilyPropertyCount from vkGetPhysicalDeviceQueueFamilyProperties (the pQueueFamilyPropertyCount was never obtained). The Vulkan spec states: queueFamilyIndex must be less than pQueueFamilyPropertyCount returned by vkGetPhysicalDeviceQueueFamilyProperties (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-VkDeviceQueueCreateInfo-queueFamilyIndex-00381)
```https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/224Extend visual model to Debug geometry2021-01-08T17:22:52-05:00Sreekanth ArikatlaExtend visual model to Debug geometryCurrently, the debug geometry directly take the render material. Since the regular objects take visualModel instead and the renderer pipeline has been updated accordingly, the material properties are not applied properly to the debug geo...Currently, the debug geometry directly take the render material. Since the regular objects take visualModel instead and the renderer pipeline has been updated accordingly, the material properties are not applied properly to the debug geometry. Besides the `updateDataSource` other calls in the `VTKRenderDelegate::update` like
```
this->updateActorTransform();
this->updateActorProperties();
```
are not applied properlyhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/223List of platforms supported by iMSTK2021-07-12T12:05:32-04:00Nicholas MilefList of platforms supported by iMSTKI think we should have a list of platforms that iMSTK intends to support (Windows 7 and above, Ubuntu for Linux, etc.).I think we should have a list of platforms that iMSTK intends to support (Windows 7 and above, Ubuntu for Linux, etc.).