View Issue Details

IDProjectCategoryView StatusLast Update
0004196OpenFOAMBugpublic2025-01-01 12:45
Reporterjskortel Assigned Tohenry  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
PlatformGNU/LinuxOSOtherOS Version(please specify)
Product Versiondev 
Summary0004196: Running the decomposePar utility fails for a case with displacementComponentLaplacian dynamic mesh motion
DescriptionThe issue appears when running the decomposePar utility and using displacementComponentLaplacian for dynamic mesh motion. The mesh
motion direction (component) is defined in the constant/dynamicMeshDict dictionary file and is, e.g., "z". The actual mesh motion (for a patch) is defined in the initial condition dictionary file 0/pointDisplacementz. When running the case as one process (i.e., not in parallel), the case runs smoothly without error or warning messages and timestep folders are generated accordingly. When trying to run the case in parallel and when using the decomposePar utility, the following error message is received:

---
...
Decomposing point fields

    Decomposing pointVectorFields

        pointDisplacementz


--> FOAM FATAL IO ERROR:
Expected a '(' while reading VectorSpace<Form, Cmpt, Ncmpts>, found on line 19 the doubleScalar 0

file: /home/jussi/OpenFOAM/jussi-dev/run/Pulse_Two/Pulse_Two-6/0/pointDisplacementz/internalField at line 19.

    From function Foam::Istream& Foam::Istream::readBegin(const char*)
    in file db/IOstreams/IOstreams/Istream.C at line 92.

FOAM exiting
---

The content of line 19 is "internalField uniform 0.0;". It looks like the decomposePar utility is errorneously expecting vector representation
of the displacement component data, which should be scalar (displacement component).

The same case runs correctly when using velocityComponentLaplacian for dynamic mesh motion (naturally with different actual mesh motion
definition with a 0/pointMotionUz dictionary file).
Steps To Reproduce1. Unzip the attached test case.
2. Run the decomposePar utility.
TagsNo tags attached.

Activities

jskortel

2025-01-01 11:42

reporter  

DynMeshMot-TEST.zip (55,148 bytes)

henry

2025-01-01 12:45

manager   ~0013498

The pointDisplacementz file supplied with the case is incorrect; user support request.

Issue History

Date Modified Username Field Change
2025-01-01 11:42 jskortel New Issue
2025-01-01 11:42 jskortel File Added: DynMeshMot-TEST.zip
2025-01-01 12:45 henry Assigned To => henry
2025-01-01 12:45 henry Status new => closed
2025-01-01 12:45 henry Resolution open => no change required
2025-01-01 12:45 henry Note Added: 0013498