Unit System for Library Object Definitions

[Rick Brice]

I am not understanding how the handling of units work. In my library I've created a solid called "WFGirder". I used internal units of INCHES when defining the volume. The solid is defined by several fixed dimensions and two variables H and Length.

I'm trying to use this solid in a project called "Jansen Creek Bridge". The internal units for this project is FEET.

I cannot get the girder solid to be at the same scale as the alignment in the Jansen Creek Bridge project.

The bottom line is that I don't fully understand how the unit system works. Please advise.

[Ali Koc]

OpenBrIM App fully supports unit systems. Unit object defined in the project named "Internal" specifies the internal unit system of the project, while others are for the end user. More information can be found here.

However, when we initially designed the OpenBrIM Library, we envisioned that the objects defined in them would be unit-less.

For example, if you have a volume defined in a library object, the dimensions of the volume is set by the input parameters which are set by the project in which this object is used. So, whatever unit system the project sets for the input parameters of the object, as long as we did not hardcode some dimensions in the library itsel, it should work, right? Well, this assumption, not surprisingly, fell apart pretty quick as design codes started to be implemented in the library.

In an update (most likely sometime next week), we will implement unit conversion between library objects and the projects in which they are used. In the meantime, it would be best if you could keep the library object and the project uniform units.

I will edit the title of this issue so that we can use it to track the development of unit system for library objects.