Skip to content

Latest commit

 

History

History
167 lines (107 loc) · 7.69 KB

README.md

File metadata and controls

167 lines (107 loc) · 7.69 KB
Raw

WebSceneStudio

Installation / Setup (local development)

  1. Get Ruby on Rails if not already installed (http://railsinstaller.org/en for Windows or Mac OS, or follow https://www.digitalocean.com/community/articles/how-to-install-ruby-on-rails-on-ubuntu-12-04-lts-precise-pangolin-with-rvm for Ubuntu/Linux)

  2. clone this repository onto your machine

  3. get a copy of the config/config.yml file from your teammates or look at the config/example.config.yml file for some directions on how to create your own from scratch. The values in this file are secrets, so you ABSOLUTELY don't want to put this file under version control or make it publicly available. For development purposes, set HOST_BASE_URL to localhost:3000. For running on MTurk, make sure the HOST_BASE_URL starts with https: and that you have a proper SSL certificate for your server.

  4. run bundle install to get all the ruby gems you need. If you have problems running bundle install, try removing your Gemfile.lock.

  5. run rake db:migrate to build/update the database

  6. run rails server to start an instance of the server running at localhost:3000. Point your browser here to visit the app.

Deployment (Apache + Passenger)

  1. Follow steps 1 - 5 as above (more convenient if checkout is through https and into a shared folder such as /home/shared)

  2. make sure the checked out repository has permissions allowing access by apache process (ensure group ownership is set to www-pub)

  3. create symlink in active apache DocumentRoot path (usually /var/www/) pointing to the SceneStudio/public directory

  4. install Phusion Passenger: gem install passenger (documentation)

  5. install passenger module for Apache: passenger-install-apache2-module and follow directions to modify apache files

  6. add a block of the following form into the active Apache site virtual host (currently /etc/apache2/sites-available/default):

    RackBaseURI /scenestudio
RackEnv production
PassengerAppRoot /path/to/SceneStudio/
<Directory /var/www/scenestudio>
 	Options -MultiViews
</Directory>
# Proxy for solr used by SceneStudio
ProxyPass /scenestudio/solr http://localhost:8983/solr
ProxyPassReverse /scenestudio/solr http://localhost:8983/solr

  7. Before running in the production environment, make sure to precompile assets through:

    RAILS_RELATIVE_URL_ROOT="/scenestudio" bundle exec rake assets:clean
RAILS_RELATIVE_URL_ROOT="/scenestudio" bundle exec rake assets:precompile

  8. Restart apache server using sudo service apache2 restart

How to create a new Mechanical Turk Experiment/Task and Manage It

The following assumes that we are running in development mode on a local machine.

  1. run rails generate experiment sampleName to generate some skeleton files. The skeleton files will be usable out of the box, so try that first.

  2. Take a look at the generated skeleton and get a feel for what everything does. Make sure to update the config/experiments/sampleName.yml with your configuration.

  3. run rake mturk:develop[sampleName] to create the database entries for the experiment and run the setup script. You can develop locally by providing a param to the appropriate address (e.g. mturk/task?assignmentId=xxx&workerId=yyy&hitId=sampleName or experiments/sampleName?task_id=7)

  4. run rake mturk:run[sampleName] in order to launch the experiment you just created on the MTurk sandbox.

  5. go to the worker sandbox (https://workersandbox.mturk.com/) and try doing your new task. You can switch to posting real HITs by flipping the sandbox boolean in config/initializers/rturk.rb -- make sure everything works out before doing this and remember to return back to sandbox mode after finishing with your task.

  6. After running a task, you can do rake mturk:recall[sampleName] to approve all workers and withdraw the task from Amazon Mturk. WARNING: This will remove all evidence of the hit from Amazon as well make it hard to adjust payment for Turkers. The data tables for the task is retains so your results are still there. For development, you may want to wipe out those tables too. To do so, you can do rake mturk:destroy[sampleName] to completely destroy all evidence of having run the experiment. WARNING: If you do this in production you will lose all your experiment data. This is a bad idea, and will make it hard/impossible to audit yourself later.

  7. When you're done playing around, make sure to get rid of all these junky template files for the sampleName task by running rails destroy experiment sampleName

  8. Now go ahead and create an experiment with an actual name!

  9. For more experiment management commands run rake --tasks or look at the lib/tasks/mturk.rake file

Existing Mechanical Turk Tasks

We currently have the following mechanical turk tasks. You can find which tasks you have in your database by going to mturk/tasks. In production mode, in order to manage the mturk tasks from the web interface, you will need to make sure that you are logged in and that the user's role is "mturk" (you can run rake mturk:allow[user's name] to give a user access to the mturk role. In development mode, there is a link to test your task.

desc2scene

Ask users to create a scene based on a textual description.

After running task, go to experiments/desc2scene/results to view results.

image2scene

Ask users to create a scene based on a image.

After running task, go to experiments/image2scene/results to view results.

rate_scene

Ask users to rate how well an image of a scene matches a description.

After running task, go to experiments/rate_scene/results to view results.

recon2scene (not working)

Ask users to create a scene based on a scanned reconstruction.

After running task, go to experiments/recon2scene/results to view results.

scene2desc

Ask users to provide a textual description of a scene.

After running task, go to experiments/scene2desc/results to view results.

image2desc

Ask users to provide a textual description of a image.

After running task, go to experiments/image2desc/results to view results.

enrich_scene (need refinement)

Ask users to enrich an existing scene by placing additional items to the scene.

After running task, go to experiments/enrich_scene/results to view results.

select_view

Ask users to select a BEST and a WORST view for a scene.

After running task, go to experiments/select_view/results to view results.

Troubleshooting

Problem setting up a new server

  • Error during bundle install.

    Try removing your Gemfile.lock

  • SSL error during bundle install

    Gem::RemoteFetcher::FetchError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B

    Try modifying Gemfile to use http instead of https source 'http://rubygems.org' See http://railsapps.github.io/openssl-certificate-verify-failed.html

  • Error precompiling assets.

    Check that your ruby version is ruby-1.9.3.
    Use rvm to manage and install ruby-1.9.3.

  • You just set up a new server, and everything should be working, but you get "The page you were looking for doesn't exist."

    If you have been testing with a different instance, try a different browser or incognito mode. You were probably logged in, and the new server doesn't know about that user. If incognito mode works, create a user and login.

Tools