View Issue Details

IDProjectCategoryView StatusLast Update
0003289OpenFOAMBugpublic2019-06-07 15:45
ReporterlinAssigned Tohenry 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformGNU/LinuxOSUbuntuOS Version14.04
Product Version6 
Fixed in Versiondev 
Summary0003289: DTCHullMoving example crashes with dynamicMeshDict.sixDoF configuration.
DescriptionOpenfoam6 version 20190304, DTCHullMoving tutorial.
The tutorial works fine with the default dynamicMeshDict configuration, but if I run it with the dynamicMeshDict.sixDoF configuration, it crashes around Time = 0.287841.

If I set a more stringent criteria in controlDict as below, the tutorial could work properly, but I do not know whether this is the optimal solution.

maxCo 5;
maxAlphaCo 3;

Can I know whether the tutorial accompanied with both dynamicMeshDict and dynamicMeshDict.sixDoF configuration files are expected to output the exact same solution with these two different configuration files?
Steps To Reproduce~/work/of6/DTCHullMoving$ mv constant/dynamicMeshDict.sixDoF constant/dynamicMeshDict

~/work/of6/DTCHullMoving$ ./Allrun
TagsNo tags attached.

Activities

lin

2019-06-07 02:58

reporter  

log.tar.gz (343,588 bytes)

henry

2019-06-07 08:59

manager   ~0010511

> Can I know whether the tutorial accompanied with both dynamicMeshDict and dynamicMeshDict.sixDoF configuration files are expected to output the exact same solution with these two different configuration files?

No, the rigidBodyModel and sixDoF are not numerically identical.

I am running the DTCHullMoving case with sixDoF in OpenFOAM-dev without issues. Try upgrading to OpenFOAM-dev and re-run your tests.

henry

2019-06-07 14:19

manager   ~0010512

The DTCHullMoving tutorial with sixDoF runs to completion in OpenFOAM-dev.

Issue History

Date Modified Username Field Change
2019-06-07 02:58 lin New Issue
2019-06-07 02:58 lin File Added: log.tar.gz
2019-06-07 08:59 henry Note Added: 0010511
2019-06-07 14:19 henry Assigned To => henry
2019-06-07 14:19 henry Status new => closed
2019-06-07 14:19 henry Resolution open => fixed
2019-06-07 14:19 henry Fixed in Version => dev
2019-06-07 14:19 henry Note Added: 0010512