diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index c75ec16..02bce65 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -41,4 +41,4 @@ jobs: with: github_token: ${{ secrets.GITHUB_TOKEN }} publish_dir: _build/html - cname: climate-cms.org + cname: coecms.github.io diff --git a/README.md b/README.md index 379c5ee..58efbb1 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ CMS Blog The blog is viewable here: -http://climate-cms.org +http://coecms.github.io See the jupyter-book docs for info on creating posts - https://jupyterbook.org/intro.html @@ -25,7 +25,7 @@ To create a new blog post: 1. Delete `branch` --- -The new blog post should appear within a few minutes at http://climate-cms.org +The new blog post should appear within a few minutes at http://coecms.github.io If it doesn't, check under "Github Pages" here for error messages: diff --git a/posts/2021-11-02-pyproj-regrid.ipynb b/posts/2021-11-02-pyproj-regrid.ipynb index 75d8be1..6c2d9ee 100644 --- a/posts/2021-11-02-pyproj-regrid.ipynb +++ b/posts/2021-11-02-pyproj-regrid.ipynb @@ -7,7 +7,7 @@ "# Regridding from one coordinate system to another with pyproj\n", "**Aidan Heerdegen, CLEX CMS**\n", "\n", - "This post follows on from a [previous post](http://climate-cms.org/2021/10/01/pyproj.html) which covered converting between coordinate systems with [pyproj](https://pyproj4.github.io/pyproj/stable/).\n", + "This post follows on from a [previous post](http://coecms.github.io/2021/10/01/pyproj.html) which covered converting between coordinate systems with [pyproj](https://pyproj4.github.io/pyproj/stable/).\n", "\n", "Some cells have `jupyter` magic `%%time` commands for no other reason than to give an indication of how long these operations typically take. Having an expectation of how long something should take is a useful metric for knowing when something is not working correctly.\n", "\n" diff --git a/posts/2022-04-26-storage-where-what-why-how.md b/posts/2022-04-26-storage-where-what-why-how.md index 368d192..b1591f9 100644 --- a/posts/2022-04-26-storage-where-what-why-how.md +++ b/posts/2022-04-26-storage-where-what-why-how.md @@ -37,7 +37,7 @@ To query usage for an on-disk file system, NCI provides commands which report on nci-files-report --group project_id ``` -CMS has put in place a dashboard for visualising a range of accounting statistics for CLEX. Please contact CMS for the passowrd to access [this server](http://climate-cms.org/dashboard/) +CMS has put in place a dashboard for visualising a range of accounting statistics for CLEX. Please contact CMS for the passowrd to access [this server](http://coecms.github.io/dashboard/) ![Dashboard](../images/dashboard_w40.PNG "Dashboard") diff --git a/posts/2022-10-26-Data-Quarantine.md b/posts/2022-10-26-Data-Quarantine.md index 5a160e0..ed2431c 100644 --- a/posts/2022-10-26-Data-Quarantine.md +++ b/posts/2022-10-26-Data-Quarantine.md @@ -64,6 +64,6 @@ For more information on these commands: https://nci.org.au/sites/default/files/ If there is data that you need to keep long term then there are a couple of things that need to be considered. You can publish your data if you have processed a lot of raw data and it doesn't already exist on the NCI system or you can move data to the tape system for long-term storage. -Please have a look at this blog: https://climate-cms.org/posts/2022-04-26-storage-where-what-why-how.html +Please have a look at this blog: https://coecms.github.io/posts/2022-04-26-storage-where-what-why-how.html Data can exist for longer on gdata than on scratch but for longer term you will need to decide on a method from the above link. \ No newline at end of file diff --git a/posts/2023-02-27-introducing-new-conda.md b/posts/2023-02-27-introducing-new-conda.md index 14f6651..3903512 100644 --- a/posts/2023-02-27-introducing-new-conda.md +++ b/posts/2023-02-27-introducing-new-conda.md @@ -56,7 +56,7 @@ The typical `analysis3` workflow comprising python scripts or jupyter notebooks ## Key differences between `conda_concept` and `conda` The key difference of the approach used by the `conda_concept` environments is the use of singularity's ability to manage squashfs file systems. A squashfs can be thought of a something like a tar file that can be accessed as if it were an entirely new file system. The obvious advantage of placing a conda environment in a squashfs is that it reduces the file count of the entire environment on `/g/data` to one. -The drawback of using singularity to manage the squashfs is that containers have a number of restrictions placed on them for security reasons, (e.g. the `newgrp`, `switchproj` and `qcat` commands cannot be run from inside a container). Because of this, once the module is loaded, the user is kept out of the containerised environment unless a command that exists inside the container is run. This is accomplished by the use of a 'launcher' script that runs `singularity` and executes the command from within the container. For more details on this, see the [CMS Wiki page](https://climate-cms.org/cms-wiki/resources/resources-conda-setup.html). This leads to known issues with the environment. +The drawback of using singularity to manage the squashfs is that containers have a number of restrictions placed on them for security reasons, (e.g. the `newgrp`, `switchproj` and `qcat` commands cannot be run from inside a container). Because of this, once the module is loaded, the user is kept out of the containerised environment unless a command that exists inside the container is run. This is accomplished by the use of a 'launcher' script that runs `singularity` and executes the command from within the container. For more details on this, see the [CMS Wiki page](https://coecms.github.io/cms-wiki/resources/resources-conda-setup.html). This leads to known issues with the environment. ### Known Issues * The path to the python executable within a conda environment cannot be used as the shbang (e.g. `#!/g/data/hh5/public/apps/cms_conda/envs/analysis3/bin/python3` on the first line of script) as the executable does not exist outside of the container. Instead, use the launcher script symlink: `#!/g/data/hh5/public/apps/cms_conda_scripts/analysis3.d/bin/python3`, which launches the container and runs the script from inside of it. diff --git a/posts/2023-07-05-select-region-shapefile.ipynb b/posts/2023-07-05-select-region-shapefile.ipynb index f7a4515..d4df884 100644 --- a/posts/2023-07-05-select-region-shapefile.ipynb +++ b/posts/2023-07-05-select-region-shapefile.ipynb @@ -1953,7 +1953,7 @@ "id": "55f86961-a6e6-427d-99a2-7cee39a3530a", "metadata": {}, "source": [ - "We open the files using preprocess argument to select our region of interest from each file before concatenating them. See this [blog](https://climate-cms.org/posts/2023-06-22-mfdataset-preprocess.html) for more information on preprocess." + "We open the files using preprocess argument to select our region of interest from each file before concatenating them. See this [blog](https://coecms.github.io/posts/2023-06-22-mfdataset-preprocess.html) for more information on preprocess." ] }, { diff --git a/posts/2024-06-05-mixing-python-envs.md b/posts/2024-06-05-mixing-python-envs.md index d008312..e8a6b8b 100644 --- a/posts/2024-06-05-mixing-python-envs.md +++ b/posts/2024-06-05-mixing-python-envs.md @@ -49,7 +49,7 @@ reproducibility is not necessary. The downside with this approach is that it can is updated to every 3 months as new environments are released. For example, if you load `conda/analysis3` today, you'll get the `conda/analysis3-24.01` environment. If you were to load the same module a couple of months from now, you'll get the `conda/analysis3-24.04` environment. Our policies around updating the conda environments -can be found [here](https://climate-cms.org/cms-wiki/services/services-conda.html). As time goes on, your +can be found [here](https://coecms.github.io/cms-wiki/services/services-conda.html). As time goes on, your locally installed package will get further and further out of date, and could potentially conflict with newer packages installed in updated analysis environments.