Stress granules change composition over time
Evidence
Share to dashboard
from Stress granules change composition over time
dashboard.mira.science/vogel-kate
1
What gets shared
R4 · self-describing bundle · a subset of the vault
Evidenceselected
Stress granules change composition over time
Across both stresses, the correlation between the two granule proteins climbs from negative to positive over ~10–15 min — they first exclude each other, then co-localize as the granule matures.
arsenite
osmotic
illustrative · unpublished — workshop prototype
Studygrounds · auto
Lattice-SIM imaging of granule formation at staged times
Protein 1–GFP and Protein 2–mKate in HeLa, imaged on a ZEISS Elyra 7 up to 30 min after stress; per-granule composition measured over time.
Protocolfollows · auto
HeLa culture → stress → Lattice-SIM → segment on SUM → composition over time
Segmenting on the per-pixel SUM of both channels is the load-bearing methods detail a reproducer traverses to.
gitvogel-lab/sg-imaging · segment_stress_granules.ijm
datagranule_composition_by_time.csv
rawNDTiff z-stacks ≈ 80 GB · Elyra 7
video2-min walkthrough
Connected nodes (optional). Two more nodes touch this Evidence in your graph. Tick to include them — you share a subset of your graph, not the whole vault.
2
Who is this dashboard for
start closed · open on purpose
deliberately hosted page
anyone with the URL · explicit hosting act required
hosted instance
Vogel × Kate · 20+ labs · a hosted instance the group’s dashboards sync to
Defaulting to consortium. It’s easier to open a closed system than to close an open one — flip to public for the lab website later.
Your dashboard runs locally by default — it’s a local server (
localhost:7979) on your machine, private and not reachable from outside. Going public means deliberately hosting it (e.g. on a server + a domain); that act — not a password — is what makes it public. Sharing to a person or consortium delivers nodes to their dashboard; sharing to the public option requires you to first host a public-facing instance.
3
Who can reach each piece
R5 · per-resource · permissions, no leaks
The shared subgraph
Evidence · Study · Protocol · Question · Candidate
Analysis & curated data
segment_stress_granules.ijm · granule_composition_by_time.csv
Raw image stacks
NDTiff ≈ 80 GB · 25 TB lab array
Private
won’t be shared
Sean’s working notes — “is the early divergence between the two stresses real below 5 min?”
Won’t be shared — and won’t leak its existence. This note links to the Evidence you’re sharing, so the relation could imply it exists. Routed through KOI, MIRA drops the dangling edge: the dashboard shows no title, no body, no “1 note hidden.” Private stays private.
4
How it arrives
read-only viewing surface
Shared = visible, not editable. The dashboard is a read-only viewing surface — Kate’s lab can read, traverse, and request, but authoring stays here in your vault. Updates you make flow out; nothing flows back in without your say.
exports as JSON-LD over KOI