Hi @KeithSloan ,
I am sorry for such a late response. I had been busy getting the latest stable release of Ladybug Tools out. I moved your question to it’s own topic since the one you originally posted on is just an info topic explaining how topics should be categorized.
I have personally not tested running Ladybug Tools in the FreeCAD environment yet but I don’t see any reason why you would not be able to run the LBT core libraries over there. We wrote the libraries that you see listed as part of the Ladybug Tools SDK to run in a wide range of Python versions (from IronPython 2.7 all of the way through cPython 3.12). We have even run them on Pyodide with a lot of success recently. The only packages that have not been written to run in all of these environments are the " Rhino/Grasshopper Libraries", which are primarily made to run in the IronPython environment of Rhino. There are also a couple of packages with C dependencies (namely, ladybug-vtk, honeybee-radiance-postprocess and honeybee-openstudio), which may create challenges in some environments but they have CLIs that make it easy to interact with them from environments that cannot load C dependencies.
So the general plan of just rewriting a lot of the ladybug-rhino methods to communicate between the ladybug-geometry objects used by Ladybug Tools and the geometry used in the FreeCAD environment is a good one.
This is exactly what Dion Moultdid when he put together the ladybug-blender plugin:
So I would recommend checking that repo out to see generally how we recommend setting up a new CAD interface for Ladybug Tools.
Let us know if you have any other questions. And definitely let us know if you end up releasing anything for people to try. We’ll be happy to feature it in the forum here to drive some traffic of testers towards your work.