to the information that you have provided here, I think that I finally understand it and I am able to make some meaningful changes in the components.
First, I have come to realize that, with the current specifications of flow/person and flow/floor area that the OpenStudio libraries have (and corresponding outdoor air object), there is essentially an assumption of demand controlled ventilation any time that the total flow/floor area is below that of the total flow/person (by default, this seems to be the case for most OpenStudio programs). Accordingly, to put in an option for demand controlled ventilation on the ideal air loads parameters component is incorrect and I have since taken it out (I have replaced it with something else described later).
Second, the big decrease in energy that you see from switching the outdoor air object to "None" is not because the air economizer is working. Rather, it is because you eliminated the requirement of fresh air changes for your zone. As such, in a tightly sealed building with low infiltration, there is a danger that occupants might not be getting enough fresh air with this setting. Still, this frees up the airflow of the system to be moderated and the supply temperature to be a nicer levels (see further explanation below).
Thirdly, I have realized that the Ideal Air System is very simple any only works in one of two ways: 1) It takes a specified outdoor air fraction and moderates the temperature of the air to meet the cooling/heating load or 2) It takes a specified supply air temperature and moderates the volume of air to meet the cooling load. The former uses a lot more energy because it often has to make supply air that is at very cold or very hot but always ensures the specified amount of outdoor air is met for the occupants and uses the ventilationPerArea and ventilationPerPerson inputs. The latter risks not supplying the right amount of fresh air if the building is tightly sealed and completely ignores the ventilatioPerArea and ventilationPerPerson inputs but returns energy values that are more reasonable. It is also closer in principle to how modern-day VAV or VRF systems operate. After a long internal debate with myself, I have decided to make the former one (with lower energy values modulating the volume of flow) the default. I now give you the option to switch between the two with a boolean on the ideal Air Parameters component.
Clearly, the air side economizer has a larger effect when the air volume is allowed to modulate so I think that you should now see larger changes in energy use from adding it in. I have also noticed that adding in the economizer while letting the supply air temperature rise seems to give some pretty high reductions in cooling energy.
Thanks again and I have attached an updated file.
-Chris…
imization.
I chose to use Octopus because of multiple objectives.(location, orientation, daylight factor, annual heating use, annual heating use.).I use Ladybug and Honeybee for the daylight environmental and energy analysis.
I am not quite sure how to connect the genomes to the geometry that is supposed to move-the window.
Check this video> it should look something like this: https://www.youtube.com/watch?v=6ssgXi9hSn0
Many thanks for the input, I will try it right away.I have some more questions:
1. First, find the best solution for the irradiation, minimum W/m2, minimum glass m2.
- should I put them in a gene pool or sliders?or a process that would give feedback from the simulations?
2.- Second, find the worst solution for the irradiation, maximum W/m2, maximum glass m2.
This could be the other genome?
Finally, you'll have your fitness criteria for galapagos. If going for 80/20, that would be 0.8*Glass_max / 0.2*Sun_min, or whatever other ratio you want.
Should I put these fitness values in numbers, or at the solver window(minimize or maximaze), I know that Galapagos supports objective only.
I have attached the images to see what I have started and another example for daylighting and shape(just for the structure of the study, I also cant figure out how she connected the dots, thats for the second part of my study, after I determine wich WWR is the fittest for few locations, to optimize the shape of the facade.)But I am not quite sure If the proces should be at the same time, both shape and WWR.
thanks again...
Best,
Nita
…
(1) I have been exporting small sections of a larger model into Maya from Rhino as FBX. In Maya I rotate and scale the models (-90 in X, Scale XYZ 0.001). The Named Views are being saved, but do not have a successful import into the Maya model. They do not appear as in Rhino, and the problem is not solved by scaling or rotating the cameras.
(2) If I try going the other direction, the cameras exported from Maya as FBX are also not aligning with the model in Rhino as they are in Maya.. I will do my best to post some images of the problem and hope you can help.
error !!
This is what the named views look like
here I am trying to the other way with a good view from Maya
strange placement..
This is the best result I can achieve, after I scale the camera by 1000
Any Advice???
Thanks, Robert.
…
ind of interface is CFD. We have done some code development and we are actualy now in the process of developing a simple interface for openfoam (Linux) that would help us streamline our simulations (which are usually one of a certain number of standard scenarios. I believe CFD to be as important as energy simulation for the built environment (perhaps even more for indoor comfort) but it's much harder for people to access. In that light, I would love to help in anyway I can in the Butterfly project. My programming skills are quite bad (although I'm home-schooling myself lately) but I do have a somewhat good understanding of openfoam/cfd. I have to admit though didn't realize there would be a Windows version, any chance we can get foam extend? Anywayds, if you go for it let me know!
Other parts I would feel there is a gap you already mentioned:
1. Visualization. Actually my home schooled programming is on javascript and d3.js. There is so much data out there concerning building operations and it's very hard to transform them to information useful for us or owners/clients. I am hoping to start a small research project soon on D3.js. My idea is to develop a kind of system in which data (presumably databases) can be 'thrown in' a D3 site which would then transform this data into a series of graphs, plots, etc., into a more structured representation. An example I'm thinking here is EMS data outputs.
2. LCA. This however is a frustrating part. My main expertise is in LCA but that doesn't mean I like the world of (especially commercial) LCA. While there are a ton of wonderful people to help you (lca-list is amazing for example) there are close to none open data for LCA. Also, one of its biggest disadvantages is it's geographic relevance (never site specific) which is quite important for the construction industry. But with the popularity EPDs are getting lately and the easy way they can be used for simple LCAs I think it's time for some development here as well. So I wouldn't mind the introduction, if the people over there require some assistance.
3. Easy use of detailed ACMV (sorry for the tropical term) simulations. I get quite frustrated when I have to use DesignBuilder for detailed simulations, the program is just so limiting in the design capabilities. That is why I am so excited for the Openstudio components getting back on track!
P.S.: Hadn't heard of 3 phase daylight simulation, sounds so cool!
Kind regards,
Theodore.…
Sunpath component. This is what I essentially did in the upper photo of my hometown's mask.For now this is working only for metric units. I will make sure that for the next release at least feets are supported as well.As for the saving of the time: try increasing the maxVisibilityRadius_ to say 300. Depending on your PC configuration and internet speed it may take as long as 15 minutes for the component to run. The topography file will first be downloaded from opentopography.org. That's the .tif file you noticed. Once the mask is created it will be saved to an .obj file. The next time you run it the mask will be imported from the .obj file, skipping the previous 15 minutes:
It still may take a a couple of minutes (depending on your PC configuration) for the component to complete loading of the mask. The reason why is: the mask needs to be scaled and centered according to the context_ input.Also the next time a user decides to change the maskStyle_ input or context_ input, the topography data will not be downloaded from the opentopography.org website, but rather created from the .tif file.For default maximalVisibility_ of 100, these .tif files are mostly a couple of megabytes, which is not that much of a burden on user's hard drive space. On the other hand keeping these .tif files on user's hard drive helps saving the opentopography bandwidth cap.Let me know if I can answer any further detail or if this one hasn't been clear.Hi Chris,
Thank you too.Please provide the following data:
1) Zip the "terrain shading mask libraries 32-bit" folder in "c:\ladybug" in case you have x86 version of Rhino 5, or "terrain shading mask libraries 64-bit" folder in case you have the 64 bit version of Rhino 5. Upload the zipped folder, and post the link in here, please.Zip the whole folder, not its content only.
2) What is the full name of the GDAL libraries .zip file that you downloaded? What is your Windows version and Rhino 5 version?
On genDayMtx.exe and install of the GDAL libraries: I am reluctant to avoid manual install due to blocking issue. Copying two folders manually is quite a small price to pay in comparison with finding the blocked library among tens of them.…
.. then you put (or drill) rather "canonical" patterns that formulate the inner/outer skin (or both).
2. The above approach hits 3 walls: (a) very slow response (Rhino is a surface modeller) (b) booleans/fillets potential issues (Rhino is a surface modeller) (c) a potential aesthetic antithesis between the liberty of the "whole" VS the "strict" rules of the "details".
3. Since you opt to work with Rhino It could be worth considering playing his own game: deforming surfaces that is ... by working against control points or via the Morph methods. Then join them and get the decorative thingy as "solid".
Images below are from a C# that actually gets the control points of Surfaces in Lists and "deforms" them according a gazillion of options (a) via any "on-the-fly" defined pattern (Take or skip this control point: shift branches/items that is) (b) using any number of attractors in any push/pull mode (c) using chaotic vector values (d) using ... well too many ways to list them here.
Imagine what the Alien cuppa def does (modifies "diagonally" control points) ... multiplied by 1000.…
ard to find example...
I do not know how to load windows form and send data to object in form.vb...using grasshopper sdk.
it is the same,, when I try to use dll(class) with VB component in grasshopper.
may be I have to make two class (class1, form1) but,
when I send data to class1, form1 can not receive class1 data because form 1 made new class1 and both class1, class1(from form1) is different session?
for novice programer,, for me it is very hard.
load class1,
class1 load form1
send data from grasshopper to form1. x
and button click
couldn't calculated,... result was always "0"
and tried many other methods,, but it failed...
may be some known technic but it is hard to find books...
Please...help me.
if possible would you tell me how to load form1 using grasshopper sdk and ""send data "" to form1
or form1 could use data from grasshopper?
Thank you....
for ex)
'(in class.vb)
Public Class Class1 Private Shared fl As Form1 Public Sub fload() If fl Is Nothing Then fl = New Form1 fl.Show() End If End SubEnd Class
'(in form1.vb)
Public Class Form1 Public x, y As Double Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
ab(x, y) MsgBox("hi" & y) End Sub Sub ab(ByRef a As Double, ByRef b As Double) b = a * 2 End SubEnd Class
'(in Grasshopper VB.component)
Dim cl As ClassLibrary1.Class1 If cl Is Nothing And f = True Then cl = New Class1 cl.fload() End If Dim fr As ClassLibrary1.Form1 If fr Is Nothing Then fr = New Form1 End If fr.x = x a = fr.y…
e options are).
1) I wish there were better search features included in the double-left-click "enter a search keyword" option, which only brings up icons/components by name in relation to what's typed but doesn't help users understand what that icon's/component's function is. I wish every keyword in the full text that is already included as each component's function description (which appears when you hover over it with the mouse, below the component name) were included in the search keywords, not just the name of the component. That would amount to searching by the function needed, not just by the name of a component (which might not help someone who has never heard of the component to know its function).
example/rephrased: if I double-left-click and type "create a point" the components that appear under "create" in the list are "create set" (or "create material", "create branch" or "create complex", but no point). To get the "create a point" component, you have to know to type "point" but then you also have to check out every point component by inserting it and hovering over it to see if one of them creates a point. However, the "Point XYZ" component's description when i hover over it says "Create a point from xyz coordinates". I wish the description text for every component was part of the searchable content, so that de facto that component would appear as an option in the list when i type "create a point."
2) All along I wished there were an online index/dictionary for all grasshopper components, downloadable and searchable, that could be organized and searchable in order by user preference, including component name, component function (both general categories like "verb" - see below - as well as its specific function) and finally with a brief description/definition of what the component is good for. I imagine categories like "verbs" (someone learning a foreign language the first time gets a list of major verbs) where all the "action functions" like graft, flatten, extrude, etc. are viewable in a single list. This way when i want to make something happen, but don't know what component to choose, i have a way to read about what's possible without going through the 250+ pages of the manual (which isn't a searchable pdf when downloaded, from what i see, and doesn't have an index).
Thanks!
Christina…
he process. The last one is there because fixing it would cause another problem, which we feel is more serious. Solutions may well be forthcoming in the future though.
1. Grasshopper curves and points are drawn more towards the camera than they really are. This is a conscious decision. Often Rhino geometry and Grasshopper geometry exist in the same place. If we would draw the Grasshopper preview in place, then there's no telling whether you'd see the Rhino curve or the Grasshopper curve. We feel it's important that you always see the Grasshopper curve on top. This is why we draw all curves and points slightly towards the camera. However we don't do this for meshes. This results in something akin to the image below. The eye represents the location of the viewport camera, the shaded box represents the actual location of the geometry and all the thick black lines represent the edges of the geometry moved towards the camera. As you can see, the red lines will be visible, even though they should be behind the shaded box. This effect can get very strong when the camera is close to some geometry relative to the size of the boundingbox of all geometry.
2. Wires behind the camera are sometimes visible. This is a bug I don't know how to solve. We'll get around to it eventually. When an object is behind the camera the display transform sometimes makes it visible in front of the camera in some weird inverted perspective mode.
3. Meshes are not z-sorted prior to display. This means that the order in which they are drawn is not back-to-front, but fairly arbitrary. This means that a transparent mesh may appear to punch a hole in the mesh behind it. If this is annoying you to no end, you can use Ctrl+F on the Grasshopper components that contain the meshes that are punching holes and then press F5 to recompute. The draw order should now be different. Of course sometimes it will only 'fix' it for a specific camera angle.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
that aren't relevant anymore or if there are any I missed please let me know. Maybe we can get a list like this in a better place as well.
Thank you.
Right Mouse - When wiring, plugs wire into multiple inputs.Shift+Click - Pick component aggregate.Shift+Clicking - Place component aggregate.Alt+Left - Click Split canvas tool.Ctrl+Q - Preview toggle.Ctrl+E - Enable toggle.Ctrl+Left - Navigate upstream.Ctrl+Right - Navigate downstream.Ctrl+M - Mesh Edge display toggle.Ctrl+1 - No previewCtrl+2 - Wireframe preview.Ctrl+3 - ShadedCtrl+Alt+Shift+Click - Save image of canvas.Ctrl+Alt and Shift+Ctrl+Alt - Highlights components on the canvas and component palette.Ctrl+Shift - Rewire component input/output.Double Click - Find/SearchAlt+Drag - Copy component on canvas.Ctrl+Tab - Document cycling.Ctrl+Shift+P - PreferencesCtrl+N - New fileCtrl+O - Open fileCtrl+S - Save file.Ctrl+Shift+S - Save as.Ctrl+Alt+S - Save backup.Ctrl+W - Close open document.Ctrl+Z - Undo copy.Ctrl+Y - RedoCtrl+X - CutCtrl+C - CopyCtrl+P - PasteCtrl+Alt+V - Paste in placeCtrl+Shift+V - Paste in centerCtrl+A - Select allCtrl+D - DeselectCtrl+Shift+I - Invert SelectionCtrl+Shift+A - Grow SelectionCtrl+Shift+Left Arrow - Grow UpstreamCtrl+Shift+Right Arrow - Grow DownstreamCtrl+Left Arrow - Shift upstreamCtrl+Right Arrow - Shift downstreamCtrl+G - Group selectionF3 - FindF4 - CreateF5 - RecomputeCtrl+B - Send to backCtrl+F - Bring to frontCtrl+Shift+B - Move backwardsCtrl+Shift+F - Move forwardsInsert - Bake selectedCtrl+Q - Toggle previewCtrl+E - Toggle enabled selected
…