diff --git a/content/404.md b/content/404.md index c7a40e5b023..1564315ac71 100644 --- a/content/404.md +++ b/content/404.md @@ -3,12 +3,14 @@ title: "Page Not Found" search: exclude hide_sidebar: true permalink: /404.html +aliases: + - /404.html editme: false ---
-![404 - page not found](images/404.png) +![404 - page not found](/images/404.png)
diff --git a/content/_index.md b/content/_index.md new file mode 100644 index 00000000000..109729a8088 --- /dev/null +++ b/content/_index.md @@ -0,0 +1,13 @@ +--- +title: preCICE - The Coupling Library +keywords: +toc: false +hide_sidebar: true +topnav: topnav +cascade: + layout: page + comments: false + search: true + sidebar: home_sidebar + topnav: topnav +--- diff --git a/content/about.md b/content/about.md new file mode 100644 index 00000000000..044deb7ceb5 --- /dev/null +++ b/content/about.md @@ -0,0 +1,59 @@ +--- +title: About the preCICE project +permalink: about.html +aliases: + - /about.html + - /timeline/ +keywords: about, project leaders, timeline, impressum, legal +summary: +hide_sidebar: true +toc: false +editme: false +redirect_from: + - /timeline/ +--- + +## Development + +preCICE is developed in the groups of [Benjamin Uekermann (Usability and Sustainability of Simulation Software)](https://www.ipvs.uni-stuttgart.de/departments/us3/) and [Miriam Schulte (Simulation of Large Systems)](https://www.ipvs.uni-stuttgart.de/departments/sgs/) at the University of Stuttgart and in the group of [Hans-Joachim Bungartz (Scientific Computing in Computer Science)](https://www.cs.cit.tum.de/en/sccs/home/) at the Technical University of Munich. [Support contracts](community-support-precice.html) are offered through [TTI GmbH](https://www.tti-stuttgart.de/). + +
+preCICE contributors +
+ +For the full list of contributors to preCICE please see our [community page](community-contributors). + +The conceptual ideas of preCICE are not completely new. preCICE is an advancement of FSI*ce, developed by Markus Brenk. + +## Planning and development of precice.org + +The website in its current form was planned and implemented by CH Lorenz Research and Innovation Consulting together with the preCICE team. For more information contact [Christopher Lorenz](https://christopherlorenz.com) at christopher[dot]lorenz[at]chlorenz[dot]ug. + +## Funding + +{{< funding >}} + +## Prince XML + +We use a non-commercial license of [Prince XML](http://www.princexml.com/) to generate the PDF version of the documentation. For more information see our [meta documentation page](docs-meta-publish-to-pdf.html). + +## Website analytics + +We use the open-source and privacy-friendly analytics service [Plausible](https://plausible.io/). Everyone can see the [analytics for this website](https://plausible.io/precice.org). + +## Impressum + +This website is maintained by + +Benjamin Uekermann - +Universität Stuttgart - +Universitätsstraße 38 - +70569 Stuttgart + +## Privacy + +You can find the preCICE [privacy policy here](privacy.html). + +![preCICE doughnuts](/images/doughnuts.jpg) + +preCICE is tasty because it is made with love by its contributors. diff --git a/content/about/_index.md b/content/about/_index.md deleted file mode 100644 index e69de29bb2d..00000000000 diff --git a/content/about/overview.md b/content/about/overview.md deleted file mode 100644 index ade1200f8a0..00000000000 --- a/content/about/overview.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -title: About the preCICE project -permalink: about.html -keywords: about, project leaders, timeline, impressum, legal -summary: -hide_sidebar: true -toc: false -editme: false -redirect_from: - - /about/ - - /timeline/ ---- - -## Development - -preCICE is developed in the groups of [Benjamin Uekermann (Usability and Sustainability of Simulation Software)](https://www.ipvs.uni-stuttgart.de/departments/us3/) and [Miriam Schulte (Simulation of Large Systems)](https://www.ipvs.uni-stuttgart.de/departments/sgs/) at the University of Stuttgart and in the group of [Hans-Joachim Bungartz (Scientific Computing in Computer Science)](https://www.cs.cit.tum.de/en/sccs/home/) at the Technical University of Munich. [Support contracts](community-support-precice.html) are offered through [TTI GmbH](https://www.tti-stuttgart.de/). - -
-preCICE contributors -
- -For the full list of contributors to preCICE please see our [community page](community-contributors). - - - -The conceptual ideas of preCICE are not completely new. preCICE is an advancement of FSI*ce, developed by Markus Brenk. - -## Planning and development of precice.org - -The website in its current form was planned and implemented by CH Lorenz Research and Innovation Consulting together with the preCICE team. For more information contact [Christopher Lorenz](https://christopherlorenz.com) at christopher[dot]lorenz[at]chlorenz[dot]ug. - -## Funding - -
-{% for item in site.data.funding %} -
-
-
- - - {{ item.title }} - - -
-
- - Logo - -
-
- {% if item.description %}

