Merge pull request #720 from LLNL/retire-radiuss

Reinstate RADIUSS browse & ripple effects of retiring standalone website

Author: hauten

README.md

@@ -10,8 +10,6 @@ See our [Contributing Guidelines](/about/contribute) for information about how t
 
 To join the LLNL GitHub organization and/or to add your LLNL repo to the catalog, start with the [FAQ](https://software.llnl.gov/about/faq/).
 
-*Note:* The [RADIUSS website](https://software.llnl.gov/radiuss/) and [product catalog](https://software.llnl.gov/radiuss/projects/) "live" on this URL but are managed by a [separate repo](https://github.com/LLNL/radiuss). See the [RADIUSS README](https://github.com/LLNL/radiuss/blob/main/README.md) for details.
-
 ## Contact
 
 For more information, check out our [FAQ](/about/faq). Contact [open-source@llnl.gov](mailto:open-source@llnl.gov) with questions about open source software at LLNL. Contact [github-admin@llnl.gov](mailto:github-admin@llnl.gov) with questions about working in the LLNL GitHub organization or to request a private repository.

_posts/2021-04-21-str.md

@@ -9,4 +9,4 @@ The latest issue of LLNL's *Science & Technology Review* magazine showcases Comp
 * Commentary: [To Exascale and Beyond](https://str.llnl.gov/2021-02/comfeb21) by Computing associate director Bruce Hendrickson
 * Cover story: [The Exascale Software Portfolio](https://str.llnl.gov/2021-02/diachin) by Holly Auten and featuring Lori Diachin, Rob Neely, Jeff Hittinger, Ulrike Meier Yang, David Beckingsale, and Tzanio Kolev
 
-> As a leader in high-performance computing, Lawrence Livermore wields a large portion of the Department of Energy’s HPC resources to advance national security and foundational science. The Sierra supercomputer supports the National Nuclear Security Administration’s Stockpile Stewardship Program by enabling more accurate, more predictive simulations. This generation of computers is known as heterogeneous, or hybrid, because their architectures combine graphics processing units and central processing units to achieve peak performance well above 100 petaflops. (A petaflop is 10^15 floating-point operations per second.) The next generation’s processing capability—at least an exaflop (10^18 flops)—will be many times greater. HPC software must adjust to these new hardware standards. As the exascale era begins, two major initiatives leverage and expand Livermore’s HPC capabilities, with a spotlight here on software. The [Exascale Computing Project](https://www.exascaleproject.org/), a joint effort between the DOE Office of Science and NNSA, brings together several national laboratories to address many hardware, software, and application challenges inherent in the organizations’ scientific and national security missions. Within the Laboratory, the [RADIUSS project](https://software.llnl.gov/radiuss/projects/) aims to benefit scientific applications through a robust software infrastructure.
+> As a leader in high-performance computing, Lawrence Livermore wields a large portion of the Department of Energy’s HPC resources to advance national security and foundational science. The Sierra supercomputer supports the National Nuclear Security Administration’s Stockpile Stewardship Program by enabling more accurate, more predictive simulations. This generation of computers is known as heterogeneous, or hybrid, because their architectures combine graphics processing units and central processing units to achieve peak performance well above 100 petaflops. (A petaflop is 10^15 floating-point operations per second.) The next generation’s processing capability—at least an exaflop (10^18 flops)—will be many times greater. HPC software must adjust to these new hardware standards. As the exascale era begins, two major initiatives leverage and expand Livermore’s HPC capabilities, with a spotlight here on software. The [Exascale Computing Project](https://www.exascaleproject.org/), a joint effort between the DOE Office of Science and NNSA, brings together several national laboratories to address many hardware, software, and application challenges inherent in the organizations’ scientific and national security missions. Within the Laboratory, the [RADIUSS project](https://computing.llnl.gov/projects/radiuss) aims to benefit scientific applications through a robust software infrastructure.

_posts/2021-06-17-axom-new.md

@@ -3,4 +3,4 @@ title: "New Repo: Axom"
 categories: new-repo
 ---
 
-[Axom](https://github.com/LLNL/axom) provides robust, flexible software infrastructure for the development of multi-physics applications and computational tools. Supported by the [Advanced Simulation and Computing](https://asc.llnl.gov/) program at LLNL and part of the Lab's [RADIUSS project](https://software.llnl.gov/radiuss/projects/), Axom is a library of robust “building block” software components that provide foundational capabilities needed for production simulation codes. The Axom team focuses on developing software infrastructure components that can be shared by HPC applications running on diverse computing platforms. [Read more about Axom](https://computing.llnl.gov/projects/axom) on the LLNL Computing website.
+[Axom](https://github.com/LLNL/axom) provides robust, flexible software infrastructure for the development of multi-physics applications and computational tools. Supported by the [Advanced Simulation and Computing](https://asc.llnl.gov/) program at LLNL and part of the Lab's [RADIUSS project](https://computing.llnl.gov/projects/radiuss), Axom is a library of robust “building block” software components that provide foundational capabilities needed for production simulation codes. The Axom team focuses on developing software infrastructure components that can be shared by HPC applications running on diverse computing platforms. [Read more about Axom](https://computing.llnl.gov/projects/axom) on the LLNL Computing website.

_posts/2022-05-03-radiuss.md

@@ -3,4 +3,4 @@ title: "Results from the First LLNL Developer Survey"
 categories: story
 ---
 
-With software development underpinning much of LLNL’s mission-driven science, the Lab’s developer community has a long history of figuring out solutions to a huge number of complex challenges. But how do we know what’s working and what isn’t? What tools or other support do developers need to do their best work? The [RADIUSS project](https://software.llnl.gov/radiuss/) team conducted a survey of LLNL developers in late 2022 to assess their happiness and needs, both for awareness and targeted action that might be pursued in the next year. Some of this insight has been published publicly for the purposes of knowledge sharing and community building. Additionally, since RADIUSS products are open source, external users can benefit from improvements LLNL makes internally and pushed out to publicly available projects. [Read the survey report.](https://software.llnl.gov/radiuss/2023/02/08/first-developer-survey/)
+With software development underpinning much of LLNL’s mission-driven science, the Lab’s developer community has a long history of figuring out solutions to a huge number of complex challenges. But how do we know what’s working and what isn’t? What tools or other support do developers need to do their best work? The [RADIUSS project](https://computing.llnl.gov/projects/radiuss) team conducted a survey of LLNL developers in late 2022 to assess their happiness and needs, both for awareness and targeted action that might be pursued in the next year. Some of this insight has been published publicly for the purposes of knowledge sharing and community building. Additionally, since RADIUSS products are open source, external users can benefit from improvements LLNL makes internally and pushed out to publicly available projects.

_posts/2022-06-23-radiuss.md

@@ -45,8 +45,6 @@ bundle exec jekyll serve
 
 Finally, open <http://localhost:4000> in a web browser.
 
-*Note:* The [RADIUSS website](https://software.llnl.gov/radiuss/) and [product catalog](https://software.llnl.gov/radiuss/projects/) "live" on this URL but are managed by a [separate repo](https://github.com/LLNL/radiuss).
-
 ## Tips
 
 The gems in your sourcefile get updated frequently. It is a good idea to occasionally run `bundle update` from within your project's root directory to make sure the software on your computer is up to date.
@@ -89,13 +87,12 @@ A [JSON file](https://github.com/LLNL/llnl.github.io/blob/main/visualize/github-
 | **Performance & Workflow** | Manage and scale complex workflows, tracking, and data collection | `performance`, `workflows` | fa-gauge-high |
 | **Portable Execution & Memory Mgmt** | Automate data motion and memory allocation on advanced architectures | `memory-management`, `portability` | fa-briefcase |
 | **Proxy Applications** | Prepare for testing and porting applications | `proxy-application` | fa-clone |
+| **RADIUSS** | Rapid Application Development via an Institutional Universal Software Stack | `radiuss` | radiuss-icon-bw.png |
 | **System Software** | Manage laptop and desktop computer systems, HPC clusters, and parallel environments | `system-software` | fa-floppy-disk |
 {:.table .table-striped .table-bordered}
 
 A repository can have up to 20 tags. In general, topic tags raise a repo's visibility on GitHub and help users find related projects. The following tags, which are not associated with the home page categories above, are recommended for LLNL repos: `amr` (adaptive mesh refinement), `arbitrary-lagrangian-eulerian` (ALE), `benchmark`, `biology`, `checkpoint`, `chemistry`, `cmake`, `compiler`, `cpp` (C++), `data-analysis`, `energy`, `exascale-computing`, `finite-elements`, `fortran`, `gpu`, `graph`, `high-dimensional-data`, `hpc`, `java`, `javascript`, `library`, `materials`, `materials-science`, `matlab`, `molecular-dynamics`, `monte-carlo`, `mpi`, `natural-language-processing`, `openmp`, `parallel-computing`, `pde`, `python`, `seismology`, `shell`, `simulation`, `solver`, `templates`, `testing`, `uncertainty-quantification`.
 
-Repos that appear on the [RADIUSS site](https://software.llnl.gov/radiuss/projects/) are listed in that repo's [`contributor-ci.yaml` file](https://github.com/LLNL/radiuss/blob/main/contributor-ci.yaml).
-
 **To add a new category to the catalog:**
 
 1. Update the list above with the category name (in alphabetical order), description, and tag.
@@ -167,7 +164,7 @@ The informational pages on this site (e.g., this page, [About](/about), [FAQ](/a
 * News post titles in title case
 * Accordion titles in the form of a sentence-case question
 
-**To update the banners on the home page:** The existing RADIUSS and IPO messages are in `<div>` containers using the [`button.html` include file](https://github.com/LLNL/llnl.github.io/blob/main/_includes/components/button.html).
+**To update the banners on the home page:** The IPO message is in a `<div>` container using the [`button.html` include file](https://github.com/LLNL/llnl.github.io/blob/main/_includes/components/button.html).
 
 **To modify the site menu:** Update the menu in the [`header.html`](https://github.com/LLNL/llnl.github.io/blob/main/_includes/header.html), rather than adding each page to the menu using page attributes.
 
@@ -225,31 +222,34 @@ Add `Materials Science` into the catalog browse by adding this code (alphabetica
 
 ## RADIUSS Features
 
-April 2022: RADIUSS launched at [github.com/llnl/radiuss](https://github.com/llnl/radiuss). See tasks in [issue 567](https://github.com/LLNL/llnl.github.io/issues/567). If we ever want/need to reinstate RADIUSS browsing, branding, and other features on *this* site, here's what to do:
+April 2022: The standalone RADIUSS site launched at [github.com/llnl/radiuss](https://github.com/llnl/radiuss) via [issue 567](https://github.com/LLNL/llnl.github.io/issues/567).
+
+September 2025: The RADIUSS site was retired and the filterable browse on this site reinstated via [issue 719](https://github.com/LLNL/llnl.github.io/issues/719).
 
-* Add `RADIUSS` back into the catalog browse (i.e., to "live" on this website) by replacing the existing code (lines 190–205) in `/visualize/github-data/category_info.json` with this:
+<!--* The code for standalone RADIUSS site was lines 190–205 in `/visualize/github-data/category_info.json`:
 
 ```bash
         "RADIUSS": {
-            "title": "RADIUSS",
-            "hash": "RADIUSS",
+            "title": "RADIUSS Software",
+            "hash": "RADIUSSSoftware",
             "icon": {
-                "path": "/assets/images/radiuss.svg",
-                "alt": "RADIUSS logo"
+                "path": "/assets/images/radiuss-icon-bw.png",
+                "alt": "RADIUSS Software"
             },
             "description": {
-                "short": "Rapid Application Development via an Institutional Universal Software Stack",
-                "long": ": LLNL's RADIUSS project aims to broaden usage across LLNL and the open source community of a set of libraries and tools used for HPC scientific application development."
+                "short": "",
+                "long": ""
             },
-                "topics":[
-                "radiuss"
-            ]            
+            "topics": [
+                "radiuss-software"
+            ],
+            "url": "https://software.llnl.gov/radiuss/projects/"
         },
 ```
 
 Note that `/project/category_info_radiuss.json` is not currently being used. If it were to be reinstated, it would need its categories updated to match the latest Catalog (e.g., `Docs and Tutorials`).
 
-<!--* Comment back in lines 31-38 in `Category.service.js`
+Comment back in lines 31-38 in `Category.service.js`
 
 ```bash
     this.containsRadiussTopics = function(catTopics, repoTopics) {
@@ -260,7 +260,7 @@ Note that `/project/category_info_radiuss.json` is not currently being used. If
         }
         return false;
     };
-```-->
+```
 
 * Update link/text on home page
 * Update links/text on [Policies & Guidelines](/about/policies)
@@ -273,6 +273,7 @@ No changes yet, if ever:
 
 * [Policies & Guidelines](/about/policies) are currently still on this site
 * RADIUSS logo (`radiuss-icon-bw.png`) is still in the `/assets/images/` folder
+-->
 
 {% endcapture %}
   {% assign accordionContent = accordionContent | markdownify %}

_posts/2023-02-08-radiuss.md

@@ -166,8 +166,6 @@ If you've set up your repository within the **LLNL organization**, you don't nee
 
 * **Standalone organization.** Alternatively, if you do not wish to transfer your repo, you can instead submit a pull request updating the [`input_lists.json` file](https://github.com/LLNL/llnl.github.io/blob/main/_visualize/input_lists.json) with your organization and/or repository names. List your organization under the `"orgs"` line *only if you intend for all of its repositories to be included in the catalog* (e.g., `glvis`); otherwise, list only the repository under the `"repos"` line within the context of your organization (e.g., `hpc/spindle`).
 
-* If your repo is part of the [RADIUSS project](https://software.llnl.gov/radiuss/projects/), be sure to add it to that website's [`contributor-ci.yaml` file](https://github.com/LLNL/radiuss/blob/main/contributor-ci.yaml).
-
 If you have a **project logo**, please follow the [Contributing Guidelines](/about/contribute) (see the question [How do I change how a specific repo appears in the catalog?](https://software.llnl.gov/about/contribute/#catalog)) for naming and uploading the file. If your repo is part of a non-LLNL organization that has its own avatar, that image will automatically display next to the repo name in the catalog, unless superseded by a repo-specific logo.
 
 Please also tag your repo with this site's **catalog categories** so it will show up in the filterable catalog. Follow the [Contributing Guidelines](/about/contribute) (see the question [How do I update or use the catalog categories?](https://software.llnl.gov/about/contribute/#categories)) for a list of tags.
@@ -220,11 +218,9 @@ If you need help re-assigning permissions in your repo, contact [github-admin@ll
 
 1. Remove the specific topic tags (e.g., `math-physics`) that connect it to this website's browsable categories.
 
-2. Remove the repo from the RADIUSS [`contributor-ci.yaml` file](https://github.com/LLNL/radiuss/blob/main/contributor-ci.yaml), if applicable.
-
-3. Submit a pull request updating the [`input_lists.json` file](https://github.com/LLNL/llnl.github.io/blob/main/_visualize/input_lists.json) to remove your repo's name.
+2. Submit a pull request updating the [`input_lists.json` file](https://github.com/LLNL/llnl.github.io/blob/main/_visualize/input_lists.json) to remove your repo's name.
 
-4. Change your repo's status via Settings > Manage Access > Who has access > Manage > Danger Zone > Archive this repository (`settings#danger-zone`). Contact [open-source@llnl.gov](mailto:open-source@llnl.gov) if for some reason GitHub won't let you complete this step.
+3. Change your repo's status via Settings > Manage Access > Who has access > Manage > Danger Zone > Archive this repository (`settings#danger-zone`). Contact [open-source@llnl.gov](mailto:open-source@llnl.gov) if for some reason GitHub won't let you complete this step.
 {% endcapture %}
   {% assign accordionContent = accordionContent | markdownify %}
   {% include components/accordion.html title='What should I do if my repo is no longer actively developed/maintained?'  slug='remove' content=accordionContent %}
@@ -239,8 +235,6 @@ Migrating the repo outside of the LLNL organization requires an organization adm
 1. Submit a pull request updating the [`input_lists.json` file](https://github.com/LLNL/llnl.github.io/blob/main/_visualize/input_lists.json) to add the new organization/repo's name. This allows for the software catalog to continue including the project even after it moves.
 
 2. Retain topic tags (e.g., `math-physics`) to connect it to this website's browsable categories.
-
-3. Update the org in the RADIUSS [`contributor-ci.yaml` file](https://github.com/LLNL/radiuss/blob/main/contributor-ci.yaml), if applicable.
 {% endcapture %}
   {% assign accordionContent = accordionContent | markdownify %}
   {% include components/accordion.html title='My repo has grown. How do I move it out of the LLNL organization?'  slug='transfer-out' content=accordionContent %}