Temperature for alquimia pk

[smolins]

In a nutshell: temperature is not being passed to the alquimia pk.

This issue is described in the user group by Sam, with a simple test example:

https://groups.google.com/g/ats-users/c/KYH5cMQGgLo/m/clwY29amCwAJ

We did not resolve it yet. Creating this issue to track progress.

[swshaheen]

It appears the updated Alquimia PK just requires a temperature key in the xml file within the surface/subsurface chemistry PKs, e.g.;

Without this, temperature is ignored whether it's present in state or not. Eventually it would be good to have a regression test or update the documentation to make this extra clear, but it doesn't appear to be the result of a bug but rather an intentional change in Alquimia_PK.cc requiring a key for temperature.

[smolins]

Does this mean that temperature in the Chemistry PK can be different from the temperature in other PKs, if defined in the other PKs? Sergi

…

On Tue, Oct 14, 2025 at 1:31 PM swshaheen ***@***.***> wrote: *swshaheen* left a comment (amanzi/ats#324) <#324 (comment)> It appears the updated Alquimia PK just requires a temperature key in the xml file within the surface/subsurface chemistry PKs, e.g.; Without this, temperature is ignored whether it's present in state or not. Eventually it would be good to have a regression test or update the documentation to make this extra clear, but it doesn't appear to be the result of a bug but rather an intentional change in Alquimia_PK.cc requiring a key for temperature. — Reply to this email directly, view it on GitHub <#324 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADXOTGTXHYXZ4VNVCUBUZDT3XVMQJAVCNFSM6AAAAACGIMECBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMBTGUYTIMRRGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>