Bugs on OpenFOAM's bug tracker I wanted to tackle, but never managed to find the time for it - wyldckat/wyldckat.github.io GitHub Wiki
The following is a list of interesting bugs I wanted to try and have a look into them, but ended up not having time to look into them. I'm leaving them here as an aside wiki page, just in case someone else wants to pick them back up again.
-
https://www.cfd-online.com/Forums/openfoam-bugs/66040-reconstructpar-filename-stripinvalid-called-invalid-filename-commandtouse-2.html#post632915
- Need to ignore other files with weird characters in the current case folder.
- Time issue in ParaView, as shown here: https://bugs.openfoam.org/view.php?id=2395
- Bug is in ParaView/VTK, which still needs to be reported and fixed!?
-
https://gitlab.kitware.com/vtk/vtk/issues/16873
- ParaView 5.3 no longer complains about missing value, but assumes "zeroGradient" in such a case.
-
http://www.openfoam.org/mantisbt/view.php?id=1232
- All that's missing is the ability to have a consistent environment!?
- See http://bugs.openfoam.org/view.php?id=2330
- Issue #1396 "blockMesh limitations regarding dual/multiple oriented curved edges" has been fixed! Need to test it!
- Have gotten permission to contribute from blueCFD-AIR to this: http://bugs.openfoam.org/view.php?id=2322
- Consolidate VTK features into a single library, as discussed in: http://bugs.openfoam.org/view.php?id=2213
-
http://bugs.openfoam.org/view.php?id=2219
- ParaView 5.2.0 is needed for double-checking support for polyhedral cells...
-
http://bugs.openfoam.org/view.php?id=2310
- check Mark's description: https://develop.openfoam.com/Development/OpenFOAM-plus/issues/280
- How to have an invert regex: PCRE could have a prefix for that
-
https://en.wikibooks.org/wiki/Linux_Applications_Debugging_Techniques/Heap_corruption#AddressSanitizer
- Built-in checks for invalid memory accesses...
- Example where this might be applicable: http://www.cfd-online.com/Forums/openfoam-programming-development/179545-custom-viscosity-model-2.html#post625159
- Commit 7ac96f1f979f8e158300f54b6561e792ef4033df in 2.3.x might have fixed one of the sampling problems...
- Ensure the user time is working: https://github.com/OpenFOAM/OpenFOAM-dev/commit/54af0e335999df303eae8f71e0854c4287e4f270
-
http://bugs.openfoam.org/view.php?id=2082
- Pointed out at OFW11 by the submitter.
-
http://www.cfd-online.com/Forums/openfoam-bugs/174933-particle-tracking-error.html
- Bug report and details on how to fix certain problems with particle tracking in OpenFOAM.
- May be related to http://bugs.openfoam.org/view.php?id=2199
- And with this: http://www.cfd-online.com/Forums/openfoam/126792-error-during-reconstructing-lagarangian-fields.html
- Possibly already fixed?
BUGNUM=2285
PATCHNAME=patch_name_v1
foam
mkdir ~/Desktop/mantis/bug$BUGNUM
tar -czf ~/Desktop/mantis/bug$BUGNUM/$PATCHNAME.tar.gz $(git diff --name-only master)
cp $(git diff --name-only master) ~/Desktop/mantis/bug$BUGNUM/
git diff master > ~/Desktop/mantis/bug$BUGNUM/$PATCHNAME.patch
These will take some considerable time to do.
-
https://develop.openfoam.com/Development/OpenFOAM-plus/issues/530
- Similar report exists at openfoam.org
- http://bugs.openfoam.org/view.php?id=2157
- http://www.openfoam.org/mantisbt/view.php?id=1936
- http://www.openfoam.org/mantisbt/view.php?id=1885
-
http://www.openfoam.org/mantisbt/view.php?id=741
- AMI instabilities?
- http://www.openfoam.org/mantisbt/view.php?id=1847
-
http://www.openfoam.org/mantisbt/view.php?id=1692
- Seems related: http://www.openfoam.org/mantisbt/view.php?id=154
- http://www.openfoam.org/mantisbt/view.php?id=1400
-
http://www.openfoam.org/mantisbt/view.php?id=1324
- http://www.openfoam.org/mantisbt/view.php?id=1335
- ACMI problems with non-zero fixed values
- http://www.openfoam.org/mantisbt/view.php?id=1026
- http://www.openfoam.org/mantisbt/view.php?id=725
- http://www.openfoam.org/mantisbt/view.php?id=1645
- http://www.openfoam.org/mantisbt/view.php?id=1682
- http://www.openfoam.org/mantisbt/view.php?id=897
- http://www.openfoam.org/mantisbt/view.php?id=1431
-
http://www.cfd-online.com/Forums/openfoam-post-processing/156277-libsampling-dym-solver-exporting-vtk-patch-problem-update-geometry.html#post567310
- Sampling problem that it's in some versions of OpenFOAM...
-
http://www.openfoam.org/mantisbt/view.php?id=347
- Actually, this is just needs some code clean up and making a pull request for the contribution request.
- http://www.openfoam.org/mantisbt/view.php?id=1428
-
http://www.openfoam.org/mantisbt/view.php?id=1377
- Same goes from some other applications that were reported as working to be able to do so, such as redistributeMesh?
- http://www.openfoam.org/mantisbt/view.php?id=1270
-
http://www.openfoam.org/mantisbt/view.php?id=793
- Adapt to PV4 the readers so that they can support OSMesa
-
http://www.openfoam.org/mantisbt/view.php?id=777
- Use "sampledSets" as a basis for creating a class that writes tabular data
- http://www.openfoam.org/mantisbt/view.php?id=1639
- http://www.openfoam.org/mantisbt/view.php?id=1569
-
http://www.openfoam.org/mantisbt/view.php?id=1554
- File driver?!
- http://www.openfoam.org/mantisbt/view.php?id=1677
- http://www.openfoam.org/mantisbt/view.php?id=1530
OK, I did a bit of looking into this and here's what I've seen so far: 1- The tutorial "multiphase/interDyMFoam/ras/floatingObject" can be used for testing this, since it has the field "pointDisplacement", which is critical for the proper operation of the simulation. Side note: Never forget that coding without unit tests is... well... not safe :) Steps: decomposePar #change core count redistributePar 2- There are a lot of mappings that need to be done in several places!!!
-
http://www.cfd-online.com/Forums/openfoam-installation/162866-openfoam-using-environment-modules-hpc.html#post574413
- modules load/unload support?
- checkMesh should have AMI checking...
- yPlus with stress based calculation
-
http://www.openfoam.org/mantisbt/view.php?id=1944
- Need to do the checks from http://www.openfoam.org/mantisbt/view.php?id=1944#c5755
- Related to http://bugs.openfoam.org/view.php?id=2353:
From the perspective of generalization, we should extend the current 'fieldMinMax' and 'fieldAverage' (and other field* function objects) to also support per-patch calculations and therefore drop the current min/max/avg feature from the yPlus function object. This would also allow for a bit more refined control on when this should be shown on standard output.
Furthermore, yPlus, wallShearStress, wallHeatFlux are all in the same boat... the 3 need patch operations of min, max, avg and sum/integral values.