-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
additional solo game configuration and integration with prolific #951
Open
sgfost
wants to merge
19
commits into
virtualcommons:main
Choose a base branch
from
sgfost:sologame-prolific
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
sgfost
force-pushed
the
sologame-prolific
branch
from
September 17, 2024 21:49
ee95892
to
0d01521
Compare
sgfost
force-pushed
the
sologame-prolific
branch
from
October 14, 2024 20:02
47f66c7
to
69c0b15
Compare
this allows for multiple configurations for the solo game (game params, treatment sets, event card sets) * add prolificId to User
TODO: define each of the event cards for the prolific configuration
* adjust starting sys health and resources for prolific configs to 15 and 10 respectively
add defaults to `SoloMarsEventCard` fields to cut down on unnecessary repetition
TODO: separate page, splash, gameover, etc..
TODO: implement the client flow in ProlificStudy.vue participants enter via /study/prolific url and a user account/participant record is set up for them. They are then redirected to a page that takes them through the process of completing the required games studyId in the /study/prolific params must match an existing study which can be created via the cli: npm run cli study create -i <studyId> -c <completionCode> -d <desc>
this requires rolling the treatment when the participant is created instead of when a game is built * swapped out two resource-affecting event cards to avoid conflict * squashed migrations
this is a more reliable way to keep track of the games that a participant played, using the User relation involves some guesswork
sgfost
force-pushed
the
sologame-prolific
branch
from
October 14, 2024 22:11
69c0b15
to
62cda36
Compare
Co-authored-by: Saachi Mota <[email protected]>
sgfost
force-pushed
the
sologame-prolific
branch
from
October 18, 2024 16:33
a66faae
to
61b5380
Compare
things went haywire without a hard refresh because events, treatment params, etc. remained the same object reference
This is mostly straightforward but seeing if you want to give any input here before merging @alee The qualtrics -> pom -> prolific trip seems to be working so we're going to shoot for a pilot study whenever $ hits the prolific account |
previously, system health would get subtracted at the start of each round after the first, which led to the last round acting as a freebie this maintains virtually the same gameplay and data recording, with the exception of the final round resolves virtualcommons#970
…eover If initialization was slow enough, the investment command could be queued before the round was fully set up, which caused compounding inconsistencies. We can use the canInvest flag to prevent this After moving system health deduction to the end of the round, the game would end before persisting the round if caused by the natural system health deduction. Now a persist cmd is queued up before the end cmd
relying on db defaults is problematic when changes are made
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.
multiple solo game configurations implemented with a game type identifier used to switch between different treatments, event sets, initial parameters, etc.
workflow:
prolific -> qualtrics -> portofmars.asu.edu/study/prolific (which redirects to a page that steps through the 2 games) -> back to prolific with a completion code
TODO:
participantId, paymentAmount
csv (can just copy paste from text box in admin page)BUG: treatment selection may not be random?resolves virtualcommons/planning#75