Skip to content

Geometric Multiscale Documentation#205

Merged
MakisH merged 11 commits intoprecice:precice-v3from
ezonta:patch-1
Jan 23, 2024
Merged

Geometric Multiscale Documentation#205
MakisH merged 11 commits intoprecice:precice-v3from
ezonta:patch-1

Conversation

@ezonta
Copy link
Copy Markdown
Contributor

@ezonta ezonta commented Sep 20, 2022

Content of PR

Added a short section on geometric multiscale mapping and how it is configured that can be extended further upon expansion of preCICE's geometric multiscale capabilities (e.g., radial geometric multiscale coupling, tutorials on 1D-3D coupling, etc.)

@ezonta ezonta marked this pull request as draft September 20, 2022 12:46
@ezonta ezonta marked this pull request as ready for review September 20, 2022 12:52
@ezonta
Copy link
Copy Markdown
Contributor Author

ezonta commented Sep 20, 2022

@MakisH I just learned that I have to add you as a collaborator to the repo before I can add you as a reviewer, so I will add you as a reviewer as soon as you accept the collaborator invite.

@uekerman
Copy link
Copy Markdown
Member

I just learned that I have to add you as a collaborator to the repo before I can add you as a reviewer, so I will add you as a reviewer as soon as you accept the collaborator invite.

I guess it's the other way around.
@ezonta you have to become a collaborator in the upstream repo. I just added you.

@ezonta
Copy link
Copy Markdown
Contributor Author

ezonta commented Sep 20, 2022

I just learned that I have to add you as a collaborator to the repo before I can add you as a reviewer, so I will add you as a reviewer as soon as you accept the collaborator invite.

I guess it's the other way around. @ezonta you have to become a collaborator in the upstream repo. I just added you.

Oh perfect, thank you!

@MakisH MakisH marked this pull request as draft September 21, 2022 09:03
Copy link
Copy Markdown
Member

@MakisH MakisH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for contributing! A few comments to start the discussion.

I also converted this to a draft, let's decide based on our strategy with precice/precice#1439

Copy link
Copy Markdown
Member

@MakisH MakisH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the updates! To save some iterations, I went ahead and directly edited the text. It looks good for now, but we can only merge when the feature is merged to develop.

@MakisH MakisH self-assigned this May 20, 2023
@MakisH MakisH added the content Content-only issues label May 20, 2023
@MakisH MakisH added this to the Version 3.0.0 milestone May 20, 2023
@MakisH MakisH changed the base branch from master to precice-v3 May 22, 2023 12:38
@MakisH
Copy link
Copy Markdown
Member

MakisH commented May 22, 2023

I changed the target branch to precice-v3, which is meant to merge once v3 is out.
So, @ezonta, if you feel that this is ready (still marked as draft), we could already merge it and move on to the next step, focusing on the cases.

@ezonta ezonta marked this pull request as ready for review July 21, 2023 14:41
@ezonta ezonta requested a review from MakisH July 21, 2023 14:42
@MakisH
Copy link
Copy Markdown
Member

MakisH commented Jul 21, 2023

@ezonta looking at the files changed, I see a few unreated changes. Could you maybe rebase on the latest state of the precice-v3 branch and force-push?

@ezonta
Copy link
Copy Markdown
Contributor Author

ezonta commented Jul 21, 2023

@ezonta looking at the files changed, I see a few unreated changes. Could you maybe rebase on the latest state of the precice-v3 branch and force-push?

I can do that! Do you know if there is way to rebase from GitHub web? I haven't yet cloned the repo, because these were only text changes. But I can also just clone the repo real quick to do it.

@MakisH
Copy link
Copy Markdown
Member

MakisH commented Jul 21, 2023

@ezonta looking at the files changed, I see a few unreated changes. Could you maybe rebase on the latest state of the precice-v3 branch and force-push?

I can do that! Do you know if there is way to rebase from GitHub web? I haven't yet cloned the repo, because these were only text changes. But I can also just clone the repo real quick to do it.

I don't think one can do that directly via the UI... :-/

@ezonta
Copy link
Copy Markdown
Contributor Author

ezonta commented Jul 22, 2023

@ezonta looking at the files changed, I see a few unreated changes. Could you maybe rebase on the latest state of the precice-v3 branch and force-push?

I can do that! Do you know if there is way to rebase from GitHub web? I haven't yet cloned the repo, because these were only text changes. But I can also just clone the repo real quick to do it.

I don't think one can do that directly via the UI... :-/

