See our Experigen tutorial for more instructions: https://osf.io/5gsey/ Components of an Experigen task ------------------------------- All scripts and associated files (e.g., sound files) must be uploaded to online storage; we use AWS S3. Our folder structure on S3 is as follows: 1. Top level folder (testexperigen folder) 2. lib folder (testexperigen/_lib): Contains the guts of Experigen, available at http://becker.phonologist.org/experigen/) 3. Setup folder (testexperigen/setup) 4. Resources folder (testexperigen/resources) 5. Views folder (testexperigen/views) 6. Plugins folder (testexperigen/plugins) ## The index.html file ## - Located in top level testexperigen folder - Name of the file specifies the URL for each task (number at the end of the URL indicates which batch within a HIT, specified by the Batch column in the items spreadsheet) - Indicates the name of the design and settings file associated with the task. ## The settings.js file ## - Located in textexperigen/setup - Specifies the server to which results are written (databaseServer) - Specifies the URL for the task; there must be agreement between the settings file and the index file in this regard - Specifies an experimentName that must be updated if you re-post a HIT, or else you will overwrite previously collected data. - Indicates where to find the below-listed pieces of information: **items** (located in testexperigen/resources): the primary text file listing the trial items to be presented, plus any files listing other types of items such as practice trials or catch trials. You will need to upload a new items file or files for each experiment. Double-check that the first column is a column of unique values, e.g. filenames. Experigen will not run correctly if there are repeated values in the first column. Also check that all columns have unique names; duplicate column names will also cause Experigen errors. **views** (located in testexperigen/views): the .ejs files that specify the text that is presented at different points throughout the experiment. If you want to edit the text of an experiment, figure out which of the views files contains the text you are interested in and download/modify/reupload it. **sounds** (subfolders of testexperigen/resources): contains sound files for each type (test trials, catch trials, etc.). You will need to upload new sound files (and most likely generate new subfolders) for each experiment. **design.js file** (located in testexperigen/setup): The guts of the experiment; get someone with knowledge of javascript to help you with this. (One exception: if you have a design file that includes filler trials or catch trials and you want to eliminate that type of trial altogether, you can comment them out in the design file.)