Issue with Vuetify slider interactor in Trame project deployed on AWS #260
-
Hi everyone, I'm currently working on a project that involves utilizing Trame on an AWS server. The deployment was done using the Trame Cookiecutter. The project incorporates a display section that showcases 3D medical image volumes for evaluation by specialists. To navigate through the image slices, we've implemented a Vuetify slider interactor. Initially, everything was functioning properly. However, we encountered an unexpected issue where the slider interactor ceased to work as intended. Currently, it only changes the slices when we click on the VTK's window, without transitioning through the slices. We suspect that this problem may be related to the VTK version. Our team has a Docker instance that was previously built, and in that instance, the transitions work fine. However, the new Docker instances no longer exhibit the expected behavior. We've noticed differences in the library versions between the new instances and the working one. Below, you'll find a comparison of the library versions: Based on this issue, I have two specific questions:
Bellow, I will provide a simplified version of our code. Thank you in advance for your assistance. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Simplified source code: main.py
ui.py
volumes.py
|
Beta Was this translation helpful? Give feedback.
-
Thanks for providing some code to test and track such issue. One way to fix and figure out which of the dependency introduce that behavior is to fix some of those dependencies. I would suggest to start by fixing Please keep us in the loop on what you find. Side note, are you sure you are not missing the |
Beta Was this translation helpful? Give feedback.
Thanks for providing some code to test and track such issue.
One way to fix and figure out which of the dependency introduce that behavior is to fix some of those dependencies.
I would suggest to start by fixing
trame-vtk==2.3.5
into that file of your repo and rebuild the server directory (you may have to delete that directory before rebuilding the full image)Please keep us in the loop on what you find.
Side note, are you sure you are not missing the
()
inctrl.volume_update
as that would do nothing if you don't execute the function.