Tier 1 — ~1 hour, entirely within our own control.
Our stargazer analysis ranks SCIInstitute's own repos as SCIRun's nearest neighbours by lift:
| Repo |
Stars |
SCIRun stargazers who also starred it |
| SCIInstitute/fluorender |
48 |
5 |
| SCIInstitute/ShapeWorks |
132 |
7 |
| SCIInstitute/SCI-Solver_FEM |
99 |
6 |
| SCIInstitute/Seg3D |
120 |
5 |
The audience overlap is already real and measured. What is missing is any navigation between the projects — a visitor who lands on Seg3D has no path to SCIRun and vice versa.
Evidence this leaks the other way too: among 609 Slicer-community developers, the SCIInstitute repos they had starred were ShapeWorks (2), UncertainSCI (1), Cleaver (1) and SCIRun (1). People are finding individual projects and never discovering the rest.
Action
Add a short, consistent "Related SCI Institute projects" section to the README of each:
One line per project describing what it does, so the section is useful rather than a link farm. Where projects genuinely interoperate (Seg3D → SCIRun, Cleaver → SCIRun meshes), say so explicitly — that is the part a reader can act on.
Tier 1 — ~1 hour, entirely within our own control.
Our stargazer analysis ranks SCIInstitute's own repos as SCIRun's nearest neighbours by lift:
The audience overlap is already real and measured. What is missing is any navigation between the projects — a visitor who lands on Seg3D has no path to SCIRun and vice versa.
Evidence this leaks the other way too: among 609 Slicer-community developers, the SCIInstitute repos they had starred were ShapeWorks (2), UncertainSCI (1), Cleaver (1) and SCIRun (1). People are finding individual projects and never discovering the rest.
Action
Add a short, consistent "Related SCI Institute projects" section to the README of each:
One line per project describing what it does, so the section is useful rather than a link farm. Where projects genuinely interoperate (Seg3D → SCIRun, Cleaver → SCIRun meshes), say so explicitly — that is the part a reader can act on.