EC
1. Between hours 1:00 to 24:002. Current document units is in Meters3. Conversion to Meters will be applied = 1.0004. [1 of 7] Writing simulation parameters...5. [2 of 6] No context surfaces...6. [3 of 6] Writing geometry...7. [4 of 6] Writing materials and constructions...8. [5 of 7] Writing schedules...9. [6 of 7] Writing loads and ideal air system...10. [7 of 7] Writing outputs...11. ...... idf file is successfully written to : c:\ladybug\Freeformtower_IDF\EnergyPlus\Freeformtower_IDF.idf12. 13. Analysis is running!...14. ......
Done! Read below for errors and warnings:
15. 16. Program Version,EnergyPlus-Windows-64 8.1.0.009, YMD=2015.04.04 23:39,IDD_Version 8.1.0.00917. 18. ************* IDF Context for following error/warning message:19. 20. ************* Note -- lines truncated at 300 characters, if necessary...21. 22. ************* 577 Zone,23. 24. ************* Only last 1 lines before error line shown.....25. 26. ************* 578 Freeformbuilding27. 28. ** Warning ** IP: IDF line~578 Comma being inserted after:" Freeformbuilding" in Object=ZONE29. 30. ** Severe ** Out of range value Numeric Field#5 (Type), value=0.00000, range={>=1 and <=1}, in ZONE=FREEFORMBUILDING31. 32. ************* IDF Context for following error/warning message:33. 34. ************* Note -- lines truncated at 300 characters, if necessary...35. 36. ************* 586 BuildingSurface:Detailed,7341.
…
Writing simulation parameters...3. [2 of 8] No context surfaces...4. [3 of 8] Writing geometry...5. unsupported operand type(s) for +: 'str' and 'list'6. Failed to write Pelle_aperture000 to idf file7. unsupported operand type(s) for +: 'str' and 'list'8. Failed to write Pelle_aperture001 to idf file9. unsupported operand type(s) for +: 'str' and 'list'10. Failed to write Pelle_aperture002 to idf file11. [4 of 8] Writing Electric Load Center - Generator specifications ...12. [5 of 8] Writing materials and constructions...13. [6 of 8] Writing schedules...14. [7 of 8] Writing loads and ideal air system...15. [8 of 8] Writing outputs...16. ...... idf file is successfully written to : C:\Users\Personal\Desktop\TESI\x001\THOR\EnergyPlus\THOR.idf17. 18. Set runEnergyPlus to True!
or this
0. Current document units is in Meters1. Conversion to Meters will be applied = 1.0002. [1 of 8] Writing simulation parameters...3. [2 of 8] No context surfaces...4. [3 of 8] Writing geometry...5. Runtime error (MissingMemberException): 'hb_EPFenSurface' object has no attribute 'blindsMaterial'6. Traceback:line 1567, in main, "<string>"line 2134, in script
i think that i've same problem with my windows...any suggestion???
Thanks for all…
ky.exe did not accept -p parameter and made empty sky.cal file.
----
Edit: solved run problem, Bee did not download OpenStudioMasterTemplate.idf
Get it here: https://github.com/mostaphaRoudsari/Honeybee/issues/119
Now get empty HDR:
C:\ladybug\prox\imageBasedSimulation>rpict -i -t 10 -vtv -vp 245.129 -226.458 20 0.405 -vd -0.549 0.656 -0.518 -vu -0.332 0.397 0.855 -vh 42.862 -vv 26.991 -v l 0 -vs 0 -vl 0 -x 800 -y 600 -af prox_RAD_Perspective.amb -ps 8 -pt 0.15 -pj 0.6 -dj 0 -ds 0.5 -dt 0.5 -dc 0.25 -dr 0 -dp 64 -st 0.85 -ab 2 -ad 1024 -as 175 -ar 150 -aa 0.200 -lr 4 -lw 0.050 -av 0 0 0 prox_RAD.oct 1>prox_RAD_Perspectiv e.unf rpict: 0 rays, 0.00% after 0.0000 hours rpict: skybright`c__ladybug_skylib_cumulativeSkies_SINGAPORE_SGP_SINGAPORE_SGP_1 : undefined variable rpict: 1020 rays, 4.91% after 0.0000 hours
----
Hi friends,
trying to get a cumulative sky image metric to run and encountered an issue with the image-based metrics component. It throws:
Runtime error (KeyNotFoundException): honeybee_materialLib Traceback: line 768, in main, "<string>" line 1442, in script
I guess this is some sort of setup issue on my end, or I messed up the definition? Any help appreciated.
Thanks,
Max
…
developments, which is an attempt to make Honeybee platform-agnostic, cloud-compatible, scalable and more flexible for development. It currently consists of a core python library and the plugin libraries for Grasshopper and Dynamo.
You can download the plugin for Grasshopper from food4Rhino and install the Dynamo plugin from the package manager. You must install the latest version of Radiance to use Honeybee[+].
This current release introduces Radiance-based workflows for daylighting simulations and supports the following simulation types:
Point-in-time illuminance (a.k.a grid-based)
Point-in-time luminance (a.k.a image-based).
Daylight coefficients (both grid-based and image-based)
Three-Phase Method (grid-based implemented, image-based to be added soon)
Five-Phase Method (grid-based implemented, image-based to be added)
NOTE: There has been a very recent update to the Five-Phase method which was presented at the IBPSA2017 conference last week. These changes have NOT been implemented in the current release. We suggest the users to use the daylight coefficient recipe for annual metrics, sDA and ASE until we apply the recent changes.
While many of you will recognize the first three simulation types above as ones that Honeybee has always supported. Image-based daylight coefficients, Three Phase Method and Five Phase Method are increasingly advanced ways of running annual or time-lapse simulations. Tensor Tree based BSDFs, while supported in Honeybee are not featured in any of the example files. We intend to incorporate this functionality in the near future. The simulation-methods listed above are based-on empirically validated research conducted primarily by researchers at the Lawrence Berkeley National Laboratory since late 1980s. There are also some special workflows (which we call recipes!) that make it easier for beginners to use the plugins.
Solar access simulation aka sunlight hours (which employs point-in-time simulation).
Daylight factor simulation (which employs point-in-time simulations).
[Annual] Radiation simulation (which employs daylight coefficients).
Annual [daylight] simulation (which employs daylight coefficients)
Energy simulation features are yet to be implemented in Honeybee[+] so, if you’re using Honeybee mostly for energy modeling you should keep using the legacy version.
Frequently Asked Questions
I'm happy with Honeybee as it is. Why should I install this one?
Honeybee[+] addresses several limitations of the legacy version of Honeybee and introduces new features which were not available before.
Broadly speaking, Honeybee[+]:
Is faster than the current annual recipe implementation as we now leverage the Radiance binaries directly instead of using Daysim.
Is more accurate at calculating direct solar contribution.
Can handle BSDF materials (unlike the current Honeybee annual daylight simulation).
Can run sub-annual daylight simulation by generating sub-annual sky matrix.
Uses an improved implementation of Radiance’s daylight coefficient based methods by using Radiance utilities for annual simulation.
Can calculate the contribution of each light source separately both for image and grid based simulation.
Has no limitations on the number of window groups and states of dynamic blinds.
It also provides a nearly-matching interface for both Grasshopper and Dynamo. There are a few platform specific components / nodes for each plugin but the overall workflow in each interface is the same. Honeybee[+] should also, in theory, work just fine on Grasshopper for Mac, although we admittedly have not tested this yet. This also means that you should be able to use Radiance’s built-in parallel processing.
We strongly encourage our experienced users to start using Honeybee[+] right away. You will enjoy the new features and the flexibility that you have come to love in the current workflow is all still there. The ability to separate the contribution of each window group is also just so cool and useful. If you’re as nerdy about daylight simulation as we are, you don’t want to miss out!
How should I get started?
You can download the installer from Food4Rhino for Grasshopper and Dynamo Package Manager for Dynamo.You can get yourself started with Honeybee[+] using the example files that is part of the installation part until we capture the video tutorials. The example files are commented as much as possible so you can educate yourself in the process. If you are already using Honeybee for Grasshopper, you will know how to use Honeybee[+]. There are a few changes in the post processing components but there is no major change from the current workflow.
Let us know if you find any bugs or have any suggestions for new features.
Can I install Honeybee[+] next to the current version of Honeybee?
For Grasshopper users, the answer is yes. Honeybee[+] is a totally separate from Honeybee and won’t replace it at least for one year.
For Dynamo users, the answer is no. The new package is an improved version of what was available before and is meant to replace it. In other words, the currently available “Honeybee for Dynamo” is built using the new Honeybee library.
How do I learn more about Honeybee[+]?
A significant portion of the development work for the daylighting methods implemented in Honeybee[+] forms the basis of Sarith’s PhD research. His dissertation, titled “Parametric Modeling Strategies for Efficient Annual Analysis of Daylight in Buildings”, is expected to be available publicly in early 2018. For the time being, we encourage you to refer the slides of this Radiance workshop presentation from 2016.
For those interested in learning more about the Radiance-based methods implemented in Honeybee[+], a comprehensive tutorial for Radiance will be released by LBNL in the coming weeks.
Where to post issues, comments or bugs?
Very soon we will compile all the discussions in our new discussion forum. It is invite only at this point until we move all the current discussions to the new forum. Meanwhile:
Post comments and questions about the Grasshopper plugin to the Grasshopper forum.
Post comments and questions about the Dynamo plugin to the Dynamo forum and tag it under Honeybee.
For bugs in the core library, please open an issue on “Honeybee” repository on GitHub.
For plugin specific bugs, please open an issue on Honeybee-grasshopper or Honeybee-dynamo GitHub pages.
Known bugs
The Room To HBZones component for Dynamo is doomed to fail for complex cases. In those cases use Dynamo’s select item(s) nodes to bring the geometries to Dynamo and create Honeybee surfaces. Also vote up this feature request which will fix this bug if you haven’t already! This will hopefully be the last release that we are still waiting for Autodesk help. If it doesn't happen the next move is to write a more solid solution to address this issue.
This is the first release. However, we have tested the workflow as much as we could and have checked the results against the original Honeybee and other Radiance-based workflows bugs are expected. Double check the results of each study and let us know if you found any bugs.NOTE: As many of you know by now, Radiance employs a combination of deterministic and stochastic methods for calculations. For this reason, the results you get from running the same Radiance simulation will be slightly different for each run by a small margin of error (this should be less than 10%).
What to expect next?
Except for the cloud computing support! We have reached all of the other major goals that we had for 2016-2017. For the rest of the year we will try to address the items below:
Documentation of the [+] developments. We need to document the current development and get more of the contributors up to speed with the new development.
Release a new version of Butterfly to support the latest release of OpenFOAM and docker-less installation for Windows 10.
Cloud computing service for Butterfly and Honeybee
Finally we will have a number of major announcement about the future of Ladybug Tools soon! Stay tuned!
Mostapha on behalf of Ladybug Tools development team
Note added by Sarith:
On the cross-platform aspect, to add to Mostapha's release notes, the core library has been tested on the following platforms:
Linux Ubuntu: Version 14.04 | 16.04 | 17.04
Linux RHEL: 6.8
Unix FreeBSD: 10.0
Linux (Cloud VM): Microsoft Azure H16mr running Ubuntu 17.04
Linux (Cloud VM): Amazon AWS EC2 t2 running Ubuntu 14.04
The core dependencies for running Honeybee on the cloud are Python 2.7, Radiance, git and honeybee . Since Apple computers typically run Unix-like OSs, we don't foresee any portability issues with them.
…
appening is that my larger definitions are actually locking up for a period of time, showing a spinning wheel and/or a not responding/grey-out condition directly after I drag a component onto the canvas, add or change a connector line, or change a variable in a component. In my more complex definitions, it will freeze up on pretty much any of these actions for several seconds (sometimes upwards of 10). It makes perfect sense to me when this happens after I change a value upstream of any calculations...but even in such instances the "solution completed" notification differs from when I can begin working on my definition again by an additional several seconds. I'm more curious as to why after a definition has been solved, making changes that don't relate to the solved action should freeze it up.
The amount of time is definitely correlated to the amount of geometry I have either referenced or generated in my definition, so I can work around it a bit by developing my defintions with smaller regions of my model geometry at any one time and then solving for the whole to test it out. I suppose I could send you my definition...but I'd hate to trouble you as it would have to include an Excel sheet, and I'm using Horster, Lunchbox, and probably a few other components from various sources like Kangaroo. I'm afraid I'm not the most elegant definition maker, either, so you'd have to avert your eyes.…
switch this talking off-line if you are interested to know the real reasons in depth.
What is the pro way? Well ... imagine objects (blobs et all) that are placed in 3d space by some per object policy whilst their "property" (bend,repulse) is user controlled on a per object basis. Then imagine variants of all that spaghetti yielded (the rays, that is) stored in parameters in order to do the obvious : take control of all your previous attempts (replace, remove, swap, reset etc etc).
Get a 10-- minute thingy (straight out of my head: NO checks OF ANY kind performed [bugs possible], just a grid that shoots rays and a single blob (a sphere) that does the job). Not even a decent random policy is applied in order to have some nice looking rays (not to mention their directions).
Now ... imagine any collection of breps distorting the ray chaos: i.e. a ray meets a blob > is distorted (or not) > then meets another > ... > blah, blah (plus some policy for killing rays heading to Sahara instead of Vienna - but that's elementary).
This requires at least 2 hours of coding to do it properly (+ the variants "management" C#).
But ... well ... it could be a good real-life case when Solaronix "sponge" type of U/V collectors could be available (rather soon) > I'll do it > the future > the glory > the cash > the polar bears.…
o connect the 'Line' for ClampLength and how it relating to Lower- and UpperLimitation.
they have differently lower and upper limitation configuration between red/blue (L:10; U: 10000000) and yellow/green(L:3; H:19)...are those parameter meaning something..?
It would be nice if you could explain about that ;-)
Otherwise, awesome example!
…
Added by Jon to Kangaroo at 3:27am on May 23, 2016
xpressions, trivial I/O <expressions> allowed)
Use of Plug-ins
Code - either VB.NET, C# or Python
Winner announced this time tomorrow (0830 GMT)
I have to bail now. Tomorrow is Saturday so I won't be able to upload the file then, so if you promise not to cheat and still want to have a go, don't look...
P R E L I M I N A R Y W I N N E R S
=========================
Native: Ángel
Plug-ins: Technically as python is a plug-in still, the winner is Anders as there were no other runners (Yet)
Scripting: Anders gets a Special mention for bringing my attention to bin(x) in python but the award goes to David
S O L U T I O N
===========
[Image will be posted Monday]
File below
…
of the surface. The "ridges" will be the high-point, if you will, and the surface will gradually taper down to the edge from that point. So the taper or curve will be different for both the top edge and bottom edge, depending on how far the ridge is from each edge. The same is true for the valley between the ridges. If the edge of the surface is 0, and the ridge is 10, the valley will fall somewhere between 1-9.
I do not know how to model this.. i've tried many different ways, but can't seem to get anything to follow a curve or line and extrude like I want it. Anything close would be great at this point. Worst part... I don't even know what to Google... what kind of action is this called?
Anyway, I've attached an image to help explain what I'm trying to do. Though crude, hopefully to makes sense of what I'm trying to do/say.
Thank you!
Below:
Red = Ridge
Cyan = Surface Edge
Green = Section Cut
Black = Surface Section Profile
…