Revision history [back]

IGRETEC and EffiBEM (disclaimer: that's my company) have contributed the open source addition of SI units to the results measure and opened a Pull request a few months ago that was merged 3 days ago. So it should be available soonish on BCL.

The measure stays the same except that you will have a dropdown argument that you can toggle to report in SI or IP units.

We have tried to set up sensible units for the new SI reporting. In the SQL file generated by E+, general SI units are used, but then a conversion happens in the measure from source to IP (existing, untouched) and now SI target units. For example a water flow rate in m3/s in the SQL file will become gal/min in IP units, but m3/h in SI units, and they will have a different number of decimals in IP and SI (eg 2 decimals for GPM, 0 for m3/h) based on what numbers are expected. This is probably not perfect and further contributions by other parties are always welcome.

Note that this is done on the Ruby side, and not on the rendering (Javascript) side, so you can't switch units after the model has run.

IGRETEC (@julien-thirifays) and EffiBEM (disclaimer: that's my company) have contributed the open source addition of SI units to the results measure and opened a Pull request a few months ago that was merged 3 days ago. So it should be available soonish on BCL.

The measure stays the same except that you will have a dropdown argument that you can toggle to report in SI or IP units.

We have tried to set up sensible units for the new SI reporting. In the SQL file generated by E+, general SI units are used, but then a conversion happens in the measure from source to IP (existing, untouched) and now SI target units. For example a water flow rate in m3/s in the SQL file will become gal/min in IP units, but m3/h in SI units, and they will have a different number of decimals in IP and SI (eg 2 decimals for GPM, 0 for m3/h) based on what numbers are expected. This is probably not perfect and further contributions by other parties are always welcome.

Note that this is done on the Ruby side, and not on the rendering (Javascript) side, so you can't switch units after the model has run.

IGRETEC (@julien-thirifays) (@Julien THIRIFAYS) and EffiBEM (disclaimer: that's my company) have contributed the open source addition of SI units to the results measure and opened a Pull request a few months ago that was merged 3 days ago. So it should be available soonish on BCL.

The measure stays the same except that you will have a dropdown argument that you can toggle to report in SI or IP units.

We have tried to set up sensible units for the new SI reporting. In the SQL file generated by E+, general SI units are used, but then a conversion happens in the measure from source to IP (existing, untouched) and now SI target units. For example a water flow rate in m3/s in the SQL file will become gal/min in IP units, but m3/h in SI units, and they will have a different number of decimals in IP and SI (eg 2 decimals for GPM, 0 for m3/h) based on what numbers are expected. This is probably not perfect and further contributions by other parties are always welcome.

Note that this is done on the Ruby side, and not on the rendering (Javascript) side, so you can't switch units after the model has run.

IGRETEC (@Julien THIRIFAYS) (@Julien THIRIFAYS) and EffiBEM (disclaimer: that's my company) have contributed the open source addition of SI units to the results measure and opened a Pull request a few months ago that was merged 3 days ago. So it should be available soonish on BCL.

The measure stays the same except that you will have a dropdown argument that you can toggle to report in SI or IP units.

We have tried to set up sensible units for the new SI reporting. In the SQL file generated by E+, general SI units are used, but then a conversion happens in the measure from source to IP (existing, untouched) and now SI target units. For example a water flow rate in m3/s in the SQL file will become gal/min in IP units, but m3/h in SI units, and they will have a different number of decimals in IP and SI (eg 2 decimals for GPM, 0 for m3/h) based on what numbers are expected. This is probably not perfect and further contributions by other parties are always welcome.

Note that this is done on the Ruby side, and not on the rendering (Javascript) side, so you can't switch units after the model has run.

IGRETEC (@Julien THIRIFAYS) and EffiBEM (disclaimer: that's my company) have contributed the open source addition of SI units to the results measure and opened a Pull request a few months ago that was merged 3 days ago. So it should be available soonish on BCL.

The measure stays the same except that you will have a dropdown argument that you can toggle to report in SI or IP units.

We have tried to set up sensible units for the new SI reporting. In the SQL file generated by E+, general SI units are used, but then a conversion happens in the measure from source to IP (existing, untouched) and now SI target units. For example a water flow rate in m3/s in the SQL file will become gal/min in IP units, but m3/h in SI units, and they will have a different number of decimals in IP and SI (eg 2 decimals for GPM, 0 for m3/h) based on what numbers are expected. This is probably not perfect and further contributions by other parties are always welcome.

Note that this is done on the Ruby side, and not on the rendering (Javascript) side, so you can't switch units after the model has run.