Enable server to handle multiple clients and multiple experiments per client
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or entry points. First map the server's client and experiment lifecycle, then determine how multiple clients and sequential experiments should coexist. Done means the server can support multiple clients, let each run multiple experiments without restarting, and enable parallel studies.
Written by the indexing model from the issue text.
Description
Currently the server can only communicate with one client and a time, and that client can only run one experiment before having to restart the server. Allowing the server to handle multiple clients and gracefully transition between experiments would make it easier for users to scale up their research by running multiple studies in parallel. This functionality could also enable the use of hierarchical modeling strategies.
- Dominant language
- HTML
- Stars
- 75
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from facebookresearch/aepsych
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
facebookresearch/aepsych#379 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
facebookresearch/aepsych#369 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
facebookresearch/aepsych#368 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
facebookresearch/aepsych#367 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
facebookresearch/aepsych#195 ·
All issues in facebookresearch/aepsych
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
micromatch/picomatch#243 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yetone/magpie#4095 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug]: Guest messages near the 4,000-char limit fail with 400 "The request was not valid." because multipart turns \n into \r\nPossibly taken @juliusmarminge claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day