[Bob Tipton]

Hello all, new to OpenFoam, but fairly experienced with FEA/CFD/CAE.

I'm stuck with a Win 10 LapTop
I'm doing some modeling of 'stiff' geometries. i.e. the geometry is large and simple, but there is a very small, low pressure ejector slot which has to maintain boundary layer attachment.

When the design works correctly, it the ejector energizes a large existing vortex. In theory the vortex should remain attached, it certainly does when not energized.


My goal was to write a new general purpose mesher that can support cases like this. I need this because the existing meshers are not sufficient to the task. Therefore I was planning on developing under git.OpenFOAM repo.

This presents several issues, and they are probably best addressed in different threads. Forgive me for starting here.

I've tried VirtualBox and WSL in the last two days and both have a lot of issues. VB was the only option that could actually compile code.


BUT IT WON'T run ParaView or paraFoam - the graphics crashes. Right now I'm stuck not being able to see the output. I suppose I could download a win version and run paraFoam on the Win 10 host instead of the Ubuntu guest.

There's also a solution convergence problem. My design is apparently working better than expected - the forces explode far into the run (t>500). It appears that the vortex keeps energizing until the simulation can't handle it. I'll post details in another thread.

The design makes use of fabric sails and deforms under load - aeroelastic case. I'm currently modeling as rigid.

I would normally drop the effort, but the early results are too good to walk away from. Most runs show no effect (flow didn't attach or too much leakage), the next group explode, the last group of 3 or 4 converge with forces 1.5 x greater than the non-energized case. It appears these can be made very large.

The science is valid, it's what keeps the boundary layers under control in engine IR suppressors and makes the NOTAR helicopter anti-torque system work. I worked with the guys who led both those efforts.

Right now, I don't want to submit a paper until I can get reliable, stable results of the energized case.

I can't effectively tune the ejector design without a much better, much faster mesher.



It's a big problem, so I'm not dumping all the data at once.

First issue is a working dev system that I can view results in.



Thanks

[HPE]

Could you please isolate your questions? Personally, didn't get what you are seeking for.

[Bob Tipton]

I apologized for the large dump before I gave it.


"It's a big problem, so I'm not dumping all the data at once."

Please remove the 'not'.


First issue is a working dev system that I can view results in.


I'm on a Win 10 laptop. Dual boot would solve part of the problem, but then I can't switch contexts as fast as I need to.


Sorry if I offend, but I do not subscribe to the 'solve the issue at hand without full background' philosophy. That road provides quick answers with long term problems.
IMO.

[HPE]

I still don't get `the` question I'm afraid, but here we go.

You can use `ParaView`+`OpenFOAM` in Windows (without virtual box) as well as almost any Unix OS without leaving one for another.