Hello,
Why this discrepancy?


Thank you,
Basile

°C can't be cancelled against K. Changes or differences of temperatures have to be tagged by Delta in the non-absolute temperature units.

See this post

It doesn't show that here: https://www.wolframalpha...input/?i=1kelvin%2F1degC

It converts °C to Kelvin before performing the division.

Edit: Here shows the result 1 K/K, but it specifies it's interpreting °C as delta degree C.

Personally, I prefer using the explicit Δ°C when performing these types of computations. I understand it's may be more confusing to some, but I also believe it's important to be explicit in syntax.

Edited by user 28 February 2019 22:55:42(UTC)  | Reason: Not specified

I've tried this one: https://www.wolframalpha.com/input/?i=1*K%2FCelsius

Did you attach the wrong image? I don't see an appropriate computation to 1. Instead, I see 1*K/K, K is not cancelled, perhaps because each stands for different quantities. Yet I don't see why any tagging or assumption making should be required for offset-free temperature units. Is there any example where such distinguishing would be required?

All the elaborate assumption making doesn't save WA from adding two absolute temperatures and taking the result as a difference.
I still vote in favour of the Delta-tagging of non-absolute units. Perhaps we should add a hint on that to the help strings of °C and °F (to use Deltas if changes or rates are expected).
As long as temperature results strictly default to K units, we are safe. If someone wants to write °C, he will see the hint and still can judge whether to tag or not to tag with Delta. This might reduce the frequency of this issue popping up in the forum.