Replies: 3 comments 1 reply
-
Hi @Tuah614 , welcome to BHoM 😄 (tl;dr at the bottom 😉 ) One of BHoM's guiding principles is to allow the object model to be universally understood (as best we can) between the different disciplines and domains within the AEC industry, with the aim to standardise the data we're using when undertaking design engineering. As part of that, we've deliberately kept the objects as simple as possible, containing only the properties which are necessary to define them for use - this does mean that some objects may appear to have less 'data' than perhaps they ought to, but by keeping them minimal it allows everyone to (hopefully) have a rich conversation around the object and its use, as opposed to debating whether the measurement property should be That said, obviously the This also helps us maintain the objects during operation. If we stored both the Part of this, includes our Query Methods framework within the engines, which exist to ask simple(ish) questions of the objects which can be derived easily from their existing properties. In this situation, the If you do a Screenshot showing the full Screenshot showing the For your particular query of the I recognise that I can easily answer this question because I've been involved in BHoM for the best part of 6 years, helping shape it on the Environments side and the DevOps side in that time, which gives me a very unfair advantage on knowing where things are (such as knowing I can use the Spatial Engine query method on a Bar for example). Therefore, any suggestions you have for improving the way we find things in BHoM will be greatly appreciated and a welcome addition to our open source community - we want a tool that everyone can use and can only achieve that with the support of everyone using it 😄 I have a few things lined up for the 2024 development calendar to improve UI/UX usage, so if you do have any suggestions please do get in touch! 🚀 tl;dr: the |
Beta Was this translation helpful? Give feedback.
-
Hi @Tuah614 - thanks for raising the question. The Length of a Bar can be obtained through a "Query" method. There are a number of ways to access Query methods through the menus and search. One nice quick way to get the right method for your Bar object input is to drag the wire from the Bar, release and then search for Length. See below. One other thing to note - the above approach helps you find the right Length query. A Bar is an IElement1D - a linear line/curve based element. So you want the Length(IElement1D) as above. Hope this helps! 😄 |
Beta Was this translation helpful? Give feedback.
-
Wow @FraserGreenroyd @al-fisher I didn't expect such detailed explanation! 💚 I appreciate the extra context you provided on BHoM's design principle - super useful especially for beginners like me who doesn't really know where to look for things. |
Beta Was this translation helpful? Give feedback.
-
Hello,
Grasshopper and Robot newbie here. I have a Robot file that contains 4 bars (beam elements from Revit). Using Robot adapter, I managed to capture the bar object from Robot to Grasshopper. What I'm trying to extract is the Length property of each bar object.
I tried exploding the object multiple times but I can't find any Length property. The current workaround I have at the moment is to get the EndNode and StartNode points and get the absolute values from subtracting both points but this is not ideal since real projects will have diagonal beams.
Beta Was this translation helpful? Give feedback.
All reactions