[Focus00000]

Hi Everyone!
We are trying to develop a GUI OF OPENFOAM FOR OUR INSTITUTE. To do so initially we are Generalizing the fvSchemes controldict and other OPENFOAM files by listing every option available in them.
The problem is with fvSolutions file every solver has a different fvSolutions file ....is it possible to make a single generalized fvSolutions file which will work with any solver ???

[simrego]

Hi!


If not for all, but for the most you can do it. Supply the PIMPLE and SIMPLE dictionary, all fields which can be in the solver. You can also use regex so for example ".*"{solverOptions} will be used for every field, etc...
You can add everything in the fvSolution, the solver will only read what is needed.


A bruteforce method can be if you just use the same fvSolution for different solvers. If the solver will miss something, just add it. Then go to the next solver with the same fvSolution...


Another possibility if you create more fvSolutions, like fvSolution.simpleFoam, fvSolution.icoFoam, etc. For all the solvers you need. And then just copy-paste the needed file into your case.

[raumpolizei]

Hey,

If you know the general structure of a solver and each of your group follows strict naming conventions, you could try to find out which fields are being solved by pattern matching the solver files. For instance, running:

grep -Erh "[a-zA-Z]*\.solve\(" | cut -f 1 -d '.'| tr -d ' '| sed "s/Eqn//"

in a solver directory should give you a list of field names. Again, here, I assume some OF conventions, for intance that the name of the matrix object to solve field 'X' is called 'XEqn' and that the field 'X' is also registered with name 'X' at runtime. It's just an idea. Maybe this helps. Also, I'm not the best at bash scripting. They are probably cleaner approaches than the one I suggest. Good luck!

[Focus00000]

Thank you So Much ...your suggestions were great help

[Focus00000]

I'm not familiar with regex .* concept.
can u help me understand it ?
I have noticed in fvSolutions with some solver options it uses .*
e.g in some files it uses "k.*" ....in others just simply k without .*?
if we use .* for every solver option or dont use .* at all ..what difference will it make?
I'm new to openfoam or ubuntu scriting ...So i hope you don't mind answering my questions ?..Thanks

[simrego]

Hi!


You can search for "POSIX regex" and probably you will find how to use it.
The most common ones I know are:


".*" -> everything matches
"U.*" -> Everything starts with U
"(U|k|h)" -> match for U, k, and h so you don't need 3 dictionary if they are the same.
"(U|k|h)Final" -> This will match for UFinal, kFinal, hFinal


You can do fancy stuff with POSIX regex, but sadly these are ones I know
Also in the tutorials you can find some usage.

I hope it helps.

[simrego]

Sorry I missed it and can't edit my post:

" are needed around the variables!!!

[raumpolizei]

Originally Posted by Focus00000

I'm not familiar with regex .* concept.
can u help me understand it ?
I have noticed in fvSolutions with some solver options it uses .*
e.g in some files it uses "k.*" ....in others just simply k without .*?
if we use .* for every solver option or dont use .* at all ..what difference will it make?
I'm new to openfoam or ubuntu scriting ...So i hope you don't mind answering my questions ?..Thanks

As you correctly figured out, the grep command means with the -E option enables regex pattern. The first part "[a-zA-Z]*" matches 0 or more of the characters in the brackets, so here any letter. Actually, it would be better to use "[a-zA-Z]+" which would mean at least one or more of the characters in the brackets. For instance, this would match "UEqn" or "pEqn" or "rhoEqn", the second part "\.solve\(" matches the part following the first part and simply translates to ".solve(". In such a manner you are able to match "UEqn.solve(".

In the fvSolution files the expression "rho.*" is also a regex expression matching. The dot "." matches any character. The "*", as previously explained, matches zero or more of the previous character. This means that the expression "rho.*" matches not only "rho" but also "rhoFinal" or "rhoAwesomeVariable234askj2" and will use the same solution settings for all these fields. Hope it's understandable.

[Focus00000]

Originally Posted by raumpolizei

As you correctly figured out, the grep command means with the -E option enables regex pattern. The first part "[a-zA-Z]*" matches 0 or more of the characters in the brackets, so here any letter. Actually, it would be better to use "[a-zA-Z]+" which would mean at least one or more of the characters in the brackets. For instance, this would match "UEqn" or "pEqn" or "rhoEqn", the second part "\.solve\(" matches the part following the first part and simply translates to ".solve(". In such a manner you are able to match "UEqn.solve(".

In the fvSolution files the expression "rho.*" is also a regex expression matching. The dot "." matches any character. The "*", as previously explained, matches zero or more of the previous character. This means that the expression "rho.*" matches not only "rho" but also "rhoFinal" or "rhoAwesomeVariable234askj2" and will use the same solution settings for all these fields. Hope it's understandable.

yeah got it....you quite clearly explained it to me ....Appreciated

[Focus00000]

raumpolizei....Thanks Man

yeah it was quite clear to understand ..i got it Thanks