Every team building on scientific software hits the same wall eventually. PESO exists to move that wall.
Without a shared ecosystem
- Installing 3rd-party libs breaks on dependency mismatches
- Version updates introduce breaking changes downstream
- New tools disrupt existing team workflows
- Portability across CPU/GPU is manually managed
- Build times balloon as projects grow
- Algorithms fall out of date, hurting performance and security
With PESO
- Curated, tested library portfolio via Spack + E4S
- Coordinated release and compatibility testing
- User- and developer-experience research baked in
- Community engagement as a first-order priority
- Direct line to CASS community expertise
- Shared investment across DOE, vendors, and academia
Want the rest of the story? See PESO Project Details for how PESO operates, its guiding principles, and key activities.