Skip to content

Commit 9722289

Browse files
bernholdbernhold
committed
Initial submissions of more FASTMath products
1 parent da08ec1 commit 9722289

File tree

3 files changed

+355
-0
lines changed

3 files changed

+355
-0
lines changed

‎_sw/strumpack.md‎

Lines changed: 125 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,125 @@
1+
---
2+
# Product information for CASS website product catalog
3+
#
4+
# INSTRUCTIONS
5+
# This is a Jekyll Markdown file, which starts with YAML "frontmatter." For the product
6+
# catalog, we will be using only the YAML frontmatter (between the "---" seperators).
7+
# Please leave the main body empty.
8+
#
9+
# Please name the file itself for the software product: <name>.md (all lowercase)
10+
#
11+
# We've tried to require the minimum, but anything optional you choose to add will enrich your
12+
# product's entry in the catalog. To provide optional items, please uncomment the keys and complete
13+
# the value appropriately.
14+
#
15+
# Please see the accompanying README.md for more detailed information and guidance.
16+
#
17+
# BASIC PRODUCT INFORMATION (ALL REQUIRED)
18+
# name: (string) REQUIRED The name under which your product should appear in the catalog
19+
# area: (string) REQUIRED The technical area of the product. For now, we are using
20+
# the areas that were used by ECP ST, except that anything that was categorized as
21+
# NNSA Software under ECP should instead be listed under the appropriate "real" area:
22+
# Values include: "dataviz", "devtools", "mathlibs", "pmr", "sweco".
23+
# We also support the values used in e4s.yml files, though we prefer those above.
24+
# cass_member: (string) REQUIRED The name of the CASS member organization (aka software stewardship
25+
# organization) you are associated with. Values include: "FASTMath", "PEOS", "RAPIDS", "S4PST", "STEP".
26+
# (other CASS members are not stewarding software products, as far as we know: COLABS, CORSA, SWAS)
27+
# description: (string) REQUIRED A short description of your software. The `description` is always shown immediately
28+
# after the `name` and they should be considered together as, in effect constructing a sentence-length
29+
# description of the product with the form `name: desciption`. However it does not need to be a complete
30+
# sentence in the grammatical sense. Key points: The `description` should *not* repeat the `name`, it
31+
# should be in sentence case, and it should *not* end with a period.
32+
# long_description: (multiline string) REQUIRED A one-paragraph description of your software. A brief, moderately technical description
33+
# of your software's primary features and capabilities.
34+
# target_audience: (multiline string) REQUIRED A one-paragraph description of who should be interested in your software. This should be
35+
# less technical than the description -- meant to guide someone who's inexpert or just trying to
36+
# figure out who might be using the software.
37+
#
38+
# Note on multline string entries (long_description and target_audience): YAML supports a multiline string entry that allows
39+
# a value to be a paragraph (or several). A multiline string value starts with a pipe ("|") following the colon of the key, with
40+
# the text of the value starting on the following line. The entirety of the value should be indented by 2-4 spaces from the
41+
# left margin. The value ends at the next outdented text (or comment).
42+
#
43+
name: STRUMPACK
44+
area: Mathmatical Libraries
45+
cass_member: FASTMath
46+
description: Low-rank STRUctured Matrix PACKage for both dense and sparse matrices.
47+
long_description: |
48+
STRUMPACK is a software library providing linear algebra routines and linear system
49+
solvers for sparse and dense rank-structured linear systems.
50+
For dense linear systems, STRUMPACK has support for the Hierarchically Semi-Separable (HSS),
51+
Block Low Rank (BLR), Hierachically Off-Diagonal Low Rank (HODLR), Butterfly and
52+
Hierarchically Off-Diagonal Butterfly (HODBF) rank-structured matrix formats.
53+
In sparse direct solvers based on multifrontal LU factorization, the fill-in in the
54+
triangular factors often has low-rank structure. Hence, the sparse linear solve
55+
algorithms in STRUMPACK exploit the different dense rank-structured matrix formats
56+
to compress the fill-in. This leads to purely algebraic, fast and scalable
57+
(both with problem size and compute cores) approximate direct solvers or preconditioners.
58+
The sparse solver in STRUMPACK can also be used as an exact direct solver,
59+
whiich delivers good performance and distributed
60+
memory scalability and provides excellent GPU support in CUDA, HIP and SYCL.
61+
STRUMPACK also provides preconditioned GMRES and BiCGStab iterative solvers.
62+
63+
target_audience: |
64+
The rank-structured matrices appear in many applications, e.g., the Boundary Element
65+
Method for discretization of integral equations, structured matrices like Toeplitz
66+
and Cauchy, kernel and covariance matrices etc. For the sparse linear systems,
67+
these preconditioners are mostly aimed at those systems coome from the
68+
discretization of a partial differential equation, but are not limited to any
69+
particular type of problem.
70+
The various comopressing formats can be useful as strong approximate
71+
factorization preconditioners for an iterative solver.
72+
#
73+
# PACKAGING INFORMATION
74+
# This information is used to connect your product with its E4S and Spack packages, if available.
75+
# e4s_product: (string) If your product is in E4S, list its e4S name here (may be different than `name`). If your
76+
# product is not in E4S, comment out this entry.
77+
# spack_name: (string) The name of your spack package(s), if available. If you don't have a Spack package, comment out this
78+
# entry. If your product has multiple Spack packages, list them using YAML list syntax:
79+
# spack_name:
80+
# - package1
81+
# - package2
82+
# - package3
83+
#
84+
e4s_product: STRUMPACK
85+
spack_name: strumpack
86+
#
87+
# ADDITIONAL PRODUCT INFORMATION
88+
# These are OPTIONAL lists of resource links that you can provide to make your catalog entry more useful.
89+
# The typical set includes: Website, Repository, Downloads, and Documentation, but all of these are optional, and
90+
# you can also add other labels. `additional_resource_links` is a general category; `end_user_resource_links` and
91+
# `developer_resource_links` are meant to target the named groups more specifically. Use them as you like.
92+
#
93+
# The essential inputs are structured as follows:
94+
# - label: Resource label # REQUIRED
95+
# url: https://example.com # REQUIRED
96+
# note: (additional info) # OPTIONAL
97+
# icon: fa-solid fa-font-awesome # OPTIONAL, a FontAwesome icon identifier
98+
#
99+
# Which would appear as (in pseudo-markdown):
100+
# {{ icon }} [{{ label }}]({{ url }}) {{ note }}
101+
#
102+
# For additional information, see _sw/README.md.
103+
#
104+
additional_resource_links:
105+
- label: Website
106+
url: https://portal.nersc.gov/project/sparse/strumpack//index.html
107+
- label: Repository
108+
url: https://github.com/pghysels/STRUMPACK
109+
- label: Downloads
110+
url: https://github.com/pghysels/STRUMPACK
111+
- label: Documentation
112+
url: https://portal.nersc.gov/project/sparse/strumpack/v7.1.0/index.html
113+
#
114+
# A set of resources specifically aimed at users of the software (OPTIONAL)
115+
#
116+
# end_user_resource_links:
117+
# - label:
118+
# url:
119+
#
120+
# A set of resources specifically aimed at developers/contributors to the software (OPTIONAL)
121+
#
122+
# developer_resource_links:
123+
# - label:
124+
# url:
125+
---

