I noticed @chris’s post about compliance to Australian regulation and went on a deep dive of the few compliance/regulation related posts on the forum. Seems people are keen to use ladybug tools to assist with compliance (not necessarily as a government approved tool but as a useful exploratory tool).
As such I was wondering if there was any strategy in place to encourage people to help in this endeavour for the core libraries? I recognise that most folk are building scripts in grasshopper to test for compliance but */!\ strong opinion warning /!* this is not scalable, error prone and difficult to share/reuse. Therefore it would seem judicious to add a
compliance section to the appropriate libraries (eg:
honeybee.radiance.compliance.leed would contain all daylight related compliance calcs/methods).
What do we think is the best way to organise this? Here is some food for thought:
An entire repository dedicated to compliance
- Easier to manage
- More difficult to integrate with rest of ladybug tools libraries/objects
Compliance classes in each repository where relevant
- Honeybee holds daylight/energy calcs
- Ladybug comfort calcs
- Butterfly (?)
- Will be more difficult to coordinate overall
How do we encourage people to contribute?
- Using core libraries rather than Hydra scripts is a barrier to entry but vastly increases the opportunity for reusability/version control etc…
- The core libraries are set up for testing/deployment but might scare some non-pythonistas
- Writing regulatory scripts could however be an excellent way to onboard new contributors as they will have to use their preferred library, write a new feature (rather than debug code) and can apply it quickly to their code once their work is tested and deployed.
Going to rope in some folk who I know will have some thoughts on this issue but feel free to bring in some more into the conversation!!