Please edit this file and push to your repository.
The Trilinos Project is a community of developers, users and user-developers focused on collaborative creation of algorithms and enabling technologies within an object-oriented software framework for the solution of large-scale, complex multi-physics engineering and scientific problems on new and emerging high-performance computing (HPC) architectures.
Trilinos is also a collection of reusable scientific software libraries, known in particular for linear solvers, non-linear solvers, transient solvers, optimization solvers, and uncertainty quantification (UQ) solvers.
Most Trilinos algorithms and software are built upon its abilities to construct and solve sparse problems, using sparse linear solvers. These solvers rely on a collection of data structure classes and functions (kernels) for parallel linear algebra, especially parallel sparse kernels.
Trilinos is targeted for all major parallel architectures, including distributed memory using the Message Passing Interface (MPI), multicore using a variety of common approaches, accelerators using common and emerging approaches, and vectorization.
Trilinos parallel functionality is written on top of libraries that support compile-time polymorphism, such that, as long as a given algorithm and problem size contain enough latent parallelism, the same Trilinos source code can be compiled and execution on any reasonable combination of distributed, multicore, accelerator and vectorizing computing devices.
| Description | Your answer |
|---|---|
| Repository URL | https://github.com/trilinos/Trilinos/tree/master |
| Main/documentation website | https://trilinos.github.io/ |
| Year project was started | September, 2003 |
| Number of contributors in the past year | 224 |
| Number of contributors in the lifetime of the project | 753 |
| Number of distinct affiliations | 1 |
| Where do development discussions take place? | Github issues, Trilinos-Users Mailing List (Discussion Forum for Trilinos users) |
| Typical number of emails/comments per week? | - |
| Typical number of commits per week? | ~ 40 |
| Typical commit size | 1-2 files changed |
| How does the project accept contributions? | Github Pull Requests |
| Does the project have an automated test suite? | yes |
| Does the project use continuous integration? | yes |
| Are any legal/licensing steps required to contribute? | no |
Check the following boxes when complete or add a note below if you encountered a problem.
- I have installed the software
- I have run at least one example
- I have run the test suite
- The test suite passes
None at this time.
Students retain copyright on any work done in completion of a CU course, so you are authorized to sign a contributor license agreement (CLA), affirm a developer's certificate of origin (DCO), etc. If you have concerns about this, please note them and/or reach out to Jed directly.