[friedenhe]

Dear Foamers,

We are pleased to introduce DAFoam: an open-source discrete-adjoint framework for multidisciplinary design optimization with OpenFOAM. The source code is available at https://github.com/mdolab/dafoam and the full documentation (download, installation, and tutorials) is available at https://dafoam.rtfd.io

DAFoam contains a suite of discrete adjoint solvers for OpenFOAM. These adjoint solvers run as standalone executives to compute derivatives. DAFoam also has a Python interface that allows the adjoint solvers to interact with external modules for high-fidelity, multidisciplinary design optimization.

DAFoam supports design optimizations for a wide range of disciplines such as aerodynamics, heat transfer, structures, hydrodynamics.
It has been used to handle optimization problems such as aircraft aerodynamic design, turbine aerothermal design, compressor aerostructural design, and ship hydrodynamic design.

We hope you will find it useful. If you want to try DAFoam and have questions, do not hesitate to contact us. Thanks!

Regards,
Ping

[JunaidAhmad]

Hello Ping,


I want to change the optimizer to snopt, but getting this error.


"pyOptSparse Error: There was an error importing the compiled snopt module"


kindly guide me.
Junaid

[friedenhe]

Originally Posted by JunaidAhmad

Hello Ping,


I want to change the optimizer to snopt, but getting this error.


"pyOptSparse Error: There was an error importing the compiled snopt module"


kindly guide me.
Junaid

Thanks for your interest. SNOPT is a commercial optimizer and is not included in the Docker image. Refer to https://mdolab-pyoptsparse.readthedo...s/pysnopt.html on how to buy and compile SNOPT in pyOptSparse.

[JunaidAhmad]

Thanks for reply.
Can you share any link where I can learn ins and outs of DAFoam via videos or written tutorials. From pyHyp, pyGeo to DAFoam all steps.

Also as DAFoam solves both in-compressible and compressible problem. however adjoint optimization in OpenFoam v1906 is only valid for incompressible flows.



Question

Is DAFoam solver are based on openFaom or ADflow for compressible flows?

[friedenhe]

Originally Posted by JunaidAhmad

Thanks for reply.
Can you share any link where I can learn ins and outs of DAFoam via videos or written tutorials. From pyHyp, pyGeo to DAFoam all steps.

Also as DAFoam solves both in-compressible and compressible problem. however adjoint optimization in OpenFoam v1906 is only valid for incompressible flows.



Question

Is DAFoam solver are based on openFaom or ADflow for compressible flows?

For your questions:

Refer to http://dafoam.github.io for DAFoam documentation. In the "Get started--Details of transcripts" section, you can find instructions on the interfaces for pyGeo, IDWarp, pyOptSparse, etc. In the tutorials section, you can find a bunch of DAFoam tutorials.

Check this website for the details of each component in the MACH optimization framework: https://mdolab-mach-aero.readthedocs...html#mach-aero

Check this open-access paper on the details of DAFoam https://doi.org/10.2514/1.J058853

For your last question: we didn't use the OpenFOAM's built-in continuous adjoint solver, which is indeed for incompressible flow only. Instead, we implemented our own discrete adjoint solvers, which apply to incompressible, compressible, and transonic flows. Check the paper mentioned above. For flow simulations, yes we use OpenFOAM's built-in solvers, like simpleFoam, rhoSimpleFoam.

[cheng1988sjtu]

Dear Ping He,

Thank you very much for the great contribution. I am learning about your code (DAFOAM), could you please elaborate more on the residual calculation? For a fvVectorMatrix UEqn, I see that the momentum residual is calculated as:

UEqn & U_ - fvc::grad(p_).

Is it the same as UEqn.A() & U_ - UEqn.H() - fvc::grad(p_) or UEqn.A() & U_ - fvc::grad(p_)?

In addition, U_ and p_ are perturbed solution, is it correct?

[friedenhe]

Originally Posted by cheng1988sjtu

Dear Ping He,

Thank you very much for the great contribution. I am learning about your code (DAFOAM), could you please elaborate more on the residual calculation? For a fvVectorMatrix UEqn, I see that the momentum residual is calculated as:

UEqn & U_ - fvc::grad(p_).

Is it the same as UEqn.A() & U_ - UEqn.H() - fvc::grad(p_) or UEqn.A() & U_ - fvc::grad(p_)?

In addition, U_ and p_ are perturbed solution, is it correct?

Hi Charlie,

Thanks for your interest in our code. If you do URes = UEqn.A() * U_ - UEqn.H() + fvc::grad(p_), I expect you will get the same results as UEqn & U_ + fvc::grad(p_). However, the latter is recommended because it is much more flexible and general.

Regarding your second question, U_ and p_ can be original (converged) fields or perturbed fields. If the former, URes is the original residual. If the latter, URes will be the perturbed residual. Both the original and perturbed residuals will be used for computing the partial derivatives using the finite-difference method.

Ping

[friedenhe]

We will no longer track this thread. If you have more questions, please post them to the DAFoam Github Discussions. We will respond as soon as possible.

[be_inspired]

Hi,

Dafoam includes IDwarp as morphing solution for the meshes. According to the documentation, it is a quite robust approach based on the displacement of points using a inverse distance algorithm.
The current displacement solvers implemented in OpenFoam are based on cell displacement and after that, the point coordinates are reconstructed. It is sometimes not very robust, mainly for high reynolds numbers flows with a y+=1.

Could it be possible to use IDwarp for that?

BR
Marcelino

[Muhammad Bilal Anwar]

Hi

Can anyone pls help me on this? I am stuck on this for the past 2 weeks and is really frustrated now.

I am using IDWarp to deform a volume mesh. I have created a fluid domain with an Onera wing inside it. The unstructured mesh (Tri, tetra) is created using ICEM and exported in .cgns format.

When I read this mesh using IDWarp it gives me th following error.

"IDWarp cannot handle boundary conditions defined by "PointRange" or "PointList". Please use boundary conditions defined by "ElementRange" or "ElementList" instead"

I don't have any idea how to do define that. I have tried different strategies to give BC inside ICEM. but none is working.

Any help on this appreciated. I am attaching the screen shot of the mesh, bounday conditions and the error.