LouDou
LouDou
Modify the .py file, add this after `self.core = Core()` `self.core.set_property("CPU", {"INFERENCE_NUM_THREADS": 8})` You can change `8` to be matching the number of cores in your system.
Yeah you're right, this maybe doesn't do exactly what I thought it did - but it looks the most likely parameter from the openvino docs that I could find (docs...
Same test on my laptop `Intel(R) Core(TM) i7-11800H @ 2.30GHz` (8C16T) `INFERENCE_NUM_THREADS: 1` = 15.11 s/it `INFERENCE_NUM_THREADS: 2` = 7.99 s/it `INFERENCE_NUM_THREADS: 3` = 5.84 s/it `INFERENCE_NUM_THREADS: 4` = 4.43...
Here's the full working PoC: https://github.com/LouDou/de-mm-poc ```bash de-mm-poc$ yarn de-mm-poc$ yarn start ``` ```bash $ curl -XPOST -H'Content-Type: application/json' -d'{}' http://localhost:3000/local/hello ```
Updated the UK band plan regions as per the colours used on the RSGB website: 
I've also included the bandplan update from https://github.com/csete/gqrx/pull/974 in the interest of avoiding a merge conflict. @francisuk1989
Final update I think here, adds a table of the visible band plan items - double click to set the rx parameters, just like bookmarks: 
I've noticed though that there are items in the bandplan.csv which are >9.98GHz - which gqrx doesn't seem to support? I'm not going to attempt to fix that, I assume...
I've also just seen that UK Ofcom publishes a spectrum map: http://static.ofcom.org.uk/static/spectrum/map.html And also the JSON data which drives it: http://static.ofcom.org.uk/static/spectrum/data/spectrumMapping.json It could be usable in this widget, except for...
Here's a preview of a 2nd band plan, using the ofcom data:  I'm not including in this PR because it's another level of substantial difference, and I'm interested in...