{{ item.description }}

{% endif %} - {% if item.number %}

Funding number: {{ item.number }}

{% endif %} -

Years running: {{ item.period }}

-
-
-
-
-
-{% endfor %} -
- -## Prince XML - -We use a non-commercial license of [Prince XML](http://www.princexml.com/) to generate the PDF version of the documentation. For more information see our [meta documentation page](docs-meta-publish-to-pdf.html). - -## Website analytics - -We use the open-source and privacy-friendly analytics service [Plausible](https://plausible.io/). Everyone can see the [analytics for this website](https://plausible.io/precice.org). - -## Impressum - -This website is maintained by - -Benjamin Uekermann - -Universität Stuttgart - -Universitätsstraße 38 - -70569 Stuttgart - -## Privacy - -You can find the preCICE [privacy policy here](privacy.html). - -![preCICE doughnuts](images/doughnuts.jpg) - -preCICE is tasty because it is made with love by its contributors. diff --git a/content/community/_index.md b/content/community/_index.md index e69de29bb2d..cc84a6dff95 100644 --- a/content/community/_index.md +++ b/content/community/_index.md @@ -0,0 +1,10 @@ +--- +title: Community +cascade: + layout: page + comments: false + search: true + sidebar: community_sidebar + topnav: topnav + toc: true +--- diff --git a/content/community/channels.md b/content/community/channels.md index cab4f650f7e..e001a8e1584 100644 --- a/content/community/channels.md +++ b/content/community/channels.md @@ -1,6 +1,9 @@ --- title: Community channels permalink: community-channels.html +aliases: + - /community-channels.html + - /resources/ keywords: contact, follow, social, stay in touch, news, videos, YouTube, Gitter, newsletter, newsfeed, mailing list, mastodon, bluesky summary: toc: false @@ -15,7 +18,7 @@ We have all been there: you start using a new tool, only to find out that you do You can find us on our [preCICE forum on Discourse](https://precice.discourse.group/), which is great for structured discussions that help everyone. We try our best to help everyone, but this approach does not scale. We would be very happy if you also try to help others - only together way we can build a helping and welcoming online community! -For quick orientation questions, feel free to drop us a short message on the [preCICE Matrix chatroom]({{ site.matrix_url }}). +For quick orientation questions, feel free to drop us a short message on the [preCICE Matrix chatroom](https://matrix.to/#/#precice_lobby:gitter.im?web-instance%5Belement.io%5D=app.gitter.im). ## I want to stay up-to-date diff --git a/content/community/contribute/contribute-to-precice.md b/content/community/contribute/contribute-to-precice.md index e3146198d6d..6cb8282ab8a 100644 --- a/content/community/contribute/contribute-to-precice.md +++ b/content/community/contribute/contribute-to-precice.md @@ -1,6 +1,8 @@ --- title: Contribute to preCICE permalink: community-contribute-to-precice.html +aliases: + - /community-contribute-to-precice.html keywords: contribute, develop summary: toc: true @@ -72,9 +74,9 @@ or to demonstrate a new feature. We welcome contributions to our [tutorials repo and we will discuss it with you over a few [review](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request) iterations. If you roughly follow the guidelines in this section, your contribution could be merged very quickly. Since we aim to maintain and update all tutorials, it is important for us that every tutorial merged follows the same structure and conventions. -{% tip %} +{{< tip >}} Get in touch with us early and we will be very happy to help you with every step! Open a first draft Pull Request on GitHub and we can together bring it into a fitting shape. -{% endtip %} +{{< /tip >}} First time working with Git? Watch a [lecture on Git](https://missing.csail.mit.edu/2020/version-control/). @@ -147,9 +149,9 @@ In the `README.md` file, following the general structure of the existing tutoria - an example picture or video of the results. - Don't forget to adapt the `permalink:` field in the beginning of the file. -{% note %} -If you add a complete new tutorial case, the case also needs to be added to the [tutorials sidebar](https://github.com/precice/precice.github.io/blob/master/_data/sidebars/tutorial_sidebar.yml) on the [tutorials website section](tutorials.html). Please open a pull request to the [website repository](https://github.com/precice/precice.github.io). -{% endnote %} +{{< note >}} +If you add a complete new tutorial case, also add its Hugo module mounts to `config/_default/module.toml` and its permalink to the [tutorials sidebar](https://github.com/precice/precice.github.io/blob/master/data/sidebars/tutorials_sidebar.yml) in a pull request to the [website repository](https://github.com/precice/precice.github.io). +{{< /note >}} ### The metadata file @@ -191,7 +193,6 @@ After testing and merging, we will generate the reference results of the new tes - Mesh names start with the participant/domain name, e.g. `Fluid-Mesh`. - Mesh names of participants with multiple interfaces contain the interface in the mesh name, e.g. `Fluid-Upstream-Mesh`. For meshes on which it is important to distinguish between face centers and face nodes, the modifier comes at the end, e.g. `Fluid-Upstream-Mesh-Centers`. - Watchpoint names should be describing the point, not be a generic name. -- Images need to be named as `tutorials--.png` to be correctly displayed on the website. You can then refer to them as `![title](images/tutorials--.png)`. Subdirectories are not allowed. ### Open a pull request @@ -215,14 +216,20 @@ We automate many checks with [GitHub actions](https://github.com/features/action ### Adding a new tutorial to the website -The content of the tutorials is sourced from the develop branch of the tutorials repository, which is specified in the `.gitmodules` file of the website repository. Hence, in general, anything merged to develop in the tutorials appears on the website. Consider putting some `note` [alert box](docs-meta-cheatsheet.html#alerts) on top of your new tutorial page to describe any unreleased requirements. +Tutorial content is imported from the tutorials repository with Hugo Modules. +The `Update Hugo modules` workflow records the selected tutorial revision in +`go.mod` and `go.sum`. Consider putting a `note` +[alert box](docs-meta-cheatsheet.html#alerts) on top of your new tutorial page +to describe any unreleased requirements. -*New* tutorials will not directly appear on the website, but they need some additional steps. After merging to the tutorials develop, open a pull request with the following changes in the [website repository](https://github.com/precice/precice.github.io) ([example](https://github.com/precice/precice.github.io/pull/275)): +New tutorials will not directly appear on the website. After merging a new +tutorial, open a pull request with these changes in the +[website repository](https://github.com/precice/precice.github.io): -1. Trigger the [update submodules workflow](https://github.com/precice/precice.github.io/actions/workflows/update-submodules.yml) and, after it completes, create a new branch and pull request (this may also happen automatically, or someone from the preCICE team may have to do it for you). -2. Edit the [`_config.yml` file](https://github.com/precice/precice.github.io/blob/master/_config.yml) to append the directory name of your tutorial under `subprojects:`. -3. Edit the [tutorials sidebar](https://github.com/precice/precice.github.io/blob/master/_data/sidebars/tutorial_sidebar.yml) to add your tutorial permalink (defined in the heading of the `README.md` you created) to a fitting place, next to a similar tutorial. -4. Edit the [tutorials landing page](https://github.com/precice/precice.github.io/blob/master/content/tutorials/overview.md) to add your tutorial to the overview. +1. Add the tutorial's Hugo module mounts to `config/_default/module.toml`. +2. Add its permalink to a fitting place in the + [tutorials sidebar](https://github.com/precice/precice.github.io/blob/master/data/sidebars/tutorials_sidebar.yml), next to a similar tutorial. +3. Edit the [tutorials landing page](https://github.com/precice/precice.github.io/blob/master/content/tutorials/overview.md) to add the tutorial to the overview. After your PR gets reviewed, approved, and merged, the website will be built automatically, and your tutorial will appear online in a couple of minutes. @@ -236,13 +243,13 @@ You can pick up issues that you would like to work on from any repository you li Look for [contributing guidelines](https://github.com/precice/precice/blob/develop/docs/CONTRIBUTING.md) in each repository. The [developer documentation](dev-docs-overview.html) will also be useful. -{% tip %} +{{< tip >}} Read on our [Roadmap](fundamentals-roadmap.html) what is already in our to-do list before starting to write large parts of code. -{% endtip %} +{{< /tip >}} -{% tip %} +{{< tip >}} There are [guidelines for adapters](community-guidelines-adapters.html) and [guidelines for application cases](community-guidelines-application-cases.html). -{% endtip %} +{{< /tip >}} ## Helping other users diff --git a/content/community/contribute/open-projects.md b/content/community/contribute/open-projects.md index 6ceba073016..396af727c1e 100644 --- a/content/community/contribute/open-projects.md +++ b/content/community/contribute/open-projects.md @@ -4,6 +4,9 @@ keywords: contribute, GSoC, google summer of code, student summary: Open opportunities for contributing to preCICE toc: true permalink: community-contribute-open-projects.html +aliases: + - /community-contribute-open-projects.html + - /gsoc/ redirect_from: - /gsoc/ --- @@ -32,9 +35,9 @@ If you want to contribute with a student project (typically a thesis), see the [ This page highlights a few specific projects that are not directly suitable for a thesis ([thesis-suitable issues in the core library](https://github.com/precice/precice/issues?q=is%3Aissue%20state%3Aopen%20label%3Athesis)), but are also a bit more than a [good first issue](https://github.com/precice/precice/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22). Some of these projects we advertise publicly, in programs such as the Google Summer of Code. -{% tip %} +{{< tip >}} Are you looking for or offering a thesis / PhD / other related job? Have a look also at [our forum](https://precice.discourse.group/c/jobs/13). -{% endtip %} +{{< /tip >}} ## Google Summer of Code (GSoC) @@ -54,16 +57,16 @@ Additionally, show us what you have tried already (see "entry test" in each proj We will contact you via replies and/or private messages in the forum, to find out together if these topics are a good fit. You can alternatively ask quick questions in the [Matrix chat](https://matrix.to/#/#precice_lobby:gitter.im?web-instance[element.io]=app.gitter.im). Don't miss the [guidelines](#general-guidelines) at the bottom of this page. -{% important %} +{{< important >}} We are a small project, and we are experiencing a spike of activity, which is very difficult to review next to the usual work. Please do not ask whether you can work on an issue - not without details. If you find something interesting to you that you feel it is clear enough for you to contribute, go ahead and submit a PR. We value quality higher than quantity. If you find something interesting, take your time and focus on it. We expect to work with the accepted GSoC participants in the summer. Our capacity to review external contributions before that is very limited. -{% endimportant %} +{{< /important >}} -{% important %} +{{< important >}} We have already received too many pull requests in the period before proposals open. For this reason, we have now restricted interactions with the preCICE repositories to collaborators. If you have not reached out so far, chances for selection are very small. -{% endimportant %} +{{< /important >}} ### Submitting proposals diff --git a/content/community/contributors.md b/content/community/contributors.md index 2c685a1bb27..c87939de075 100644 --- a/content/community/contributors.md +++ b/content/community/contributors.md @@ -1,6 +1,8 @@ --- title: Contributors permalink: community-contributors.html +aliases: + - /community-contributors.html keywords: contributors, developers, maintainers summary: toc: true @@ -8,33 +10,7 @@ toc: true ## Maintainers -
-{% assign dev_main = site.data.developer.main | sort: "name" %} -
-
-
    - {% for p in dev_main %} - -
    - {% if p.img %} - Portrait - {% endif %} -
    -
    -

    - {{ p.fullname }}
    - {{ p.institution }} -

    -
    -
      - {% if p.orcid %}
      • {% endif %} - {% if p.github %}
      • {% endif %} -
    - - {% endfor %} -
