Temperature Gradient

[dglozano]

Hi 👋🏻 I am using UnitsNet quite a lot and I really love it! So far it has covered most of my use cases, but I recently I got the need to use a TemperatureGradient quantity (https://en.wikipedia.org/wiki/Temperature_gradient).

I know there is LapseRate quantity which is also TemperatureDelta / Length, but it seems to be "semantically" focused on the atmospheric temperature variation and it supports only the DegreesPerKilometer unit.

I was wondering if adding a new TemperatureGradient is an option? If so, I would be willing to create a PR to add it.

Another option would be to make the LapseRate support more units I guess, but both the name and description of the quantity can be a little misleading.

Related (ish) to #324

[angularsen]

Hi, without knowing this domain I would favor moving everything to TemperatureGradient. It might be more consistent with our other quantities to name it TemperaturePerLength, but it seems TemperatureGradient is a well established quantity and maybe the better choice .

LapseRate has been touched in:
#316
#321
#324

@ferittuncer @jnyrup
What do you guys think about merging it into TemperatureGradient (or TemperaturePerLength), and marking LapseRate as obsolete?

There is currently a v5 branch where we allow breaking changes, where we can remove anything made obsolete in v4.
#982

[jnyrup]

I'm fine with obsoleting LapseRate as it is a quite meteorology specific unit and a special case of a temperature gradient.

It corresponds to the vertical component of the spatial gradient of temperature
https://en.wikipedia.org/wiki/Lapse_rate

Some observations regard naming.
UnitsNet has several PerLength units and only a single Gradient unit (ElectricCurrentGradient).
Googling a bit it seems TemperatureGradient is an established term.
UnitsNet has ForcePerLength for Surface Tension.

[angularsen]

@dglozano It seems we agree then, please go ahead with the PR:

• Obsolete LapseRate (Add "ObsoleteText": "Use TemperatureGradient instead." on the quantity in LapseRate.json and make sure an obsolete attribute is added to the generated LapseRate struct afterwards.)
• Add TemperatureGradient with your units plus LapseRate's units
• Copy any usages of LapseRate: https://github.com/angularsen/UnitsNet/search?q=lapserate
  • Seems used in UnitsNet/CustomCode/Quantities/TemperatureDelta.extra.cs

[dglozano]

Have created a PR to implement the suggested changes 😄

Not sure how to copy the / operation for TemperatureDelta/Length without making a breaking change by removing the old one that gives a LapseRate as result.

Any suggestion on how to procede?

[angularsen]

Oh, that's right. Hm. I propose we allow that breaking change, since those updating will get a compile error (safe) and have an obsolete warning instructing them what to do.

[0xferit]

Hi, without knowing this domain I would favor moving everything to TemperatureGradient. It might be more consistent with our other quantities to name it TemperaturePerLength, but it seems TemperatureGradient is a well established quantity and maybe the better choice .

LapseRate has been touched in: #316 #321 #324

@ferittuncer @jnyrup What do you guys think about merging it into TemperatureGradient (or TemperaturePerLength), and marking LapseRate as obsolete?

There is currently a v5 branch where we allow breaking changes, where we can remove anything made obsolete in v4. #982

Hello @angularsen, I don't see a problem with this but my opinion might not be so helpful since I'm out of sync for since last 3 years.

[angularsen]

No problem @ferittuncer , I just thought I recognized your name in one of the PRs. It helps to know that you don't mind the change, anyhow 👍

[dglozano]

Solved in #991 , so I am closing this 😁