face, the larger the number of modules and system size, there for the higher annual energy generation.baseSurface_ - this input exists only for "PV SWH system size" component. It's purpose is to represent a mounting plane on which the PV modules will be put onto. The dark blue colored roof in the photo below is that mounting surface in this case:
So the size of area of the baseSurface_ is not important but its plane.
2) It is important. It basically sets the initial losses of the system.
If that is the soiling value you have, then yes, you need to add it to the DC to AC derate factor component, and then plug its output to "DCtoACderateFactor_" input. I did that in the attached definition below.
3) The north vector/numeric value is not propagated due to possible independent usage of components.I plugged the 0 value to all three component's which have "north_" input. You can change it to what ever value you need.
Please let me know if I didn't answer completely to your questions, or if you have more of them.…
my algorithm has some problems :
1 . the base of spikes should be a circle i guess mine is hexagonal
2. the tip of the spikes should be closed mine are open !
3. i cant achieve an attractor point / field force effect for the spikes (for example if i move a point the spikes tend to go towards that direction)
4.the smoothness of the spikes !
5. the length of the spikes (this one should be linked to the attractor i guess )
image#1 image#2
thanks a lot for reading and i will be grateful if you could help me solve the problem
…
Ls which need to be compiled for a specific platform. Currently numpy/scipy for IronPython will only run in 32bit applications on Windows. I contacted the guys at Enthought and they do plan on releasing a 64bit version for Windows, but they want to make sure everything is working on 32bit first. They have some doubts about being able to release a mono version for you Mac guys out there.
2 – Install numpy/scipy for IronPython Follow the instructions on this site http://www.enthought.com/repo/.iron/
3 – Modify settings in RhinoPython Start Rhino 5 – 32bit version and run “EditPythonScript” to bring up the editor. Go to the options dialog by selecting Tools->Options from the menu
Add site-packages and DLLs to the search paths (see image). This helps RhinoPython find the numpy/scipy packages and associated DLLs.
Check the “Frames Enabled” option since numpy/scipy requires this to be turned on.
I decided to make the “Frames Enabled” an optional engine feature since it does have a performance impact on scripts. Numpy/scipy requires this feature to be turned on.
4 – Run a test
# For now, we need to manually load mtrand before using numpy or scipy# I'm still trying to figure out why mtrand is not automatically getting# loaded when numpy/scipy imports it. If I can fix this, we won't need# the following two linesimport clrclr.AddReference("mtrand") import numpyimport rhinoscriptsyntax as rs x_coord = [ 0, 1, 2, 3, 4, 5, 6]y_coord = [0.0,0.1,0.5,2.5,2.5,2.5,4.0]xyz = zip(x_coord,y_coord,[0]*len(x_coord))rs.AddPoints(xyz) degree = 5eq = numpy.polyfit(x_coord, y_coord, degree)fitfunc = numpy.poly1d(eq) fit_points = []for i in range(61): x = i/10.0 y = fitfunc(x) fit_points.append((x, y, 0))rs.AddPolyline(fit_points)
If you get a polyline in rhino fit through a series of points then you are all all set; if not go back to step 1 and repeat.
This looks like a good place to start if you want to learn more about numpy/scipy
http://docs.scipy.org/doc/…
ntermediate) mode very quickly, in a matter of days or even less, but the initial cold shower is at least 3 degrees warmer if you're staring at 300 components instead of 600.
Entire Ribbon panels would disappear for example (Math.Domain, Math.Util, Sets.Tree, Vector.Colour, Mesh.Triangulation, Transform.Group, Transform.Util at a first glance). As well as a lot of components in the remaining panels. I'd say at least 50% of what's there now will be gone.
I can draw additional information in the ribbon indicating that one is currently in beginner mode and how to switch to advanced mode etc. etc.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
that, I have a few more comments on what you are trying to do:
1. It is not possible to divide the surface of a sphere with regular hexagons [the most efficient way includes pentagons as well (classic soccer ball)].
So I believe that in the image you posted there is some serious twisting taking place at the back side (you can actually see this starting on the right side of the picture).
Lunchbox's [hexagon cells] component divides the surface in U and V (orange slices for a sphere) and draws hexagons on it. The result is some serious deformation on the 2 poles and many non-planar cells. If you are ok with this, then my only tip would be to use an even number for the U divisions in order to have a clean seam:
instead of:
2. The hexagons you have defined in 2d are wrong as they are overlapping and also leaving gaps between them:
You should define your hexagons so that they form a honeycomb pattern. It could be something like this:
3. There is no direct way for hexagonal mapping, so your best bet would be to draw your pattern inside each cell (good GH data structure understanding is crucial for this). Also, the non-planar cells will probably give you a hard time there...
Hope I cleared some things and didn't cause more confusion!
Nikos
…
ould be a smooth transition. somehow the vertex within a face are put out of order.
when i look at a really simple example i noticed that there each vertex colour is export 8 times (right) to the bitmap; wouldn't it be possible write 4 pixel (like on the left) for this 4 vertex mesh? or am i overseeing something?
…
ate):
1) go to: https://github.com/mostaphaRoudsari/ladybug/2) click on "clone or download"/Download ZIP
3) Download and extract the folder wherever you want on your machine
4) Open the folder and open "userObjects"
5) you'll see something like this
6) open Grasshopper/File/Special Folders/User Object Folder
7) Select and delete all Ladybug components
8) Drag all components of the point 5) into the canvas of Grasshopper wherever you want or inside the "User Object Folder"... it is the same thing.
And it should be fine.
Let me know if it works.
Best
Antonello
…
you may know, PCS (from now I will call polar coordinate system with PCS, and cartesian one with CCS) describes point position with 2 values (like x and y in CCS) which are r and theta(r,theta). r is for distance from PCS center, theta is angular dimension which is in 0 to 360 or 0 to 2*pi domain.
To hark back to David's guide line - here it is replaced with guide circle.
Why to sort points like this ? As usual, one image tells more...
Here is logic behind all this stuff :
Find an average point of all given points*
Search for furthest point from an average point*
Create a circle with center at average point and radius = distance from average point to furthest point*
*Steps 1-3 can be replaced with custom hand-made circle, I decided to automate it that way.
For each point find closest point on circle - this will be used for finding theta value
For each point find distance to average point - this is r value
To overcome problem with same theta (t) values (like same x values in CCS), instead of multiplying by 1000, we will use a new create set component. This component creates set of integers, each one representing one unique input value. So if points A, B, C, D, E are (r,theta) :
A (1, 30)
B (2, 30)
C (3, 30)
D (1, 45)
E (1, 60)
Then create set will output list of integers = 0,0,0,1,2 (same theta for A, B, C other theta for D and E). Now its getting really easy - remap r values to domain 0 to 0.5 (or any less then 1), and add integers from create set component to remapped r values.
7. So what we have now is list of floating point numbers : A=0, B=0.25, C=0.5, D=1, E=2
Profit of remapping is that r values will never affect integers representing theta values - and all the information is stored in one floating point number ! By sorting these values we will obtain proper order of points - to complete this, we need to sort points parallel with values.
What's really cool about polar sorting - there could be any amount of points, but polyline connecting all of them will never self-intersect. Probably there is some relation with 2d convex hull.…
tive: I want to calculate annual lighting energy consumption and annual illuminance value because of electric lighting and daylight.
2. To do this, I make my own lighting schedule based on simple supposed-to-be 'lux sensor'. The scheduling will be stored in "S_T_(something)" number component (picture A).
Based on daylighting of certain points, if the illuminance at the point don't reach 300 lux then the luminaire will be 'On' (1 because I use only manual switch). Some luminaire will be turned on if one of the two points doesn't meet 300 lux (thus the need of 'OR' gate).
The rest is just usual addition and multiplication to obtain the annual energy consumption (picture B).
3. For the annual illuminance, based on scheduling, the illuminance value of daylighting and electric lighting ("T_[something]" number component) will be added (picture C). Then we get the annual illuminance value.
Some say the clustered one makes it more heavier to compute. Is there another way I don't ned to use Cluster? (Picture C)
*By the way, all the calculation need to be matched with Occupancy value (it will be computed only when Occupancy is "1").
***
Where do you think it can be simplified even more? I think the expressions makes the calculation a bit heavy, but I don't how to simplify it even more. I suspect making the whole canvas as script will be more efficient, but I don't have any clue in programming language.
I will be waiting for your great replies!
…