On Scaling and Component Input Docs

Hi, I just got the beta 0.4.8 Eddy3D and that wind tunnel template to work with RH8-Win. Great stuff, thank you guys SO MUCH for this beginner-friendly access / entry to openFoam!!

Now I want to replace the template geometry with my own.
I’m trying to work out some general force boundaries of a CSP heliostat. Generally speaking: a 5m x 5m mirror surface with a 10-20cm sandwich plate as support, everything flat n boxy.

  1. Would you see a problem using Eddy for this kind of detail-model-size-case? I don’t need hyper-precise results, just a general idea of the wind loads on the mirror/surfaces.

  2. Does Eddy3D necessarily need to work in a meter-unit model?
    My model is in mm and it’s about 5m x 5m x 5m large. Would you recommend scaling my model DOWN (to meters) or the boundary boy UP (and try n work with mm in Eddy)?

  3. I’m guessing a resolution between 10 and 100 per meter would be helpful for understanding my load case.
    Is there a documentation of Eddies component inputs and what they stand for, number-domains etc? I’m guessing it would be a subset of some OpenFoam params – maybe a link to the corresponding page of the doc.OpenFoam.com on the Eddy3D support page (per component) would do the trick?

Thanks again, I’m really grateful somebody implemented a tool like this for GH !!

1 Like

Ok, so apparently this time there is a description of the components that’s actually helpful!
I’m working with RH/GH for several years now, and I STILL get slapped in the face by trivial stuff…

Wow, ok so the help is only displayed when there are NO other components connected.
even the right-click-help-menu gives a different level of detail…

Is that a common Grasshopper UI philosophy?? WHY !?!?



Thanks, Vincent! Keeping this alive and moving forward while attending to new responsibilities is difficult but we are trying our best.

  1. Sounds realistic to me.
  2. Yes it does. I would work in meters only.
  3. Eddy3D adheres to the official OpenFOAM dimensions which you can fine here and here.