Learn diagnostics system by returning photolysis fields as diagnostics

[alanjhewitt]

Are there any linked Issues or Pull Requests?

No response

Brief description

Hi Zubair,

As you mentioned before, the dry diameter would not be a good example diagnostic to get on with, since they are already labelled as "prognostic" fields in lfric_apps.

Mohit suggested that adding a couple of extra photolysis fields would probably be a useful way of learning the pipework involved in the diagnostics.

Would it be possible for you to add these four UM diagnostics into lfric_apps with UM stashcode and UM variable name below
50-228 (jO1D)
50-229 (jNO2)
50-245 (jO2)
50-246 (jO3(P))

I think they should already be part of "photol_rates" in the lfric_apps kernel and algorithm

Kind regards,

Alan

Further details of the issue.

No response

[zmaalick]

Inspecting jO1d:

The existing photol_rate_jo1d field is already filled with the correct data (extracted from photol_rates via the jo3a case). It is currently written to XIOS as chemistry__photol_rate_jo1d with output name photol_rate_jo1d. To also expose it under the UM name jO1D, we need to write the same field to a second XIOS id and register that second id in the XML.