Having trouble getting started..

[seandoyle]

Hi -

I can install the docker container and export DICOM images to it -but it's not clear to me how to install the viewer so that I can see them. Do I need to copy the viewer files to the docker instance? Or do these somehow run on my local machine which uses web services on doctor instance?

I'm running this on a Mac but I could run on a different OS if that made things simpler.

Thanks

Sean

[swederik]

Hi Sean

The Viewer(s) run on Meteor, so you'll need to install that if you don't have it already. You'll probably also need node.js and NPM to run the CORS proxy that's also included. You can run one of the viewers (either OHIFViewer or LesionTracker) by changing to their directory and running

./bin/localhostOrthanc.sh

You'll also need to change to the etc directory and run:

./setupLocalOrthanc.sh

You should run this after the Docker Orthanc instance is started. The script just checks the IP for Docker and sets up a proxy that will direct localhost traffic on 8042 to the docker IP, while adding "Access-Control-Allow-Origin" to the header.

After all that is working you can just point your browser to http://localhost:3000/

Oh, and there is some rudimentary documentation here: http://ohif.github.io/Viewers/

See: http://ohif.github.io/Viewers/Usage/index.html

Let me know if you have any problems.

[seandoyle]

Thanks - i’ve gotten much further but I’m still having an issue.

I can see the viewer and select the one study on the system - but when I click on it I get a 401: http://192.168.99.100:8042/wado?requestType=WADO&studyUID=1.2.840.113619.2.207.3596.11971688.22188.1190386386.467&seriesUID=1.2.276.0.45.45.2.51.3.84320313.20141010.12360428303&objectUID=1.2.276.0.45.45.2.51.4.84320313.20141010.12365429236&contentType=application%2Fdicom

If I enter the URL into the browser and enter the username/password that is in the config file I can download the DCM just fine.

This is what I have in the config file: { "dicomWeb" : { "endpoints": [ { "name": "Orthanc", "wadoUriRootNOTE" : "either this uri is not correct for wado-uri or wado-uri is not configured on orthanc currently", "wadoUriRoot" : "http://192.168.99.100:8042/wado", "qidoRoot": "http://192.168.99.100:8042/dicom-web", "wadoRoot": "http://192.168.99.100:8042/dicom-web", "qidoSupportsIncludeField": false, "imageRendering" : "wadouri", "requestOptions" : { "auth": "orthanc:orthanc", "logRequests" : true, "logResponses" : false, "logTiming" : true } } ] } }

Could there be a conflict between the domain of the URL I’m using to launch the viewer (localhost:3000) and the 192* address of the docker instance?

Thanks

Sean

On Jan 4, 2016, at 8:38 AM, Erik Ziegler notifications@github.com<mailto:notifications@github.com> wrote:

Meteor

The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.

[swederik]

The localhostOrthanc.json configuration file should not be using the IP from docker, it should just have http://localhost:8042/whatever.

That is what the node CORS proxy is for. You run it, and all connections that attempt to reach http://localhost:8042 are sent to the docker IP (http://192.168.99.100) for you. They are returned with the proper headers so you don't get errors in the browser from having different domains (since everything is using localhost).

[seandoyle]

Ah :-)

This makes complete sense - I was wondering where the magic remapping was happening. I was looking at the instructions on https://github.com/OHIF/Viewers and I didn’t see the page http://ohif.github.io/Viewers/Usage/index.html which shows how the CORS proxy is set up. It’s working now.

I had to make one change to a port number in localHostOrthanc.json: diff --git a/config/localhostOrthanc.json b/config/localhostOrthanc.json index 0097b2f..0ded25f 100644 --- a/config/localhostOrthanc.json +++ b/config/localhostOrthanc.json @@ -4,7 +4,7 @@ { "name": "Orthanc", "wadoUriRootNOTE" : "either this uri is not correct for wado-uri or wado-uri is not configured on orthanc currently",

• "wadoUriRoot" : "http://localhost:8043/wado",
• "wadoUriRoot" : "http://localhost:8042/wado", "qidoRoot": "http://localhost:8042/dicom-web", "wadoRoot": "http://localhost:8042/dicom-web", "qidoSupportsIncludeField": false,

Thanks!

Sean

On Jan 4, 2016, at 11:09 AM, Erik Ziegler notifications@github.com<mailto:notifications@github.com> wrote:

The localhostOrthanc.json configuration file should not be using the IP from docker, it should just have http://localhost:8042/whatever.

That is what the node CORS proxy is for. You run it, and all connections that attempt to reach http://localhost:8042 are sent to the docker IP (http://192.168.99.100http://192.168.99.100/) for you. They are returned with the proper headers so you don't get errors in the browser from having different domains (since everything is using localhost).

— Reply to this email directly or view it on GitHubhttps://github.com/OHIF/Viewers/issues/2#issuecomment-168719445.

The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.

[swederik]

Ah yep that's my fault. 8043 there is for when Orthanc is running outside of Docker. I'll fix that.

[aksg87]

I am also having trouble pulling images into OHIF viewer from the proxy server.

When I trace the setup scripts it seems like all of the specifications for the OHIF viewer to talk to the server is in the localhostOrthanc.json file. Do we need to change the wadoUriRoot port from 8043? It seems like this is the last piece of setup I need to have everything running properly -- please let me know if you have suggestions!

[swederik]

The proxy is now internal, so I'm going to close this. Reopen it if you run into issues.