CFD Online Discussion Forums - [swak4Foam] swak4foam for fe40: fvOption library don't compile?

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)

- OpenFOAM Community Contributions (https://www.cfd-online.com/Forums/openfoam-community-contributions/)

- - [swak4Foam] swak4foam for fe40: fvOption library don't compile? (https://www.cfd-online.com/Forums/openfoam-community-contributions/181703-swak4foam-fe40-fvoption-library-dont-compile.html)

swak4foam for fe40: fvOption library don't compile?

Hi
I installed fe40 and swak0.4.0 (Ubuntu 16.04)

I see no obvious error and I have what seems a reasonable build that work
...except that fvOption library is missing.

I see no error message in the attached log below but no mention of fvOption either.

Code:

Previously compiled for OpenFOAM 4.0



/home/foamtest/foam/foam-extend-4.0/ThirdParty/rpmBuild/BUILD/swak4Foam-0.4.0/privateRequirements/bin existing. Prepending to PATH-variable (private version of Bison)



No file 'swakConfiguration'. Python etc won't work. See README for details

Try 'ln -s swakConfiguration.automatic swakConfiguration' for automatic configuration. BEWARE: this does not work on some systems

Checking swak4Foam-version and generating file

Swak version is 0.4.0

Bison is version 2.7.12-4996

Flex is version 2.6.0 (Minor version: 0)

OpenFOAM-version: Major 4 Minor 0 Patch 0 (-1 == x / 0) Fork: extend

No change to swak4FoamParsers/foamVersion4swak.H

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswak4FoamParsers.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakLagrangianParser.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libgroovyBC.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakFunctionObjects.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libsimpleFunctionObjects.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libsimpleLagrangianFunctionObjects.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libsimpleSearchableSurfaces.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libsimpleSwakFunctionObjects.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakTopoSources.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakSourceFields.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakFiniteArea.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libgroovyStandardBCs.so' is up to date.



SWAK_PYTHON_INCLUDE not defined .... no Python-Integration. Most people are fine without it



'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakChemistryModelFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakDynamicMeshFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakFvcSchemesFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakLagrangianCloudSourcesFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakLocalCalculationsFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakMeshQualityFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakMeshWaveFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakMRFFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakRadiationModelFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakRandomFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakSurfacesAndSetsFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakThermoTurbFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakTransportTurbFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakVelocityFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakFacSchemesFunctionPlugin.so' is up to date.

'/home/foamtest/foam/site/4.0/lib/linux64GccDPOpt/libswakCoalCloudAdaptor.so' is up to date.



If you have your own function-plugins you can specify them using the SWAK_USER_PLUGINS environment variable and they would be compiled now. If you don't know what this means: don't bother. You propably don't need it





SWAK_PYTHON_INCLUDE not defined .... no Python-Integration. Utility funkyPythonPostproc not compiled



make[1]: '/home/foamtest/foam/site/4.0/bin/linux64GccDPOpt/funkyDoCalc' is up to date.

make[1]: '/home/foamtest/foam/site/4.0/bin/linux64GccDPOpt/calcNonUniformOffsetsForMapped' is up to date.

make[1]: '/home/foamtest/foam/site/4.0/bin/linux64GccDPOpt/funkySetAreaFields' is up to date.

make[1]: '/home/foamtest/foam/site/4.0/bin/linux64GccDPOpt/fieldReport' is up to date.

make[1]: '/home/foamtest/foam/site/4.0/bin/linux64GccDPOpt/funkySetBoundaryField' is up to date.

make[1]: '/home/foamtest/foam/site/4.0/bin/linux64GccDPOpt/funkySetLagrangianField' is up to date.

make[1]: '/home/foamtest/foam/site/4.0/bin/linux64GccDPOpt/funkyWarpMesh' is up to date.

make[1]: '/home/foamtest/foam/site/4.0/bin/linux64GccDPOpt/funkySetFields' is up to date.

make[1]: '/home/foamtest/foam/site/4.0/bin/linux64GccDPOpt/replayTransientBC' is up to date.





If you want to use swakCoded-function object or compile software based on swak set the environment variable SWAK4FOAM_SRC to /home/foamtest/foam/foam-extend-4.0/ThirdParty/rpmBuild/BUILD/swak4Foam-0.4.0/Libraries (most people will be fine without setting that variable)

Do I miss something?
Is it a known bug ( I went through the readme file and saw nothing obviously related..)

Any idea what I am doing wrong?
Thanks
JF

Ok
I think I can answer my question:

I checked the source of fe40 and it seems there is no fvOption in it ( am I mistaken?)

That will explain the fact that swak4foam does not create its Fvoption library.

Does anybody knows if there is a reason why fvoptions have not been included in FE?

Thanks

JF

Quote:

Originally Posted by jf_vt (Post 630556)

Does anybody knows if there is a reason why fvoptions have not been included in FE?

Quick answer: Not enough time and because fvOptions is still not at 100% functionality. See http://openfoam.org/news/funding-2017/ - section "Specific Aims for 2017".

Nonetheless, foam-extend still has the precursor to the fvOptions feature, usable by swak4Foam... look for "sourcesProperties" in the "Examples" folder in swak4Foam.

Quote:

Originally Posted by wyldckat (Post 630647)

Hi, Bruno
Have you ever considered to copy the src/fvoptions in OpenFOAM 3.0.1 to foam-extend, then change some variables and paths in make/option, and compile the specific fvoptions for foam-extend.

I want to have a try, but the my poor programming knowledge......

I am trapped by the different susp between OpenFOAM 3.0.1 and foam-extend 3.2

Sorry for lack of information,since my laptop is not by side......

Sent from my iPad using CFD Online Forum mobile app

Quote:

Originally Posted by zhouqy1994 (Post 643207)

Hi, Bruno
Have you ever considered to copy the src/fvoptions in OpenFOAM 3.0.1 to foam-extend, then change some variables and paths in make/option, and compile the specific fvoptions for foam-extend.

Quick answer: As I wrote before, due to "Not enough time" is one of the reasons why no one has ported "fvOptions" to foam-extend.

Furthermore, the other reason as to why "fvOptions" hasn't been ported to foam-extend, is because the feature is not yet 100% completed, as I mentioned in my previous post.

I am trying to simulate mi case using fe40 and swak4Foam and I get this error:

--> FOAM FATAL ERROR:

gradientInternalCoeffs cannot be called for a genericFvPatchField (actual type groovyBC)
on patch inlet of field U in file "/home/mapache/Documentos/aneurisma/coarse/0/U"
You are probably trying to solve for a field with a generic boundary condition.

those are my U and controlDict files

Somebody can help me please.

Quote:

Originally Posted by wyldckat (Post 630647)

Hi Bruno - sorry to drag up an old post, but is this still true of foam-extend 4.0?

I tried running the two Example cases "pitzDailyWithExplicitPoroPlug" and "pitzDailyWithImplicitSource", and they run ok (except that they don't like the streamlines definition in the controlDict) but the momentum source defined in the "sourcesProperties" file doesn't appear to have any impact on the solution.

Is there something else needed to introduce additional sources in fe-4.0?

Hi Bruno,
Is it possible to use fvOption in fe-4.1 now? I ran into some problems and needed to use fvoption to fix them.
Thanks
Young