Use case: converting ACCESS output for use in CABLE

[aidanheerdegen]

Rachel Law described the process required to convert ACCESS output to a format usable as input for stand-alone CABLE in this forum post:

https://forum.access-hive.org.au/t/cable-site-runs-with-access-forcing/2108/5

This is a potential use-case amami could (should?) target. Thoughts @ccarouge?

[ccarouge]

Anything that would make that process straightforward would be welcome. We will need a well-described way to do it as we are likely to do it regularly from various ACCESS experiments.

Rachel is describing a particular workflow since she is using timeseries output at a single location from ACCESS. So it's not using the standard output from the UM.

[atteggiani]

@ccarouge you said Rachel is describing a particular workflow. amami could serve to write a script to help Rachel (in this case) make her process straightforward and easier/quicker to carry out. But I think we should not directly support specific workflows with amami.

What I think is worth understanding and possibly supporting (and documenting) is the more general workflow that most users would carry out.

[ccarouge]

@atteggiani It's fine with me. I'll try and find someone in my team to write something with amami for Rachel's workflow. We'll let you know when we have something (you might hear from us for advice before then...) and we'll share on the forum. This way you can use that as an example if needed.

[atteggiani]

That sounds good, thank you. Also, if we think anything from that example can be replicated as a more frequent workflow, we can think about implementing that part as a standalone amami feature.