Closed mdecandia closed 7 months ago
Docs for problem_timing_data
.
@mdecandia, @fionahanington, I'm not convinced we should add all these parameters to the inspector UI. It's 14 new parameters (we currently have 24 displayed), the value of which is questionable for human consumption.
Wasn't this solver property added mainly for programmatic use, like QPU access time estimation?
Have in mind we currently don't render "big" properties like qubits
, couplers
and anneal_offset_ranges
.
That makes sense. I don't think it's a must. I'll close this issue.
to help with QPU runtime estimation and ensure that users can see all the solver properties that are available to them. The property could be rendered similarly to how it is rendered in the Leap Solver Details modal: