Currently, MBF’s Quark pipeline integration requires passing a Quark-specific configuration file that defines how the benchmark should be executed. This prevents using MBF’s own adapters to connect to and execute benchmarks on quantum resources.
Ideally, the pipeline should allow MBF adapters to be passed through to Quark, keeping resource handling within MBF. Or, different alternatives like implementing this in the QUARK-plugin level is also viable.
Issue first needs a dedicated design discussion to establish the appropriate integration before implementation.
This is planned as part of the v2 architecture and is intentionally not addressed in PR #59
Currently, MBF’s Quark pipeline integration requires passing a Quark-specific configuration file that defines how the benchmark should be executed. This prevents using MBF’s own adapters to connect to and execute benchmarks on quantum resources.
Ideally, the pipeline should allow MBF adapters to be passed through to Quark, keeping resource handling within MBF. Or, different alternatives like implementing this in the QUARK-plugin level is also viable.
Issue first needs a dedicated design discussion to establish the appropriate integration before implementation.
This is planned as part of the v2 architecture and is intentionally not addressed in PR #59