I cloned the repo and force pushed a rebased version, hope it worked out.

@MakisH
Copy link
Copy Markdown
Member

MakisH commented Jul 24, 2023

I cloned the repo and force pushed a rebased version, hope it worked out.

Strange... Looking at https://github.com/precice/precice.github.io/pull/205/files, I still see unrelated changes (and unrelated commits).

@MakisH
Copy link
Copy Markdown
Member

MakisH commented Aug 8, 2023

I rebased on precice-v3:

  1. git checkout precice-v3 && git pull
  2. gh pr checkout 205
  3. git rebase precice-v3
  4. git push --force

I now only see the relevant files.

Copy link
Copy Markdown
Member

@MakisH MakisH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is how this section looks like now:

Screenshot from 2023-08-08 16-15-37

Unless we change anything else in precice/precice#1675, this is ready to merge once the PR in preCICE is merged.

@MakisH MakisH merged commit d5c6998 into precice:precice-v3 Jan 23, 2024
@MakisH MakisH deleted the patch-1 branch January 23, 2024 20:44
uekerman added a commit that referenced this pull request Feb 12, 2024
* Fix whitespace.

* Update action config docs to v3 (#254)

* Update Roadmap

* Update fundamentals-roadmap.md

* Use time step, not timestep. (#259)

* v3: Update documentation w.r.t getMaxTimeStep(). (#258)

* Update documentation w.r.t getMaxTimeStep().
* Implements changes from precice/precice#1623

---------

Co-authored-by: Benjamin Uekermann <[email protected]>

* Minor follow-up for #258.

* Update documentation for initialize (#186)

* Documentation for data initialization changes introduced in v3.0.0.
* Cleanup initializeData.

---------

Co-authored-by: Benjamin Uekermann <[email protected]>
Co-authored-by: Benjamin Uekermann <[email protected]>

* Update profiling section (#266)

* Update profiling section

* Update examples in profiling section

* Apply suggestions from code review

Co-authored-by: Benjamin Uekermann <[email protected]>

* Add motivation for custom tool

* Wording tweaks

* More rewording

* Update event files in output files

---------

Co-authored-by: Benjamin Uekermann <[email protected]>

* Fix typo in profiling

* Update profiling info in guide

* Update CMake variables to new names (#289)

* Clarify some instructions in porting guide (#287)

Co-authored-by: Gerasimos Chourdakis <[email protected]>

* Fix minor issues in tooling/performance-analysis (#272)

* Rename events to profiling

according to precice/precice #1787

* Mention where to find the precice-profiling

* Add hint regarding the event flag in precice-profiling

* Add recommendation for `imvj-restart-mode` in configuration of acceleration (#296)

* Update configuration-acceleration.md

Add recommendation to use restart mode in `IQN-IMVJ` method for large-scale simulations.

* Update pages/docs/configuration/configuration-acceleration.md

Improve descriptive accuracy

Co-authored-by: Benjamin Uekermann <[email protected]>

---------

Co-authored-by: Benjamin Uekermann <[email protected]>

* Apply trivial renaming changes.

* Fix naming.

* Add note.

* Update breaking API changes (#299)

---------

Co-authored-by: Gerasimos Chourdakis <[email protected]>

* Fix token

* Fix arg

* Bump preCICE version

* Update hint on formatting configuration files

* Refer to precice.hpp instead of participant.hpp

* Update version in docs sidebar

* Rewrite mapping docs (#308)

* Add overview figure

* Work in progress

* Fix links

* Transform pdfs to svgs

* Update kernel method section

* Also write about GPU executors

* Language edits by Benjamin and Makis

Co-authored-by: Gerasimos Chourdakis <[email protected]>
Co-authored-by: Benjamin Uekermann <[email protected]>

* Review updates

* Makis language edits

Co-authored-by: Gerasimos Chourdakis <[email protected]>

* Fix typos via aspell

---------

Co-authored-by: Gerasimos Chourdakis <[email protected]>
Co-authored-by: Benjamin Uekermann <[email protected]>

* Fix some outdated solver-interface and dimensions (#314)

* Migrate use-mesh to provide/receive-mesh

* Migrate binprecice to precice-tools

* Update config-visualizer page

* Include instructions to remove .data() in readData function (#313)

* Include instructions to remove .data() in readData function
* Mention span replacing raw pointers
* Remove raw pointers from general porting example

* Cleanup porting guide example

* Update couple your code

* Remove obsolete section regarding IDs

* Apply suggestions from code review

Co-authored-by: Ishaan Desai <[email protected]>

* This PR adds C++ STL linking from Doxygen to cppreference

* Fix WD

* Link to porting guides from the source docs

* Add list of porting guides to overview

* Add new solid solver to Nutils adapter overview page (#325)

* Geometric Multiscale Documentation (#205)

Co-authored-by: Gerasimos Chourdakis <[email protected]>

* Update submodules

* Ignore tooling in images

* Update xmlreference to v3.0.0

* Cleanup porting guide API+Config (#317)

Co-authored-by: Ishaan Desai <[email protected]>
Co-authored-by: Gerasimos Chourdakis <[email protected]>

* Update the rust bindings page

* Fix link

* Make dt in readData mandatory in documentation (#257)

* v3: Make dt mandatory in documentation

* Update read data functions to use relativeReadTime.

* change precice_dt to preciceDt and solver_dt to solverDt to follow
conventions.

* Add missing.

* Shorten a bit.

* Minor follow-up for #258.

* Add figure.

* Remove outdated note.

* Use dt properly.

* Remove unnecessary pdf.

* Partial update of documentation w.r.t breaking changes.

* Redice diff.

* Redice diff.

* Reduce diff.

* Fix some more breaking changes.

* Add how dt is computed. See #257.

* Apply suggestions from code review

Co-authored-by: Gerasimos Chourdakis <[email protected]>

* Remove unneeded.

* Add pointer to interpolation section.

* Fix format.

* Add advice on precice/precice#1866.

* Apply suggestions from code review

* Update some minor, obviously outdated points.

* Update png.

* Update pages/docs/couple-your-code/couple-your-code-mesh-and-data-access.md

Co-authored-by: Frédéric Simonis <[email protected]>

* Update heading.

* Moved changes to #326.

* Update pages/docs/couple-your-code/couple-your-code-mesh-and-data-access.md

* Update pages/docs/couple-your-code/couple-your-code-waveform.md

---------

Co-authored-by: Gerasimos Chourdakis <[email protected]>
Co-authored-by: Frédéric Simonis <[email protected]>
Co-authored-by: Benjamin Uekermann <[email protected]>

* Update submodules

* Remove v3 tip from roadmap

* Add rust bindings to installation overview

* Update libprecice2 to libprecice3 on Ubuntu packages page

* Update header names in installation-linking

* Update porting information on configuration overview page

* Update several things on configuration basics page

* Update configuration communication page

* Revert tweaks in configuration basics page

Previously, I changed from precice to participant as name for the preCICE handle and I used "Force" instead of "Forces" to be consistent with the tutorial guidelines. But both changes would also need updates on many other pages. Thus, I left them for the moment for consistency.

* Refer to QN default values on acceleration configuration

* Update porting info and mention Rust on couple your code start

* Change global dim to mesh dim in step 3

* Remove dim handling from step 6

* Fix getDataDim arguments in step 3

* Fix dim handling in step 9

* Fix dim in direct access

* Fix and tweak porting guide

* Make linter happy

* Make linter happier

* Add missing tutorials in the sidebar and overview (#334)

* Add partitioned-pipe-two-phase to sidebar and overview

* Add oscillator overlap in sidebar and overview

* Add partitioned-heat-conduction-overlap to the sidebar and overview

* Add volume-coupled-flow to sidebar and overview

* Add two-scale-heat-conduction to sidebar and overview

* Update pages/tutorials/tutorials.md

Co-authored-by: Ishaan Desai <[email protected]>

* Update pages/tutorials/tutorials.md

---------

Co-authored-by: Benjamin Uekermann <[email protected]>
Co-authored-by: Ishaan Desai <[email protected]>

* Update bindings overview picture (#333)

* Update bindings overview picture

* Move arrow of Python bindings to precice.hpp

* Add Rust bindings

---------

Co-authored-by: Benjamin Rodenberg <[email protected]>
Co-authored-by: Gerasimos Chourdakis <[email protected]>
Co-authored-by: Benjamin Rodenberg <[email protected]>
Co-authored-by: Frédéric Simonis <[email protected]>
Co-authored-by: David Schneider <[email protected]>
Co-authored-by: carme-hp <[email protected]>
Co-authored-by: June <[email protected]>
Co-authored-by: homspons <ge35joj>
Co-authored-by: Ishaan Desai <[email protected]>
Co-authored-by: Elia Zonta <[email protected]>
Co-authored-by: precice-bot <[email protected]>
Co-authored-by: Ishaan Desai <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content Content-only issues

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants