-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read properties of undefined (reading 'graphicType') #256
Comments
@imedia3 can you share the console logs of and right before the error occurs? |
@imedia3 if you could share a couple of sample studies where this happens it would also be very helpful. |
@imedia3 unfortunately, the resources we have available for maintenance of Slim are very limited right now. The only project that is funding Slim maintenance at this time is Imaging Data Commons, where the main use case is support of visualization of images and annotations hosted via Google Healthcare DICOMweb implementation. Creation of annotations is not a feature we are actively using or maintaining at this time. We are actively looking for opportunities to secure resources to allow us to do more. We can spend only minimal time trying to investigate this issue, and @pedrokohler did that. You are welcome to contribute to Slim by submitting a PR if you manage to identify and address the underlying issue. |
Getting errors when trying to Draw ROI's:
What's Been Done:
git clone https://github.com/ImagingDataCommons/slim/ slim && cd slim
Connected to Orthanc/DICOMweb in
public/configs/local.js
Started the application with:
docker compose up -d --build
ORyarn start
Accessed the Web UI, opened a study (any), and attempted to draw an ROI.
Result: The UI crashed with multiple pop-up errors.
Example:
Is it a Bug, or we do wrong something? Few days ago it was working fine and I was able to draw ROIs (actually I had problems before some fixes on Nginx reverse-proxy for Orthanc side, but now without any changes it's stopped to work
The text was updated successfully, but these errors were encountered: