A collection of reusable scientific computing software components for solving large-scale, complex multi-physics engineering problems.
Trilinos is an open-source software framework for developing and deploying scalable algorithms to solve large-scale, complex multi-physics engineering and scientific problems. It provides a collection of reusable components and packages that enable researchers to build high-performance simulation codes. The framework focuses on enabling scientific computing across diverse hardware architectures at scale.
Computational scientists, engineers, and researchers working on large-scale simulations in fields like computational fluid dynamics, structural mechanics, and multi-physics modeling who need scalable numerical algorithms.
Trilinos offers a comprehensive, modular collection of battle-tested numerical algorithms that can be combined flexibly, avoiding the need to reinvent foundational scientific computing components. Its package-oriented design allows users to select only the components they need while ensuring interoperability.
Primary repository for the Trilinos Project
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Organized as a collection of independent, reusable packages, allowing selective use and interoperability, which is central to its philosophy as described in the README.
Provides linear, nonlinear, and transient solvers optimized for high-performance computing, enabling large-scale simulations across diverse hardware architectures.
Designed to run efficiently from laptops to supercomputers, supported by sample build scripts for various platforms, as mentioned in the documentation.
Includes packages for linear algebra, discretizations, optimization, and more, offering a comprehensive toolkit for scientific computing workflows.
Setting up requires platform-specific configuration and build scripts, which are only a starting point and can be daunting, as noted in the sampleScripts section.
Documentation is scattered across multiple package websites and general guides, making it difficult for users to find cohesive information, as highlighted in the README links.
Licenses vary per package, with some under BSD and others under (L)GPL, requiring careful attention to compliance, as detailed in the license section.