CamiTK Community Edition issueshttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues2023-10-26T16:58:56+02:00https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/167ITK Registration Action2023-10-26T16:58:56+02:00Celine FouardITK Registration Action| | |
|--|--|
| **As a** | CamiTK User / Student |
| **I would like to** | Use basic registration technics to align 2 images |
| **So that** | I could visualize registration results directly on CamiTK |
| **Epic/Topics** | Integrate ITK ...| | |
|--|--|
| **As a** | CamiTK User / Student |
| **I would like to** | Use basic registration technics to align 2 images |
| **So that** | I could visualize registration results directly on CamiTK |
| **Epic/Topics** | Integrate ITK Registration into CamiTK |
## Description / Overview
Select mandatory registration parameters on an Action interface. Apply registration
## Acceptance tests
[Please enter acceptance tests as TODOs. Acceptance test explains how to test that this issue is solved]
- [ ] [Test 1]
- [ ] [Test 2]
- [ ] [...]
## Track
[Please keep only one of the following label]
## Misc
- Automatic subscription of issue creator:
**If appropriate, do not forget to mark this issue as "confidential"** by checking the corresponding tick box belowCeline FouardCeline Fouardhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/36Interface Data2018-06-13T10:41:45+02:00Emmanuel PromayonInterface Data| | |
|--|--|
| **As a** | CEP developer |
| **I would like to** | add easily manipulate array of data (values, signals, vectors...) to any type of component (not MeshComponent nor ImageComponent) |
| **So that** | I can visualize/inter...| | |
|--|--|
| **As a** | CEP developer |
| **I would like to** | add easily manipulate array of data (values, signals, vectors...) to any type of component (not MeshComponent nor ImageComponent) |
| **So that** | I can visualize/interact data as colors on a mesh, as graph/curve |
| **Epic/Topics** | Interface Data |
## Description / Overview
The epic is called "Interface Data" or how to include 1D temporal signal in CamiTK.
This is a new facet for `Component` that enables storage, manipulation, visualization and interaction with/of array of data. The idea is to offer data abstraction and minimal default behaviour for signal and temporal values.
In the design stage, first check:
- Check the Pulse project to check how they store the signals
- Check the work done by Nico (see `incubator-local/respirm` CEP) in order to handle 1D signal and their representation using a dedicated viewer based on vtkChart library (and some action to process them). In particular check the viewer and the defined actions.
- Check open-source application that help manipulate data and display charts to deduce best practices
- Check for standard in signal processing data format and processing library (if any)
One idea would be to be able to use a python interface/shell/script in order to process the signal directly from a console...
## Hints
As for any creation of interface in CamiTK, this can be done following these steps:
- Create a new interface that add the management of a list of `vtkDataArray` in `Component`
- Create the corresponding helper class
- Create the corresponding viewer (using vtkChart and the possibility to add data as if it was a live physiological signal) and integrate it to camitk-imp
- Create another viewer to display data in a table/spreadsheet
- Take into account the fact that `MeshComponent` can project the data as colors
- move addPointData/addCellData in `InterfaceGeometry` or to the new `InterfaceData` interface (may be use an enum for `FREE`, `ATTACHED_TO_CELLS`, `ATTACHED_TO_POINTS` etc...
## Acceptance tests
- [ ] a new tutorial component that shows how to add/remove/show these data in the new viewer
- [ ] a new tutorial MeshComponent that shows how data can be displayed directly _on_ the mesh surface
- [ ] a new tutorial that shows generates random value based on a sinus function to show how update/acquisition can be done
## Track
/label ~"Track Technology Integration"https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/48External lib link issue for the release build under MVS2018-06-04T16:56:48+02:00Antoine TacheauExternal lib link issue for the release build under MVSAbout you:
Antoine Tacheau, user of CamiTK and developer of a CEP
Overview:
Link is not well define in cmake files regarding external libs
Steps to Reproduce:
Create a CEP that needs an exte...About you:
Antoine Tacheau, user of CamiTK and developer of a CEP
Overview:
Link is not well define in cmake files regarding external libs
Steps to Reproduce:
Create a CEP that needs an external lib
-> Build in debug
==> It works
-> Build in release
==> Missing links
Actual VS Expected Result:
A CEP should be 'buildable' in debug and release
Relevant logs and/or screenshots:
NA
Interpretation & Possible fixes:
Update lines "optimized ${EXTERNAL_LIBRARY}" to "optimized ${EXTERNAL_LIBRARY}.lib" in CamiTKLibrary.cmake, CamiTKExtension.cmake and may be in CamiTKApplication.cmake
CamiTK Version:
- CamiTK version......................... CamiTK 4.1.0.develop.99ad37ea
- CamiTK Short Version................... camitk-4.1
- CamiTK SO NAME......................... 4
- Operating System....................... WIN32
- Build type............................. RELEASE
- QT Version............................. 5.6.1
- VTK Version............................ 6.3.0
- CamiTK Global Installation Directory... C:/Users/tacheaua/AppData/Roaming/CamiTK
- User Installation Directory............ C:/Users/tacheaua/AppData/Roaming/CamiTK
- Current Working Directory.............. C:/Users/tacheaua
- Test Data Directory.................... C:/Users/tacheaua/AppData/Roaming/CamiTK/share/camitk-4.1/testdata
- Component Extension Directories........ C:/Users/tacheaua/AppData/Roaming/CamiTK/lib/camitk-4.1/components
- Action Extension Directories........... C:/Users/tacheaua/AppData/Roaming/CamiTK/lib/camitk-4.1/actions
- Number of Component Extensions......... 14 (locations: 13 global, 0 local, 0 in working directory, 1 by user)
- Number of File Extensions Supported.... 38
- Number of Action Extensions............ 27 (locations: 27 global, 0 local, 0 in working directory, 0 by user)
- Number of Actions...................... 104
- Registered components (G=Global, L=Local, W=Working, U=User):
- Alias Wavefront OBJ Component (obj) [G]
- ITK-US Cardio Vet Component Extension (mha, testus) [U]
- ItkImages Component (hdr, spr, gipl, pic, lsm, nrrd, hdr.gz, nii, nii.gz, img, img.gz) [G]
- MML Component (mml, scn) [G]
- Msh Component (msh) [G]
- Off Component (off) [G]
- PML Component (pml) [G]
- Pick Me Component (pickme) [G]
- STL Component (stl, STL) [G]
- Testing Mixed Component (mixed) [G]
- VRML 2 Component (vrml, wrl) [G]
- VTK Component (vtk) [G]
- vtkImages Component (jpg, png, tiff, tif, bmp, pbm, pgm, ppm, mhd, mha, raw) [G]
- DICOM (directory) [G]
- Registered actions (G=Global, L=Local, W=Working, U=User):
- Application Level Action Extension [G]: 20 actions ()
- AverageVoxelValuesExtension [G]: 1 actions ()
- Basic Mesh Extension [G]: 9 actions ()
- Basic Picking Tutorial [G]: 1 actions ()
- Basic Topology [G]: 2 actions ()
- BoxVOIExtension [G]: 1 actions ()
- Frame Edition Extension [G]: 1 actions ()
- ITK Filters [G]: 14 actions ()
- ITK Segmentation [G]: 3 actions ()
- Image LUT [G]: 1 actions ()
- ImageAcquisitionActionExtension [G]: 7 actions ()
- MML [G]: 2 actions ()
- Mesh Point Data [G]: 1 actions ()
- Mesh Processing [G]: 17 actions ()
- Mesh Selection [G]: 1 actions ()
- MultiPickingExtension [G]: 1 actions ()
- PMLExploreExtension [G]: 2 actions ()
- Pixel Color Changer [G]: 1 actions ()
- PropertiesExtension [G]: 3 actions ()
- Reconstruction [G]: 1 actions ()
- Reorient Image Extension [G]: 1 actions ()
- ResampleExtension [G]: 1 actions ()
- Shaker Extension [G]: 3 actions ()
- ShowIn3DExtension [G]: 5 actions ()
- Sleeping While Working [G]: 2 actions ()
- VolumeRenderingExtension [G]: 1 actions ()
- Vtk Widget Tutorial [G]: 2 actions ()Antoine TacheauAntoine Tacheau