tName_FinalProject_PartD.pdf
Below is the desk crit list, please sign up for a spot in the comments below:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
See you Monday!…
asuring Urbanity."
The seminar aims at re-centering the debate of measuring urban form on the contemporary issues of designing, planning and regulating the extensive city. It will bring together a group of international experts on the subject and the objective is to discuss the importance of combined qualitative-quantitative approaches on the generation of new insights on the contemporary urban environment and planning strategies.
The workshop presents a set of innovative approaches and methodologies using its own software. At the workshop participants will be invited to use the available toolset to address a specific urban issue where the construction of models for automatic measurement of urban indicators will be part of the urban design process.The workshop is intended for all urban planning professionals who want to improve their skills and knowledge as well as for students or doctoral students in urban planning. The CIAUD will issue a participation certificate equivalent to 3 ECTS credits.The workshop will run from 7 to 12 May 2012 and the seminar will be held on May 11, 2012 in FAUTL.The seminar and workshop program can be found attached ora t the website: http://www.measurb.org/en/home.html We thank in advance for the dissemination of this event to whom might be interested.
Best regards
José Beirão
Cristina Cavaco
workshop.pdf
seminar.pdf
Measuring urbanity…
all normals got pointed to the outside.
But I am still not out of the woods - even though the normals are OK now. I attached a 3DM file baked from my current GH layout. The part is made using 4 basic steps: (1) capping the outside surface which is made by joining 2 surfaces, each lofted from 11 polyline curves, (2) capping the inside surface made by lofting 11 circles, (3) whacking 5 units of height off the bottom of (2) by doing SDiff with a 5 unit high capped cylinder, and (4) using SDiff to subtract (3) from (1)
Step 3 is necessary to allow for a solid bottom thickness of 5 units. All the surfaces are NURBS, none have been converted to meshes.
I would have thought that there would be no problems printing this part because it is made from only solid surfaces. The 3DM file has no naked edges - which is what I expected. But my generated STL file is 23.19 MB in size and the 3D Builder program says it has errors. The 3DB program "fixes" the errors, but when it does so it closes the top of the part, so that function is useless. 3DB will also simplify the STL file and create a resulting file that is much smaller, but this also has problems that would result in a failed 3D print.
I totally realize that my problem may lie completely outside GH & Rhino and I don't mean to add clutter up this board with extraneous posts. It's just that I have not had issues like this until I tried the idea of joining 2 lofted surfaces that have reverse twists. I have made many parts before that included reverse twists - but not lofted surfaces. Here is just one example: http://www.thingiverse.com/thing:1606442…
Added by Birk Binnard at 3:22pm on September 14, 2016
s
(distance from Spine to Profile)
4) Create Circles at each floor
5) Rotate Each Floor by twisted amount
(according to height of floor)
6) Divide each floor by number of Flutes
7) Flip Matrix of Flute Points (version 0.7)
(if using v0.6 then search flip matrix on site for method)
(Rows to Columns)
8) Interpolate Curve through Flute Points
9) Mirror Flute Curves
10) Create display grid
11) Make a vector 2Pt from the floor centre
to the corresponding display point…
I extract the first two with a "Redim Preserve t(1)" command.
In the first case, the redim is correct, Line 7 = Line 2 and Line 8 = Line 3. It just kept the first two values like it is supposed to be.
But, for the second curve starting Line 9, some t values are messed up after the Redim. Line 16 = Line 17 despite Line 11 was different from Line 12. That's what is creating a problem later in the Split.
Weird.
…
se of the tool at one building per time and it is even not very efficient. For example in a situation like the image I attach I have four buildings facing the area on which I need to calculate the solar envelope that guarantees 2 hours of direct sunlight on all the surrounding facades. If I have to input the sun vectors that guarantee 2 hours insolation for the South facing facade (from 11 to 13) then the solar envelope is most likely not correct for the East and West facing facades and it totally null for the North facing facade. So the suggestion is to develop further Solar Envelope component and add to the _sunVectors input also another input for the required minimum hours on specific facades. Thank you!!
Francesco
…
ber of mesh vertices is defined as (precision_+1)^2.So if you would like to have its beam, diffuse and ground-reflected components as well, that means 3 * 8760 values per single point.Example: if you set your precision_ input to 20, the number of values would be a couple of millions:
(20+1)^2 * 8760 * 3 = 11 589 480 hourly values
Check the attached definition below. The outputs that you need are: "Ebeam", "Ediffuse", "Eground".They contain annual hourly values for each tilt and azimuth combination (that's what upper mesh vertices represent) in a data tree.…
as follows.
We have a grid which consists of a collection of columns, where each column consists of a list of points. You said flattening is out of the question, so we need to cull items from each list individually.
Let's say our culling pattern is KDDDKDD (repeat as needed). K = Keep, D = Ditch. If a column contains 18 points, the pattern needs to be repeated until it is 18 items long. In this case:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
K D D D K D D K D D D K D D K D D D
We can now cull each column, but they will all be culled in the same way. By shifting the pattern one more index for each column, we can cycle the culling.
The fix incidentally is to Shift the pattern PRIOR to repeating it. Then it works as expected:
--
David Rutten
david@mcneel.com
Tirol, Austria…
Added by David Rutten at 2:49pm on October 2, 2013
(18, 11, 0, 17), also put in the assembly component.
How can I know which value of the reaction forces correspond to which support?
In the manual is stated that when the reaction force component is used, than the values are displayed in ascending sequence of the corresponding nodes.So if I input the support nodes like thispoint with index 18point with index 11point with index 0point with index 17are the reaction forces displayed like this (per loadcase)?0 - reaction forces in point with index 01 - reaction forces in point with index 112 - reaction forces in point with index 183 - reaction forces in point with index 17
Thanks!
BestLara…
into new tree, so that branch {0} has points from branch {0} {1} {2} combined, branch {1} has points from {2} {3} {4}... as it shows in the atached image.
The main problem is that points need to overlap in the new tree.
Any suggestions?…