General Discussion

Wink wink 😉

@lhoward BIMTrack is doing a lot better then Trimble Connect it seems.

It removes the elements, and the viewpoints/ports and thus certainly the markups or sections.

4aaac25d-2084-4c26-95da-afe79d493877-image.png

Okay. Thank you very much for your response.

I will have an eye on the save point. I really didn’t made that… Thanks.

@inatofalvi It’s a pipe not a covering. When I add the contents of “components 2” of the rule into the basket (=) I see all the pipes, including those not identified as clashing with the walls . It’s almost as if the rule only checks horizontally.

That should be possible with SOL #231 and some classification work.

bc84704e-777f-48f1-b2e9-e1842f1972ef-image.png

In this quick example the Slab has 9m^2 in a 16m^2 space.
The condition is that the Slab in the same space should be at least > than 90% of the Space Area (which would be the 14,4 m^2). In you case it would then e.g. be <= 0.3 I guess.

99997a5b-ca7a-4f96-bcc0-37ff9527f12a-image.png

to be honest, 5h on a workstation and 8h on a laptop…still it is way too long to check!
On the other hand more then 200k elements is also not the lightest model.

I have a model with around 50k and it takes me up to 10min running on [email protected] and 32Gb RAM.
I think it also depends which rules are you using since in my experience some take much faster time then others.

@jsn @lvsteijn

BCF API doesn’t support “default” viewpoint. When loading issues from a BCF Server like BIMcollab the server returns a list of viewpoints. Solibri shows the first as default in BCF Live View.

https://github.com/buildingSMART/BCF-API#451-get-viewpoints-service

Does you classification give colours to objects? If so, I believe, that it overides the coulours of ITO.

@mathieu-farine

Ok, i understand. Unfortunately the degree is not currently possible to adjust.

Meaning that this is turning into a feature/improvement request in the existing rule 🙂 : https://society.solibri.com/category/18/feature-requests

Br,
Lauri

@agroni said in Minimum space requirement:

You misunderstood me because I did not speak about optimizing the space.

Well, probably because you described the task like the following in the first post, without giving much details.

I am trying to figure out a way to calculate the minimum space requirement around an object. (…)

So, from your other posts now I better know what you want to achieve

If I can model something physical for a space requirement, I don’t actually need solibri to check for collision. I could also do it directly in Archicad or even visually control in 3d if everything sits correctly. 🙄

To sum this up simplified,
// you want to check your containers
// they have four sides
// 3 are equal distance x, and on the e.g. front they need more space, so x+y

An idea. Would it eventually be a possibility to use #226 with some modelling support?
You could use it 2x
// first to check for distance x on all four sides
// secondly, which checks for the extra distancy x+y, just on the front side - wasn’t there a possibility to do so?

Edit: Ok, this was just possible for walls and I think there is no other rule where you can just specify the fron, isn’t it?

So in my eyes it would be actually the best approach if #226 gets a remake where you can specify the checked sides of the component a bit better - it needs a new look anyhow as the description is very poor as discussed elsewhere …

@agroni said in Defined Type Check:

I am curious in which instances in your opinion does the #230 not work???

Well, the example from Paola above demonstrates it - it seems to me that this rule does not work and I just even tried it to test again - with the same result and I don’t see any mistake in this quick example.

25fc005a-a6d4-482a-a1b3-f66dab3fa825-image.png

But then again, I am pretty sure I have also used it as you described it and ran into the same weird results a while ago - searching for alternatives for such use cases I now always rely on #203 as I lost my faith in #230 in that specific context.

@jsn said in Objects should not to be in the model:

use SOL 230

In some cases the rule #230 can be used without classifications.

This example shows checking of invalid spaces:

266e38d8-0a07-462d-a967-7756f3db259c-image.png