Open arcondello opened 4 years ago
I suggest we:
1) wait for the lightweight client,
2) implement this as a utility function available as dwave.system.samplers.get_samplers()
or similar.
Reasons: 1) prevent system resources depletion, 2) hierarchy; makes sense to scope "get all samplers" method in level with (or above) the individual samplers (analogously to Client/Solver).
Alternatively, we could implement some sort of DWaveSamplersFactory
with the get_samplers
method, but even if we decide for that in the future, having the utility form is still useful.
One quirk also worth mentioning here, however we proceed, is that the filtering language vocabulary of get_samplers
will probably have to be extended to support sampler-level features (in addition to client/solver-low-level ones).
Semper Fi
Analogous to Client.get_solvers but at the
DWaveSampler
level. Something likeor possibly
would only need to be a thin wrapper.