Hey ho,
I can’t get Eddy3D running. I spent the whole day trying to get it running… I have blueCFD2020-1 running in Rhino8 on Win11, downgraded from a newer MPI Version to the one blueCFD is installing after i got this error:
now I have tested the paraviewer demo (can.ex2, which is running), several openfoam environments (the actual is " OpenFOAM 8 mingw-w64 Double Precision (of8-64), using MSMPI71" which says it is rdy) but there was also no change in the outcome of the Eddy simulations.
I also made sure that I’m admin in this session. I rebuilded the template with the Eddy 0.4.8 components but also no change.
Some other findings which I could not investigate to further tackle this down:
the clean component turns red when pressed if it is in Mesh Directory mode, its not possible to access this error, it seams it does nothing in the folder on run
the indoor domain component seams to do something but it does not make a log file unfortunatly
the probing does not complain in most “simulation” cases (after installing blueCFD) but returns no results, there is a glimps of a terminal window opening but its impossible to read the information it provides
is it possible to active some additional logging for indoor simulation? some other ideas what can cause this? how to proceed?
any help is very welcome, greets and all the best,
Martin
an additional observation: the Eddy3d intersection component seams not to work as expected or I misunderstand the use of it. It does not react on any height change at all. I use mesh split now which gives more credible results and is faster than the Eddy intersect component.
Thank you for the reply! I tested your workaround but once I change the geometry the component fails again. For me it seems like its just doing fine if you stay inside this demo-case but maybe I’m wrong…
For now I give up using Eddy3D with my setup (Rhino8 / Win11 / BlueCFD2020) but I would really like to test it in the future after the update you mentioned!
For whom it may interest- I now use GH_Wind which is no OpenFoam simulator but at least its working with my setup and gives some results (not jet validated if they are correct) which looks something plausible…
Thanks and greets,
Martin
Can you guys give us an update of when you’re planning this update? I also run onto the issues mention in this post and others. Looking forward to start using it
@martin.c.baier did you manage to run GH_Wind in rhino8?
I tried it for both R7 and R8, but i’t does load, seems to be compiled for R6 (which i don’t have). I also run into this bug R* that is unfortunately failing eddy3d at the moment.
Hi @eddy3d , do you think there is a workaround until McNeel fixes this issue? It seems like a mismatch in the mapping of Probing, between the output Probing Points and Probing Vectors
here the visualistion of simple wind analysis. May we can in the meanwhile remap the points or vectors??
I’m struggling to follow what the issues are here. Probing works for me with Rhino 8.8. Could you please post your issues here in separate threads including your Rhino and Eddy3D versions?
0.4.8 does not work with R8.13 for indoor simulations, the simulations runs, but doesn’t seem to run successfully, can’t be probed and can’t visualize residuals. Works for outdoor simulations tho.
Interestingly, 0.4.1.4 seems to work fine on R8.13 for both inddor and outdoor.