مندان برای شرکت در کلاسها و کارگاهها
دعوت می شود
email: behrange@gmail.com از طریق
و یا شماره تماس 09197804306 جهت ثبت نام تماس حاصل نمایند
جهت شرکت در کلاسهای فوق مبلغ 3500000 ریال به شماره حساب0215461257000 بانک ملی ایران واریزنموده
و فیش واریزی را به همراه کپی کارت ملی تحویل دهید
محل برگزاری کلاسها : تهران خیابان پاسداران خیابان بهستان سوم پلاک 9 …
Angeles, which has 12% of the year made comfortable, and Shiraz, Iran, which also has 12% comfortable (assuming default parameters).
Jerusalem also makes sense to me. There is only a maximum possible 9% of the year that is inside the polygon (you'll see this if you set the timeConstant to a very high number). The default strategyPar makes 6% of these hours comfortable and 3% without cool enough temperatures in the previous hours. This seems reasonable to me.
I could be convinced to change the default time constant to 12 hours (instead of 8) as I know that 12 is the default of climate consultant but that seemed really idealized in my opinion. You'll need really high exposed mass and insulation without much internal heat gain to make conditions stable for more than 8 hours in my opinion.
As for the solarHeatCapacity, I get changes when I drop it down to 10 W/m2 or boost it up to 100 W/m2. It's definitely a parameter that operates on an "order of magnitude" scale and little tweaks to it won't change it too much. You can think of this number as representative of a lot of other physical properties: most notably the depth of the space being passively heated and the thermal mass of that space's materials that participate in heat exchange over the time constant. Climate consultant uses a default assumption of 30 W/m2 but, from my calculations, this is likely assuming a space that has a facade to floor area ratio that is greater than 1. If we say that we need to raise the temperature of 10 cm of an exposed concrete floor for passive heating purposes, and we have a facade-to-floor area ratio of 1:
Required solar flux = ((1 facade-to-floor ratio) x (0.1 m3 of concrete) x (2400 kg/m3 concrete density) x (880 J/kg-K concrete specific heat capacity)) / 3600 seconds/hour
This lands you with a required solar flux of 58 W, which is almost twice the 30 W climate consultant default. While me might say that not all 10 cm of concrete participates over the course of a default 8-hour time constant (most of the action is probably within the first 5 cm), we also have to account for things like transmittance of solar though the window, which, for triple pane, is probably only half of the incident solar. So 50 W seemed to be a more reasonable rule of thumb from my perspective, essentially assuming a facade-to-floor ratio of roughly 1 with 5 cm of concrete participating in an 8 hour heat exchange and a little more than half of solar heat getting through a fully glazed window.
Let me know if that makes sense or if you have any suggestions,
-Chris…
With that in mind, you could use either the subtraction method (set the fitness target to 0) or the division method (set the fitness target to 1).
I know the problem you are trying to solve is just a way to get to know Galapagos, but be aware that there are an infinite number of solution to your problem (there is a infinite line along which all points are equidistant to your two reference points). If you are trying to create an equilateral triangle, the distance between the two reference points needs to figure into your solution.
I do believe that Galapagos works within the limits of the sliders, although it does not seem to pay any heed to the numerical accuracy (so even if the slider floats to 3 decimal places, Galapagos will examine solutions to 8 or 9 decimal places).…
Added by Jason Fleming at 1:30pm on November 1, 2010
...
Set 2
Point 6 (X, Y, same Z)
Point 7 (X, Y, same Z)
Point 8 (X, Y, same Z)
Point 9 (X, Y, same Z)
....
and so on. Then I could use the Polyline command to connect all the points in Set1 to one Polyline, all the Points in Set2 to one line no matter how much points are in one Set
…
-axes
2nd copy 6° rotation out of x-axes
3rd copy 9° rotation out of x-axes
and so on
and I want to change the rotation
I have manage to do that for each object but with more than 100 copies this is pretty uncomfortable. There must be an easier way with the array command but how can I add the rotation to each objectt?
Please help, thanks.…
int on your curves, filling in all black regions with a new color one by one
2. expand live paint, and delete all white-filled regions
3. export the file as a DWG with "maximum editability"
4. export the same file as a JPG or other image format
5. import the DWG into rhino
6. import the image into rhino as a pictureframe to use as an underlay
7. select all the curves
8. use the Hatch Command with "Boundary" enabled
9. Pick points in the drawing where there should be a hatch but isn't, using the image as reference
10. Complete the command, and explode all hatches.
If you needed the white regions as surfaces two, I'd recommend exporting them separately and using a similar process. Having duplicate outlines (one bounding the white, one bounding the black) throws off Rhino's curve boolean processing, which is used for the hatch command as well as the Planar Surface command in some instances.…
and perpframes
3) Ellipse on perframes
4) Series + Move + Series + Scale + Series + rotate (to create generations)
5) Divide curve (ellipse) + Dispatch only seleced points + join those points on ellipse using Intercurve + Divide the resulting intercurve
6) List items (I used list items 4 times, you could do as many). For 'i' parameter in list item i used slider to create generations. depending upon your definition, at this stage you might have to flatten your list output
7) joint the points you get from list output to form another intercurve + repeat that for all items.
8) Loft the curve
9) to form fenestrations, i again used rhino closed curves.
8) Project curve onto surface + copy trim + surface to mesh + mesh thickening from WB.
Hope this helps
Cheers
aB
…
I had a look at the code on Github and it looks like there is code to deal with ngons, but I haven't been able to get it to work in a C# custom goal.
I used this workflow:
1) Select a K2 constraint and setup a simple demo patch in GH2) Create a C# component3) Go to Github and copy paste the source code containing the entire 'public class NameOfConstraint' inside the curly brackets4) Copy paste the code into the C# component into the section titled // <Custom additional code>5) Right-click on the C# component and select 'Manage Assemblies...'6) In the dialog add the Kangaroo.solver from you GH libs7) Recreate the C# component inputs based on the original K2 constraint paying attention to Access and Type hints8) Add a line of code into the C# component in the main 'private void' section creating a new instance of the main Class with the component input variables. A = new FunctionName(x, y);9) Replace any occurrencies of Particles with KangarooSolver.Particle…