Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 480
    • Issues 480
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #2340

AMI patch addressing fails, solver crashes when using cellZone created via topoSet

I have a rather strange issue, and I have tried every workaround I can think of with no success.

When running AMI + mesh motion, I'm able create isoSurfaces at run time, including limiting them to a specific cellZone via the "zone" entry. However, the AMI patch addressing crashes if the cellZone I choose was generated via topoSet - in my case using searchable surfaceToCell. logFiles: log.FAIL_production_pimpleFoam log.FAIL_tutorial_pimpleFoam

Luckily, the issue can be easily reproduced with the rotatingFanInRoom tutorial. Steps:

  1. run Allrun.pre
  2. topoSet -time constant -constant -dict system/topoSetTest, using attached STL and topoSetDict topoSetTestsearchableStl.stl
  3. check mesh to verify the new cellZone exists and has cells
Checking basic cellZone addressing...
                CellZone        Cells       Points       VolumeBoundingBox
           rotatingZone        26544        35177        1.043 (-3.789551 1.210449 2.256408) (-2.210449 2.789551 2.8)
           **fluid_test**    **1154**       1725     1.169422 (-4.411605 1.29768 1.205809) (-1.691286 2.813284 1.512392)
  1. Solve using the attached controlDict (or add the lines below to controlDict.functions) controlDict
  2. Of note is that using the other cell zone, created by snappy, works fine.
    runTimeObj_isoQ
    {
	timeStart	0;
        type             surfaces;
        libs             (sampling);
        executeControl   timeStep;
        executeInterval  1;
        writeControl     timeStep;
        surfaceFormat    vtk;
        writeInterval    1;
        fields           (U p);
        surfaces
        {
            qIsoSurf
            {
                type            isoSurface;
                interpolate     true;
                store           true;
                isoField        p;
                isoValue        0;
		zone		fluid_test;
            }
        }
    }
Edited Jan 27, 2022 by Aaron
Assignee
Assign to
Time tracking