Name: experimenter
Owner: Center for Open Science
Description: Admin interface for researchers using COS's behavioral data collection service
Created: 2016-01-25 14:53:05.0
Updated: 2017-10-04 17:03:58.0
Pushed: 2017-10-20 19:45:56.0
Homepage: http://experimenter.readthedocs.org/en/latest/
Size: 17747
Language: JavaScript
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
A platform to create and administer experiments.
Documentation available here
You will need the following things properly installed on your computer.
Experimenter is designed to talk to a JamDB server for all data storage. In most cases you will be provided a remote staging server for development purposes, but for advanced development, these setup scripts can help define a basic skeleton for your project.
git clone <repository-url>
this repositoryyarn install --pure-lockfile
bower install
To use the video capture facilities of Experimenter, you will also need to place the file VideoRecorder.swf
in your <project_name>/public/
folder. This file is not part of the git repository; it is from the HDFVR flash video
recorder and must be obtained from a team member with access to the licensed version. They can also provide the
necessary configuration to talk to a valid and licensed streaming media server (eg Wowza); see below.
ib
submodule init
submodule update
The exp-player and exp-models addons live in the lib directory. This is Ember's conventional place
for putting in-repo-addons (see package.json also). If you need to develop on either of the exp-*
addons, simply do your work in the submodule directory (lib/exp-
To login via OSF:
CLIENT_ID="\<client ID for staging account\>"
SCOPE="osf.users.profile_read"
URL="https://staging-accounts.osf.io"
RY_DSN=""
A_PHP='{}'
A_ASP='{}'
First:
yarn run bootstrap
This:
schemas/*.json
to validate records in the corresponding collections.dev/permissions.py
dev/data
. See dev/data/admins.json
for example logins; use:space=experimenter
ection=admins
name=<id>
word=password
Then:
ember server
Sometimes, you will want to install an additional third-party package. In place of npm, this project uses yarn
.
Most of the commands are the same, but this alternative tool
provides a way for two developers to guarantee they are using the same versions of underlying code. (by running
yarn install --pure-lockfile
) This can help avoid a situation where things break unexpectedly when run on a different
computer.
Whenever you choose to update your dependencies (yarn add x
or yarn install
), make sure that code still runs, then
be sure to commit the modified yarn.lock
file, which represents the “current
known working state” for your app.
Make use of the many generators for code, try ember help generate
for more details
ember test
ember test --server
ember build
(development)ember build --environment production
(production)Specify what it takes to deploy your app.
Want to help save science? Want to get paid to develop free, open source software? Check out our openings!