.. I think I should modify the workflow to collect all the results and then bake them all together so the presentation of the result can be more solid.
2. radiationResult is the amount of radiation for each test point in [kWh/m2]
Note: each test point is the center of a mesh face and the number represents the amount of radiation for per m2 of that mesh face.
totalRadiation is radiationResult for each point [kWh/m2] * area of the face [m2] so it is in [kWh]
As you can see in the image below if you multiply the radiationResult with the area of the faces the result will be equal totalRadiation.
Regards, -Mostapha
…
tenary=cosh(x/a)).
If you're interested in the math behind it I may just write it down here. I also have a big equation which may be a solution for finding this "a" number, but there are imaginary numbers and this is math going far beyond my comprehence. The current script just starts with "a=0" and increases it slowly looking for a good curve*.
The def with vb script is in the attachment. I will post it later as .gha to milkbox group.
*Actually it looks for horizontal distance between 2 points on catenary curve, but the curve does not need to be constructed.
EDIT: There is a bug with final curve orientation, but the curve is a proper one.…
ind that a ?^@&@% door for your next 7 series (avoid that car at any cost) is rated about 10M (the so called development cost) whilst the whole car may require 500++ M. Did you know that the software used in a 7 series exceeds 70M lines of code? Therefor ... blah, blah.
Back to real-life things:
One "suitable" solution for flattish stuff the likes that you've captured is:
1. Make a BoundingBox and make a Point3d grid using, say, the bottom 4 corners (a single dimension tree)..
2. Declare a nullable Point3d grid [ DataTree<Point3d?> hitsTree = new DataTree <Point3d?>();].
3. Shoot a Ray3d from each point using some Vector3d (for instance using p4 - p0 out of the box points). If the Ray hits a brepface get the point if not put a null. That way you have a tree of equal List sizes and "combining" things (Points) for your patterns is greatly simplified [you can use the crude try{} catch{} approach].
4. If all these sound a bit freaky to you ... post a flattish test case (with different U/V) and give some hints about what "pattern" means to you.
best…
guess this is just a rectangle you are starting with and, if I read your intentions correctly, you want to start with a box and be able to move its top vertices independently in x,y and z and also rotate them altogether (this seems a bit unnecessary since you already control each vertex independently but ok).
Starting from the beginning of your definition: You don't need to actually create the brep and then extract the vertices and move them and then re-create it. Instead you can just get the bottom vertices from the [Boundary curve], using [Discontinuity] and move them by a vectorZ equal to [Building Height]:
Next you want to create four vectors and move the four vertices. The only thing that could help reduce components here is to merge the four vectors into one list (since you already have the vertices in a list):
Then you can add the rotation just like you did in your definition:
and finally you can create the twisted box. At this point you have 2 lists of 4 points each. Like you did in your definition, you have to use a [List Item] component to get each vertex but instead of using 4 components you can use just one and create more outputs by zooming in and clicking the (+) icon at the bottom:
and you finally have this:
Hope this helps
ps. the reason you were getting 3 breps is because you were creating 3 seperate vectors (x,y,z) instead of one, so you were actually moving each vertex 3 times.
…
lding facade, with a set of specific module size (say 500, than 1000, then 1200, then 1500, then 2500) along the axis but NOT along the surface?
at the end I hope I can feed the data to isotrim so that I can get the data the see the facade panel size.
please help~
thanks a lot…
0 bend strength, relative hinge strength of 353 for the torsion and stiffness 1000 for all springs except from the connection springs. Any idea of what this might be?
I am thinking about going back to having hinge resistance in the changing diagonals only - as before, but keeping the mesh as it is now.…
assume we want to format two numbers, one integer and a floating point value. The integer represents an index and it should appear inside square brackets, then we want the floating point number rounded to a maximum of 4 decimal places (but always using at least one decimal place, even if it's zero), and then, in parentheses a scientific notation representation using 8 decimal digits of the number.
So, assuming the index is 16 and the value is 47.280006208, what we are after is:
[16] 47.28 (4.72800062E+001)
To make this work, we need a formatting pattern that looks like:
[{0}] {1:0.0###} ({1:E8})
The square brackets, spaces and parenthesis are just part of the output, they have no meaning whilst formatting. Everything inside the curly brackets though will be replaced with a specific formatting of one of the values.
When using the Format component as shown above, the formatting pattern is just text data. The component knows that it is supposed to use the Format() function using the pattern text and whatever additional data is provided.
When you invoke the Format() method in an expression, you do need to make sure that the pattern is actually text:
So here the pattern needs to be encased in double quotes, otherwise it will be treated as code, rather than text.
You cannot use the formatting method in the internal expression of a number parameter, because this method returns text, whereas the number parameter is only capable of storing numbers. Any expression that you put into a number parameter had better return numbers as a result.…
B sunlightHours:1) check the direction of analysis surfaces, sometimes it doesn't work because they are flipped.2) when the model is huge like this one, try to simplify it. If it is not possible, try with a part of it and when you are sure and all it is fine, run the complete model. Moreover, for the first tests of your model I suggest that you use a big gridSize, e.g. 10 meters.
Let me know if it works
- Antonello…
p of the other(they could be extruded but its still the same thing). This is a bit different from what you were doing so far.
So for adding time into the equation, I can think of 2 approaches:
1. Use metaballs to draw smooth circular outiles around the points and subtract those from the rectangle. Repeat the above for every time step and stack those surfaces in layers.
This can easily be constructed using plexiglass layers with standoff fasteners:
2. For each vessel, draw a curve that rises in Z direction and draw pipes around those curves. This is better if you want to focus on the the vessels' routes but I can't think of a direct way to construct it.
Anyway, see how these work out and I am waitting for your feedback.
Good luck, Nikos …
Added by nikos tzar at 6:03am on November 17, 2014