mturk-issue-#96 #98
Merged
mturk-issue-#96 #98
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- align mturk branch w/ prolific branch - new section in config file for CR codes - completion page now displays completion codes
- remove vestigial code
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To address #96. In short, Cloudresearch is no longer using dynamic completion codes. Instead, they have switched to a static completion code system like Prolific.
To address this problem, I've made the MTurk branch more similar to the Prolific branch. The major changes were:
app.ini) file now accepts real and decoy codes (the latter is currently non-operational, as rejected participants are currently sent to the 1005 error).I've tested this branch for a recent experiment with @seanmallan, and it worked fine. Given that the MTurk branch is used less often than the Prolific branch, I am bypassing code review. If problems creep up, feel free to contact me (@szorowi1).