-
-
+{{< developer_list group="main" >}} If you are interested in joining the team of preCICE maintainers, please [contact Benjamin Uekermann](https://www.ipvs.uni-stuttgart.de/departments/us3/). @@ -42,52 +18,10 @@ If you are interested in joining the team of preCICE maintainers, please [contac Previous maintainers and their affiliation at the time of their last significant contribution. -
-{% assign dev_premain = site.data.developer.main-inactive | sort: "name" %} -
-
-
    - {% for p in dev_premain %} - -
    -

    - {{ p.fullname }}
    - {{ p.institution }} -

    -
    -
      - {% if p.orcid %}
      • {% endif %} - {% if p.github %}
      • {% endif %} -
    - - {% endfor %} -
-
-
+{{< developer_list group="main-inactive" >}} ## Further contributors Previous contributors and their affiliation at the time of their last significant contribution. -
-{% assign dev_contrib = site.data.developer.contributors | sort: "name" %} -
-
-
    - {% for p in dev_contrib %} - -
    -

    - {{ p.fullname }}
    - {{ p.institution }} -

    -
    -
      - {% if p.orcid %}
      • {% endif %} - {% if p.github %}
      • {% endif %} -
    - - {% endfor %} -
-
-
+{{< developer_list group="contributors" >}} diff --git a/content/community/minisymposia/eccomas-congress-2022.md b/content/community/minisymposia/eccomas-congress-2022.md index d451f767d59..74d66236057 100644 --- a/content/community/minisymposia/eccomas-congress-2022.md +++ b/content/community/minisymposia/eccomas-congress-2022.md @@ -3,6 +3,8 @@ title: ECCOMAS Congress 2022 keywords: 2022, ECCOMAS, event, events, minisymposium summary: permalink: eccomas-congress-2022.html +aliases: + - /eccomas-congress-2022.html toc: false --- diff --git a/content/community/minisymposia/eccomas-coupled-2019.md b/content/community/minisymposia/eccomas-coupled-2019.md index 320c0bcaa7a..adafa1ec65a 100644 --- a/content/community/minisymposia/eccomas-coupled-2019.md +++ b/content/community/minisymposia/eccomas-coupled-2019.md @@ -3,6 +3,8 @@ title: ECCOMAS Coupled Problems 2019 keywords: 2019, ECCOMAS, COUPLED, event, events, minisymposium summary: permalink: eccomas-coupled-2019.html +aliases: + - /eccomas-coupled-2019.html toc: false --- diff --git a/content/community/minisymposia/eccomas-coupled-2021.md b/content/community/minisymposia/eccomas-coupled-2021.md index 405bed358db..8a06b1d3103 100644 --- a/content/community/minisymposia/eccomas-coupled-2021.md +++ b/content/community/minisymposia/eccomas-coupled-2021.md @@ -3,6 +3,8 @@ title: ECCOMAS Coupled Problems 2021 keywords: 2021, ECCOMAS, COUPLED, event, events, minisymposium summary: permalink: eccomas-coupled-2021.html +aliases: + - /eccomas-coupled-2021.html toc: false --- diff --git a/content/community/minisymposia/eccomas-coupled-2023.md b/content/community/minisymposia/eccomas-coupled-2023.md index 20598e20bac..5cd9413af4b 100644 --- a/content/community/minisymposia/eccomas-coupled-2023.md +++ b/content/community/minisymposia/eccomas-coupled-2023.md @@ -3,6 +3,8 @@ title: ECCOMAS Coupled Problems 2023 keywords: 2023, ECCOMAS, COUPLED, event, events, minisymposium summary: permalink: eccomas-coupled-2023.html +aliases: + - /eccomas-coupled-2023.html toc: false --- diff --git a/content/community/minisymposia/eccomas-coupled-2025.md b/content/community/minisymposia/eccomas-coupled-2025.md index 3c2af1fe02d..a42208e9cc8 100644 --- a/content/community/minisymposia/eccomas-coupled-2025.md +++ b/content/community/minisymposia/eccomas-coupled-2025.md @@ -3,6 +3,8 @@ title: ECCOMAS Coupled Problems 2025 keywords: 2025, ECCOMAS, COUPLED, event, events, minisymposium summary: permalink: eccomas-coupled-2025.html +aliases: + - /eccomas-coupled-2025.html toc: false --- diff --git a/content/community/minisymposia/eccomas-eccm-ecfd-2018.md b/content/community/minisymposia/eccomas-eccm-ecfd-2018.md index d400e778a56..99e92b546fd 100644 --- a/content/community/minisymposia/eccomas-eccm-ecfd-2018.md +++ b/content/community/minisymposia/eccomas-eccm-ecfd-2018.md @@ -3,6 +3,8 @@ title: ECCOMAS ECCM ECFD 2018 keywords: 2018, ECCOMAS, event, events, minisymposium summary: permalink: eccomas-eccm-ecfd-2018.html +aliases: + - /eccomas-eccm-ecfd-2018.html toc: false --- diff --git a/content/community/minisymposia/iacm-wccm-2024.md b/content/community/minisymposia/iacm-wccm-2024.md index a0acc671d92..fe35a79dc84 100644 --- a/content/community/minisymposia/iacm-wccm-2024.md +++ b/content/community/minisymposia/iacm-wccm-2024.md @@ -3,6 +3,8 @@ title: iacm WCCM 2024 keywords: 2024, IACM, ECCOMAS, WCCM, event, events, minisymposium summary: permalink: iacm-wccm-2024.html +aliases: + - /iacm-wccm-2024.html toc: false --- diff --git a/content/community/minisymposia/wccm-2021.md b/content/community/minisymposia/wccm-2021.md index 8f62ac72e68..5e844c64751 100644 --- a/content/community/minisymposia/wccm-2021.md +++ b/content/community/minisymposia/wccm-2021.md @@ -3,6 +3,8 @@ title: ECCOMAS WCCM 2020 keywords: 2020, WCCM, ECCOMAS, event, events, minisymposium summary: permalink: community-events-wccm-eccomas-2020.html +aliases: + - /community-events-wccm-eccomas-2020.html toc: false --- @@ -14,9 +16,9 @@ The [ECCOMAS WCCM 2020](https://web.archive.org/web/20201203110253/https://www.w Thanks to the WCCM organizers, authors were given access to their recorded talks to be shared with the public. The links of the titles below lead to the recordings on SlideLive. -{% note %} +{{< note >}} If you gave a talk at the minisymposium, please contact us and we will include it in the list! -{% endnote %} +{{< /note >}} - 2067 - [An Introduction to the preCICE Coupling Library](https://slideslive.com/38944676) by Gerasimos Chourdakis - 2340 - [Adaptive Dynamic Meshes for Fully-Parallel Partitioned Multi-Physics in preCICE](https://slideslive.com/38944678) by Frédéric Simonis diff --git a/content/community/minisymposia/wccomas-wccm-2026.md b/content/community/minisymposia/wccomas-wccm-2026.md index 3c49e68512d..d890e30a0fc 100644 --- a/content/community/minisymposia/wccomas-wccm-2026.md +++ b/content/community/minisymposia/wccomas-wccm-2026.md @@ -3,6 +3,8 @@ title: ECCOMAS WCCM 2026 keywords: 2026, ECCOMAS, WCCM, event, events, minisymposium summary: permalink: eccomas-wccm-2026.html +aliases: + - /eccomas-wccm-2026.html toc: false --- diff --git a/content/community/overview.md b/content/community/overview.md index 47116813b8c..eaf2de3144f 100644 --- a/content/community/overview.md +++ b/content/community/overview.md @@ -1,19 +1,21 @@ --- title: Become part of the preCICE community permalink: community.html +aliases: + - /community.html keywords: summary: toc: false editme: true --- -preCICE Workshop banner +preCICE Workshop banner ## preCICE workshops Do you want to meet the community and learn what is new in preCICE? There is no better way than to join [one of our workshops](precice-workshop.html) or [trainings](community-training.html)! -preCICE Workshop group picture +preCICE Workshop group picture ## The preCICE forum @@ -30,12 +32,7 @@ There are different ways how to support preCICE and get priority support from th We have compiled a community showcase with several of the most impressive preCICE implementations. The range of application fields is diverse, including e.g. simulating the [temperatures on the moon](community-projects.html#simulation-of-temperatures-on-the-moon-with-thermos), the [biomechanics of the heart valve](community-projects.html#evaluation-of-heart-valve-biomechanics), [modelling wind in urban areas](community-projects.html#hybrid-simulation-methods-for-wind-modelling-in-urban-areas), and simulating [high impact loads on structures](community-projects.html#fsi-simulations-of-high-impact-loads-on-structures). You can find many more use cases on the [community stories page](community-projects.html). -{% assign testimonials = site.testimonials | reverse %} -{%- for testimonial in testimonials -%} -{%- if testimonial.img -%} -Overview of preCICE user stories -{%- endif -%} -{% endfor %} +{{< testimonial_avatars >}} ## Contributions to preCICE @@ -43,4 +40,4 @@ Since its first commit in 2008, preCICE has been developed by three generations Some of the people that have significantly contributed to repositories of preCICE on GitHub (arbitrary order): -{% include community_spotlight.html %} +{{< community_spotlight >}} diff --git a/content/community/projects.md b/content/community/projects.md index 1e959e9f846..998d7dbc1c4 100644 --- a/content/community/projects.md +++ b/content/community/projects.md @@ -1,6 +1,9 @@ --- title: Community stories permalink: community-projects.html +aliases: + - /community-projects.html + - /testimonials/ keywords: summary: toc: true @@ -8,37 +11,15 @@ redirect_from: /testimonials/ editme: false --- -{{site.data.alerts.note}} +{{< note >}} Do you use preCICE? We are always happy to hear about interesting projects that use preCICE. To add your project here, just fill the form and we will take care of the rest. -If you prefer, you can directly create a pull request to the website repository on GitHub (it is easy also if you don't yet have any GitHub experience!). A copy of a previous testimonial is a great starting point. Adjust it to your liking, and add a picture. +If you prefer, you can directly create a pull request to the website repository on GitHub (it is easy also if you don't yet have any GitHub experience!). A copy of a previous testimonial is a great starting point. Adjust it to your liking, and add a picture. A good example is this pull request.
-{{site.data.alerts.end}} +{{< /note >}}
-{% assign testimonials = site.testimonials | reverse %} -{% for testimonial in testimonials %} - -

{{ testimonial.title }}

- -
-
- -{{ testimonial.content }} -—**[{{ testimonial.author }}]({{ testimonial.author_link }})** -{{ testimonial.organisation }} - -
-
- -
-{{ testimonial.title }} -
{{ testimonial.title }}
-
- -
-
-{% endfor %} +{{< testimonials >}}
diff --git a/content/community/support-precice.md b/content/community/support-precice.md index 4e7e128778c..8a05c9de89d 100644 --- a/content/community/support-precice.md +++ b/content/community/support-precice.md @@ -1,6 +1,8 @@ --- title: You support preCICE – preCICE supports you permalink: community-support-precice.html +aliases: + - /community-support-precice.html keywords: support, priority support, private support, research project, industry, commercial, license, contracting, sub-contracting, service level agreement, NDA, price, on-site meeting, training summary: Support preCICE to help the software remain and grow. In return, the preCICE team supports your work. There are three different variants for such a collaboration. toc: true diff --git a/content/community/training.md b/content/community/training.md index fdbcdb8d47d..4e8dabd6e72 100644 --- a/content/community/training.md +++ b/content/community/training.md @@ -3,6 +3,8 @@ title: preCICE training keywords: workshop, teaching, support, api, implicit coupling, tools, data mapping, training summary: A hands-on introduction to preCICE, recommended for new users that want to learn how to couple their own codes and beyond. permalink: community-training.html +aliases: + - /community-training.html toc: true --- @@ -22,43 +24,43 @@ The course currently consists of four modules. Several more will follow. We couple two simple Python codes, discussing the basic methods of the preCICE API. -![Basics training: Configuration](images/training/training-basics.png) +![Basics training: Configuration](/images/training/training-basics.png) ### Tools We take a tour over available tools to configure, understand, and post-process preCICE simulations. More specifically, we have a look at the preCICE logger, config visualizer, mesh exports, and watchpoints of preCICE. We also discuss common tips for visualizing partitioned simulations in ParaView. -![Basics training: Tools](images/training/training-tools.png) +![Basics training: Tools](/images/training/training-tools.png) ### Implicit coupling We use a conjugate heat transfer scenario coupling OpenFOAM with Nutils to study implicit coupling, including acceleration methods. -![Basics training: Implicit coupling](images/training/training-implicit-coupling.png) +![Basics training: Implicit coupling](/images/training/training-implicit-coupling.png) ### Data mapping We explore aspects of accuracy and efficiency in data mapping, using [ASTE](tooling-aste.html). -![Basics training: Mapping](images/training/training-mapping.png) +![Basics training: Mapping](/images/training/training-mapping.png) ### Workflow for FSI simulations In this [community-contributed part of the course](https://github.com/precice/community-training/tree/main/fsi-workflow), we are going step by step through the process of creating a fluid-structure interaction simulation coupling CalculiX and OpenFOAM. We start by creating the meshes for both solvers, using FreeCAD and snappyHexMesh. We then setup and run single-physics simulations, before we couple them. -![Application training: FSI workflow](images/training/training-fsi.png) +![Application training: FSI workflow](/images/training/training-fsi.png) ### Parallelization and HPC workflows We parallelize the same Python codes used in the Basics module, we analyze the performance-related events, run partitioned simulations in parallel on SLURM-enabled systems, and look deeper into common performance-related pitfalls. -![HPC training: Tracing](images/training/training-hpc.png) +![HPC training: Tracing](/images/training/training-hpc.png) ### Macro-micro coupling We couple many micro simulations to a macro simulation: We use the [Micro Manager](tooling-micro-manager-overview.html) to set up Python and C++ micro simulations, learn how manage runtime using adaptivity, implement model adaptivity, and run the micro simulations in parallel with adaptivity and load balancing. -![Macro-Micro training: Adaptivity](images/training/training-mm.png) +![Macro-Micro training: Adaptivity](/images/training/training-mm.png) ## How to prepare? @@ -67,10 +69,10 @@ Most of these tools work best (or only) on a Linux system. You can either (a) use a prepared system image that we provide (e.g., in a virtual machine), or (b) install the dependencies directly on your system. To reduce system-related friction during the training, we recommend starting with option (a). -{% important %} +{{< important >}} At the end, verify your installation, and contact us as soon as possible regarding any issues. Find verification instructions at the end of each section. -{% endimportant %} +{{< /important >}} ### Provided system @@ -84,11 +86,11 @@ With this `.iso` file, you can either: In both cases, you can either install the modified Ubuntu image, or try a live session, without any permanent changes (or result file saves) to your system. Get the smoothest experience by installing the image in a VM, so that your changes are saved between sessions, and you can at the same time access your host OS. -{% note %} +{{< note >}} At the moment, this modified Ubuntu image is only available for Intel/AMD x86-64 CPUs. In our on-site trainings, some prepared USB sticks are provided. These should work on any laptop with an x86-64 CPU, as long as you have the rights to boot from USB. In particular, these do not work on Apple Silicon systems. -{% endnote %} +{{< /note >}} Configure the VM with these settings: @@ -119,13 +121,13 @@ Further important settings: To check your installation, run the [1D elastic tube tutorial](tutorials-elastic-tube-1d.html) (Python solvers) inside the VM. -{% important %} +{{< important >}} If you use a bootable USB, make sure to select trying a live session, and not installing (or take care that you do not remove your data). If you have [secure boot](https://en.wikipedia.org/wiki/UEFI#Secure_Boot) enabled, this will need to be turned off to boot this unsigned OS. In case you use Windows with [BitLocker](https://en.wikipedia.org/wiki/BitLocker) enabled, you will not be able to boot on Windows while secure boot is disabled (BitLocker will be asking for the decryption key). Remember to switch secure boot on again to be able to use your system as before. Do not remove the USB during a live session. -{% endimportant %} +{{< /important >}} ### Individual dependencies diff --git a/content/community/trainings/2026-10.md b/content/community/trainings/2026-10.md index 84bd074a784..17b8792d0c5 100644 --- a/content/community/trainings/2026-10.md +++ b/content/community/trainings/2026-10.md @@ -3,10 +3,12 @@ title: preCICE online training 2026 keywords: precice training 2026, event, events, training summary: permalink: precice-online-training-2026-oct.html +aliases: + - /precice-online-training-2026-oct.html toc: false --- -preCICE training banner +preCICE training banner In October 5-9, 2026, we are organizing the first online preCICE training, mainly targeting participants in the US, Canada, and Latin America (time: 12–3 pm EDT (UTC-4)) that cannot easily travel to the [preCICE Workshop](precice-workshop.html) – with the [next workshop being in March 2027](precice-workshop-2027.html). Over the span of one week, the training will include elements of the longer [training course](community-training.html) of the preCICE Workshop, invited talks, and news from the preCICE developers. @@ -50,7 +52,7 @@ We are preparing an interactive online event with 3h slots over a week. Prelimin Feel free to use [this advertising material](https://ipvscloud.informatik.uni-stuttgart.de/s/5tMqRPek4MKq9F9). Did you know? Many past participants only discovered this workshop via a direct email. -preCICE online training advertising slide (png thumbnail) +preCICE online training advertising slide (png thumbnail)