View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002487 | OpenFOAM | Bug | public | 2017-03-06 11:52 | 2017-03-10 20:49 |
| Reporter | yuanchuanliu | Assigned To | henry | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | GNU/Linux | OS | Ubuntu | OS Version | 16.04 |
| Fixed in Version | dev | ||||
| Summary | 0002487: Error with sixDoFRigidBodyDisplacementPointPatchVectorField in parallel | ||||
| Description | When a case using sixDoFRigidBodyDisplacement as the BC for a patch in the pointDisplacement field is decomposed and runs in parallel, the following error occurs: keyword solver is undefined in dictionary "case/processor0/0/pointDisplacement.boundaryField.body". | ||||
| Additional Information | It is associated with the write function in the sixDoFRigidBodyMotion library, which does not write the variables related to SixDoFSolver settings when called by sixDoFRigidBodyDisplacementPointPatchVectorField::write(). | ||||
| Tags | No tags attached. | ||||
|
|
Do you have a small case which reproduces this problem? All of the tutorial cases run fine using the newer and better sixDoFRigidBodyMotion specification so I do not have a case which fails. |
|
|
|
|
|
I have added a case adapted from the floatingObject tutorial using the interDyMFoam solver. Execute Allrun script to attempt to run the case in parallel, which will exit with the error reported above. |
|
|
One possible fix for this problem is to remove the deprecated sixDoFRigidBodyDisplacement BC altogether. Is there a particular reason why you need this BC rather than use the more flexible sixDoFRigidBodyMotion solver? |
|
|
Not at all. I was just running some old simulations and encountered this issue so I chose to report it. I agree with you that the sixDoFRigidBodyMotion solver is better. Please do so if it is easier to remove this BC than to develop a fix with a lot of efforts. Thanks. |
|
|
OK, thanks for the clarification. I think at this stage it is more efficient to move to the new method rather than spend effort maintaining legacy and deprecated functionality. |
|
|
Resolved in OpenFOAM-dev by commit 55f3e808eddb1180b459a81d724de84638ad6933 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-03-06 11:52 | yuanchuanliu | New Issue | |
| 2017-03-06 20:21 | wyldckat | Relationship added | related to 0001530 |
| 2017-03-09 16:08 | henry | Note Added: 0007871 | |
| 2017-03-09 17:07 | yuanchuanliu | File Added: floatingObject-pointDisplacement.tar.gz | |
| 2017-03-09 17:09 | yuanchuanliu | Note Added: 0007880 | |
| 2017-03-09 17:40 | henry | Note Added: 0007883 | |
| 2017-03-09 17:51 | yuanchuanliu | Note Added: 0007886 | |
| 2017-03-09 18:00 | henry | Note Added: 0007887 | |
| 2017-03-09 23:22 | henry | Assigned To | => henry |
| 2017-03-09 23:22 | henry | Status | new => resolved |
| 2017-03-09 23:22 | henry | Resolution | open => fixed |
| 2017-03-09 23:22 | henry | Fixed in Version | => dev |
| 2017-03-09 23:22 | henry | Note Added: 0007888 |
