Merge pull request #55 from Pressio/54-rename-pressio-to-pressio-rom

#54: rename pressio to pressio-rom

Author: Francesco Rizzi

.github/workflows/test-all.yml

@@ -54,7 +54,7 @@ jobs:
           wget -O - https://apt.kitware.com/keys/kitware-archive-latest.asc 2>/dev/null \
             | gpg --dearmor - \
             | sudo tee $CMAKE_KEYRING >/dev/null
-          echo "deb [signed-by=$CMAKE_KEYRING] https://apt.kitware.com/ubuntu/ focal main" \
+          echo "deb [signed-by=$CMAKE_KEYRING] https://apt.kitware.com/ubuntu/ jammy main" \
             | sudo tee /etc/apt/sources.list.d/kitware.list >/dev/null
           sudo apt-get update
           rm $CMAKE_KEYRING

README.md

@@ -2,7 +2,7 @@
 # pressio-tutorials
 
 This repository contains tutorials covering
-the [pressio C++ library](https://pressio.github.io/pressio/html/index.html).
+the [pressio-rom C++ library](https://pressio.github.io/pressio-rom/html/index.html).
 
 
 Click below to checkout the documentation:

docs/source/build.rst

@@ -50,7 +50,7 @@ More details on dependencies
 
 The tutorials have the following dependencies:
 
-- pressio C++ library: contains the C++ code that this tutorials repo convers
+- pressio-rom C++ library: contains the C++ code that this tutorials repo convers
 - pressio-demoapps: provides a suite of physics problems that are used in the tutorials to demonstrate the functionalities of pressio
 - Eigen: is the library used by pressio-demoapps
 - Python: is used in pressio-demoapps to implement all the ROM workflow drivers

docs/source/endtoend/readthisfirst.rst

@@ -1,11 +1,11 @@
 Start reading here
 ==================
 
-Describing how to use pressio for ROMs cannot be simply
+Describing how to use pressio-rom for ROMs cannot be simply
 boiled down to presenting the API, because setting up, running
 and processing a ROM involves several steps.
 We believe the best way to understand these steps and also
-what pressio offers in this context is via demos where the logical sequence
+what pressio-rom offers in this context is via demos where the logical sequence
 of steps is presented and explained.
 To this end, we have developed a workflow-based framework where
 one can *express* what to do, and the framework helps
@@ -19,7 +19,7 @@ Key features
 - each demo is defined via a yaml workflow file (`example <swe_galerkin_default.html#workflow-file>`__),
   which is used by the `driver scripts <https://github.com/Pressio/pressio-tutorials/tree/develop/end-to-end-roms>`__ we provide to execute that demo
 
-- one can easily extend the framework by adding new ROM methods in pressio or account
+- one can easily extend the framework by adding new ROM methods in pressio-rom or account
   for variations in how each step is run
 
 - pressio-demoapps: for the end-to-end demos we rely on pressio-demoapps,
@@ -33,7 +33,7 @@ Outcomes
 --------
 
 - by reading these end-to-end demos you should be able to understand
-  the various steps and how these steps map to pressio code
+  the various steps and how these steps map to pressio-rom code
 
 - you can easily explore the impact of changing the parameter spaces,
   or the basis size by just changing the workflow file and rerunning

docs/source/index.rst

@@ -4,7 +4,7 @@
 Pressio Tutorials
 =====================
 
-Tutorials suite for the `pressio C++ library <https://pressio.github.io/pressio>`_.
+Tutorials suite for the `pressio-rom C++ library <https://pressio.github.io/pressio-rom>`_.
 
 
 Scope and Motivation
@@ -15,15 +15,15 @@ reduced-order models (ROMs), which is a strongly multidisciplinary topic.
 Working on a production-level ROM capability inevitably means touching
 multiple fields, ranging from, e.g., linear algebra, nonlinear solvers
 and optimization, to time integration, generic programming, and distributed computing/HPC.
-This is clearly reflected in the `structure of pressio <https://pressio.github.io/pressio>`__:
+This is clearly reflected in the `structure of pressio-rom <https://pressio.github.io/pressio-rom>`__:
 each component handles a specific capability and depends
 on the ones below it. This allows users to use a component directly, but, as a whole,
-the full stack constitutes the foundation of the top-level ``pressio/rom``.
+the full stack constitutes the foundation of the top-level ``pressio-rom/rom``.
 
-Describing how to use pressio for ROMs cannot be simply reduced to presenting the API.
+Describing how to use Pressio for ROMs cannot be simply reduced to presenting the API.
 Several steps are involved, and the best way to understand them is via examples.
 Therefore, these tutorials are designed to show how to *integrate* various
-capabilities of pressio to do something meaningful, as well as unveil
+capabilities of Pressio to do something meaningful, as well as unveil
 some details that might not be obvious, and are organized into these sections:
 
 1. End-to-end ROMs using pressio-demoapps