‎_sw/sundials.md‎

Lines changed: 109 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,109 @@
1+
---
2+
# Product information for CASS website product catalog
3+
#
4+
# INSTRUCTIONS
5+
# This is a Jekyll Markdown file, which starts with YAML "frontmatter." For the product
6+
# catalog, we will be using only the YAML frontmatter (between the "---" seperators).
7+
# Please leave the main body empty.
8+
#
9+
# Please name the file itself for the software product: <name>.md (all lowercase)
10+
#
11+
# We've tried to require the minimum, but anything optional you choose to add will enrich your
12+
# product's entry in the catalog. To provide optional items, please uncomment the keys and complete
13+
# the value appropriately.
14+
#
15+
# Please see the accompanying README.md for more detailed information and guidance.
16+
#
17+
# BASIC PRODUCT INFORMATION (ALL REQUIRED)
18+
# name: (string) REQUIRED The name under which your product should appear in the catalog
19+
# area: (string) REQUIRED The technical area of the product. For now, we are using
20+
# the areas that were used by ECP ST, except that anything that was categorized as
21+
# NNSA Software under ECP should instead be listed under the appropriate "real" area:
22+
# Values include: "dataviz", "devtools", "mathlibs", "pmr", "sweco".
23+
# We also support the values used in e4s.yml files, though we prefer those above.
24+
# cass_member: (string) REQUIRED The name of the CASS member organization (aka software stewardship
25+
# organization) you are associated with. Values include: "FASTMath", "PEOS", "RAPIDS", "S4PST", "STEP".
26+
# (other CASS members are not stewarding software products, as far as we know: COLABS, CORSA, SWAS)
27+
# description: (string) REQUIRED A short description of your software. The `description` is always shown immediately
28+
# after the `name` and they should be considered together as, in effect constructing a sentence-length
29+
# description of the product with the form `name: desciption`. However it does not need to be a complete
30+
# sentence in the grammatical sense. Key points: The `description` should *not* repeat the `name`, it
31+
# should be in sentence case, and it should *not* end with a period.
32+
# long_description: (multiline string) REQUIRED A one-paragraph description of your software. A brief, moderately technical description
33+
# of your software's primary features and capabilities.
34+
# target_audience: (multiline string) REQUIRED A one-paragraph description of who should be interested in your software. This should be
35+
# less technical than the description -- meant to guide someone who's inexpert or just trying to
36+
# figure out who might be using the software.
37+
#
38+
# Note on multline string entries (long_description and target_audience): YAML supports a multiline string entry that allows
39+
# a value to be a paragraph (or several). A multiline string value starts with a pipe ("|") following the colon of the key, with
40+
# the text of the value starting on the following line. The entirety of the value should be indented by 2-4 spaces from the
41+
# left margin. The value ends at the next outdented text (or comment).
42+
#
43+
name: SUNDIALS
44+
area: mathlibs
45+
cass_member: FASTMath
46+
description: The SUNDIALS library of time integrators and nonlinear solvers provides robust and efficient numerical methods for ordinary differential equations (ODEs), differential-algebraic equations (DAEs), and nonlinear algebraic systems.
47+
long_description: |
48+
The SUNDIALS library of time integrators and nonlinear solvers provides robust and efficient numerical methods for ordinary differential equations (ODEs), differential-algebraic equations (DAEs), and nonlinear algebraic systems. SUNDIALS is freely available and developed on GitHub. SUNDIALS is comprised of following packages: ARKODE, a solver with one-step methods for stiff, nonstiff, mixed stiff-nonstiff, and multirate ODE systems; CVODE, a solver with Adams and BDF methods for stiff and nonstiff ODE systems; CVODES, an extension of CVODE with forward and adjoint sensitivity analysis capabilities for stiff and nonstiff ODE systems; IDA, a solver with BDF methods for DAE systems; IDAS, an extension of IDA with forward and adjoint sensitivity analysis capabilities for DAE systems; KINSOL, a solver for nonlinear algebraic systems. The SUNDIALS packages share many components and are organized as a family built on a common infrastructure including abstract interfaces for vectors, matrices, and algebraic solvers. Several implementations of these interfaces are provided with SUNDIALS supporting a range of parallel computing paradigms including shared-memory, distributed memory, and GPU computing.
49+
target_audience: |
50+
The SUNDIALS time integration library is targeted towards scientists and engineers working on simulations involving systems of ordinary differential equations, differential algebraic equations, and nonlinear algebraic equations. SUNDIALS provides capabilities for these systems for users running simulations on hardware ranging from laptops to leadership class exascale supercomputers and is designed to be incorporated into existing codes.
51+
#
52+
# PACKAGING INFORMATION
53+
# This information is used to connect your product with its E4S and Spack packages, if available.
54+
# e4s_product: (string) If your product is in E4S, list its e4S name here (may be different than `name`). If your
55+
# product is not in E4S, comment out this entry.
56+
# spack_name: (string) The name of your spack package(s), if available. If you don't have a Spack package, comment out this
57+
# entry. If your product has multiple Spack packages, list them using YAML list syntax:
58+
# spack_name:
59+
# - package1
60+
# - package2
61+
# - package3
62+
#
63+
e4s_product: sundials
64+
spack_name: sundials
65+
#
66+
# ADDITIONAL PRODUCT INFORMATION
67+
# These are OPTIONAL lists of resource links that you can provide to make your catalog entry more useful.
68+
# The typical set includes: Website, Repository, Downloads, and Documentation, but all of these are optional, and
69+
# you can also add other labels. `additional_resource_links` is a general category; `end_user_resource_links` and
70+
# `developer_resource_links` are meant to target the named groups more specifically. Use them as you like.
71+
#
72+
# The essential inputs are structured as follows:
73+
# - label: Resource label # REQUIRED
74+
# url: https://example.com # REQUIRED
75+
# note: (additional info) # OPTIONAL
76+
# icon: fa-solid fa-font-awesome # OPTIONAL, a FontAwesome icon identifier
77+
#
78+
# Which would appear as (in pseudo-markdown):
79+
# {{ icon }} [{{ label }}]({{ url }}) {{ note }}
80+
#
81+
# For additional information, see _sw/README.md.
82+
#
83+
additional_resource_links:
84+
- label: Website
85+
url: https://computing-staging.llnl.gov/projects/sundials
86+
- label: Repository
87+
url: https://github.com/LLNL/sundials
88+
- label: Downloads
89+
url: https://computing.llnl.gov/projects/sundials/sundials-software
90+
- label: Documentation
91+
url: https://sundials.readthedocs.io/en/latest/index.html#
92+
# A set of resources specifically aimed at users of the software (OPTIONAL)
93+
#
94+
end_user_resource_links:
95+
- label: Documentation
96+
url: https://sundials.readthedocs.io/en/latest/index.html#
97+
- label: Issue Tracker
98+
url: https://github.com/LLNL/sundials/issues
99+
- label: User Support Mailing List Archive
100+
url: https://groups.google.com/g/sundials-users
101+
#
102+
# A set of resources specifically aimed at developers/contributors to the software (OPTIONAL)
103+
#
104+
developer_resource_links:
105+
- label: Developer Guide
106+
url: https://sundials.readthedocs.io/en/latest/developers/index.html
107+
- label: Contributing Guide
108+
url: https://sundials.readthedocs.io/en/latest/contributing/index.html
109+
---

0 commit comments

Comments
 (0)