Set up LDSC as a remote tool

Sharing this model for a user, not developing it? Follow the tooluniverse-share-computer guide; no ToolUniverse source checkout is needed. The model runs in its own Python environment, with its dependencies:

~/.local/bin/uv venv --python 3.12 ~/.tooluniverse/envs/ldsc
curl -fsSL -o ~/.tooluniverse/envs/ldsc-tooluniverse.txt https://connect.aiscientist.tools/install-requirements.txt
curl -fsSL -o ~/.tooluniverse/envs/ldsc-requirements.txt https://raw.githubusercontent.com/mims-harvard/ToolUniverse/main/src/tooluniverse/remote/ldsc/requirements.txt
~/.local/bin/uv pip install --python ~/.tooluniverse/envs/ldsc/bin/python -r ~/.tooluniverse/envs/ldsc-tooluniverse.txt -r ~/.tooluniverse/envs/ldsc-requirements.txt
~/.local/bin/tu remote check ldsc --python ~/.tooluniverse/envs/ldsc/bin/python   # lists anything still missing
~/.local/bin/tu serve --allow ldsc --python ~/.tooluniverse/envs/ldsc/bin/python --share --detach --name "<computer name>" --service https://tooluniverse-backend.onrender.com

If the check reports a missing environment variable (a data folder, a model cache, a provider key), set it in the same shell before tu serve; "Obtain credentials, data, and model weights" below says what each one is. The model reads only the variables it declares.

The rest of this guide is for developers working from the ToolUniverse source, and for diagnosing problems with this model.

Validation status (2026-08-16): CBIIT LDSC and its official simulation ran through live loopback MCP; heritability and genetic-correlation calls returned finite parsed statistics. Real population panels, public publication, cross-user isolation, broad concurrency, and biological validation remain incomplete. Authenticated private Platform import and owner testing passed on 2026-08-16; public publication and independent-caller authorization/isolation remain untested.