In my initial brainstorming of annotation I was coming up with a definition which defines a vendor (or an implementation of MPI) in one annotation. This leads to another annotation being parsed.
So the definition of CUDA would appear under .nvidia.cuda.version:
https://github.com/supercontainers/compspec/blob/6764db83a00974ff590a41292df597e72c733a79/supercontainers/compspec.json#L14
Like:
gpu.vendor = nvidia
gpu.nvidia.cuda.version = 12.1
Not sure if that is the best approach, as we might just assume that if the gpu.nvidia.cuda.version entry exists it is present. For containers which are even able to support both a selector (defining which vendor to go with) might be a hinderance.
In my initial brainstorming of annotation I was coming up with a definition which defines a vendor (or an implementation of MPI) in one annotation. This leads to another annotation being parsed.
So the definition of CUDA would appear under
.nvidia.cuda.version:https://github.com/supercontainers/compspec/blob/6764db83a00974ff590a41292df597e72c733a79/supercontainers/compspec.json#L14
Like:
Not sure if that is the best approach, as we might just assume that if the
gpu.nvidia.cuda.versionentry exists it is present. For containers which are even able to support both a selector (defining which vendor to go with) might be a hinderance.