Comments (6)
I opened a more detailed issue in precice/precice#1984.
An interesting observation, which is probably worth checking even before getting into fieldcompare
is that the iterations differ in both cases.
from tutorials.
I understand that this issue has two parts:
- the "getting different results between v3.0.0 and develop" has been addressed in precice/precice#1984
- the "getting different results locally than on GitHub runners" is partially not an issue, partially covered by #393.
Closing as duplicate.
from tutorials.
Sounds like an instance of #393
from tutorials.
Alright, so I wait for the bug investigation in preCICE before looking deeper into this from the perspective of the system tests.
from tutorials.
My last comment is a bit off topic.
I cannot reproduce the reference results locally (this issue) and the precice develop produces different results than my local v3.0.0 results (linked issue).
from tutorials.
Well, every system is expected to give a bit different results, hence the selection of the tolerance is important.
Reference results are generated on the GitHub runners with this workflow: https://github.com/precice/tutorials/actions/workflows/generate_reference_results_manual.yml
from tutorials.
Related Issues (20)
- Job summaries for system tests HOT 1
- Conversion errors in FEniCS FSI cases HOT 2
- Nutils cases are extremely slower than the rest HOT 4
- peprpendicular-flap solid-openfoam case needs tuning HOT 7
- The `setup-dumux.sh` couldn't install DuMuX properly HOT 4
- Integrate updating/checking the config visualizations in the CI
- Docker build sometimes produces empty stdout.log
- Quickstart solid-cpp not being built automatically HOT 1
- Python packages not installed automatically for all tutorials HOT 2
- two-scale-heat-conduction DuMuX dependencies setup HOT 1
- Nutils tutorials always download pyprecice 3.0.0.0 HOT 1
- pushing to Git LFS
- Reference results metadata is outside the reference_results directory
- Source test cases from other repositories
- volume-coupled-flow: Source term incomplete
- Gradients: Surface-normal (scalars) vs complete (vector) HOT 1
- Missing requirements.txt and venv in some Python-based examples
- Fine-grained history and citation guidelines for each tutorial
- Specify default build arguments
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tutorials.