Kitware / visualizer

The ParaViewWeb Visualizer application which can be used standalone or as a component within another web context.
https://kitware.github.io/visualizer/
BSD 3-Clause "New" or "Revised" License
115 stars 28 forks source link

Unable to build on Linux #9

Closed tldv closed 8 years ago

tldv commented 8 years ago

Am running on an Amazon Linux AMI: NAME="Amazon Linux AMI" VERSION="2015.03" ID="amzn" ID_LIKE="rhel fedora" VERSION_ID="2015.03" PRETTY_NAME="Amazon Linux AMI 2015.03"

Running "npm install -g pvw-visualizer" yields

/usr/bin/Visualizer -> /usr/lib/node_modules/pvw-visualizer/bin/pvw-visualizer-cli.js

pvw-visualizer@1.0.11 postinstall /usr/lib/node_modules/pvw-visualizer fix-kw-web-suite || true sh: fix-kw-web-suite: command not found /usr/lib └── pvw-visualizer@1.0.11

jourdain commented 8 years ago

Did that break? Normally the " || true" is to prevent the script to fail. As this command should succeed only when developing.

jourdain commented 8 years ago

I've tried on OS X and I do get the message, but everything works as expected.

tldv commented 8 years ago

Okay. Maybe I'll wait until a user guide exists before I bother you again. Thanks.

jourdain commented 8 years ago

No problem, thanks for trying...

On EC2, you probably don't want/need to install the Visualizer via npm as you only need to serve via Apache the "dist" directory of that repo. But on a local system npm will provide an easy to use command line that will use an install version of ParaView.

While on a real system, you need a launcher and need to configure Apache for some WebSocket forwarding.

tldv commented 8 years ago

Okay thanks, I'll give that a shot. In the meantime, I'm anxious to be the guinea pig for any quick start guide for deployment on AWS EC2. Thanks.

jourdain commented 8 years ago

I think the first thing is to understand the pieces that ParaViewWeb needs (PV 4+) and then just replace the html/js code with the new one (at some point). For that you can still use ParaView 5 for the backend for both JS versions.

http://pvw.kitware.com/#!/guide/multi_user_setup

If you get the setup working with the current documentation, then migrating using the new "client" code base should be fairly easy.

Did you tried one of our public AMI already configured with ParaView 4.4 and Visualizer?

tldv commented 8 years ago

Thanks. If you have an AMI ID or some other identifier, that would be very useful. The AMI search comes up with nothing.

jourdain commented 8 years ago

Ok will do. I'll add a new page on paraviewweb with those IDs. And post back here with the link.

tldv commented 8 years ago

I tried using Paraview 5.0.1 for the backend, but Visualizer, in pvw-visualizer.py line 85, raised an ImportError: No module named web in line 85.

Looking in my 5.0.1 (EDIT: Windows 10 64bit) install, there doesn't seem to be a web module folder in \lib\paraview-5.0\site-packages\paraview\