l operations. Aside from its geopolitical position and commercial significance, Thessaloniki has been for many centuries the military and administrative hub of the region, and beyond this the transportation link between Europe and the Levant. A series of design studies will be put forward to rethink the way by which city environment in Thessaloniki have been affecting its’ population according to changing needs and to visualize such urban shifts on a more hyper specific contextualized construction model. Throughout the investigations on the research agenda, current trends on the habits of architectural practice will be re-visited.
Innovative urban interventions informed by bottom-up rules extracted from existing city conditions will formulate the major focus of design proposals. Design teams will be working with simulation tools and digital fabrication methods throughout the design research phase. The design brief will be initially explored through the combinatorial use of different computational design tools. Methods of connecting form‐finding methods with form‐making techniques will be investigated. Various manufacturing techniques enabling a hands‐on experience on the diverse range of digital fabrication systems will formulate the starting point for the physical tests. Finally, the design and fabrication of a one-to-one scale pavilion will unify the goals of the programme.
Prominent features of the programme / skills developed:
- Participants will be part of an active learning environment where the large tutor to student ratio (5:1) allows for personalized tutorials and debates.
- The toolset of AA Thessaloniki includes Autodesk Maya, Rhinoceros, Grasshopper and Arduino.
- Participants will have access to digital fabrication tools such as 3-axis CNC router, laser-cutter, and 3d-printer.
- Design seminars and lecture series will support the key objectives of the programme, disseminating knowledge on new design anatomies including machinic control, computational space, and complexity in systems, and innovative urban design approaches.
Eligibility: The workshop is open to architecture and design students and professionals worldwide.
Accreditation: Participants receive the AA Visiting School Certificate with the completion of the Programme.
Fees: The AA Visiting School requires a fee of £600 per participant, which includes a £60 Visiting membership fee. The deadline for applications is 15 October 2015. No portfolio or CV is required.
Discount options are available. Please contact the AA Visiting School Coordinator for more details.
Online application link:
https://www.aaschool.ac.uk/STUDY/ONLINEAPPLICATION/visitingApplication.php?schoolID=316
Programme Director:
Alexandros Kallegias (AA Greece VS Director): alexandros.Kallegias@aaschool.ac.uk…
es at the beginning. But as I make changes to the input (or just hit the recompute button) the time it takes to execute increases. This has happened to me with other scripts I've written with the python component. Why does this happen? And how do I fix it? Does python hold onto data from one execution to the next? The only solution I have found is to relaunch Rhino. Even if I copy the component into a fresh grasshopper canvas, the computation time does not return to original.
The images below illustrate the time increase. I simply hit the recompute button between each pass. All inputs remain the same the whole time. There are 6400 curves being projected. I will say that with fewer curves, the increase in time is nonexistent or perceivable. (I have 24 GB RAM and it is did not even reach 50% of usage during the tests)
My python code:
import ghpythonlib.components as ghcompimport ghpythonlib.parallel
def project (tempc): tempresult=ghcomp.Project(tempc,B,D) return tempresult
a=ghpythonlib.parallel.run(project,C,True)
I have attached the GH file with the inputs internalized if anyone wants to try for themselves.
Pass 1= 444ms
Pass 5= 610ms
Pass 10= 908ms
Pass 15= 1.2s
Pass 20= 1.4s
…
Added by Lawrence Yun at 3:19pm on December 10, 2014
Illuminants like "A" or "D65" are spectral power distributions that are defined (as per CIE S 014-2/E:2006) for wavelengths ranging from 300nm to 830nm.
For example, CIE Illuminants A,B and C are defined as :
And D65 is defined as :
For illuminance and luminance calculations, the radiation from such illuminants are converted to Lux or Candela/sq.m by weighing them against the Photopic Luminous Efficiency function (also called as V-lambda):
The equation (1) used for this purpose is
Where y corresponds to the V-lambda function and J corresponds to an illuminant like "D65" or "A".
So, why is all this relevant? Honeybee/Radiance also use a similar method for calculation of luminous flux, illuminance and luminance. However, in the case of Honeybee/Radiance the lighting calculations are limited only 3 (R,G,B) channels (and not the 300nm to 830nm). So the equation (1) from above becomes something like:
F = 47.4*R+120*G+11.6*B
Where (R,G,B) refers to the spectral power of the radiation and the numbers (47.4,120,11.6) relate to the V-lambda function. So, the bottom line is that an accurate representation of CIE illuminants is not possible inside Radiance/Honeybee as the spectral information is severely restricted. Some studies have proposed using Radiance with more than 3 channels. For example: http://link.springer.com/article/10.3758%2FBRM.40.1.304 . However, such attempts have been limited. What is possible with Radiance/Honeybee is to create a fairly accurate representation of brightness of the sky. Although, I can explain that too, I would suggest that you try this link first: http://www.bozzograo.net/radiance/index.php?module=FAQ&func=dis...
By the way, which CIE document are you referring to for CIE sky definitions ?…
ting.
Thanks
Rania
** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.
** Warning ** Version: in IDF="'8.2.7'" not the same as expected="8.2"
** Warning ** ManageSizing: For a zone sizing run, there must be at least 1 Sizing:Zone input object. SimulationControl Zone Sizing option ignored.
** Warning ** ManageSizing: For a plant sizing run, there must be at least 1 Sizing:Plant object input. SimulationControl Plant Sizing option ignored.
************* Testing Individual Branch Integrity
************* All Branches passed integrity testing
************* Testing Individual Supply Air Path Integrity
************* All Supply Air Paths passed integrity testing
************* Testing Individual Return Air Path Integrity
************* All Return Air Paths passed integrity testing
************* No node connection errors were found.
************* Beginning Simulation
************* Simulation Error Summary *************
** Warning ** The following Report Variables were requested but not generated
** ~~~ ** because IDF did not contain these elements or misspelled variable name -- check .rdd file
************* Key=*, VarName=ZONE IDEAL LOADS SUPPLY AIR TOTAL COOLING ENERGY, Frequency=Hourly
************* Key=*, VarName=ZONE IDEAL LOADS SUPPLY AIR TOTAL HEATING ENERGY, Frequency=Hourly
************* Key=*, VarName=ZONE PACKAGED TERMINAL HEAT PUMP TOTAL COOLING ENERGY, Frequency=Hourly
************* Key=*, VarName=ZONE PACKAGED TERMINAL HEAT PUMP TOTAL HEATING ENERGY, Frequency=Hourly
************* Key=*, VarName=CHILLER ELECTRIC ENERGY, Frequency=Hourly
************* Key=*, VarName=BOILER HEATING ENERGY, Frequency=Hourly
************* Key=*, VarName=FAN ELECTRIC ENERGY, Frequency=Hourly
************* Key=*, VarName=ZONE IDEAL LOADS SUPPLY AIR LATENT HEATING ENERGY, Frequency=Hourly
************* Key=*, VarName=ZONE IDEAL LOADS SUPPLY AIR LATENT COOLING ENERGY, Frequency=Hourly
************* Key=*, VarName=ZONE IDEAL LOADS SUPPLY AIR SENSIBLE HEATING ENERGY, Frequency=Hourly
************* Key=*, VarName=ZONE IDEAL LOADS SUPPLY AIR SENSIBLE COOLING ENERGY, Frequency=Hourly
************* Key=*, VarName=SYSTEM NODE MASS FLOW RATE, Frequency=Hourly
************* Key=*, VarName=SYSTEM NODE TEMPERATURE, Frequency=Hourly
************* Key=*, VarName=SYSTEM NODE RELATIVE HUMIDITY, Frequency=Hourly
************* There are 3 unused schedules in input.
************* There are 5 unused week schedules in input.
************* There are 13 unused day schedules in input.
************* Use Output:Diagnostics,DisplayUnusedSchedules; to see them.
*************
************* ===== Recurring Surface Error Summary =====
************* The following surface error messages occurred.
*************
************* Base Surface does not surround subsurface errors occuring...
************* Check that the GlobalGeometryRules object is expressing the proper starting corner and direction [CounterClockwise/Clockwise]
*************
** Warning ** Base surface does not surround subsurface (CHKSBS), Overlap Status=No-Overlap
** ~~~ ** The base surround errors occurred 1 times.
** ~~~ ** Surface "839A5ADACCE44BC0AF00_GLZP_31" misses SubSurface "839A5ADACCE44BC0AF00_GLZP_31_GLZ_31"
** Warning ** Base surface does not surround subsurface (CHKSBS), Overlap Status=Partial-Overlap
** ~~~ ** The base surround errors occurred 1 times.
** ~~~ ** Surface "839A5ADACCE44BC0AF00_GLZP_34" overlaps SubSurface "839A5ADACCE44BC0AF00_GLZP_34_GLZ_34"
*************
** ~~~ ** The base surround errors occurred 2 times (total).
*************
************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.
************* EnergyPlus Sizing Error Summary. During Sizing: 2 Warning; 0 Severe Errors.
************* EnergyPlus Completed Successfully-- 7 Warning; 0 Severe Errors; Elapsed Time=00hr 07min 35.94sec…
ncluded 3) using a freaky thing that "makes" Planes in order to do ramps (spot the Vodka option = Mobius + antigraviity OFF).
Don't touch the freaky things: for the moment just go and play with this palatable portion (GH components, nothing to fear he he):
depending on choice in gates: Paranoid (Mobius "shifted in Z")
sane (using corrected Planes):
not so sane:
What we have learned so far? Well ramps (and most of other things) ... it's about Planes (coordinate systems) you know.
Again: this is for fun/demo ONLY. I'll prepare a dedicated def for your case soon.
have fun, be brave
…
ges can have much stronger impact on the final design.
The problem is that usually the more "nonlinear" the mapping is the more interesting the result usually are because a definition with a very "linear" mapping doesn't have so much potential for surprise and unforeseen solutions.
It can be a random number as you stated, but also some like for example a slightly different point coordinate leads to different typology in a delaunay triangulation, now the strength of the impact also depends on the total sum of the delaunay points as well on how early the triangulation happens in the definition.
I seen that a shape analysis is a not easy at all not only technical but especially by defining the criteria. Looking forward to see your approach compare genotype and phenotype 'solution' spaces. Maybe an additional approach could be to have something like a gene manager where you can narrow down ranges of certain genes, weight them or freeze them.
to 4) and 5) looking forward to see the history once its ready. I think it could be beneficial to also be able to insert solution "by hand" for further crossbreeding and saving.
What i found myself doing quite often was taking solutions from the biomorpher and then tweaking one or more parameters "by hand" because then you can really see the impact and then you would like to have the possibly to bring that solution back into the biomorpher process.
I will go on testing and get back to you guys in some weeks! I attached you the my definition in case you want to have a look. Its needs kangaroo1, lunchbox, heteroptera and wb. Its more a graphical formal exercise:
best, chris…
hit Commit.
I'm wondering how hard it would be to have an edit box which shows the
number the user could click inside of then type in a new number, then
hit enter. :)
2) How would I go about using one line from a table and assign each
field to a variable? Then, move a slider or something and use the values
from the next row?
background: I'm recreating elbows, Tees, and other fittings using
paramatric scripts, then baking and exporting them. Here's one source
table, http://www.wardfittings.com/Assets/PDFs/0902CatalogColorOld.pdf
page 5, the uniform elbows.
Current Setup: the attached ghx file. Create a point at 0,5,0 in a blank
document with units set to inches, then assign that point to the top
left 'Center Pnt' in the ghx file.
Current workflow:
a) Modify variables A, B, H, and Nominal Dia to match one line from the
table in the linked PDF file, page 5, table of regular elbows.
b) Select the 'Nodes' and 'Surfaces' with a drag box
c) Click 'Bake'
d) Switch to Rhino window, do the 'sellast' command.
e) Drag baked objects along Y axis so the center point is at 0,0,0
f) Run 'Join'
g) Run 'Cap'
h) set the 'node' points to a layer called 'nodes'
i) set the surface to a layer called 'fit-3d'.
j) select the surfaces and nodes
k) export selected
This elbow that I'm doing only has 12 rows, so doing it the above method
doesn't take THAT long. I'm also going to be doing a couple with larger
tables like the Tee on page 8, and in other spec files. As you can
imagine, entering in EACH value into a slider is a bit tedious.
I'd love to take the pdf table, run it through an OCR program to convert
to excel, modify the headers so the ghx script knows what they are, then
paste it into grasshopper, or save it and have grasshopper read it, and
I be able to move a slider or something to to select one line at a time.
Has anyone done something similar? ie: assigned one row in a table to a
predefined set of variables, each variable coming from one field in the row?
Thanks for taking the time to read this message. :)
I'm making a rhino script to do steps d-k, so that part will be much faster.
-Suthern…
the other pluggins again, I doubt that problems arise and if I already have them Which are due to the autodesk pluggins that I can install on another computer or mount a virtual machine, but I doubt it, I simply had to install Grasshopper first and then the rest.)
Problem:
Good day, afternoon or night, please help I can not install the Grasshopper plugin 0.9.76.0 in Rhinoceros 5SR13, I do not know if it is because I uninstalled the version of 32 Bit of Rhinoceros and I only have installed the 64 Bit version, I have installed on Rhinoceros 64 Bit:
Autodesk Realtime Renderer 2014 x64 Autodesk Shape Modeling 2014 x64 Autodesk T-Splines 2015 x64 V-Ray 2.00.23938 for Rhinoceros 5 x64 V-Ray Express 2 for Rhinoceros 5
I would infinitely appreciate the resolution to this problem, for the moment I can not think of anything other than to uninstall everything and leave only installed the program Rhinoceros 5SR13 with Grasshopper 0.9.76.0 and nothing more.
I already tried to download another new file from Grasshopper 0.9.76.0, which ruled out that this installer is wrong, what I could do is look for another version of Rhinoceros but I have the newest one or one of the newest versions: Rhino_5.13.60913.21340_x86_x64_Multi. Exe
I understand that the Grasshoper installer is showing me a message where it says there is a Win32 exception where the system can not find the source file, what I do not know is if this exception has to do with the Windows C /: Folder: Windows, subfolder: System32 or I do not know if it refers to that as I do not have the 32 bit version of Rhinoceros maybe the installer gets confused and generates the installation error exception.
Another thing to which the exception is associated is the start process file: Start.nfo or start information.
There is also a programming argument for file upload errors of boolean operations (geometry operators) associated with the platform operating system, a process called child process.
Also appears another note that says the installed package of a plugin called inspector and I do not know what else I can not explain.
I do not know what to do, I just happen to uninstall and install everything and I do not think the Rhinoceros installer has any errors, I have Windows 10 edition of Red Stone 1 of 64 Bit.
Thanks and if anyone had this problem and solved it please tell me how to fix it or if someone knows about programming you can tell me why all those errors or exceptions are.
Greetings, have a nice day, afternoon or night wherever you step or stand or wherever you are sitting or lying down.…
n lofting, though, it makes perfect sense to scale sections independently from the distance between them.
For practical use, I found the graph mapper clumsy; too course and approximate. So I adapted the code I wrote here (Maths + Divide Curve) so that a list of numbers drives the spacing and, optionally(!), the scaling.
When 'Scale by Distance' is false, the numbers in the list determine scaling; '1' is actual size, '0.5' is half size, '2' is twice the size, etc.
When 'Scale by Distance' is true, the distance between the points is used for scaling. This is an indirect effect of the list of numbers (which determines point spacing) and the size of the original shape relative to the curve length.
'Tangent 0' is the curve tangent at each point. It works well for lofting.
'Tangent 1' is the vector between each point and its successor. It works well for orienting solids.
There are still some mysteries... ("Where there is mystery, there is no mastery.")
Lofting doesn't always work well, 'Cap Planar Holes' doesn't work anymore...
I had hoped that this sequence, ".5,1,2,1,.5", would result in:
two half size shapes, one at each end of the curve.
two full size ("1") and one double size ("2") shapes, spaced appropriately.
But I have a mental block about how to achieve that...? :( Instead, I settled for the last of the five shapes being one point short from the end of the curve, and the spacing is off.
Even so, I find this approach easier to use on a practical basis than the graph mapper.
…