[Horus]

Hello,

it seems to be possible to use regular expressions in some?/all? openfoam configuration files. However, I was unable to find any announcement or documentation about that features.

For example I try to include all STLs from the triSurface directory in my snappyHexMesh:

geometry
{
        ".*\.stl"
    { type triSurfaceMesh; }
};

This returns:

--> FOAM FATAL ERROR: 
Cannot find triSurfaceMesh starting from "/scratch/flindner/snappy/constant/triSurface/.*\.stl"

    From function triSurfaceMesh::checkFile(const fileName&, const fileName&)
    in file searchableSurface/triSurfaceMesh.C at line 116.

Is there any information on how this works?

Thanks,

Florian

[wyldckat]

Hi Florian,

By what I can see, OpenFOAM uses POSIX regular expressions, but it only applies to OpenFOAM's keywords; doesn't work for files.

• Here is something that implies this, namely regex is only usable in "#remove", not "#include": http://www.openfoam.org/docs/user/basic-file-format.php
• As for the kind of regex, it was added back in OpenFOAM 1.6: http://www.openfoam.org/archive/1.6/...ease-notes.php - quoting:

  Dictionaries can use words (unquoted) or regular expressions (quoted) for their keywords. When searching, an exact match has priority over a regular expression match. Multiple regular expressions are matched in reverse order.

I think this wasn't extended to filenames due to the overhead of having to go through the file system looking for matches.

The work around is to use the following structure:

1. Replace in "snappyHexMeshDict":

   geometry
   {
           ".*\.stl"
       { type triSurfaceMesh; }
   };

   For this:

   geometry
   {
       #include "sHM.geometries"
   };

2. Generate the file "system/sHM.geometries" with the following commands:

   rm system/sHM.geometries
   find constant/triSurface/ -name "*.stl*" -type f -printf "%f\n" | sed 's=\.gz==' | while read file; do
     echo $file >> system/sHM.geometries
     echo { type triSurfaceMesh; } >> system/sHM.geometries
   done

By the way, find doesn't use POSIX regex, it uses shell patterns.

Best regards,
Bruno

[Horus]

Hello!

Thanks for your explanation. One problem still:

    refinementSurfaces
    {
      "(BPID|GOPT|GRWS).*"
        { level (0 1); }
    }

Works as intended, picking all geometries starting with BPID, GOPT or GRWS, but this somehow fails:

    refinementRegions
    {
      "VRES.*"
        {
         mode inside;
         levels ((0 1));
        }
}

FOAM says:

--> FOAM FATAL ERROR: 
No surface called "VRES.*"
Valid surfaces are 
19
(
[...]
VRES0300.stl
VRES0400.stl
VRES0500.stl
VRES0600.stl
VRES0700.stl
)


    From function shellSurfaces::shellSurfaces(const searchableSurfaces&, const dictionary>&
    in file autoHexMesh/shellSurfaces/shellSurfaces.C at line 429.

FOAM exiting

According to my understanding of the regexp abore the VRES geometries should have been matched... Any idea why not?

Another question: Is is possible to use groups and reference them later? My idea is something like that:

    refinementRegions
    {
      "VRES0(.)00\.stl"
        {
         mode inside;
         levels ((0 $1));
        }
}

Regards,

Florian

[wyldckat]

Hi Florian,

If you search for "POSIX regex" online, you should pick up on several tutorials.

The ".*" regular expression doesn't pick up on certain characters. This is because sometimes this helps isolate sentences.

In your case, you might want to use either one of these:

• "VRES.*\..*"
• "VRES[0-9]*\..*"
• "VRES0[0-9]00.stl"

Best regards,
Bruno

[Horus]

I did use a regular expression tester which matches exactly the way I planned.

The problem seems to be somewhere else, none of the regexps you proposed worked. They all produce the same error:

No surface called "VRES[0-9]*\..*"

Regards,

Florian

[wyldckat]

Hi Florian,

I've tried to reproduce the error you're getting, but I haven't managed to get it.

The only thing I can figure out is that you're trying to use a surface to define a region, which I don't think snappyHexMesh allows...

If you can provide a (small) test case, it's easier to figure out what is happening.

Best regards,
Bruno

[philippose]

Hello there,

A Good Evening to you!

I was just thinking...... I am quite certain that snappyHexMesh does not use the "regular expression" system available in OpenFOAM while reading the snappyHexMeshDict file....

If you look into the code of "refinementSurfaces.C" starting from line 300, you will notice, that it uses the simple ".found(....)" function to locate the names of the geometries specified in the "refinementSurfaces" sub-dictionary.... As far as I know, this does not support Regular Expressions.

It looks like as of now, OpenFOAM allows "Regular Expressions" only for patch names, like in the "0/U", "0/p", etc.... files, and in some other internal usages..... In order to use Regular Expressions, you need to use a function "findStrings", into which you give a list of allowed names, and the regular expression.... and it tries to find matches....

I have explicitly modified some of my post-processing code to use Regular Expressions for finding patches (using the functionality provided within OpenFOAM).... it was not something which worked out of the box without changes to my code.

Disclaimer ;-):
Due to the complexity of OpenFOAM, I think what I have just said above is correct..... but again..... I might be wrong..... it would be great if someone could check this out.....


Have a nice day ahead!

Philippose

[Horus]

Hello!

Partly it seems to use regular expressions, since

 refinementSurfaces
    {
      "(BPID|GOPT|GRWS).*"
        { level (0 1); }
    }

works as intended. The same configuration put under refinementRegions fails as I have described.

Funny thing...

Thx!
Florian

[Horus]

Just as an addition, layers seem to support regexp too:

addLayersControl { layers ".*" { ... } }

works.

[wyldckat]

I've written this above:

Originally Posted by wyldckat

The only thing I can figure out is that you're trying to use a surface to define a region, which I don't think snappyHexMesh allows...

Does defining the full name directly in the region block work?

[Horus]

Using a surface in refinementRegions works perfect. In fact, since STL defines nothing but surfaces thats the only way if you want to use a STL file. The surface must be closed so you can define inside and outside.

If works perfect when using the full name of the surface. My question is just if ommiting the full name and using regular expressions is possible. It seems to be possible for refinementSurfaces and layers, but not for refinementRegions.

Or did I misunderstand you?

[wyldckat]

Hi Florian,

Mmm, I think you understood me correctly. I didn't know we could use a closed STL region for the "refinementRegions" block. And I assume you also defined them in the first geometries block as well.

Therefore, I think this can be considered a bug, namely that regex not working in the "refinementRegions" block. Please create a small example case and report it on the official bug tracker: http://www.openfoam.org/mantisbt/my_view_page.php

Best regards,
Bruno

[Horus]

I don't think a test case is necessary.

http://www.openfoam.org/mantisbt/view.php?id=527

[wyldckat]

Hi Florian,

Then at least provide a complete "snappyHexMeshDict" that exemplifies the problem. Otherwise they might simply say something like it works as intended or indicate that there isn't enough information to reproduce the reported issue.

Best regards,
Bruno

[Horus]

Ok, did it.