ACCESS-TEST Dependency Structure

[CodeGat]

Currently in #29 we have the ACCESS-NRI dependency structure:

access-test (the model deployment repository)
  ^ access-test-model (either the component in a coupled model (like access-om2s mom5, etc, or a model itself like access-om3-nuopc?)

There is a proposal to add a access-test-model-component to the access-test package (access-test-model?) which would lead to the heirarchy of:

access-test (the model deployment repository)
  ^ access-test-model (a model itself like access-om3-nuopc)?
    ^ access-test-model-component (a dependency of the above access-test-model model?)

Is this what is intended? Seems like we should either have a series of model components like:

access-test
  ^ access-test-model-component1
  ^ access-test-model-component2

in the access-om2 style, or:

access-test
  ^ access-test-model

in the current access-om3 style.

What is everyones thoughts?

[harshula]

I would expect:

access-test (MDR)
access-test (SBR)
  ^ access-test-model (SPR)

[aidanheerdegen]

The fact that I haven't made PRs for the SPRs might be causing some confusion?

Done now: ACCESS-NRI/spack-packages#214

But I'll also need to make one for https://github.com/ACCESS-NRI/spack-packages/blob/main/packages/access-test/package.py to point to above

[aidanheerdegen]

Spoke too soon. I had done a PR for that one already. But created ACCESS-NRI/spack-packages#215 and requested reviews

[CodeGat]

I've reviewed it, but am still a bit confused. How does the dependency structure look?

[aidanheerdegen]

For completeness, now it is

access-test-model (MDR)
access-test-model (SBR)
  ^ access-test-component (SPR)

[harshula]

Hi @aidanheerdegen , I think you meant:

access-test (MDR)
access-test (SBR)
  ^ access-test-component (SPR)