iMSTK issueshttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues2017-07-03T15:39:10-04:00https://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.0https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/67Update parts of Wiki2018-11-12T11:40:16-05:00Sreekanth ArikatlaUpdate parts of WikiSome parts of the wiki are outdated and lean more towards discussions ratherSome parts of the wiki are outdated and lean more towards discussions ratherRelease 1.0.0https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/64Build failing on OSX2016-09-25T20:12:37-04:00Sean RadiganBuild failing on OSXSee the Dashboard here:
http://my.cdash.org/viewBuildError.php?buildid=917830
Relevant messages:
```
"imstk::ToolCoupler::ToolCoupler(std::__1::shared_ptr<imstk::DeviceInterface>)", referenced from:
std::__1::shared_ptr<...See the Dashboard here:
http://my.cdash.org/viewBuildError.php?buildid=917830
Relevant messages:
```
"imstk::ToolCoupler::ToolCoupler(std::__1::shared_ptr<imstk::DeviceInterface>)", referenced from:
std::__1::shared_ptr<imstk::ToolCoupler> std::__1::shared_ptr<imstk::ToolCoupler>::make_shared<std::__1::shared_ptr<imstk::VRPNForceDevice>&>(std::__1::shared_ptr<imstk::VRPNForceDevice>&&&) in SDK.cpp.o
"imstk::ToolCoupler::~ToolCoupler()", referenced from:
std::__1::__shared_ptr_emplace<imstk::ToolCoupler, std::__1::allocator<imstk::ToolCoupler> >::~__shared_ptr_emplace() in SDK.cpp.o
std::__1::__shared_ptr_emplace<imstk::ToolCoupler, std::__1::allocator<imstk::ToolCoupler> >::~__shared_ptr_emplace() in SDK.cpp.o
"imstk::DeviceInterface::~DeviceInterface()", referenced from:
std::__1::__shared_ptr_emplace<imstk::VRPNDeviceServer, std::__1::allocator<imstk::VRPNDeviceServer> >::~__shared_ptr_emplace() in SDK.cpp.o
std::__1::__shared_ptr_emplace<imstk::VRPNDeviceServer, std::__1::allocator<imstk::VRPNDeviceServer> >::~__shared_ptr_emplace() in SDK.cpp.o
"imstk::InitIODelegates()", referenced from:
imstk::SDK::initialize() in SDK.cpp.o
```
I believe the issue can be fixed by adding ```Devices``` and ```VirtualTools``` to the ```target_link_libraries(SimulationManager``` function.
I can't verify this on OSX though.
Here is a patch that I believe would solve this.
```diff
diff --git a/SimulationManager/CMakeLists.txt b/SimulationManager/CMakeLists.txt
index 254289c..4964437 100644
--- a/SimulationManager/CMakeLists.txt
+++ b/SimulationManager/CMakeLists.txt
@@ -29,11 +29,13 @@ imstk_add_library(SimulationManager
target_link_libraries(SimulationManager
PRIVATE
+ Assembler
Core
- Simulators
- Rendering
CollisionContext
- Assembler
+ Devices
+ Rendering
+ Simulators
+ VirtualTools
)
if(BUILD_TESTING)
```
Release 1.0.0Sean RadiganSean Radiganhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/54Better logging mechanism2017-06-30T12:29:35-04:00Sreekanth ArikatlaBetter logging mechanismSomething like:
http://www.codeproject.com/Articles/288827/g-log-An-efficient-asynchronous-logger-using-Cplus (Source: https://bitbucket.org/KjellKod/g2log)Something like:
http://www.codeproject.com/Articles/288827/g-log-An-efficient-asynchronous-logger-using-Cplus (Source: https://bitbucket.org/KjellKod/g2log)Release 1.0.0Nicholas MilefNicholas Milefhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/38VTK Rendering Issues2017-02-06T16:02:27-05:00Ricardo OrtizVTK Rendering IssuesThe VTK rendering engine has some issues with the update rates. It seems to be slow and jerky when interacting with the model (rotating, etc.).
@dcthomp Suggested that this could be an issue within the window interactor.The VTK rendering engine has some issues with the update rates. It seems to be slow and jerky when interacting with the model (rotating, etc.).
@dcthomp Suggested that this could be an issue within the window interactor.Release 1.0.0David ThompsonDavid Thompsonhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/22Standardize error handling across the framework2020-11-14T02:25:45-05:00Sreekanth ArikatlaStandardize error handling across the frameworkRelease 1.0.0https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/19Create a macro to export symbols when building library in windows.2020-11-14T02:25:45-05:00Sreekanth ArikatlaCreate a macro to export symbols when building library in windows.Release 1.0.0Ricardo OrtizRicardo Ortizhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/16clean up smVAO and smVBO2020-11-14T02:25:44-05:00Sreekanth Arikatlaclean up smVAO and smVBOAfter looking at smVAO, it looks like it was just smVBO, copied and then modified, as there are several member variables that aren't used, and at neamed/typed the same as in smVBO, most notably:
GLuint vboDataId;
GLuint vboIndexId;
...After looking at smVAO, it looks like it was just smVBO, copied and then modified, as there are several member variables that aren't used, and at neamed/typed the same as in smVBO, most notably:
GLuint vboDataId;
GLuint vboIndexId;
QHash<smInt, smInt> dataOffsetMap;
QHash<smInt, smInt> indexOffsetMap;
QHash<smInt, smInt> numberofVertices;
QHash<smInt, smInt> numberofTriangles;Release 1.0.0Sean RadiganSean Radiganhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/12Update rendering to use the latest OpenGL standard2020-11-14T02:25:44-05:00Sreekanth ArikatlaUpdate rendering to use the latest OpenGL standardThe code has many legacy OpenGL calls, this costs the framework rendering speed, causes confusion for users, and causes incompatibility with other libraries like Oculus (Oculus' SDK rendering changed, so no longer an issue)
1. This ta...The code has many legacy OpenGL calls, this costs the framework rendering speed, causes confusion for users, and causes incompatibility with other libraries like Oculus (Oculus' SDK rendering changed, so no longer an issue)
1. This task would greatly improve performance: Implement a VBO for storage of vertex data on the GPU for any rendered meshes (this might be just smSurfaceMeshes, not sure though).
2. Create default pass-through vertex and fragment shaders for objects that won't require custom shaders for rendering
3. Remove all fixed pipeline OpenGL code, and force a shader style rendering that takes MVP matricesRelease 1.0.0Sean RadiganSean Radiganhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/10Remove dependency on CUDA helper files in smSolvers2020-11-14T02:25:44-05:00Sreekanth ArikatlaRemove dependency on CUDA helper files in smSolversRelease 1.0.0https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/8Use size_t for all index type variables2020-11-14T02:25:44-05:00Sreekanth ArikatlaUse size_t for all index type variablesRelease 1.0.0Dženan ZukićDženan Zukićhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/7Add coding guidelines wiki page2020-11-14T02:25:44-05:00Sreekanth ArikatlaAdd coding guidelines wiki pageRelease 1.0.0Ricardo OrtizRicardo Ortizhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/5Enable the rest of the examples2020-11-14T02:25:44-05:00Sreekanth ArikatlaEnable the rest of the examplesRelease 1.0.0https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/3Documetation setup2020-11-14T02:25:44-05:00Sreekanth ArikatlaDocumetation setupRelease 1.0.0David ThompsonDavid Thompsonhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/2rename and repurpose DummySimulator2020-11-14T02:25:44-05:00Sreekanth Arikatlarename and repurpose DummySimulatorRelease 1.0.0https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/33Implement generic IO module2015-09-02T07:43:49-04:00Ricardo OrtizImplement generic IO moduleThis task splits from the vtk Rendering interface module. The need for creating a generic interface for reading VTK files,.stl,.obj and .veg as well as textures that can be loaded both by vtk engine as well as for the original engine.This task splits from the vtk Rendering interface module. The need for creating a generic interface for reading VTK files,.stl,.obj and .veg as well as textures that can be loaded both by vtk engine as well as for the original engine.Sprint IRicardo OrtizRicardo Ortizhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/27Re-Naming2020-11-14T02:25:46-05:00Ricardo OrtizRe-NamingDrop the sm prefix.
Restructure the directories so everything resides on the top directory.
+ Issue #2Drop the sm prefix.
Restructure the directories so everything resides on the top directory.
+ Issue #2Sprint IRicardo OrtizRicardo Ortizhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/25Implement New Rendering Interfaces2020-11-14T02:25:45-05:00Ricardo OrtizImplement New Rendering InterfacesImplement rendering interface to connect SimMedTK to the new rendering engine.
Implementation will depend on the rendering engine chosen but these are requirements on the design:
1. The design should abstract the interface so that m...Implement rendering interface to connect SimMedTK to the new rendering engine.
Implementation will depend on the rendering engine chosen but these are requirements on the design:
1. The design should abstract the interface so that most communication occurs at a higher levels in the hierarchy.
2. Should allow for external renderers to be plug in to the library.
Issues #4 and #12 come under this
Sprint IRicardo OrtizRicardo Ortizhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/20Standardize and enable phantom omni interface2020-11-14T02:25:45-05:00Sreekanth ArikatlaStandardize and enable phantom omni interfaceSprint ISean RadiganSean Radiganhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/222The code walk-through-example appears to be outdated.2020-12-08T10:20:43-05:00Sukhraj SinghThe code walk-through-example appears to be outdated.The walk-through example at: https://imstk.readthedocs.io/en/latest/documentation.html#walk-through-example appears to be outdated.
Further, why is it not part of examples, it looks like an interesting example.The walk-through example at: https://imstk.readthedocs.io/en/latest/documentation.html#walk-through-example appears to be outdated.
Further, why is it not part of examples, it looks like an interesting example.Release 2.0.0