e is 50mm
the hight is 100mm
to bigger base is 87mm
imagining now to want to move to 200H rather then 100.
at 200, the new bigger base would be 87+37= 124mm
How can I make the grasshopper do this calculations without me having to redo them every time?
Thank you!…
ort and export from the images below and also from the HELP file of DB in attachments (Page 71: Importing Geometric Data; Page 78-80: Import 3 - D CAD Data). In their HELP file, they mention about "import geometric data".
However, regarding the input of schedules, loads, constructions and etc., DB normally uses "Component " and "Template" (Page 29: Templates And Components; Page 591: Templates; Page 533: Components). "Templates" are databases of typical generic data, including Activity templates, Construction templates, Glazing templates, Facade templates, HVAC templates, Location Templates, and etc. "Component " are databases of individual data items (e.g. a construction type, material, window pane).
Both "Component " and "Template" are allowed to be imported and exported by using "Import / Export library data" command (.ddf format - DB Database File; Page 734: Import Components/Templates, Export Components/Templates). DB also allows us to build up our own libraries of templates and components (Page 731: Library Management; Page 733: Template Library Management).
In order to import both geometric information and other information related to schedules, loads, constructions and etc. from GH to BD, we supposed the following two ways:
1. GH(HB+GB) --> gbXML (both geometric and "Component " and "Template" information) --> DB
This is the way we most prefer. We did see information related to schedules, loads, constructions encoded in the gbXML file generated by GB, but still do not know the reason why DB did not take this information (I also mentioned this in Q6 within the gh file). We assume this might because the gbXML file we create encodes the schedules based on a different template / schema than the one DB expects. We also post this question to the DB forum for help.
(http://www.designbuilder.co.uk/component/option,com_forum/Itemid,25/page,viewtopic/p,13755/#13755)
2. GH(HB+GB) --> gbXML (geometric information only) + .ddf ("Component " and "Template" information only) --> DB
If the first way doesn't work and DB only takes geometric information from the gbXML, then we might think of the other way - generating the .ddf files from GH(HB+GB) to pass the schedule, load and construction information to DB.
I was wondering if it is feasible for HB and GB to have this function? And what is your suggestion to achieve this?
In addition, we notice that DB can export XML files (not gbXML), so we are trying to figure out if DB also accepts / reads the XML file. If so, we might be able to convert the gbXML (with both geometric and schedule information) to XML. What do you think about that?
Thank you again for all your help!
Best,
Ding
DB import
DB export
Template libraries
Component libraries
…
1. Buy some anti gravity tissue (available on request by Fotiadis ACME Industries: any color you want, payment in advance, cash only).
2. Create a pavement with a rectangular hole. Use Buchtal Bosco tiles (the most expensive stuff around > we live once). Avoid trees (it's too late) and/or anything (Less is more).
http://www.agrob-buchtal.de/en/cd/produkte/produkte_seiten_2_19881.html?pe_id=88
3 .Put Vodka into the hole (I do hope Russian top stuff).
4. Do a semi submerged grid of tissues (vertical due to 1 - or your money back).
4. Provide armchairs to the spectators (these things take time). Put ZZTop on the stereo (or Cure). Empty your mind. Reset.
5. Wait for some appropriate wind and/or the 4 horsemen (whatever comes first).
Moral: ResetNowForEver…
rees west to 1 degree west). Changing the latitudinal domain from, say, 0:1 (the equator to 1 degree north) to 88:89 (88 degrees north to 89 degrees north), has zero effect on the x,y shape of the topography map generated. However, in reality, the map should be far, far thinner in the latter case, because longitudinal lines get closer together toward the north and south poles. In actuality, the shape should be close to a trapezoid in both cases, but this is probably not a necessary detail for most people producing maps, since, at an urban or smaller scale, the latitudinal lines bounding the north and south of the map will probably not be that significantly different in length. But the maps should at least stretch from close-to-square for a 1 degree x 1 degree map near the equator to an extremely thin rectangle for a 1 degree x 1 degree map near the north pole.
As an example, I'm looking at a location in Sheffield, UK. The relevant SRTM HGT file spans from 53 N to 54 N, and 2 W to 1 W. The length of the map in the north-south direction should be approximately 111 km, as is the case with the topo map generated by Elk (and a near-standard for 1 degree latitude anywhere in the world). The length of the map in the east-west direction, however, should be somewhere in the range of 67 km, since the 2 W and 1 W longitudinal lines are much closer together at this latitude than they are at the equator. Thus the map should be nearly twice as long in the North-South direction as it is wide in the East-West direction.
If this were to be sorted out, I think it would be really nice to then have the SRTM topo map be positioned automatically in relation to the OSM map being brought in. I think it's good that the OSM map is positioned at 0,0, rather than it's world coordinates, but maybe the SRTM topo map could be aligned with it based on the latitude and longitude domains we input to the SRTM grasshopper module.…
1 and A1 that define the first eye point, P1.
Then a row width and a constant value for C that define the next eye point.
Angle 2 will then give Height 2, Height 2 gives Angle 3 etc...
You can easily do this as a series of functions that follow on from each other,
but there could be a very large number of these, and also a variable number, not a great way to do it.
What I really want is three series that output numbers to define values for Distance, Height and Angle.
D can be defined as a series, but H and A need to be calculated sequentially.
A2 gives H2, then H2 gives A3 etc... One series needs to the input of the other and vice versa. Doesn't work with Logic/sets/series as you end up with circular inputs.
Any ideas on best way to set this up greatly appreciated.
Thanks.…
other notation... where x, y and z are variables, and a,b,c... are constants but sliders, open for dynamic change. + Defining its interval.
- Another minor question; the intcrv box, it is by default a polynomial interpolation? In general, where can you get information on the underlying math behind the boxes?
- Is it possible to define the intervals on the sliders based on other sliders or inputs?
Many questions, but I have been trying to figure this out for quite some time now. I am truly grateful for all help on this matter! :) Maybe they will be of help to other engineers or architects out there...
…
but as one would imagine after 6 or so 'animals' it gets so large that the machine starts to crawl :/
88% of the resources come from the permutation script, my guess is that if the permutation were calculated on the fly with the counter(the engine) it wont have to pre-compile the list which would be much faster...
If anyone has an idea im all ears....
I attached the file (re-written in C#) …
make a new curve from points I attempt to do it by writing:
Curve cv = new Curve();
This gives me the error:Error: 'Rhino.Geometry.Curve.Curve()' is inaccessible due to its protection level (line 88)
I have also tried calling the CreateInterpolatedCurve() from the Curve class, but
Curve cv = null; cv = new Curve.CreateInterpolatedCurve(Mould.Branch(0), 3);
But from this i get:
Error: 'Rhino.Geometry.Curve.CreateInterpolatedCurve(System.Collections.Generic.IEnumerable<Rhino.Geometry.Point3d>, int)' is a 'method' but is used like a 'type' (line 89)I'm really quite lost about how I can this to work. Can anyone help me?…
ells on nurbs surfaces. It references GH_IO.dll, Grasshopper.dll and Rhinocommon.dll.
Custom Class : GS_Mesh
Custom Type : GHType_GSMesh : GH_Goo<GSMesh>
Custom Parameter : GHParam_GSMesh : GH_Param<GHType_GSMesh>
Now, i'm developing a set of structural analysis components to relax gridshells. Those components are grouped in a new project called "Marsupilami".
Naturally my components would eat GS_Mesh objects and relax them. My project references GH_IO.dll, Grasshopper.dll, Rhinocommon.dll and Gridshell.dll.
But I can't build my code because I get the following error, where I try to instantiate a GHType_GSMesh object :
Errorr 3 The type 'Grasshopper.Kernel.Types.GH_Goo`1<T0>' is defined in an assembly that is not referenced. You must add a reference to assembly 'Grasshopper, Version=1.0.0.20, Culture=neutral, PublicKeyToken=null'. C:\Documents and Settings\l.dupeloux.TESS\Mes documents\Dropbox\Dev\Marsupilami\1 - visual studio\Marsupilami\GHComponents\GHComponent_GSMeshRelax.cs 97 13 Marsupilami
I've checked many times but the assembly seems to be referenced in both projects (local copy = false) in the required version (1.0.0.20).
Do you have any idea how to solve this problem ?
Many Thanks
Lionel
…
rld.wolfram.com/EnnepersMinimalSurface.html
when i type the equations for z,y,z it says a syntax error so i obviously do not understand how to construct an expression. (screen capture attached)
Any help/explanation of using this function would be greatly appreciated
thanks so much
Capture.JPG…