Use Cases
Teach Drylab Your Lab's Protocol
Save your lab's QC thresholds, naming rules, statistics and figure style once in a protocol file, then mention it in your chats.
For PIs, core facilities and anyone who repeats the same kind of analysis: write your lab's conventions down once in a protocol file, then mention it in your chats. Drylab reads the file and uses your thresholds and figure style instead of picking its own. Check its first answer to make sure it did (see below).
When to use it
- Everyone in the lab should use the same QC cutoffs, for example 200-6000 genes per cell and under 15% mitochondrial reads.
- You always name output files the same way, so results from different people line up.
- Your lab has fixed statistical choices: the test, the multiple-testing correction, the significance cutoff.
- Journals or your PI expect one figure style: file type, resolution, colors, font size.
Prompt examples
The protocol to save (as lab_protocol.md):
# Morgan Lab scRNA-seq protocol
## QC
- Keep cells with 200 to 6000 detected genes.
- Keep cells with less than 15% mitochondrial reads.
- Report how many cells each filter removed.
## Clustering
- Use Leiden clustering with resolution 0.5.
## Statistics
- Find markers with the Wilcoxon test and Benjamini-Hochberg correction; call genes with adjusted p < 0.05.
## Figures and file names
- Save every figure as a 300 dpi PDF.
- Name files <sample>_<plot>.pdf, for example PBMC1_umap.pdf.A chat that relies on it:
Follow @lab_protocol.md. Run QC and clustering on @pbmc_sample.h5ad and tell me how many cells each QC filter removed.Check the rules before running anything:
Read @lab_protocol.md. Before I upload my next sample, list the QC thresholds, clustering resolution and figure format it tells you to use. Don't run any analysis.Same protocol, different sample:
Apply @lab_protocol.md to @pbmc_sample2.h5ad and save the UMAP and the QC violin plots with our file names.Steps
- Save the protocol as
lab_protocol.mdin your project's Project Files: upload it, or paste the text in a chat and ask Drylab to save it there. In the Desktop App, put the file anywhere in your project folder. - In each request, mention the file with
@, for exampleFollow @lab_protocol.md and run QC on @pbmc_sample.h5ad. Drylab reads exactly that file. See Mention Files and Resources. - Check the answer before you trust the results: Drylab should repeat your thresholds and file names. If it uses other values, point it back to the file.
To change a rule later, edit the file in Project Files (or ask Drylab to update it). The next chat that mentions it uses the new version.
Tips
- Mention the file in every request. Drylab doesn't apply your protocol to every chat on its own; the mention makes sure it reads it.
- Keep the protocol short and specific. Numbers, test names and file-name patterns work better than general advice. One file per kind of analysis is easier to reuse than one long document.
- Start the file with when it applies, for example "Use for paired tumor vs normal bulk RNA-seq", so a colleague picks the right one.