@@ -20,11 +20,47 @@ You will need the following things properly installed on your computer.
2020* ` npm install `
2121* ` bower install `
2222
23+ ### Install submodule dependencies
24+
25+ ``` bash
26+ cd lib
27+ git submodule init
28+ git submodule update
29+ ```
30+
31+ You may need to run the npm and bower install commands in ` lib/exp-player ` and ` lib/exp-models ` as well.
32+
2333## Running / Development
2434
35+ Setup instructions are broadly derived from those of the [ experimenter addon] ( https://github.com/CenterForOpenScience/experimenter/ ) .
36+ For most use cases, it should be possible to run against a remote installation of JamDB. The instructions below assume a staging server,
37+ ` https://staging-metadata.osf.io ` .
38+
39+ To login via OSF:
40+ * create .env file in top directory
41+ * in .env file include:
42+ * OSF_CLIENT_ID=\< client ID for staging account\>
43+ * OSF_SCOPE="osf.users.all_read"
44+ * OSF_URL="https://staging.osf.io "
45+ * OSF_AUTH_URL=https://staging-accounts.osf.io
46+ * JAMDB_URL=https://staging-metadata.osf.io
47+ * EXPERIMENT_ID=\< jam db document ID referencing the desired ISP study\>
48+
49+ * Find jam db document id at: https://staging-experimenter.osf.io/experiments/ (this is the EXPERIMENT_ID)
50+ * Create a new participant at https://staging-experimenter.osf.io/participants
51+ * Study ID: test
52+ * Participant ID: <look in the downloaded csv file >
53+
54+ Then run the ember application:
55+
2556* ` ember server `
2657* Visit your app at [ http://localhost:4200 ] ( http://localhost:4200 ) .
2758
59+ ### Trying an experiment
60+ Once the app is started, you will need to log in. Provide a study ID and participant ID.
61+ These are human readable strings as defined by the researchers, and are available on request (not committed to Github).
62+ There may be different study IDs to test conditions at different times of day.
63+
2864### Code Generators
2965
3066Make use of the many generators for code, try ` ember help generate ` for more details
0 commit comments