Hi to All.
In the official tables, the “specific heat” of the oil is:
1850 J/kg x °C
Is it correct the following my conversion?
1850000000 mJ/t x °C
Thank you very much
Cheers
Giovanni
Hi to All.
In the official tables, the “specific heat” of the oil is:
1850 J/kg x °C
Is it correct the following my conversion?
1850000000 mJ/t x °C
Thank you very much
Cheers
Giovanni
Yes.Google is surprisingly good for unit conversion. In this case, you just have to use Kelvins for Google conversion (they are equivalent to Celsius degrees here):
In other situations, I use WolframAlpha, SMath Studio and online converters (rarely).
Uauuu.
Thank you very much,
Very Useful
Cheers.
Thank you
Giovanni
Well, PrePoMax has unit conversion capabilities. That means you can enter the specific heat as 1850 J/(kg·°C) and it will be automatically converted to the unit system you selected. If you selected mm, N you will get 1850000000 mJ/(t·°C)! But since this feature is not used a lot (I do not know why) it is not thoroughly tested.
I thought that it may not handle such complex units with fractions and Celsius degrees but it’s cool that it can do it. I will show this handy feature in my next YouTube tutorial and mention it in the next version of the documentation. To be honest, I discovered it quite recently, when I saw your video about hydrostatic pressure.
Very good.
Thank you
much thanks for this useful features, hope MKS unit system (kgf.cm) also supported in the future.
regarding conversion features in PrePoMax, i have found small problem in Tied Contact value adjustment. the value of slope over-closure given the same value no matter unit set are defined, but stick slope is not.
another problems are in moment force, typing kip*in
units is not approved reporting as not valid input values. however, typing in kN*m
or kn*m
is accepted and not a problems in conversions.
I have fixed the default values in the surface behaviour properties. Now they are defined using units and when a different unit system is defined they are appropriately converted. Then they are rounded to 3 significant digits.
Not all possible unit abbreviations are supported. [kip] is currently not a supported unit of force. I will try to add some kind of information to the user, which units are supported.
however, in concentrated forces menu definition. a (kip)
units is valid input and accepted without any error message.
Yes, you are right. I missed that.
The problem is, that there are two different types of derived units. Since I am using a simple library for unit conversion, one type of derived units are the built in/integrated derived units. Like pressure. Here the authors supported only some combinations of force-length pairs (here kip is not supported).
The other type of derived units are the ones I added to account for some strange FEM unit combinations. Like force per volume, which is not included in the unit library I use. In this unit type, I separate the derived unit into its base units and recompute their value. So all unit abbreviations that are integrated into the base unit are supported (here kip is supported).
The advantage of the first type are unit abbreviations, that cannot be broken automatically into their base units. Like bar for pressure. The advantage of the second type is the possibility to support all possible pairs/tuples of base units.
Maybe I could add the second approach also to the built-in units to reduce the confusion for the user.
I have added additional data to the failed unit conversion. Now the error window shows all possible units for the current value that can be used:
The problem at the moment is that the Details button has to be clicked to show the actual error message. I am looking at how to improve this.
It is not a very intuitive way of finding all supported units, but it is the only way at the moment.
thank for explanations, hope it will be supported many common units for the future versions.
If you mean new consistent unit systems, this is not a problem. If you mean single units for specific properties, I think a lot of units are already supported. Since this capability depends on the library I am using it will probably not change a lot.
thank you.
currently four units system preset in model properties available (length,force,pressure)
another common units did not yet supported,
(in, kip, ksi) units mostly used in engineering book and report, also (cm, kgf, kgf/cm2) units at early an oldies.
could be useful when these units system preset are supported.