Chemotion LabIMotion 1.3.0 Preview

[cllde8]

Chemotion LabIMotion 1.3.0 Preview

Important Notice: Change in Test Instance

We're glad to share the upcoming features we've prepared. Please feel free to explore these enhancements in our test instance.

• Export/Import Collection function: This function now includes self-designed elements within the same instance. See discussion for further details.
• Restriction Setting: New restriction options are available, and you can also assign an alternative name for the field. Refer to the discussion for more information.
• Generic Element Split Function: Introduce the 'Split' function, allowing users to split elements and establish parent-child relationships. Check discussion for more details.
• Generic Element Reporting Function: This feature enables users to generate a basic report based on a generic element in docx format. Check discussion for more details. A visual demonstration is available.
• System Units: Additional system units are now supported. Click here to view the complete list.
• Customize Default Unit for Field: As a Designer, you can set a preferred unit for a field as the default option within the template. A visual demonstration is available.
• Additional information has been added to the field header to provide designers with a quick overview.

We invite you to try out these features in the test instance and share any feedback or observations in this thread. Creating a Discussion is welcome. Your insights are valuable, and we appreciate them.

-- Edit: (1) Added discussion links and video links. (2) Added one feature: Customize Default Unit for Field.

[JohnJolliffe-JGU]

Feedback regarding the generic Element Reporting Function

• Temperatures in degrees Celsius are only reported as "C" with the "°" sign missing
• Download is initially prevented by google chrome "unsafe download blocked" (maybe this has something to do with the test instance though I am not sure)
• Data from generic segments not reportable

[cllde8]

Dear @JohnJolliffe-JGU

Thank you for your feedback. We would like to inform you that we have implemented the updates and applied them to the test instance. All three points have been resolved. Please try them out and share your feedback with us.

Additionally, to mitigate potential impacts caused by the unavailability of the current instance's cloud service, we have established a new test instance. You can access the new test instance at https://labimotion-stage.ibcs.kit.edu/home.

Best regards,
Claire

[herrdivad]

Hi Team,
we have some issues / confusions with System-Defined Units:

• The unit of Farady is currently set to "C/m". Please set it to "Fd" (https://www.chemie.de/lexikon/Faraday_(Einheit).html)

• Also could you please add a new entry name "Electric Charge per mol" with the unit of C/mol ?

Thanks in Advance.

[cllde8]

Hi @herrdivad ,

Following the discussion with Nicole, this requirement has been clarified and the final version has been confirmed. Please don't hesitate to reach out if you have any questions.

Best regards,
Claire

[herrdivad]

Hi Team,

I have noticed a possibly incorrect behavior in the formula fields:
The fact that input fields for formulas can have system-defined units, while the result field has none, can lead to errors in the formula if the user uses the green button to convert units (e.g. m -> mm).
Let's look at the simple example of the speed calculation v = s/t :

As long as the user does not change anything, the calculation works as intended 10 m / 2 s = 5 m/s
But if the users chlicks to change m to mm:

The result would be 1000 times greater. This would be fine, if the system was able to change the unit of the velocity to mm/s by itself, which is not yet possible, as formular-fields cannot have any system-defined units (or am I wrong?).
But without auto-units for results, the calculations is faulty.
Possible workarounds / fixes would be:

• make it possible for admins to lock unit fields to a specific unit and therefor take the user the possibility to change e.g. m to mm.
• don't stipulate a specific unit for the result, so that the users has to think for themself, if the result is m/s or mm/s. But that would not be a good idea and gets more complicated if hidden constants and conversion factors will be included in the formular.

Thanks in Advance.

[herrdivad]

Nicole also asked herself, if the value given by the use is saved, and the translation to other units is only an other "representation", or if the value is actually overwritten each time a unit conversion is performed.
In case of "only representation", that could solve the formular issues, because the calculations always uses the "saved value" and not the "shown" value (which includes the conversion factor).

[cllde8]

Hi @herrdivad ,

Thank you for your message. After discussing with Nicole, there seems to be a misunderstanding regarding the 'Formula-Field'. To gain a better understanding of how the 'Formula-Field' component works, please refer to the Formula-Field section available at the documentation site.

As always, if you require any assistance or wish to share feature requests, please visit the Get Assistance and Share Feature Requests page.

Best regards,
Claire

[herrdivad]

Hi Team,

the conversions of the time / Duration System Definied units has a rounding error from about 3-4 %.

->
->

This seems to be not much, but this error can propagate into formulas (e.g. in my previous report about the velocity)

Thanks in Advance.

[herrdivad]

The Error will be much smaller the greater the starting number will be.
E.g. 100000 s will result in 100000.224 s.
So maybe the reason is just a simple resolution problem of doubles / floats.

[cllde8]

Hi @herrdivad ,

Thank you for your message. Please note that the result is rounded to 5 decimal places. If your application requires further assistance, please feel free to refer to the Get Assistance and Share Feature Requests page.

Best regards,
Claire

[herrdivad]

Hi Team,

Nicole asked if these "up-and-down" buttons are truly necessary:

She asked if it is possible to please remove them?

Also, "mM" is not the same as "mmol". The same goes for "M" and mol. <- See the units in brackets in the example above.
The capital "M" stands for molar, which is actual "mol/L". So please remove it from the "amount of substance" unit entry.

Thanks in Advance.

[cllde8]

Hi @herrdivad ,

Thank you for your message. After discussing with Nicole, the brackets will be removed to make more space.
Please feel free to refer to the Get Assistance and Share Feature Requests pages for any requests. Thank you for your cooperation.

Best regards,
Claire

[herrdivad]

Hi Team,

just a short reminder:
Formulas / calculations and Restriction Setting are currently not possible in tables.

[cllde8]

Hi @herrdivad ,

Thank you for your message. Please note that this thread is specifically designated for the Chemotion LabIMotion 1.3.0 Preview. To review the items included in this preview version, kindly refer to the first post.

For any assistance or to share feature requests, you can visit the Get Assistance and Share Feature Requests page.

Best regards,
Claire

[cllde8]

Released!