|
1 | | ----# Product information for CASS website product catalog## INSTRUCTIONS# This is a Jekyll Markdown file, which starts with YAML "frontmatter." For the product# catalog, we will be using only the YAML frontmatter (between the "---" seperators).# Please leave the main body empty.## Please name the file itself for the software product: <name>.md (all lowercase)## We've tried to require the minimum, but anything optional you choose to add will enrich your# product's entry in the catalog. To provide optional items, please uncomment the keys and complete# the value appropriately.## Please see the accompanying README.md for more detailed information and guidance.## BASIC PRODUCT INFORMATION (ALL REQUIRED)# name: (string) REQUIRED The name under which your product should appear in the catalog# area: (string) REQUIRED The technical area of the product. For now, we are using# the areas that were used by ECP ST, except that anything that was categorized as# NNSA Software under ECP should instead be listed under the appropriate "real" area:# Values include: "dataviz", "devtools", "mathlibs", "pmr", "sweco".# We also support the values used in e4s.yml files, though we prefer those above.# cass_member: (string) REQUIRED The name of the CASS member organization (aka software stewardship# organization) you are associated with. Values include: "FASTMath", "PEOS", "RAPIDS", "S4PST", "STEP".# (other CASS members are not stewarding software products, as far as we know: COLABS, CORSA, SWAS)# description: (string) REQUIRED A short description of your software. The `description` is always shown immediately# after the `name` and they should be considered together as, in effect constructing a sentence-length# description of the product with the form `name: desciption`. However it does not need to be a complete# sentence in the grammatical sense. Key points: The `description` should *not* repeat the `name`, it# should be in sentence case, and it should *not* end with a period.# long_description: (multiline string) REQUIRED A one-paragraph description of your software. A brief, moderately technical description# of your software's primary features and capabilities.# target_audience: (multiline string) REQUIRED A one-paragraph description of who should be interested in your software. This should be# less technical than the description -- meant to guide someone who's inexpert or just trying to# figure out who might be using the software.## Note on multline string entries (long_description and target_audience): YAML supports a multiline string entry that allows# a value to be a paragraph (or several). A multiline string value starts with a pipe ("|") following the colon of the key, with# the text of the value starting on the following line. The entirety of the value should be indented by 2-4 spaces from the# left margin. The value ends at the next outdented text (or comment).#name: MAGMAarea: mathlibscass_member: FASTMathdescription: Matrix Algebra on GPUs and Multicore Architectures is a library for BLAS and LAPACK on GPUs.long_description: | MAGMA is a node-level mathematical library for dense linear algebra algorithms on GPU-accelerated HPC systems. MAGMA provides BLAS, batch BLAS, LAPACK, and batch LAPACK functionality on NVIDIA, AMD, and Intel GPUs, often complementing the industrial numerical libraries. MAGMA pioneered hybrid CPU-GPU algorithms for dense matrix factorizations, linear solvers, eigenvalue, and singular value decompositions. MAGMA has been partially adopted by NVIDIA and AMD into their numerical linear algebra libraries. It is an integral component of many DOE applications, and is part of xSDK and E4S.target_audience: | Computational scientists from various domains, numerical analysts, HPC scientists, certain AI applications, developers of other math libraries such as Finite elements analysis, sparse direct solvers, computational statistics, computer vision, and others.## PACKAGING INFORMATION# This information is used to connect your product with its E4S and Spack packages, if available.# e4s_product: (string) If your product is in E4S, list its e4S name here (may be different than `name`). If your# product is not in E4S, comment out this entry.# spack_name: (string) The name of your spack package(s), if available. If you don't have a Spack package, comment out this# entry. If your product has multiple Spack packages, list them using YAML list syntax:# spack_name:# - package1# - package2# - package3#e4s_product: MAGMAspack_name: magma## ADDITIONAL PRODUCT INFORMATION# These are OPTIONAL lists of resource links that you can provide to make your catalog entry more useful.# The typical set includes: Website, Repository, Downloads, and Documentation, but all of these are optional, and# you can also add other labels. `additional_resource_links` is a general category; `end_user_resource_links` and# `developer_resource_links` are meant to target the named groups more specifically. Use them as you like.## The essential inputs are structured as follows:# - label: Resource label # REQUIRED# url: https://example.com # REQUIRED# note: (additional info) # OPTIONAL# icon: fa-solid fa-font-awesome # OPTIONAL, a FontAwesome icon identifier## Which would appear as (in pseudo-markdown):# {{ icon }} [{{ label }}]({{ url }}) {{ note }}## For additional information, see _sw/README.md.## additional_resource_links:# - label: Website# url:# - label: Repository# url:# - label: Downloads# url:# - label: Documentation# url:## A set of resources specifically aimed at users of the software (OPTIONAL)## end_user_resource_links:# - label:# url:## A set of resources specifically aimed at developers/contributors to the software (OPTIONAL)## developer_resource_links:# - label:# url:additional_resource_links: - label: Website url: https://icl.utk.edu/magma - label: Repository url: https://github.com/icl-utk-edu/magma - label: Documentation url: https://icl.utk.edu/projectsfiles/magma/doxygen/index.html--- |
| 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: MAGMA |
| 44 | +area: mathlibs |
| 45 | +cass_member: FASTMath |
| 46 | +description: A library for BLAS and LAPACK on GPUs |
| 47 | +long_description: | |
| 48 | + MAGMA (Matrix Algebra on GPUs and Multicore Architectures) is a node-level mathematical library for dense linear algebra algorithms on GPU-accelerated HPC systems. MAGMA provides |
| 49 | + BLAS, batch BLAS, LAPACK, and batch LAPACK functionality on NVIDIA, AMD, and Intel GPUs, often complementing the industrial |
| 50 | + numerical libraries. MAGMA pioneered hybrid CPU-GPU algorithms for dense matrix factorizations, linear solvers, eigenvalue, and |
| 51 | + singular value decompositions. MAGMA has been partially adopted by NVIDIA and AMD into their numerical linear algebra libraries. |
| 52 | + It is an integral component of many DOE applications, and is part of xSDK and E4S. |
| 53 | +target_audience: | |
| 54 | + Computational scientists from various domains, numerical analysts, |
| 55 | + HPC scientists, certain AI applications, developers of other math libraries |
| 56 | + such as finite elements analysis, sparse direct solvers, computational statistics, |
| 57 | + computer vision, and others. |
| 58 | +# |
| 59 | +# PACKAGING INFORMATION |
| 60 | +# This information is used to connect your product with its E4S and Spack packages, if available. |
| 61 | +# e4s_product: (string) If your product is in E4S, list its e4S name here (may be different than `name`). If your |
| 62 | +# product is not in E4S, comment out this entry. |
| 63 | +# spack_name: (string) The name of your spack package(s), if available. If you don't have a Spack package, comment out this |
| 64 | +# entry. If your product has multiple Spack packages, list them using YAML list syntax: |
| 65 | +# spack_name: |
| 66 | +# - package1 |
| 67 | +# - package2 |
| 68 | +# - package3 |
| 69 | +# |
| 70 | +e4s_product: MAGMA |
| 71 | +spack_name: magma |
| 72 | +# |
| 73 | +# ADDITIONAL PRODUCT INFORMATION |
| 74 | +# These are OPTIONAL lists of resource links that you can provide to make your catalog entry more useful. |
| 75 | +# The typical set includes: Website, Repository, Downloads, and Documentation, but all of these are optional, and |
| 76 | +# you can also add other labels. `additional_resource_links` is a general category; `end_user_resource_links` and |
| 77 | +# `developer_resource_links` are meant to target the named groups more specifically. Use them as you like. |
| 78 | +# |
| 79 | +# The essential inputs are structured as follows: |
| 80 | +# - label: Resource label # REQUIRED |
| 81 | +# url: https://example.com # REQUIRED |
| 82 | +# note: (additional info) # OPTIONAL |
| 83 | +# icon: fa-solid fa-font-awesome # OPTIONAL, a FontAwesome icon identifier |
| 84 | +# |
| 85 | +# Which would appear as (in pseudo-markdown): |
| 86 | +# {{ icon }} [{{ label }}]({{ url }}) {{ note }} |
| 87 | +# |
| 88 | +# For additional information, see _sw/README.md. |
| 89 | +# |
| 90 | +# additional_resource_links: |
| 91 | +# - label: Website |
| 92 | +# url: |
| 93 | +# - label: Repository |
| 94 | +# url: |
| 95 | +# - label: Downloads |
| 96 | +# url: |
| 97 | +# - label: Documentation |
| 98 | +# url: |
| 99 | +# |
| 100 | +# A set of resources specifically aimed at users of the software (OPTIONAL) |
| 101 | +# |
| 102 | +# end_user_resource_links: |
| 103 | +# - label: |
| 104 | +# url: |
| 105 | +# |
| 106 | +# A set of resources specifically aimed at developers/contributors to the software (OPTIONAL) |
| 107 | +# |
| 108 | +# developer_resource_links: |
| 109 | +# - label: |
| 110 | +# url: |
| 111 | +additional_resource_links: |
| 112 | + - label: Website |
| 113 | + url: https://icl.utk.edu/magma |
| 114 | + - label: Repository |
| 115 | + url: https://github.com/icl-utk-edu/magma |
| 116 | + - label: Documentation |
| 117 | + url: https://icl.utk.edu/projectsfiles/magma/doxygen/index.html |
| 118 | +--- |
0 commit comments