-
Notifications
You must be signed in to change notification settings - Fork 0
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
results upload #6
Comments
this is an interesting one... we could actually use the results to connect to other tools we have developed to clone TCRs... i.e. go from sequence on the screen to DNA in a tube. These are also implemented in R, though a key part might run better in python... I'll think about this |
if we get the TCR manufacturing paper out, then we could use this to drive academic interest towards our solution |
Following today's discussion on uploading the results:
|
- runner creates two folders and uploads them as zipfiles - `/user_results`: provided to user - `/trusted_user_results`: provided to user if they have "full results" enabled by an admin - `/admin_results`: only visible to admins - admin results are always uploaded, included for failed runs (for debugging) - user results are only provided if the run was successful - add `PREDICTCR_RUNNER_SCRIPT_DIR` env var to docker compose to specify where script & model can be found - add /admin/result endpoint to download admin results zipfile - switch from micromamba to miniconda docker image - reticulate doesn't seem to support micromamba, at least within docker - re-enable runner docker image CI - update runner README.md - resolves #6 - resolves #43 Also refactor admin views using tabs
- runner creates three folders where the script runs, and uploads their contents as zipfiles: - `/user_results`: provided to user - `/trusted_user_results`: provided to user if they have "full results" enabled by an admin - `/admin_results`: only visible to admins - admin results are always uploaded, included for failed runs (for debugging) - user results are only provided if the run was successful - add `PREDICTCR_RUNNER_SCRIPT_DIR` env var to docker compose to specify where script & model can be found - add /admin/result endpoint to download admin results zipfile - switch from micromamba to miniconda docker image - reticulate doesn't seem to support micromamba, at least within docker - re-enable runner docker image CI - update runner README.md - resolves #6 - resolves #43 Also refactor admin views using tabs
- runner creates three folders where the script runs, and uploads their contents as zipfiles: - `/user_results`: provided to user - `/trusted_user_results`: provided to user if they have "full results" enabled by an admin - `/admin_results`: only visible to admins - admin results are always uploaded, included for failed runs (for debugging) - user results are only provided if the run was successful - add `PREDICTCR_RUNNER_SCRIPT_DIR` env var to docker compose to specify where script & model can be found - add /admin/result endpoint to download admin results zipfile - switch from micromamba to miniconda docker image - reticulate doesn't seem to support micromamba, at least within docker - re-enable runner docker image CI - update runner README.md - resolves #6 - resolves #43 Also refactor admin views using tabs
results from runner analysis script will be:
The text was updated successfully, but these errors were encountered: