Skip to content
This repository has been archived by the owner on Oct 6, 2023. It is now read-only.

Windows and Docker both output an invalid image #8

Open
1 of 3 tasks
Karelger opened this issue Apr 1, 2019 · 5 comments
Open
1 of 3 tasks

Windows and Docker both output an invalid image #8

Karelger opened this issue Apr 1, 2019 · 5 comments
Assignees

Comments

@Karelger
Copy link
Contributor

Karelger commented Apr 1, 2019

Currently both the Windows binary and the Dockerized instance output an unreadable image. This is likely due to incorrect DLL's or linking.

  • Determine cause
  • Implement fix
  • Release updated version
@Karelger Karelger self-assigned this Apr 1, 2019
@Karelger
Copy link
Contributor Author

Compression method doesn't seem to impact the created image.

@Karelger
Copy link
Contributor Author

Applying the LUT table also doesn't impact the incorrectly created image. Though the LUT application does require optimizations.

Karelger added a commit that referenced this issue Apr 19, 2019
Karelger added a commit that referenced this issue Apr 19, 2019
@Karelger
Copy link
Contributor Author

Karelger commented May 7, 2019

The issue is indeed caused by incorrect DLL's. The compiled version of the MultiResolutionInterface doesn't seem to be complete or correct, as it differs heavily from the one supplied by the most recent ASAP release.

@sebastianffx
Copy link

We have the same issue of obtaining an invalid image as output, both with the container version and by compiling WSICS from the sources in Ubuntu 18.04 using the latest ASAP release.

@AGFoersch
Copy link

Has this been adressed? Is there a way to fix this? Unfortunately, I also cannot open the output images. I'm in dire need of a method to normalize WSIs and I thought I had finally found a solution.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants