Update README.md
Browse files
README.md
CHANGED
|
@@ -1,3 +1,48 @@
|
|
| 1 |
-
---
|
| 2 |
-
|
| 3 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# MD-trajectories-CPPF-tubulin-heterodimer-and-monomers
|
| 2 |
+
|
| 3 |
+
**Copy this file into the Hugging Face dataset “README” (Dataset card).**
|
| 4 |
+
Source of truth in Git: `https://github.com/jasperyeoh/integrative-ai-assisted-modeling-of-cppf-tubulin-interaction-suggest-beta-tubulin-binding-preference` — see `docs/DIMER_TRAJECTORY_NAMING.md`.
|
| 5 |
+
|
| 6 |
+
---
|
| 7 |
+
|
| 8 |
+
## What this dataset contains
|
| 9 |
+
|
| 10 |
+
All-atom GROMACS **production trajectories** (`.xtc`) for **CPPF** with **human tubulin**: **three heterodimer replicates** (extended to **~400 ns** per replicate) and **six monomer replicates** (~**200 ns** each: α/β × three replicates).
|
| 11 |
+
Checksum sidecars: `HF_UPLOAD_SHA256SUMS_all.txt`, `HF_UPLOAD_SHA256SUMS_dimer_extensions.txt` (commit may split uploads across bundles).
|
| 12 |
+
|
| 13 |
+
---
|
| 14 |
+
|
| 15 |
+
## Important: dimer files named `*_md_200ns.xtc` are **not** “only 0–200 ns”
|
| 16 |
+
|
| 17 |
+
**There is no missing 200–300 ns segment in the dimer data.**
|
| 18 |
+
|
| 19 |
+
GROMACS often **keeps the first output basename** when the run is **continued** (checkpoint / append). The on-disk file is still called `md_200ns.xtc`, but the **trajectory inside can run from ~0 to ~300 ns** for the dimer. The next time windows are stored in the **separate** part files below.
|
| 20 |
+
|
| 21 |
+
| Approx. time (dimer) | What to use on this Hub (replicate in filename) | Typical on-disk name in the GitHub `revision_exec` tree |
|
| 22 |
+
|----------------------|--------------------------------------------------|--------------------------------------------------------|
|
| 23 |
+
| **~0 → 300 ns** | `dimer_rep{1,2,3}_md_200ns.xtc` | `rep*/prod/md_200ns.xtc` (name is **legacy**; **content is not “200 ns only”**) |
|
| 24 |
+
| **~300 → 350 ns** | `dimer_rep1_md_350ns.part0004.xtc` or `dimer_rep{2,3}_md_350ns.part0003.xtc` | `md_350ns.part0004` (rep1) or `md_350ns.part0003` (rep2/3) |
|
| 25 |
+
| **~350 → 400 ns** | `dimer_rep1_md_400ns.part0005.xtc` or `dimer_rep{2,3}_md_400ns.part0004.xtc` | matching `md_400ns.part*` |
|
| 26 |
+
|
| 27 |
+
Part indices **differ between rep1 and rep2/3** because of how extensions were launched (`-noappend`, run numbering).
|
| 28 |
+
|
| 29 |
+
**Monomers:** `monomer_*_md_200ns.xtc` correspond to **~200 ns** production per replicate (standard naming matches length).
|
| 30 |
+
|
| 31 |
+
---
|
| 32 |
+
|
| 33 |
+
## Human-readable aliases (optional, Git repo only)
|
| 34 |
+
|
| 35 |
+
The GitHub repo may contain **symlinks** such as `segment_0-300ns.xtc` → `md_200ns.xtc` under `revision_exec/rep*/prod/` (created by `revision_exec/scripts/create_dimer_trajectory_symlinks.sh`). **These symlinks are not required on the Hub**; they exist to avoid renaming canonical MD files that scripts and checkpoints rely on.
|
| 36 |
+
|
| 37 |
+
---
|
| 38 |
+
|
| 39 |
+
## Workflow & environments
|
| 40 |
+
|
| 41 |
+
- Scripts and topology: **same GitHub repo** as above.
|
| 42 |
+
- Conda / GROMACS environment notes: `docs/CONDA_ENVIRONMENTS.md`.
|
| 43 |
+
|
| 44 |
+
---
|
| 45 |
+
|
| 46 |
+
## License
|
| 47 |
+
|
| 48 |
+
MIT (same as repository; confirm here matches your publication requirement).
|