Actions to be done
Actions to be
done by Victor Reijs
is licensed under CC BY-NC-SA 4.0



Actions
This are actions that are important to work on (these are puple bold texts in the below
linked web pages).
Green texts are for VR's actions.
Black texts are for simulation (CFD/formula/etc.) interested
people.
Red categories are important to me.
Categories of the actions:
- To be checked during the present
SlimmeMolen prototype
- For possible integration in future
SlimmeMolen prototype
- Problems with software
- More theory/literature needed
- Possible new definitions
- Include in future simulations
- Better 3D-modeling sofware
slimmemolen
- A: The amount of Bytes needs to be
determined over the coming time.
- A: Need to check the sensor (AS3935)
during thunder storms. Hopefully in the coming autumn/winter
weeks.
- B: It would be good to test the
LMS303DLHC (which is used in the smartmolen project). Not
planned for this prototype.
- B: Perhaps better to use the ESP-12F (or
ESP32 variant?) for lower power usage, but it is not expected
that this will be prototyped.
- B: LoRaWAN should be a better
alternative then WiFi and/or ESP-Mesh. It is not expected that
this will be prototyped.
- B: For this prototype the accuracy of
acceleration and speed is ok-ish, but it is expected
improvements (by calibrating) can be made
- C: Need to determine why the InfluxDB
database grows fast. The first 55 days of InfluxDB data 4GByte
and the last few 10 days around 100MByte/day/2mills, we need
to compare this to the 4.5MByte of JSON messages that are
generated with the Boxes/day/2mills; why is there a difference
of a factor of 20!?
- C: Does someone know a solution of the
maximum message size of I2C? Please let me know.
For now, I am splitting the I2C messages.
- C: This ESP-Mesh instability is still a
major issue!!! A question has been asked on the painlessMesh
GitHub site. Perhaps using LoRaWAN (which is expected not to
be tested with this prototype).
Boomsim
- D: De verhouding stam hoogte en boom grootte is voor volwassen
bomen 1 op 1. Maar er zullen meestal ook struiken (tot 6m)
onder bomen, in een tuin, staan. Dit verdient nog aandacht.
- G: Cd is depending on velocity, so it would be good to be able
to include (in SIMSCALE) velocity in f.
molenbiotoopDenOord2
- D: Turbulentie (Turbulent
Kinetic Energy: TKE) is belangrijk, door bomen die aanwezig zijn
rondom de locatie van de wieken.
- E: Meestal is de windsnelheid niet echt mooi horizontaal
gelamineerd (bv door bomen) en ook is ze links en rechts van de
askop verschillend. Op deze webpagina is daarom een aanvulling
gedaan: "de gemiddelde windsnelheid op 1m boven de ΒΌ van
horizontale wiekuiteinden".
Workflow3dmodel
- D: Is IDW a good methodology to determine the local wind
speed, or is (C)K(S/D) better?
- D: This theoretical z0t
should be closer to the 0.39m, or not? So is my assumption
wrong for this theoretical terrain?
- D: Incorporating the roof
form can be important in a CFD (certainly for nearby buildings).
- F: In the next iteration: use a
reference ABL (with a certain z0) and then go to
60m and then get a new uref in ABL formula for the
different z0. In the below: Only the z0
was changed and not the uref.
- F: In the next iteration this opening
between trees at 280deg will be rectified.
- G: The STL file made by SketchUp has
problems. Advised to use STEP or Parasolid. Onshape could be
used.
DeHoopSim
- D: This lower ABL at inlet Flow Volume needs to be
investigated/understood to make a proper comparison.
- E: Welke gebouwen: alle
binnen de 400m straal of alleen de meest invloedrijke(n). In
STworkflow (3 meest invloedrijke); DHMworkflow (1 meest
invloedrijke); VR workflow (alle gebouwen).
- E: Welke bomen: alle
binnen de 400m straal of alleen de meest invloedrijke(n). In
STworkflow (3 meest invloedrijke); DHMworkflow (1 meest
invloedrijke); VR workflow (alle bomen).
Acknowledgements
I would like to thank people, such as
and others for their help, encouragement and/or constructive
feedback. Any remaining errors in methodology or results are my
responsibility of course!!! If you want to provide constructive
feedback, please let me
know.
Major content related
changes: October, 27, 2024