I did a similar project at 18. Needless to say I didn't have enough HW and SW skills to do much since I implemented the most naive form of the TDOA algorithms as well as the most inefficient way of estimating the time difference through cross correlation. I still learnt a lot and it led me to eventually getting a PhD in SAR systems, which are actually beamformers using the movement of the platform instead of an array
There's even "passive cooling" (called thermal mass activation) where you circulate groundwater through the floors/ceiling or concrete walls to cool them down. Ideally combined with a geothermal source heat pump to recover the waste heat dumped to the ground in the cold season
In Switzerland most offices and the majority of houses have exterior metal slat blinds or rolling shutters. Almost all are operated electrically and quite a few are controlled by inputs from wind and sunlight sensors. Since you can adjust the angle of the slats you can significantly cut down solar gains and glare while still providing ventilation and natural light
Count me in the club of failed scientists. In my case it was the geosciences, I would spend hours trying to make all my analysis reproducible and statistically sound while many colleagues just published preliminary simulation results obtaining much more attention and even academic jobs. On the flip side, the time spent improving my data processing workflows led to good engineering jobs so the time wasn't entirely wasted
Thank you for the extensive reply! The first part you mentioned is exactly what we were missing back then, we wanted to dynamically generate workflows starting from a configuration selected by the user. This wasn't really possible unless we would generate the YAML openflow specification ourselves.
At the end we gave up and rolled our own simple tool that just does what little we need. This said, it is cool that you are considering offering a more code-friendly way to define workflows. I still think this doesn't offer the same level of dynamism of dragster, where you could easily design branching/conditional workflows. I suppose your considerations regarding the decorators/compilers go exactly in that direction
It was several months ago, so it is entirely possible. Back then I got the feeling that windmill tried to be more of a low code business/internal tool platform than a data/ETL workflow tool, I especially missed an expressive way to define workflows programmatically (i think you had a JSON schema but nothing as powerful as dragster where you can define a whole workflow in pure python)
I briefly tried windmill for a project that involved creating custom workflows on-demand from a configuration file. I can't recommend windmill for data pipelines, it is meant to be more of a low-code internal app platform like retool or budibase. It is meant for a relatively static workflow that requires human intervention, like a simple business process involving some API calls and humans approvals in the loop. For complex (and potentially reconfigurable) data pipelines, dragster is a much better choice