diff --git a/_data/sidebars/docs_sidebar.yml b/_data/sidebars/docs_sidebar.yml index 6c89f68e8d..a575ded658 100644 --- a/_data/sidebars/docs_sidebar.yml +++ b/_data/sidebars/docs_sidebar.yml @@ -39,6 +39,10 @@ entries: - title: Roadmap url: /fundamentals-roadmap.html output: web, pdf + + - title: Previous versions + url: /fundamentals-previous-versions.html + output: web, pdf - title: Installation output: web, pdf diff --git a/images/events/precice2021-group.png b/images/events/precice2021-group.png new file mode 100644 index 0000000000..f9e6eb78ae Binary files /dev/null and b/images/events/precice2021-group.png differ diff --git a/images/events/precice2022-group.png b/images/events/precice2022-group.png new file mode 100644 index 0000000000..4559a27a6c Binary files /dev/null and b/images/events/precice2022-group.png differ diff --git a/images/events/precice2023-group.jpg b/images/events/precice2023-group.jpg new file mode 100644 index 0000000000..66daa63d5e Binary files /dev/null and b/images/events/precice2023-group.jpg differ diff --git a/imported/tutorials b/imported/tutorials index 362606a417..8f9125a86d 160000 --- a/imported/tutorials +++ b/imported/tutorials @@ -1 +1 @@ -Subproject commit 362606a417e297eeda2373964f54925130b57af5 +Subproject commit 8f9125a86d7d94def84e5d2fb3ca95a8243586ac diff --git a/pages/community/precice-workshop-2021.md b/pages/community/precice-workshop-2021.md index 3306ee1e05..8ef18e506c 100644 --- a/pages/community/precice-workshop-2021.md +++ b/pages/community/precice-workshop-2021.md @@ -9,7 +9,9 @@ redirect_from: /preCICE2021/ preCICE Workshop banner -The 2nd preCICE Workshop will be held virtually through the [University of Stuttgart](https://www.uni-stuttgart.de/en/), from February 22-25, 2021. The workshop is a coming together of the preCICE community to share ideas, experiences and knowledge about using preCICE, and to learn from others in the process. [Registration](https://precice.org/precice-workshop-2021.html#registration) for the workshop is still open. +Group picture + +The 2nd preCICE Workshop was held virtually through the [University of Stuttgart](https://www.uni-stuttgart.de/en/), between February 22-25, 2021. The workshop is a coming together of the preCICE community to share ideas, experiences and knowledge about using preCICE, and to learn from others in the process. [Registration](https://precice.org/precice-workshop-2021.html#registration) for the workshop is closed. If you have any questions regarding the workshop, please contact us at precice2021@ipvs.uni-stuttgart.de. diff --git a/pages/community/precice-workshop-2022.md b/pages/community/precice-workshop-2022.md index 8185bddb97..c270588735 100644 --- a/pages/community/precice-workshop-2022.md +++ b/pages/community/precice-workshop-2022.md @@ -9,11 +9,11 @@ redirect_from: /preCICE2022/ preCICE Workshop banner -The 3rd preCICE Workshop will be held virtually through [SimTech](https://www.simtech.uni-stuttgart.de/) and the [University of Stuttgart](https://www.uni-stuttgart.de/en/), on February 21-24, 2022. The workshop is a coming together of the preCICE community to share ideas, experiences and knowledge about using preCICE, and to learn from others in the process. +Group picture -[Registration](https://precice.org/precice-workshop-2022.html#registration) is now open. We look forward to welcoming back previous participants, and introducing more members to the preCICE community. +The 3rd preCICE Workshop was held virtually through [SimTech](https://www.simtech.uni-stuttgart.de/) and the [University of Stuttgart](https://www.uni-stuttgart.de/en/), on February 21-24, 2022. The workshop is a coming together of the preCICE community to share ideas, experiences and knowledge about using preCICE, and to learn from others in the process. -Due to the uncertain times we are experiencing with the ongoing COVID-19 pandemic and the great success of the virtual workshop in February 2021, we are planning to host the workshop virtually again. +[Registration](https://precice.org/precice-workshop-2022.html#registration) is closed. If you have any questions regarding the workshop, please contact us at [`precice2022@ipvs.uni-stuttgart.de`](mailto:precice2022@ipvs.uni-stuttgart.de). diff --git a/pages/community/precice-workshop-2023.md b/pages/community/precice-workshop-2023.md index 1fda0fec42..bce01b9d67 100644 --- a/pages/community/precice-workshop-2023.md +++ b/pages/community/precice-workshop-2023.md @@ -13,6 +13,8 @@ redirect_from: /preCICE2023/ This workshop is now over. See you next in [SIAM CSE23](https://meetings.siam.org/program.cfm?CONFCODE=CSE23) with several talks, a poster, and two minitutorial sessions, as well as in [ECCOMAS COUPLED23](eccomas-coupled-2023.html) with a minisymposium. {% endnote %} +Group picture + The 4th preCICE Workshop was held in-presence at the campus Garching of the [Technical University of Munich](https://www.tum.de/) ([Leibniz Supercomputing Center](https://www.lrz.de/)), on February 13-16, 2023. The workshop is a coming together of the preCICE community to share ideas, experiences and knowledge about using preCICE, and to learn from others in the process. Expect user and developer talks, hands-on training sessions, discussions with the developers on your applications and use cases, feedback rounds, and plenty of opportunities to network with the rest of our vibrant community. diff --git a/pages/docs/couple-your-code/couple-your-code-porting-v2-3.md b/pages/docs/couple-your-code/couple-your-code-porting-v2-3.md index 2811a083d2..0b29271e56 100644 --- a/pages/docs/couple-your-code/couple-your-code-porting-v2-3.md +++ b/pages/docs/couple-your-code/couple-your-code-porting-v2-3.md @@ -36,7 +36,7 @@ Please add breaking changes here when merged to the `develop` branch. The previously optional argument `relativeReadTime` is now mandatory for read data calls. This requires you to update all read data calls. See [time interpolation](couple-your-code-waveform) for more details on this argument. If you don't want to use subcycling or time interpolation, you can simply get the required `relativeReadTime` by calling `double preciceDt = getMaxTimeStepSize()` call. Change: -```diff cpp +```diff - couplingInterface.readBlockVectorData(meshName, dataReadName, numberOfVertices, vertexIDs.data(), readData.data()); + preciceDt = couplingInterface.getMaxTimeStepSize(); + couplingInterface.readBlockVectorData(meshName, dataReadName, numberOfVertices, vertexIDs.data(), preciceDt, readData.data()) @@ -44,7 +44,7 @@ The previously optional argument `relativeReadTime` is now mandatory for read da If you use subcycling, please do the following: -```diff cpp +```diff - couplingInterface.readBlockVectorData(meshName, dataReadName, numberOfVertices, vertexIDs.data(), readData.data()); + preciceDt = couplingInterface.getMaxTimeStepSize(); double dt = min(preciceDt, solverDt); @@ -55,7 +55,7 @@ If you use subcycling, please do the following: The API function `initializeData()` has been removed in [#1350](https://github.com/precice/precice/pull/1350). `initialize()` now takes care of all the initialization – including data initialization. This means, you have to call `initialize()`, where you previously called `initializeData()`. Be aware that this means that you have to write initial data before calling `initialize()`. Change: -```diff cpp +```diff - double dt = 0; - dt = couplingInterface.initialize(); std::vector writeData(dimensions, writeValue); diff --git a/pages/docs/couple-your-code/couple-your-code-time-step-sizes.md b/pages/docs/couple-your-code/couple-your-code-time-step-sizes.md index 257cb71548..4ee1531fca 100644 --- a/pages/docs/couple-your-code/couple-your-code-time-step-sizes.md +++ b/pages/docs/couple-your-code/couple-your-code-time-step-sizes.md @@ -3,6 +3,8 @@ title: Step 5 – Non-matching time step sizes permalink: couple-your-code-time-step-sizes.html keywords: api, adapter, advance, timestepping, subcycling, adaptivity summary: "In this step, you learn how preCICE handles non-matching time step sizes and a few more things about simulation time." +redirect_from: + - couple-your-code-timestep-sizes.html --- In previous steps, you have already seen that there are quite some things going on with time step sizes. Let us now have a look at what is actually happening. diff --git a/pages/docs/fundamentals/fundamentals-previous-versions.md b/pages/docs/fundamentals/fundamentals-previous-versions.md new file mode 100644 index 0000000000..2e78d0597a --- /dev/null +++ b/pages/docs/fundamentals/fundamentals-previous-versions.md @@ -0,0 +1,15 @@ +--- +title: Previous versions +permalink: fundamentals-previous-versions.html +keywords: pdf, export, v1, v2 +summary: "Archives of this documentation" +--- + +In regular intervals, we archive PDF exports of this documentation. Refer to those when you are looking for information regarding previous versions: + +- For preCICE v2.x: [libprecice2_2.2.5_docs_v202211.0.0.pdf](https://github.com/precice/precice.github.io/releases/download/v202211.0.0/libprecice2_2.2.5_docs_v202211.0.0.pdf) +- Before preCICE v2.x, the documentation was hosted in a [GitHub Wiki](https://github.com/precice/precice/wiki/Home/f6bfac33aa878ab3e89e60720894e4fe0a547ab4). For each page you want to visit, look at the previous revisions. + +We only support the latest version of preCICE, but upgrading is easy: See our [porting guides](./couple-your-code-porting-overview.html). + +The PDF exports of the documentation are part of the [preCICE Distribution](./installation-distribution.html). Alternatively, you can build [previous states of this website](https://github.com/precice/precice.github.io). diff --git a/pages/index.html b/pages/index.html index e4f0c6484c..0e698143b6 100644 --- a/pages/index.html +++ b/pages/index.html @@ -318,6 +318,40 @@

Academic at heart, 100% free software

+ + +
+
+
+ +
+
+

Join the community!

+
+
+ +
+
+

We develop everything in the open, with continuous feedback by a vivid community. Be part of it:

+
    +
  • Ask for help and help others in the preCICE forum and register to receive news.
    • +
  • Directly edit the documentation. We review and help - nothing can go wrong.
    • +
  • Report issues on GitHub and help us solve them for everyone.
    • +
  • Contribute code and simulation examples - we help you with guidelines, tools, and reviews.
    • +
  • Meet the community in one of the preCICE workshops and conference sessions.
    • +
+
+
+ + preCICE Workshop group picture + +
+
+
+
+
+ +