General Discussion

@andyb Hello, where can I find more information about this job.

That’s indeed poorly explained.

I have not used it a while but I once created some notes for me to remember how it works and it basically should be like the following:

a812264f-3e5a-432d-8d23-5d8e0fcfb777-image.png
The first value (row) is always giving the Limiter - let’s ignore it for a second.

The second and the third values define the basic bounding box range. So if you define here nothing or 0 then e.g. the component Width is taken.

If you do not use the limiter, than it makes sense to just work with min or max values.

If you however, want to set an offset, or a tolerance then you us the limiter values and now min and max makes sense. E.g. You set the width to 0 and the limiter to 500 (or -500) then the bounding box will change accordingly.

So for the Height this would mean, you set a Limiter of (+) -100 to lower (or raise) the bounding box accordingly and then give it a maximum height to specify it (and not just use the component height).

a03081f2-6ec7-4e14-817b-7b339ec6a84a-image.png

If you would use on the other hand the following settings for the mentioned example above, then rule would be passed, as the object is about 966m away and due to the limiter setting it “jumps” 999mm forward and checks the remaining 999 to 2000 mm.

3643d664-3db3-49a9-b7a1-29357f366d47-image.png

So the rule is not that simple, and actually it is very easy “to mess it up by yourself” when you type in non-logic values, and then there is no warning sign or error message. Combined with the poor documentation, wrong translations (e.g. german) this is something which should definitely be improved. I am even not sure if my interpretation is fully correct, but with this information in mind you should be able to play around a bit and find out which settings suits your needs best.

Edit:

So for your given example, the following should do the job if I understood correctly.

05954c3b-0197-4968-87e7-7f8958819e7d-image.png

@johane the only work-around I have found is to undock the Live Issues Details" panel and place on a second monitor. This will allow you to see everything at once without the need to scroll. I use a laptop with two external monitors when I’m in the office and I have a custom layout saved for office and another for home (1 external monitor at home).

@eric Thanks, i got it! 🙂

Thanks Marchi.

Good to see I am not the only one with this shocking result.

I know what to do.

#topic can be closed.

I guess this is the same issue

first create a classification for the groups, returning the group names.
2257de99-362e-456c-9a62-34c37b4cf613-image.png

Then create a ITO based on the classification names

Hi @lmicoltadiaz ,

As a viewpoint is unmodifiable after it has been synchronised with the server, we do not allow users to add components to the viewpoint. That is why Selection basket is not responsive for those synchronised viewpoints.

Could you provide us your smc model only with the issue where the components get missing upon sync?

Thank you!

@lraimo said in Rule Intersections in MEP Models:

According BIM requirements in Estonia, such elements must be assigned to the lowest storey

Good to know that there are some guidelines dealing with it.
If you have any links to such a reference I would appreciate it. (Might be also ok if it’s written in Estonian).