ossibly not doable atm. However, I think it would be quite inefficient way to run things.
My above answer was concerning this sentence
Or can I even set up a case on my Windows Laptop and use the seperate Linux machine (or maybe even an Amazon EC2 instance) to run the OF calculations?
This is certainly possible with the use of BF I described above. Concerning AWS instances, I am about to find out this week hopefully when I'm going to try my first cloud OF run. Will let everyone know if I do.
Kind regards,
Theodore.…
It seems that the X and Z direction are graded, with the grading in the X direction not being symmetrical (which is ok if X is the wind direction). If you didn't we would need to check our default settings but if memory serves they should be set at no grading.
As a side note here, a suggestion is to keep your refinement levels, either global or the ones set per boundary, to equal (optimal case) or not very different values. The (2,10) you supplied could potentially create sudden cell size changes which is not optimal, even though probably the 10 isn't going to be used. Settings like (2,3) or (2,4) would be ok. If you want to go higher, raise both numbers.
The update fvSchemes functionality is an added option of BF itself and not a command within OF. Essentially what it does is apply proper schemes to your model according to the mesh quality you have achieved. This is why OF won't recognize it. When we get BF going with the new version this will be done automatically for you.
Finally, the error you are seeing is again eliminated through the use of BF which takes care of the clean up and folder set up for you prior to running the case. For now, to do it manually, what you need to do is this:
1.Delete the /constant/polyMesh folder
2.Cut the polyMesh folder from the /2 folder and paste it to your /constant/polyMesh folder.
3.Delete the /1 and 2/ folders
4.Rename the /0.org folder to /0 (if that was not the case already)
4a.Run the case in serial mode with the simpleFoam command.
or
4b.Run the case in parallel with:
decomposePar mpirun -np x simpleFoam -parallel
Where the x is the number of processors set in your decomposeParDict found in the /system folder, usually set at 4. You can change that number of processors by simply changing that number in the beginning of the dictionary. To avoid other problems here with different number of processors change to scotch method in the same dictionary.
P.S.: Another easier but dirty (to my sensibilities) way is to simply paste the 0 folder inside the 2 folder. Provided boundaries and boundary conditions are set ok this should run. This would work for the serial way.
I hope this helps! When BF is up and running soon most of this will be hidden in the background. But the brute force method you are taking now is also quite educational.
Let me know if you have any other questions or issues! Thanks for testing!
Kind regards,
Theodore.
…
ntended for an easier application of BF and not really for learning how to use BF, hope it was helpful. Not sure what this error is though as I can't reproduce it in my computer. Are you sure you have the latest Human components? I'll try and look it up when I can for you.
Concerning your results, they do look as expected. A heavy wake area behind the building has been created as you can see, with a quite clear pattern of wind deceleration and a recirculating vortex. This is a standard pattern in outdoor wind and something that generally we try to either minimize or plan activities around since these areas tend to have lower wind velocities and less recirculation, thus leading to debris/dust deposition and potentially higher pollutant concentration.
There are a lot of nice examples of urban wind patterns online you can check, it makes easier for you to help validate the results you get.
Finally, the k and epsilon values for outdoor studies are currently being calculated with (pretty) standard equations for the k-e family of turbulence models. I believe you can find these in the BF source code. Unfortunately I don't have access right now to check where exactly but I would look before the blockMesh component, since the case folder with all the values is created at that point.
Good luck in your CFD journey! Please keep posting results and issues!
P.S.: Btw if you are interested on the effect of your building geometry at a section parallel to the wind direction you could also try a 2D simulation. You can do that either by manually editing your blockMeshDict and setting 1 cell width on the direction perpendicular to your wind or by simply assigning a 1m wide windTunnel (centered at your geometry). This will allow you to refine your model much more than possible in a 3D case with lower run times as well. Ofc it's not as accurate as a 2D case but it's nice for experimentation.
Kind regards,
Theodore.…