FNNDSC / FNNDSC/ami

Error when loading DICOM images, image with noise when using Arch Linux

Open
#277 9 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
JavaScript
Stars
745
Forks
212
PR merge metrics
No merged PRs in 30d

Description

Hi,

I'm using AMI.js with OHIF Viewer, and it was working fine in Ubuntu, but when I'm using Arch Linux, every image loaded came with some noise (see Figure 1), then I zoomed to see what is this noise, and discover that is like the image has been sliced in many rows, and between this rows there a space (Figure 2). The Figure is from lesson 1 example.

Figure 1
![fig1](https://user-images.githubusercontent.com/14366202/39138162-b668e660-46f5-11e8-8765-14ebf1dedc24.png)

Figure 2
![fig2](https://user-images.githubusercontent.com/14366202/39138163-b6903134-46f5-11e8-8290-58cdc87f31a2.png)

About the machine:
I'm using an Intel i7, 8Gb of RAM, Google Chrome version 66 and Firefox 59 (both presented the same issue). When I run the script `$uname -a` I get:
`Linux Schaefer 4.16.3-1-ARCH #1 SMP PREEMPT Thu Apr 19 09:17:56 UTC 2018 x86_64 GNU/Linux`

I believed that was an error with the three.js lib, but I can't reproduce the error with their examples, so I decided to post it here to see if I get some possible cause of this error.

Thank you,
Murilo Schaefer

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the lesson 1 example, where the reported rendering artifact appears, and compare its DICOM image loading and display on Arch Linux with Ubuntu. Use the supplied browser and system details to reproduce the noise and row gaps; done means the image renders without those artifacts or the cause is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, three.js
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.