I have a question about the structure of the ladybug tools repositories on Github and how they relate to each other
I’m going to be using Ladybug Tools 1.1.0 for my thesis work. I have successfully installed Ladybug Tools 1.1.0 for Rhino-Grasshopper (https://github.com/ladybug-tools/lbt-grasshopper/wiki/1.1-Windows-Installation-Steps) but I would like to also access Ladybug Tools 1.1.0 through an IDE such as Spyder. So here is the question: What repos from Github do I need to “pip install …” through the IDE to have a full Ladybug Tools 1.1.0 installation ? As I see it
and not
is the repos being used for Ladybug Tools 1.1.0, but what versions of these three repos are corresponding to Ladybug Tools 1.1.0 ?
Furthermore I’m a bit confused with documentation is up to date? E.g.
Lastly is it still possible to specify someway what Radiance method to use such as 3PM in Ladybug Tools 1.1.0 ?
Ladybug Tools 1.1.0 is the Grasshopper plugin. If you want to use the python libraries from the command line then you can install the core libraries.
For daylight simulation use pip install honeybee-radiance for energy pip install honeybee-energy and so on. We use dependabot to keep all the versions updated. You can use the -U flag to get the latest version of the library and this will also update all the dependencies to the latest version.
pip install honeybee-energy -U
If you want to get all of them in one go, then you can install dragonfly-energy which has dependencies on all the other libraries. Also see this post here which is a more organized version of what I wrote here:
Yes, as in we have finished developing a workflow language which we also use for creating simulation recipes for Ladybug Tools. This should give you a better idea of how things are designed.
The recipes that are used in this example are hosted here:
As you can see there is only two of them currently available. We will transfer all the recipes at some point but it can take some time. What makes it a bit tricky is that the recipes that you see in that repository are auto-generated! The real recipe is written in a language called queenbee. We just added a Pythonic way to write Queenbee recipes to make it easier for everyone to develop their own recipes.
Will probably be working with Honeybee Plus due to its nice exposure of the underlying Radiance calls in the commands.bat files. For my thesis I’m looking at GPU based methods for daylight and energy simulation and will be working with Accelerad, EnergyPlus and Neural Networks.
Yes, there are 3 “editions” but the Legacy edition cannot be run outside of Rhino/Grasshopper and the honeybee_plus one is deprecated and only supported single-cpu radiance workflows.
The diagram there shows you how all of the core repos/libraries relate to one another and gives you searchable docs for each repo/library. I should note that the core library dependency tree does not include the queenbee-python-dsl that @mostapha mentioned and you can think of queenbee as a layer above the core libraries, which allows you to write recipes using the LBT commands and Radiance commands in a manner that can be scaled to multiple CPUs. Once you have familiarized yourself with the latest core libraries, I really recommend getting to know the queenbee-python-dsl.
