Upgrading to Use New Units
- Last UpdatedMay 17, 2023
- 2 minute read
To take advantage of the new functions, attributes need to be set to the correct dimension. This has been done for the standard attributes. Customers will need it to do it for their UDAs and catalogue and design parameters and properties. Any data imported to a Schematic database using Schematic Model Manager will need to have the 12.1 upgrade applied.
It is not necessary to change all dimensions at the same time. For example, Lengths are already handled correctly. It is expected that angles are stored in Degrees, so they will also be handled correctly, but users will have to identify which UDAs are angles and set their UUNIT to ANGL.
This will be done for a project; the administrator also needs to determine how to handle each of the dimensions used for other attributes – volumes, densities, pressures It is possible to continue as before for any by using the NUMERIC option. For details, please refer to the 12.0 to 12.1 Upgrade manual. The process for each will be:
If all quantities have been stored in the new Database Units
-
Set the UUNIT for any UDA’s.
-
Any UDAs used to store the Unit values are no longer required and can be deleted.
-
Any customer appware managing unit conversion or display can be removed or replaced by standard functions.
If all quantities have been stored in the same unit (which is not the new Database Unit)
-
Set the UUNIT for any UDA’s.
-
Output a datal file with the dimensions being set to numeric, for example: UNITS NUMERIC TEMPERATURE
-
Read the datal file back in with the current units set appropriately so that unqualified values are assumed to be in those units: UNITS DEGF TEMPERATURE
-
Any UDAs used to store the Unit values are no longer required and can be deleted.
-
Any customer appware managing unit conversion or display can be removed or replaced by standard functions.
If quantities have been stored in mixed units with a UDA recording the unit for each
-
Set the UUNIT for any UDA’s.
-
Set the dimensions to numeric, for example,. UNITS NUMERIC TEMPERATURE
-
Output a file with the attribute values, with the value from the unit UDA appended.
-
Check the format of the value plus unit conforms to new input format rules.
-
If necessary edit the file with a text editor or script to achieve this.
-
Read the file back in.
-
Set current units as preferred, for example, UNITS DEGF TEMPERATURE
-
Any UDAs used to store the Unit values are no longer required and can be deleted.
-
Any customer appware managing unit conversion or display can be removed or replaced by standard functions.
If quantities have been stored in mixed units with ‘custom and practice’ being the only record of the unit, which is hopefully rarely the case:
-
For the short-term set the dimensions to NUMERIC.
-
Plan to move to more rigorous use of units, probably employing a combination of the techniques above.