s is like flattening your data PARTIALLY - chopping an index off the end of the branch paths without obliterating the tree entirely. When working with one "set" of input data, a flatten works to get these lists to match up - but when working with multiple sets, we need to be careful to preserve the original branch indices that keep all four of your original regions separate. As a rule, whenever you're feeding two data trees into any component, they should have the same number of branches. (or one should have branches and the other should be a flat list, in other cases).
The rule of thumb I tend to teach is this:
In 90% of cases...
For lists, all your inputs should either have 1 item or N items. That is to say, if you're feeding 4 items into one input and 9 items into another, something is probably wrong.
For trees, all your inputs should have either 1 branch or M branches. That is to say, if you're feeding a tree w/ branches {0;0} to {0;3} into one input, and a tree w branches {0;0;0} to {0;3;8} into the other input, something is probably wrong.
Grasshopper essentially matches up branches first, then lists second. By "matching" I mean it processes them together. Simple example of the Line component - it will match the first branch of points in the A input to the first branch of points in the B input, creating lines between those points, then match the second branches, the third branches, etc. THEN, it applies the same logic to the level of the list (with a pair of matched branches {0;2}, match all the items in those branches to each other - first item in one branch to the first item in the other branch, etc.)
This is a tricky concept but it seems like you're already well on your way to understanding it from your definition - "PShift" is a critical tool in your path management arsenal. I hope this (overly long) response helps clear things up for you!
…
he TOF and TSRF indices. They show, how "distant" is your _PV_SWHsurface from the optimal _PV_SWHsurface surface in terms of tilt and azimuth angles.However, in your case we are not interested in TOF and TSRF indices. We would just like to know what are the _PV_SWHsurface optimal tilt and azimuth angles, regardless of the supplied _PV_SWHsurface.
So the circular surface supplied to the "TOF" component's _PV_SWHsurface input is irrelevant. It can be of any area, and any tilt/azimuth angle.The PV_SWHsurfacesArea output of the "PV SWH system size" component depends on a couple of factors:moduleActiveAreaPercent_ (leave it at 90%).
moduleEfficiency_,
systemSize_.Calculation of systemSize_ depends on your electricity demand, cost of the PV system, type of the object, country, local regulations etc. This is something that an engineer needs to determine.For example, in USA for a residential house in the Sunbelt, depending on finances, a household would try to cover 100% of its annual electricity needs with their PV system. Which means that the systemSize_ you chose needs to cover the annual electricity consumption. You can perform EnergyPlus simulation or use any other way to get the annual electricity consumption.
Ladybug "Photovoltaics Performance" component can calculate the optimal systemSize_ by given the annual electricity consumption.However the component is made to address fixed tilt and azimuth PV systems only.An approximate way to overcome this is to calculate the optimal systemSize_ for fixed tilt and azimuth PV system, and then multiply it with the "difference in %s" panel at the very right of the fixed_vs_tracker_PV2.gh file. Again, this is not what Ladybug "Photovoltaics Performance" component is made to do, but it will probably get you in a ball park.
Inputted 32 degrees for north_ direction is actually 328 degrees.This is due to Ladybug Photovoltaics being based on NREL model which uses clockwise angles convention. This convention is also most commonly used in solar radiation analysis.
Dubai weather data files are uploaded in here.
…
le discontinuous list of index numbers and I'd like to be able to generate a set of domains where each span of numbers would have its own domain. For example:
This list: 5,6,7,8,9,22,23,24,25,26,77,78,79,80,81...
Would give these domains: 5 to 9, 22 to 26, 77 to 81...
I'm at a loss as to how I can achieve this though. I know I can use the bounds function on the list but that would give a single domain, not several. In case it helps the list in question was generated by a true/false cull pattern from the complete list of indices so simply determining the indices of the beginning and end of each chunk of 'trues' in the cull pattern would work as well as it would give the same domains. I can post an example file if anyone would like but I figure this is a pretty general issue.
So anybody have any ideas on how to solve this multiple domains from a single list problem? Thanks in advance for any help at all, I'd really appreciate it!
James…
the various digital design methods and technologies that they employ in their design workflow, highlighted at various scales through their recent work. Organizers and Moderators: Andrew Haas, Program Co-Director, Architectural Association Visiting School New York Alfonso Oliva, Associate/Director, LERA Consulting Structural Engineers Speakers: Luc Wilson, Senior Associate Principal and Director, KPF Urban Interface Dan Levine, Associate Director, Solutions Engineering – United Technologies (UTC) Jan Leenknegt, Architect and BIM Manager, Bjarke Ingels Group (BIG) Introductions by AIANY Technology Committee Co-Chairs: Michael Brotherton, AIA, VP of Operations, Situ Fabrication LLC Alexandra Pollock, AIA, LEED AP BD+C, Director of Design Technology, Senior Associate, FX Collaborative – Due to building security requirements, a state-issued photo ID or valid passport is required to obtain building entry. Advanced registration is required. This event is free and open to the public. Refreshments and pizza will be served.
Register: https://www.facebook.com/events/1019498534923019…
Added by Andrew Haas at 10:42am on October 30, 2018