Radomir Stevanovic

Yes, I still have `dwave.common` on my todo list. It would include: - logging stuff - profiling (like `tictoc`) - testing utils, like various `assertX` - misc commonly used utils...

Hi Brian, the module you're referring to, `dwave_bm` was privately available to a customer of D-Wave. It is not publicly available, nor it is open-sourced.

I'm not sure if those materials are still available to you, you should check with the course organizer. But `dwave_bm` package is not publicly available.

Hey Brian, unfortunately that package is no longer available. Even if it would be made available for you, you still wouldn't be able to use it with our stable/supported libraries....

Verified fix: - [ ] decrease default batch size to 10 (~5 MiB for 10 full Advantage-size problems) - [ ] ideally, limit batch size by payload bytes (default to...

Until dwave-tabu/dwave-neal are updated to return useful results when interrupted, intermediate (alternative) solution is #101.

Hi, @29rou! Thanks for bringing our attention to this issue. My understanding is this is an actual issue only on a "FIPS-compilant" system with a non-standard Python build. Is that...

Sure, feel free to monkey-patch it locally. I'm just reluctant to make that change in the cloud-client.

Hi @AjayKumar-LVLS, 1. Yes, D-Wave Hybrid allows purely classical workflows. Several of the [examples in the repo](https://github.com/dwavesystems/dwave-hybrid/tree/master/examples) are classical only. 2. Yes, check the following examples: dialectic-search, parallel-tempering or population-annealing....

I agree it would be nice to have consistency across platforms. However, config paths are currently chosen in a way that should be the most natural on each platform. Also,...