CamiTK Community Edition issueshttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues2024-02-23T11:13:30+01:00https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/117Update upstream-ci/master in order to fix package build2024-02-23T11:13:30+01:00Emmanuel PromayonUpdate upstream-ci/master in order to fix package build## About you
CamiTK dev & maintainer
## Overview
## Steps to Reproduce
See error for instance in Job [#187192](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/187192) failed for f1e1a157f156667c4c74908c54343597739b4...## About you
CamiTK dev & maintainer
## Overview
## Steps to Reproduce
See error for instance in Job [#187192](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/187192) failed for f1e1a157f156667c4c74908c54343597739b4412:
## Actual VS Expected Result
no package build vs debian unstable package are build
## Relevant logs and/or screenshots
See error for instance in Job [#187192](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/187192) failed for f1e1a157f156667c4c74908c54343597739b4412:
## Interpretation & Possible fixes
- Check lintian message
- Check d/r
It seems the first time the package build failed was after !156 was merged, see #109
## CamiTK Version
Current development as of 23 dec 2020
## Latest info
As of 1 feb 2021
Job [#197871](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/197871) failed for 45108ed033f366a2c065e14aae61c1fd7c83255b:
The package was not generated, please check the artifacts and fix the problem:
- summary: https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/197871/artifacts/raw/packaging-debian-unstable-develop/log/summary.log
- check environment: https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/197871/artifacts/raw/packaging-debian-unstable-develop/log/check-environment.log
- build package: https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/197871/artifacts/raw/packaging-debian-unstable-develop/log/build-package.log
- prepare package environment: https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/197871/artifacts/raw/packaging-debian-unstable-develop/log/prepare-package-environment.log
---
**please do not remove anything below this line**CamiTK 5Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/115Pipeline does not detect failed tests2020-11-22T10:07:31+01:00Emmanuel PromayonPipeline does not detect failed tests## About you
CamiTK developer
## Overview
The action state machine tests failed, tests are sometimes reran, but the errors are not detected by the test script.
The pipeline does not fail although it should clearly fail. We are lull to ...## About you
CamiTK developer
## Overview
The action state machine tests failed, tests are sometimes reran, but the errors are not detected by the test script.
The pipeline does not fail although it should clearly fail. We are lull to a false sense of security, while there is a bug!
The two Linux configuration shows different logs but both do not detect the error
## Steps to Reproduce
- For linux stable: check [Job #177308](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/177308)
- For linux LTS: check [Job #177309](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/177309)
## Actual VS Expected Result
The pipeline should fail when there is a failed test, independently of the type of failure.
## Relevant logs and/or screenshots
### On Linux stable
In the [Job #177308](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/177308) log,
the initial tests failed with:
```
4/5 Test #132: application-actionstatemachine-5 .........Child aborted***Exception: 2.81 sec
5/5 Test #131: application-actionstatemachine-4 .........***Timeout 1800.13 sec
```
But then at the end of the job log we have:
```
===== Fatal errors =====
Found fatal error in /builds/CamiTK/CamiTK/debian-stable-develop/log/ci-test.log
===== Failed tests =====
===== Re-running failed tests =====
Re-ran tests OK
```
The relevant lines in the test.log show:
```
132: X Error of failed request: BadWindow (invalid Window parameter)
132: Major opcode of failed request: 2 (X_ChangeWindowAttributes)
132: Resource id in failed request: 0x2
132: Serial number of failed request: 7
132: Current serial number in output stream: 9
132: terminate called after throwing an instance of 'std::bad_array_new_length'
132: what(): std::bad_array_new_length
4/5 Test #132: application-actionstatemachine-5 .........Child aborted***Exception: 2.81 sec
5/5 Test #131: application-actionstatemachine-4 .........***Timeout 1800.13 sec
```
The rerun-test.log contains only one line:
```
Checking /builds/CamiTK/CamiTK/debian-stable-develop/log/test.log for failed test
```
### On Linux LTS
In the [Job #177309](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/177309) log,
the initial tests failed with:
```
4/5 Test #131: application-actionstatemachine-4 .........Child aborted***Exception: 0.71 sec
5/5 Test #132: application-actionstatemachine-5 .........***Timeout 1800.13 sec
```
But then at the end of the job log we have:
```
===== Fatal errors =====
Found fatal error in /builds/CamiTK/CamiTK/ubuntu-lts-develop/log/ci-test.log
===== Failed tests =====
===== Re-running failed tests =====
Re-ran tests OK
```
The relevant lines in the test.log show:
```
131: ...
131: X Error of failed request: BadWindow (invalid Window parameter)
131: Major opcode of failed request: 2 (X_ChangeWindowAttributes)
131: Resource id in failed request: 0x2
131: Serial number of failed request: 7
131: Current serial number in output stream: 9
131: terminate called after throwing an instance of 'std::bad_alloc'
131: what(): std::bad_alloc
4/5 Test #131: application-actionstatemachine-4 .........Child aborted***Exception: 0.71 sec
5/5 Test #132: application-actionstatemachine-5 .........***Timeout 1800.13 sec
```
The rerun-test.log contains only one line:
```
Checking /builds/CamiTK/CamiTK/ubuntu-lts-develop/log/test.log for failed test
```
## Interpretation & Possible fixes
The test script is faulty, see `.gitlab/test.sh`.
It should be better at parsing the log to detect problems
## CamiTK Version
CamiTK 4.2.dev.develop.92087062
Compiled using git Hash: 92087062bc6533f58297c18826f5256436b37807, Date: Tue Oct 20 00:24:15 2020 +0200.CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/114Failed test in action state machine2020-11-25T01:00:51+01:00Emmanuel PromayonFailed test in action state machine## About you
CamiTK developer
## Overview
Job [#178103](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/178103) failed for 92087062bc6533f58297c18826f5256436b37807
- The new action state machine test generates a bug, ...## About you
CamiTK developer
## Overview
Job [#178103](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/178103) failed for 92087062bc6533f58297c18826f5256436b37807
- The new action state machine test generates a bug, see
## Steps to Reproduce
Just check the pipeline.
On Linux (Job [#178103](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/178103)):
```
132: X Error of failed request: BadWindow (invalid Window parameter)
132: Major opcode of failed request: 2 (X_ChangeWindowAttributes)
132: Resource id in failed request: 0x2
132: Serial number of failed request: 7
132: Current serial number in output stream: 9
132: QObject::disconnect: Unexpected null parameter
```
On Windows (Job [#175675](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/175675)):
```
131: 2020-11-10 05:27:09.600 [TRACE ] Application "camitk-actionstatemachine" - Logging in C:/builds/win10-develop/sdk/applications/actionstatemachine/2020-11-10T05-27-09
131: 2020-11-10 05:27:10.760 [ERROR ] Application "camitk-actionstatemachine" - Caught an unknown exception
131: C:/builds/win10-develop/bin/camitk-actionstatemachine-debug.exe aborted...
131: Unknown Exception
1/1 Test #131: application-actionstatemachine-4 ...***Exception: SegFault 6.90 sec
```
(there is also another bug in this job, as the error is not considered failed by the pipeline)
## Actual VS Expected Result
Should not failed
## Relevant logs and/or screenshots
See related jobs
## CamiTK Version
CamiTK 4.2.dev.develop.92087062
Compiled using git Hash: 92087062bc6533f58297c18826f5256436b37807, Date: Tue Oct 20 00:24:15 2020 +0200.
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/111Camitk-imp crash when "Application-Close" on a component.2020-08-28T18:24:28+02:00Sylvain GuyCamitk-imp crash when "Application-Close" on a component.## About you
Developer of a CEP
## Overview
Applying "Application-Close" on a camitk component results sometimes in a crash. It doesn't seem to be deterministic. It may crash on the load or close.
## Steps to Reproduce
File- Open - "...## About you
Developer of a CEP
## Overview
Applying "Application-Close" on a camitk component results sometimes in a crash. It doesn't seem to be deterministic. It may crash on the load or close.
## Steps to Reproduce
File- Open - "brain.mha". Right click on "brain" -Application - Close.
If it doesn't crash direclty, reload brain.mha and close again. It will end up crashing on the loading or the closing.
## Relevant logs and/or screenshots
**Crash on the loading (after 2 load close)**
```
*** Program received signal SIGSEGV (Segmentation fault) ***
#0 tcache_get (tc_idx=<optimized out>) at malloc.c:2937
#1 __GI___libc_malloc (bytes=24) at malloc.c:3051
#2 0x00007f63c3d21c29 in operator new(unsigned long) () at /lib/x86_64-linux-gnu/libstdc++.so.6
#3 0x00007f63c2c32604 in vtkTransformConcatenationStack::New() () at /tmp/dependencies/VTK-6.3.0/Common/Transforms/vtkAbstractTransform.h:402
#4 0x00007f63c2c3284f in vtkTransform::Push() (this=0x562eaca5c000) at /tmp/dependencies/VTK-6.3.0/Common/Transforms/vtkTransform.h:280
#5 0x00007f63c2d30923 in vtkAssemblyPath::AddNode(vtkAssemblyNode*) (this=0x562eacca10d0, n=0x562eadc89e90) at /tmp/dependencies/VTK-6.3.0/Rendering/Core/vtkAssemblyPath.cxx:55
#6 0x00007f63c2d308d5 in vtkAssemblyPath::AddNode(vtkProp*, vtkMatrix4x4*) (this=0x562eacca10d0, p=0x562eac88cc70, m=0x562eacca42f0) at /tmp/dependencies/VTK-6.3.0/Rendering/Core/vtkAssemblyPath.cxx:45
#7 0x00007f63c2ccb2d2 in vtkProp3D::InitPathTraversal() (this=0x562eac88cc70) at /tmp/dependencies/VTK-6.3.0/Rendering/Core/vtkProp3D.cxx:600
#8 0x00007f63c5d6e71d in camitk::RendererWidget::addProp(vtkSmartPointer<vtkProp>, bool) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#9 0x00007f63c5d55202 in camitk::InteractiveViewer::addActor(camitk::Component*, vtkSmartPointer<vtkProp>) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#10 0x00007f63c5d54913 in camitk::InteractiveViewer::refresh(camitk::Viewer*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#11 0x00007f63c5d685a8 in camitk::InteractiveViewerFrame::showEvent(QShowEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#12 0x00007f63c56552b6 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f63c5702d52 in QFrame::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f63c5612a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f63c561c0f0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f63c5cd9428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#17 0x00007f63c4bfa93a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f63c5651c17 in QWidgetPrivate::show_helper() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007f63c5654d6b in QWidgetPrivate::setVisible(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007f63c5d73ba9 in camitk::Viewer::setVisible(bool) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#21 0x00007f63c5bb7793 in MedicalImageViewer::updateLayout() () at /home/guys/.config/CamiTK/lib/camitk-4.2/viewers/libmedicalimageviewer.so.4
#22 0x00007f63c5bb6043 in MedicalImageViewer::refresh(camitk::Viewer*) () at /home/guys/.config/CamiTK/lib/camitk-4.2/viewers/libmedicalimageviewer.so.4
#23 0x00007f63c5ceda2f in camitk::MainWindow::refresh() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#24 0x0000562ea8d62f40 in ImpMainWindow::refresh() ()
#25 0x00007f63c5cd9c0b in camitk::Application::refresh() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#26 0x00007f63c5cda83b in camitk::Application::open(QString const&) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#27 0x00007f6373d0047f in OpenFile::apply() () at /home/guys/.config/CamiTK/lib/camitk-4.2/actions/libapplication.so.4.2.dev
#28 0x00007f63c5cd22b2 in camitk::Action::applyAndRegister() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#29 0x0000562ea8d6700f in ImpMainWindow::openRecentDocuments() ()
#30 0x0000562ea8d61e98 in ImpMainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) ()
#31 0x00007f63c4c26300 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x00007f63c560c3e6 in QAction::triggered(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#33 0x00007f63c560eaa2 in QAction::activate(QAction::ActionEvent) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#34 0x00007f63c5794d12 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#35 0x00007f63c579c4ae in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#36 0x00007f63c579d4d2 in QMenu::mouseReleaseEvent(QMouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#37 0x00007f63c56552b6 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#38 0x00007f63c579fadb in QMenu::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#39 0x00007f63c5612a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#40 0x00007f63c561c343 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#41 0x00007f63c5cd9428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#42 0x00007f63c4bfa93a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#43 0x00007f63c561b457 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#44 0x00007f63c5671ce4 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#45 0x00007f63c56741ec in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#46 0x00007f63c5612a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#47 0x00007f63c561c0f0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#48 0x00007f63c5cd9428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#49 0x00007f63c4bfa93a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#50 0x00007f63c4fe37d3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#51 0x00007f63c4fe510b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#52 0x00007f63c4fbf35b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#53 0x00007f63bcca432e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#54 0x00007f63c0d80fbd in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#55 0x00007f63c0d81240 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#56 0x00007f63c0d812e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#57 0x00007f63c4c52565 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#58 0x00007f63c4bf94db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#59 0x00007f63c4c01246 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#60 0x00007f63c5cd9bbe in camitk::Application::exec() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#61 0x0000562ea8d6c6d4 in main ()
```
**Crash after closing (after 2 load close)**
```
malloc_consolidate(): invalid chunk size
*** Program received signal SIGABRT (Aborted) ***
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007f7908e07859 in __GI_abort () at abort.c:79
#2 0x00007f7908e723ee in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f7908f9c285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#3 0x00007f7908e7a47c in malloc_printerr (str=str@entry=0x7f7908f9e278 "malloc_consolidate(): invalid chunk size") at malloc.c:5347
#4 0x00007f7908e7ac58 in malloc_consolidate (av=av@entry=0x7f78fc000020) at malloc.c:4477
#5 0x00007f7908e7c160 in _int_free (av=0x7f78fc000020, p=0x7f78fc01a460, have_lock=<optimized out>) at malloc.c:4400
#6 0x00007f7909fa8637 in QObject::~QObject() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007f7909f2ff3d in QItemSelectionModel::~QItemSelectionModel() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007f7909f9e01e in QObjectPrivate::deleteChildren() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x00007f790a9cac29 in QWidget::~QWidget() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007f790ac4735d in QTableView::~QTableView() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f790b098f0e in camitk::ImageComponent::~ImageComponent() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#12 0x00007f78bb094048 in VtkImageComponent::~VtkImageComponent() () at /home/guys/.config/CamiTK/lib/camitk-4.2/components/libvtkimage.so.4
#13 0x00007f78bb09409c in VtkImageComponent::~VtkImageComponent() () at /home/guys/.config/CamiTK/lib/camitk-4.2/components/libvtkimage.so.4
#14 0x00007f790b055eb7 in camitk::Application::close(camitk::Component*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#15 0x00007f78b90721f8 in CloseAction::apply() () at /home/guys/.config/CamiTK/lib/camitk-4.2/actions/libapplication.so.4.2.dev
#16 0x00007f790b04c2b2 in camitk::Action::applyAndRegister() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#17 0x00007f790b04c068 in camitk::Action::trigger(QWidget*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#18 0x00007f790b02eac3 in camitk::Action::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#19 0x00007f7909fa0300 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f790a9863e6 in QAction::triggered(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x00007f790a988aa2 in QAction::activate(QAction::ActionEvent) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x00007f790ab0ed12 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x00007f790ab164ae in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x00007f790ab174d2 in QMenu::mouseReleaseEvent(QMouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x00007f790a9cf2b6 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x00007f790ab19adb in QMenu::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x00007f790a98ca66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x00007f790a996343 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#29 0x00007f790b053428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#30 0x00007f7909f7493a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x00007f790a995457 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#32 0x00007f790a9ebce4 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#33 0x00007f790a9ee1ec in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#34 0x00007f790a98ca66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#35 0x00007f790a9960f0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#36 0x00007f790b053428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#37 0x00007f7909f7493a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#38 0x00007f790a35d7d3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#39 0x00007f790a35f10b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#40 0x00007f790a33935b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#41 0x00007f790201e32e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#42 0x00007f79060fafbd in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#43 0x00007f79060fb240 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#44 0x00007f79060fb2e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#45 0x00007f7909fcc565 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#46 0x00007f7909f734db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#47 0x00007f790ab140b1 in QMenu::exec(QPoint const&, QAction*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#48 0x00007f790af190bf in Explorer::rightButtonPressed(QPoint const&) () at /home/guys/.config/CamiTK/lib/camitk-4.2/viewers/libexplorer.so.4
#49 0x00007f790af169cc in Explorer::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /home/guys/.config/CamiTK/lib/camitk-4.2/viewers/libexplorer.so.4
#50 0x00007f7909fa0300 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#51 0x00007f790a9b52d9 in QWidget::customContextMenuRequested(QPoint const&) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#52 0x00007f790a9cff85 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#53 0x00007f790aa7cd52 in QFrame::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#54 0x00007f790ac01482 in QAbstractItemView::viewportEvent(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#55 0x00007f790ac6f62f in QTreeView::viewportEvent(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#56 0x00007f7909f7464b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#57 0x00007f790a98ca55 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#58 0x00007f790a996b93 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#59 0x00007f790b053428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#60 0x00007f7909f7493a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#61 0x00007f790a9eb94a in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#62 0x00007f790a9ee1ec in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#63 0x00007f790a98ca66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#64 0x00007f790a9960f0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#65 0x00007f790b053428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#66 0x00007f7909f7493a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#67 0x00007f790a35d7d3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#68 0x00007f790a35f10b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#69 0x00007f790a33935b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#70 0x00007f790201e32e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#71 0x00007f79060fafbd in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#72 0x00007f79060fb240 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#73 0x00007f79060fb2e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#74 0x00007f7909fcc565 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#75 0x00007f7909f734db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#76 0x00007f7909f7b246 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#77 0x00007f790b053bbe in camitk::Application::exec() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#78 0x000055ad5179f6d4 in main ()
```
## Interpretation & Possible fixes
At the beginning I thought it was the fault of the destructors of my component, but since the bug also appears with the basic component of CamiTK, I have no idea where the issue could come from.
## CamiTK Version
CamiTK 4.2.dev.develop.32c2e525
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/110Outdated documentation2021-01-18T17:29:51+01:00Theophile TiffetOutdated documentation## About you
Tiffet Théophile PhD student
## Product
Documentation for CamiTK
## Overview
Following the modification of the viewers, their doxygen documentation was not updated. Classes like PropertyExplorer, MedicalImageViewer and o...## About you
Tiffet Théophile PhD student
## Product
Documentation for CamiTK
## Overview
Following the modification of the viewers, their doxygen documentation was not updated. Classes like PropertyExplorer, MedicalImageViewer and others still are considered singleton with a getInstance static method in the documentation. This should be with the new way of refreshing them, getting access to them with the string you have to use.
A migration guide would also be welcome.
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/109Wrong installation directory for libraries2024-02-23T11:13:30+01:00Theophile TiffetWrong installation directory for libraries## About you
Tiffet Théophile PhD student
## Overview
Variable CMAKE_INSTALL_LIBDIR and CMAKE_INSTALL_BINDIR are no respected during install, which can lead to problems on some distribution.
## Interpretation & Possible fixes
The var...## About you
Tiffet Théophile PhD student
## Overview
Variable CMAKE_INSTALL_LIBDIR and CMAKE_INSTALL_BINDIR are no respected during install, which can lead to problems on some distribution.
## Interpretation & Possible fixes
The variables CMAKE_INSTALL_LIBDIR and CMAKE_INSTALL_BINDIR should be used instead of hard coded path.
## CamiTK Version
Last develop version (933bc0c2)
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/107wrong tag for debian packaging CI2020-07-12T17:30:19+02:00Emmanuel Promayonwrong tag for debian packaging CIJob [#154819](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/154819) failed for 933bc0c2568482881247687a45ccc27f9856a371:Job [#154819](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/154819) failed for 933bc0c2568482881247687a45ccc27f9856a371:Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/105Invisible VTK 3D widgets2020-07-09T21:29:06+02:00Emmanuel PromayonInvisible VTK 3D widgets## About you
CamiTK dev
## Overview
VTKWidgets not visible in 3D
## Steps to Reproduce
1. Open a mesh component file
2. Launch the Mesh Clipping action
3. Nothing vtk widget appears in 3D
## Actual VS Expected Result
There should...## About you
CamiTK dev
## Overview
VTKWidgets not visible in 3D
## Steps to Reproduce
1. Open a mesh component file
2. Launch the Mesh Clipping action
3. Nothing vtk widget appears in 3D
## Actual VS Expected Result
There should be a vtk widget to change the cutting plane
## Interpretation & Possible fixes
Check the action code, is the widget properly initialized
## CamiTK Version
CamiTK 4.2.dev.develop.04a1c024
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 2Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/102INTERACTIVEVIEWER_API undefined in RenderWidget.h2020-06-26T08:52:48+02:00Theophile TiffetINTERACTIVEVIEWER_API undefined in RenderWidget.h## About you
PhD student
## Problem
'INTERACTIVEVIEWER_API' is not defined in 'sdk/libraries/core/viewer/RenderWidget.h line 102 and 105. A quick search through files showed that it is not defined anywhere.
## Possible solution
Should...## About you
PhD student
## Problem
'INTERACTIVEVIEWER_API' is not defined in 'sdk/libraries/core/viewer/RenderWidget.h line 102 and 105. A quick search through files showed that it is not defined anywhere.
## Possible solution
Should it be CAMITK_API ?
## CamiTK Version
As of 15/06/2020, last version in the develop branch.
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 1Jean-Loup HaberbuschJean-Loup Haberbuschhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/98CMake code generation over viewer's extension targets2020-09-28T20:36:22+02:00Emmanuel PromayonCMake code generation over viewer's extension targets## About you
CamiTK dev
## Overview
If a component or action declares a dependency to a viewer extension, CMake generates an error during generation.
```bash
CMake Error in actions/testactions/CMakeLists.txt:
The dependency target ...## About you
CamiTK dev
## Overview
If a component or action declares a dependency to a viewer extension, CMake generates an error during generation.
```bash
CMake Error in actions/testactions/CMakeLists.txt:
The dependency target "viewer-medicalimageviewer" of target
"action-testactions_autogen" does not exist.
```
→ The viewer's extension targets are not exported properly and generate an error
## Steps to Reproduce
In an action `CMakeLists.txt`, add the following line inside the `camitk_extension` parameters:
```cmake
camitk_extension(ACTION_EXTENSION
...
NEEDS_VIEWER_EXTENSION medicalimageviewer
...
)
```
## Actual VS Expected Result
When running the CMake generation on the project, the following error is generated
```bash
CMake Error in actions/testactions/CMakeLists.txt:
The dependency target "viewer-medicalimageviewer" of target
"action-testactions_autogen" does not exist.
```
The target is not known by the CEP as it is not exported by CamiTK CE.
The expected result is a error free CMake generation
I created a specific branch and MR (see !147) with cepgenerator test files.
This can be considered as fixed when the test `application-cepgenerator-bash-test` in MR !147 returns no error.
To run the test :
- checkout branch `bug/target-export`
- configure and build
- run the corresponding test:
```bash
ctest -VV -R application-cepgenerator-bash-test
```
## Interpretation & Possible fixes
Two possible fixes:
- ~~either fix CamiTK CMake files so that extensions are exported~~
- ~~tweak the cepgenerator to add the following lines in the generated action `CMakeLists.txt` AND document the manual fix in the wiki.~~
```cmake
# Add this line in the action or component CMakeLists.txt, before the call to the camitk_extension macro
add_library(viewer-medicalimageviewer INTERFACE IMPORTED)
```
- ~~FindCamiTK.cmake includes these export lines~~
Note that a similar line has to be added from each added NEEDS_VIEWER_EXTENSION dependencies
## CamiTK Version
`CamiTK version........................... CamiTK 4.2.dev.bug-target-export.0cf6a8fa`
~"Track Debugging"CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/94Wizard generation problem2020-03-13T20:37:01+01:00Maxime CalkaWizard generation problem## About you
PHD Student and CamiTK developer
## Overview
Problem to generate CEP with wizard
## Steps to Reproduce
Try to create CEP with wizard
## Actual VS Expected Result
Seg fault during CEP creation vs Create CEP
## CamiTK V...## About you
PHD Student and CamiTK developer
## Overview
Problem to generate CEP with wizard
## Steps to Reproduce
Try to create CEP with wizard
## Actual VS Expected Result
Seg fault during CEP creation vs Create CEP
## CamiTK Version
[Copy/Paste the output of `camitk-config -b` CamiTK Version part ]
---
**please do not remove anything below this line**Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/88Problem Import DLL Windows2019-10-23T08:18:41+02:00Maxime CalkaProblem Import DLL Windows## About you
Developper on the Meniscare project.
## Overview
Problem to import functions of InteractiveViwerFrame, SliderSpinBoxWidget, SliderTextWidget.
## Steps to Reproduce
No step to reproduce
## Interpretation & Possible fixes...## About you
Developper on the Meniscare project.
## Overview
Problem to import functions of InteractiveViwerFrame, SliderSpinBoxWidget, SliderTextWidget.
## Steps to Reproduce
No step to reproduce
## Interpretation & Possible fixes
InteractiveViewerFrame.h
Actual:
class InteractiveViewerFrame : public QFrame {
public:
Expected:
class CAMITK_API InteractiveViewerFrame : public QFrame {
public:
SliderSpinBoxWidget.h
Actual:
class SliderSpinBoxWidget : public QWidget {
Q_OBJECT
Expected:
class CAMITK_API SliderSpinBoxWidget : public QWidget {
Q_OBJECT
SliderTextWidget.h
Actual:
class SliderTextWidget : public QWidget {
Q_OBJECT
Expected:
class CAMITK_API SliderTextWidget : public QWidget {
Q_OBJECT
## CamiTK Version
4.1
---
**please do not remove anything below this line**https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/85Bug install qtpropertybrowser debian2021-03-18T16:45:30+01:00Clement BeitoneBug install qtpropertybrowser debianOn linux if the package manager is used to install camitk, the package qtpropertybrowser is installed by default in /usr/include. In case of a manual compile / installation this package is installed in ${CAMITK_INCLUDE_DIR}/libraries/
...On linux if the package manager is used to install camitk, the package qtpropertybrowser is installed by default in /usr/include. In case of a manual compile / installation this package is installed in ${CAMITK_INCLUDE_DIR}/libraries/
The CamiTKConfig.cmake is not aware of this system path.
To fix this issue the variable `QTPROPERTYBROWSER_ROOT_INCLUDE_DIR` should be used in CamiTKConfig.cmake and added in:
`set(CAMITK_INCLUDE_DIRECTORIES...)`CamiTK 5https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/84Bug in refreshInterfaceNode in Explorer.cpp2019-05-30T10:04:25+02:00Matthias TummersBug in refreshInterfaceNode in Explorer.cppI am a CamiTK developer working on the FOCUS CEP
When Working with multiple components with parent/child relationships, Explorer::refreshInterfaceNode() will fail to remove all the components from the maps but effectively delete de the ...I am a CamiTK developer working on the FOCUS CEP
When Working with multiple components with parent/child relationships, Explorer::refreshInterfaceNode() will fail to remove all the components from the maps but effectively delete de the components. This leaves the Explorer with invalid references to components in its maps and will eventually cause a crash.
## CamiTK Version:
- CamiTK version........................... CamiTK 4.1.2
- CamiTK Short Version..................... camitk-4.1
- CamiTK SO NAME........................... 4
- Operating System......................... WIN32
- Build type............................... DEBUG
- QT Version............................... 5.6.1
- VTK Version.............................. 6.3.0
- Global Installation Directory [G]........ C:/dev/CamiTK/install
- Local Installation Directory [L]......... C:/Users/tummersm/AppData/Roaming/CamiTK
- Current Working Directory [W]............ C:/dev/CamiTK/install/bin
- Test Data Directory...................... C:/dev/CamiTK/install/share/camitk-4.1/testdata
- Component Extension Directories.......... C:/dev/CamiTK/install/lib/camitk-4.1/components
- Action Extension Directories............. C:/dev/CamiTK/install/lib/camitk-4.1/actions
- Number of Component Extensions........... 15 (locations: 15 global, 0 local, 0 in working directory, 0 manually installed by user)
- Number of File Extensions Supported...... 39
- Number of Action Extensions.............. 28 (locations: 28 global, 0 local, 0 in working directory, 0 manually installed by user)
- Number of Actions........................ 106
- Registered components:
- [G] Alias Wavefront OBJ Component...... obj
- [G] FocusImageComponentExtension....... fcs, fcs3
- [G] 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 Abort Component............ abort
- [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
- Registered actions:
- [G] Application Level Actions.......... 21 actions
- [G] AverageVoxelValuesExtension........ 1 actions
- [G] Basic Mesh Extension............... 9 actions
- [G] Basic Picking Tutorial............. 1 actions
- [G] Basic Topology..................... 2 actions
- [G] BoxVOIExtension.................... 1 actions
- [G] FocusActionExtension............... 1 actions
- [G] Frame Edition Extension............ 1 actions
- [G] ITK Filters........................ 14 actions
- [G] ITK Segmentation................... 3 actions
- [G] Image LUT.......................... 1 actions
- [G] ImageAcquisitionActionExtension.... 7 actions
- [G] MML................................ 2 actions
- [G] Mesh Point Data.................... 1 actions
- [G] Mesh Processing.................... 17 actions
- [G] Mesh Selection..................... 1 actions
- [G] MultiPickingExtension.............. 1 actions
- [G] PMLExploreExtension................ 2 actions
- [G] Pixel Color Changer................ 1 actions
- [G] PropertiesExtension................ 3 actions
- [G] Reconstruction..................... 1 actions
- [G] Reorient Image Extension........... 1 actions
- [G] ResampleExtension.................. 1 actions
- [G] Shaker Extension................... 3 actions
- [G] ShowIn3DExtension.................. 5 actions
- [G] Sleeping While Working............. 2 actions
- [G] VolumeRenderingExtension........... 1 actions
- [G] Vtk Widget Tutorial................ 2 actions
---
**please do not remove anything below this line**Matthias TummersMatthias Tummershttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/66Load mha rotation/translation in the proper order2023-07-20T13:09:48+02:00Emmanuel PromayonLoad mha rotation/translation in the proper order## About you
This was a bug submitted to the old bugzilla by Guillaume Custillon on 2016-03-17
## Overview
> When loading an mhd/mha image that contains some transformation, the translation (offset) is not handled correctly.
> Indeed...## About you
This was a bug submitted to the old bugzilla by Guillaume Custillon on 2016-03-17
## Overview
> When loading an mhd/mha image that contains some transformation, the translation (offset) is not handled correctly.
> Indeed, the rotation matrix should be applied and then the translation in the world frame. However, on CamiTK the rotation is applied, and then the translation in the rotated frame.
## Steps to Reproduce
> - Open imp and load the attached mha test image:
>
> [test_frame_image.mha](/uploads/f3a59f67822c289391ac36321be032af/test_frame_image.mha)
>
> It is a 2D image with a rotation of 45° around z axis and a translation of 10 mm on the x axis.
> - Display the world frame.
## Actual VS Expected Result
> - Observe the location of the image: the translation is not made on the x axis of the world frame, but on the x axis of > the rotated image frame.
## Relevant logs and/or screenshots:
## Interpretation & Possible fixes:
This is the answer given by @jaffarda on 2016-03-22
> Following is based on the test image provided by Guillaume.
>
> ***** The Bug, reworded ******
> According to the data in file:
> TransformMatrix (which contains rotation matrix of frame) is
> 0.707 -0.707 0 0.707 0.707 0 0 0 1
> and
> Offset (which contains translation of frame) is
> 10 0 0
>
> Opening this image with camiTK:
> rotation is OK
> translation become 7.07 7.07 0
>
> in other words, the translation is applied in rotated frame, but we expect it to be applied in world frame
>
> ***** suggested fix *****
>
> based on tests on this image,
>
> in ImageComponent.cpp (line 290), the line
> ```cpp
vtkMatrix4x4::Multiply4x4(rotationMatrix, initialTranslation->GetMatrix(), initialFrameMatrix);
> ```
> should become :
> ```cpp
> vtkMatrix4x4::Multiply4x4(initialTranslation->GetMatrix(), rotationMatrix, initialFrameMatrix);
> ```
>
> ***** WARNING *****
> This change in a core file should only be commit after deep tests on every thing it may impact.
## CamiTK Version:
This was submitted for CamiTK 3.5.0.svn but is still present in CamiTK 4.1.develophttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/65Unexpected image behaviors in Viewers2023-05-15T15:59:39+02:00Emmanuel PromayonUnexpected image behaviors in Viewers## About you
Bug filed on Bugzilla by @jaffarda on 2016-04-22
## Overview:
> when looking at an image in 2D viewer (axial for exemple)
> - pb1/ border voxels are only half-sized (both in 2D and in 3D)
> - pb2/ border...## About you
Bug filed on Bugzilla by @jaffarda on 2016-04-22
## Overview:
> when looking at an image in 2D viewer (axial for exemple)
> - pb1/ border voxels are only half-sized (both in 2D and in 3D)
> - pb2/ border box does not adjust to displayed image
> - pb3/ picking is not possible a all places inside pixels
> - pb4/ picking is possible outside the image
> - pb5/ picking actor (crossing bars are not always visible)
> attached images are very small in number of voxels for a better view
> provided:
> - testImage.bmp (the expected visble result)
> - testData.raw (raw file for 2D images)
> - testData3D.raw (raw file for 3D image)
> - test1.mhd ( image 5x5x1 black & white grid, spacing 10x10x1)
> - test2.mhd ( image 5x5x1 black & white grid, spacing 1x1x1)
> - test_3D.mhd ( image 5x5x5 black & white grid, spacing 1x1x1)
[testImages.zip](/uploads/dbdae0b5992f6f646f9f890d03bd277e/testImages.zip)
## Steps to Reproduce
> - step 1/ Load test1.mhd in camitk
> - step 2/ click on centralViewer and press I (to toogle off image interpolation)
> - step 3/ open axial viewer (ctrl + 2)
> - step 4/ Pick a point (ctrl + click) close to the middle of a pixel
> - step 5/ Pick a point (ctrl + click) close to the border of a pixel
> - step 6/ Pick a point (ctrl + click) close to the middle of a pixel but on the outside of the displayed image
> - step 7/ Load test2.mhd, open axial viewer, toogle off interpolation
> - step 8/ Pick a point (ctrl + click) close to the middle of a pixel
## Actual VS Expected Result
> - at step 2/ we see pb1 all the pixels are not the same size but they should
> - at step 3/ we see pb1 all the pixels are not the same size but they should
> - at step 3/ we see pb2 the border does not match the image but should
> - at step 5/ we see pb3 picking works close to centre of pixel but nowhere else
> picking should be available everwhere
> - at step 6/ we see pb4 it is possible to pick a point outside the image,
> it should not
> - at step 8/ we see pb5 when picking works (see with pb3) the actor (small lines) are not visible, it should
## Relevant logs and/or screenshots:
See [testImages.zip](/uploads/dbdae0b5992f6f646f9f890d03bd277e/testImages.zip)
## Interpretation & Possible fixes:
> - pb1/ maybe miss set of dimensions?
> - pb2/ probably linked to pb1 the boxing seems to be the good size if pixels were correctly displayed
> - pb3/ maybe bad use of pixel size?
> - pb4/ probably linked to pb1 the selection box should be in pixel if pb1
> - pb5/ no ideas
## CamiTK Version:
Filed for CamiTK 3.6, but confirmed still on 4.1.develophttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/62Manual threshold does not allow a threshold greater than 2552019-05-08T17:03:47+02:00Emmanuel PromayonManual threshold does not allow a threshold greater than 255## About you
This bug was submitted by @fouardc on bugzilla, on 2015-10-23
## Overview:
> While utilizing ITK Segmentation -> Manual Threshold Filter, it is not possible to choose a low threshold or a high threshold ...## About you
This bug was submitted by @fouardc on bugzilla, on 2015-10-23
## Overview:
> While utilizing ITK Segmentation -> Manual Threshold Filter, it is not possible to choose a low threshold or a high threshold higher than 255, or lower than 0.
> This raises no problem for medical images encoded on unsigned char, however, for other kind of images (for example CT Scanner generally encoded on signed short), higher threshold values or negative threshold value may come handy.
> -- C. Fouard
## Steps to Reproduce:
> Open an image not encode in unsigned char. For example:
> - open the sinus dicom in the examples data base
> - select this image in the explorer and choose to apply ITK Segmentation -> Manual Threshold Filter
> - try to set the lower threshold to -53 and the higher threshold to 455 (yes, why not, if my algorithm says so?)
> - it is not possible
## Actual VS Expected Result:
> The fact that it is not possible is ok for some images, but it would be nice for the user to be able to choose any lower and higher threshold within the range of the encoded type of the image.
## Relevant logs and/or screenshots:
[Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.]
## Interpretation & Possible fixes:
>It may come from the lines 63 and 64 of ManualThreshold.cpp :
>```cpp
> lowThresholdProperty->setAttribute("minimum", 0);
> lowThresholdProperty->setAttribute("maximum", 255);
>```
>and the lines 69 and 70 of the same file:
>```cpp
> highThresholdProperty->setAttribute("minimum", 0);
> highThresholdProperty->setAttribute("maximum", 255);
>```
>
>These 2 values 0, and 255 may not be encoded hardwire but may be declared as variables updated when a new image is set as input (an override of the getWidget method implementation may be needed) with the minimum and maximum value of the encoding type of the input image.
## CamiTK Version:
This was submitted for CamiTK 3.5.0.2135
But the bug is still present in version 4.0.x and 4.1.0.develop
---
**please do not remove anything below this line**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 Tacheauhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/33Save as STL2018-03-28T08:03:18+02:00Emmanuel PromayonSave as STLIt seems that `camitk-imp` does not show STL in save as dialog box.
`StlComponentExtension` should inherits from `MeshComponentExtension` not directly from `ComponentExtension`It seems that `camitk-imp` does not show STL in save as dialog box.
`StlComponentExtension` should inherits from `MeshComponentExtension` not directly from `ComponentExtension`Sprint 7Emmanuel PromayonEmmanuel Promayon