Doc: BLAST-WarpX/warpx Links (BLAST-WarpX#5757)

Replace links from ECP-WarpX to BLAST-WarpX.

Note that the new repo name will be lowercase, as is common and sensible
(for the git dir it creates locally for developers).

Author: ax3l

.azure-pipelines.yml

@@ -116,7 +116,7 @@ jobs:
       python3 -m pip cache purge
       # external repositories required for test analysis
       cd ..
-      git clone --depth 1 https://github.com/ECP-WarpX/warpx-data.git
+      git clone --depth 1 https://github.com/BLAST-WarpX/warpx-data.git
       # TODO select only specific datasets?
       git clone --depth 1 https://github.com/openPMD/openPMD-example-datasets.git
       cd -

.github/ISSUE_TEMPLATE/blank_issue.md

@@ -6,9 +6,9 @@ labels: [question]
 
 Are you here because you have something to report that is neither a bug, a new feature, nor an installation problem?
 
-Before opening this issue, consider opening a [discussion](https://github.com/ECP-WarpX/WarpX/discussions) instead!
+Before opening this issue, consider opening a [discussion](https://github.com/BLAST-WarpX/warpx/discussions) instead!
 
 Issues are used to report bugs, installation problems or to request new features.
 Discussions are used to ask more open-ended questions, brainstorm, ask our feedback, etc.
 
-You can find more details on how to use issues and discussions [here](https://github.com/ECP-WarpX/WarpX/blob/development/CONTRIBUTING.rst).
+You can find more details on how to use issues and discussions [here](https://github.com/BLAST-WarpX/warpx/blob/development/CONTRIBUTING.rst).

.github/workflows/clang_sanitizers.yml

@@ -152,7 +152,7 @@ jobs:
         mpirun -n 2 ./build/bin/warpx.2d Examples/Physics_applications/laser_acceleration/inputs_base_2d warpx.serialize_initial_conditions = 0
         mpirun -n 2 ./build/bin/warpx.3d Examples/Physics_applications/laser_acceleration/inputs_base_3d warpx.serialize_initial_conditions = 0
 
-        git clone https://github.com/ECP-WarpX/warpx-data ../warpx-data
+        git clone https://github.com/BLAST-WarpX/warpx-data ../warpx-data
         cd Examples/Tests/embedded_circle
 
         ulimit -c unlimited

.github/workflows/dependencies/dpcpp.sh

@@ -26,7 +26,7 @@ sudo apt-get update
 
 df -h
 # Install and reduce disk space
-# https://github.com/ECP-WarpX/WarpX/pull/1566#issuecomment-790934878
+# https://github.com/BLAST-WarpX/warpx/pull/1566#issuecomment-790934878
 
 # try apt install up to five times, to avoid connection splits
 # FIXME install latest version of IntelLLVM, Intel MKL

.github/workflows/intel.yml

@@ -82,7 +82,7 @@ jobs:
     runs-on: ubuntu-20.04
     # Since 2021.4.0, AMReX_GpuUtility.H: error: comparison with NaN always evaluates to false in fast floating point modes
     # oneAPI 2022.2.0 hangs for -O2 and higher:
-    #   https://github.com/ECP-WarpX/WarpX/issues/3442
+    #   https://github.com/BLAST-WarpX/warpx/issues/3442
     env:
       CXXFLAGS: "-Werror -Wno-error=pass-failed -Wno-tautological-constant-compare"
     # For oneAPI, Ninja is slower than the default:
@@ -147,7 +147,7 @@ jobs:
     runs-on: ubuntu-20.04
     # Since 2021.4.0, AMReX_GpuUtility.H: error: comparison with NaN always evaluates to false in fast floating point modes
     # oneAPI 2022.2.0 hangs for -O2 and higher:
-    #   https://github.com/ECP-WarpX/WarpX/issues/3442
+    #   https://github.com/BLAST-WarpX/warpx/issues/3442
     env:
       CXXFLAGS: "-Werror -Wno-tautological-constant-compare"
     # For oneAPI, Ninja is slower than the default:

CONTRIBUTING.rst

@@ -19,24 +19,24 @@ What to do when
 Issues
 """"""
 
-`Issues <https://github.com/ECP-WarpX/WarpX/issues>`__ are used to track tasks that the contributors and/or maintainers can work on.
+`Issues <https://github.com/BLAST-WarpX/warpx/issues>`__ are used to track tasks that the contributors and/or maintainers can work on.
 Use issues for reporting bugs or installation problems and for requesting new features.
 
-If you've found a bug and wish to report it, first search the open issues and `pull requests <https://github.com/ECP-WarpX/WarpX/pulls>`__ to see if someone else has already reported the same thing.
+If you've found a bug and wish to report it, first search the open issues and `pull requests <https://github.com/BLAST-WarpX/warpx/pulls>`__ to see if someone else has already reported the same thing.
 If it's something new, open an issue using a template.
 We'll use the issue to address the problem you've encountered.
 
 Discussions
 """""""""""
 
-`Discussions <https://github.com/ECP-WarpX/WarpX/discussions>`__ are for open-ended conversations, general questions, brainstorming ideas.
+`Discussions <https://github.com/BLAST-WarpX/warpx/discussions>`__ are for open-ended conversations, general questions, brainstorming ideas.
 Please, use discussions if you want to ask us something that is not technically a bug or a feature.
 Feel free to ping us there!
 
 Pull Requests (PRs)
 """""""""""""""""""
 
-Open a `pull request <https://github.com/ECP-WarpX/WarpX/pulls>`__ if you want to add a new feature yourself.
+Open a `pull request <https://github.com/BLAST-WarpX/warpx/pulls>`__ if you want to add a new feature yourself.
 Follow the guide below for more details.
 
 
@@ -58,7 +58,7 @@ First, let's setup your Git environment and GitHub account.
 Make your own fork
 ^^^^^^^^^^^^^^^^^^
 
-First, fork the WarpX `"mainline" repo on GitHub <https://github.com/ECP-WarpX/WarpX>`__ by pressing the *Fork* button on the top right of the page.
+First, fork the WarpX `"mainline" repo on GitHub <https://github.com/BLAST-WarpX/warpx>`__ by pressing the *Fork* button on the top right of the page.
 A fork is a copy of WarpX on GitHub, which is under your full control.
 
 Then, we create local copies, for development:
@@ -67,7 +67,7 @@ Then, we create local copies, for development:
 
    # Clone the mainline WarpX source code to your local computer.
    # You cannot write to this repository, but you can read from it.
-   git clone [email protected]:ECP-WarpX/WarpX.git
+   git clone [email protected]:BLAST-WarpX/warpx.git
    cd WarpX
 
    # rename what we just cloned: call it "mainline"

Docs/Doxygen/main.dox

@@ -17,7 +17,7 @@
   It supports many features including Perfectly-Matched Layers (PML),
   mesh refinement, and the boosted-frame technique.
   WarpX is freely available on Github at
-  <a href="https://github.com/ECP-WarpX/WarpX">ECP-WarpX/WarpX</a>
+  <a href="https://github.com/BLAST-WarpX/warpx">BLAST-WarpX/warpx</a>
 
   WarpX is developed at LBNL in DOE's Exascale Computing Project and
   receives essential contributions from many collaborators, especially
@@ -36,7 +36,7 @@
   \subsection development_of_warpx Development
 
   All of WarpX' development is done in the GitHub repository under the
-  <a href="https://github.com/ECP-WarpX/WarpX/tree/development">
+  <a href="https://github.com/BLAST-WarpX/warpx/tree/development">
   development branch</a>; anyone can see the latest updates. A monthly release is
   tagged at the beginning of each month.
 
@@ -48,13 +48,13 @@
   Any level of changes are welcome: documentation, bug fixes,
   new test problems, new solvers, etc.
   For more complex projects, consider opening an
-  <a href="https://github.com/ECP-WarpX/WarpX/issues">issue</a>
+  <a href="https://github.com/BLAST-WarpX/warpx/issues">issue</a>
   first to coordinate development and gather feedback.
 
   To obtain help, simply post a
-  <a href="https://github.com/ECP-WarpX/WarpX/discussions">discussion</a>
+  <a href="https://github.com/BLAST-WarpX/warpx/discussions">discussion</a>
   or an
-  <a href="https://github.com/ECP-WarpX/WarpX/issues">issue</a>
+  <a href="https://github.com/BLAST-WarpX/warpx/issues">issue</a>
   on the WarpX GitHub page.
 
 */

Docs/source/acknowledge_us.rst

@@ -23,14 +23,14 @@ Please add the following sentence to your publications, it helps contributors ke
 
 **Plain text:**
 
-  This research used the open-source particle-in-cell code WarpX https://github.com/ECP-WarpX/WarpX. Primary WarpX contributors are with LBNL, LLNL, CEA-LIDYL, SLAC, DESY, CERN, Helion Energy, and TAE Technologies. We acknowledge all WarpX contributors.
+  This research used the open-source particle-in-cell code WarpX https://github.com/BLAST-WarpX/warpx. Primary WarpX contributors are with LBNL, LLNL, CEA-LIDYL, SLAC, DESY, CERN, Helion Energy, and TAE Technologies. We acknowledge all WarpX contributors.
 
 **LaTeX:**
 
 .. code-block:: latex
 
   \usepackage{hyperref}
-  This research used the open-source particle-in-cell code WarpX \url{https://github.com/ECP-WarpX/WarpX}.
+  This research used the open-source particle-in-cell code WarpX \url{https://github.com/BLAST-WarpX/warpx}.
   Primary WarpX contributors are with LBNL, LLNL, CEA-LIDYL, SLAC, DESY, CERN, Helion Energy, and TAE Technologies.
   We acknowledge all WarpX contributors.
 

Docs/source/dataanalysis/paraview.rst

@@ -36,7 +36,7 @@ For openPMD output, WarpX automatically creates an ``.pmd`` file per diagnostics
 
 .. warning::
 
-   `WarpX issue 21162 <https://github.com/ECP-WarpX/WarpX/issues/1803>`__:
+   `WarpX issue 21162 <https://github.com/BLAST-WarpX/warpx/issues/1803>`__:
    We currently load WarpX field data with a rotation.
    Please apply rotation of ``0 -90 0`` to mesh data.
 

Docs/source/dataanalysis/sensei.rst

@@ -250,7 +250,7 @@ First, log into cori and clone the git repo's.
    cd $SCRATCH
    mkdir warpx
    cd warpx/
-   git clone https://github.com/ECP-WarpX/WarpX.git WarpX-libsim
+   git clone https://github.com/BLAST-WarpX/warpx.git WarpX-libsim
    git clone https://github.com/AMReX-Codes/amrex
    git clone https://github.com/ECP-WarpX/picsar.git
    cd WarpX-libsim
@@ -301,7 +301,7 @@ First, log into cori and clone the git repo's.
    cd $SCRATCH
    mkdir warpx
    cd warpx/
-   git clone https://github.com/ECP-WarpX/WarpX.git WarpX-catalyst
+   git clone https://github.com/BLAST-WarpX/warpx.git WarpX-catalyst
    git clone --branch development https://github.com/AMReX-Codes/amrex
    git clone https://github.com/ECP-WarpX/picsar.git
    cd WarpX-catalyst