ROMS selects physics and other model options at compile-time. The spack package currently only supports two "applications": benchmark and upwelling:
https://github.com/ACCESS-NRI/spack-packages/blob/main/packages/ancoms-roms/package.py#L35-L41
This is bad from an infrastructure point of view where we'd prefer to deploy a single executable that caters to a range of needs that can be selected at run time.
Given this situation isn't likely to change in the short term, one work-around would be to deploy multiple executables corresponding to multiple applications.
See this related issue: ACCESS-NRI/access-spack-packages#309
ROMS selects physics and other model options at compile-time. The spack package currently only supports two "applications":
benchmarkandupwelling:https://github.com/ACCESS-NRI/spack-packages/blob/main/packages/ancoms-roms/package.py#L35-L41
This is bad from an infrastructure point of view where we'd prefer to deploy a single executable that caters to a range of needs that can be selected at run time.
Given this situation isn't likely to change in the short term, one work-around would be to deploy multiple executables corresponding to multiple applications.
See this related issue: ACCESS-NRI/access-spack-packages#309