fairly simple issue but i’m stuck here
Notice your item at index [0][0] for the surface area and index [0] don’t match. This is because you’re working with a float which is less stable.
Round your values before you get the maximum value so that you’re comparing integers instead to prevent this.
1 Like
Or sort them (ascencing order) and take the last item of each nested list.
2 Likes
thanks all, seems both rounding and sorting doesn’t work, but my logic (of list handling) is correct, right?
right, it works, thanks.
but how to get the index from original list? in fact, i just want to get the face list w/ maximum area, not area itself
Try to change the “element” input of indexOf node to @L1
not working, warning: argument is invalid
1.3.2
Auto lacing isn’t in the supported 1.3.2 though… unless I missed something.
no auto lacing, but my Dynamo is most updated, isn’t it?
ah! I asking @tiagocorradi, not you @Ning_Zhou. Sorry for the confusion.
These are the two methods discussed above working off of a simulated data set. The idea behind the math.round is to prevent the bad data reads which can happen when pulling Revit data and converting units.
right, float value is always dangerous, thanks and have great weekend!
What is auto lacing? I have never seen it before.
1 Like
Something which appears to only have made it into the daily builds. I’m not yet comfortable enough to speak on it. Perhaps someone else more familiar will speak up on this, but might be best to wait until it’s commonly available before you start to worry. 