Julien Dubiel

If you are using cloudflare, disable the "Rocket Loader" Speed option.

It looks like it works fine: ``` [root@gpu1 ~]# awk '{u=$2+$4; t=$2+$4+$5; if (NR==1){u1=u; t1=t;} else print ($2+$4-u1) * 100 / (t-t1); }'

Here it is: :) ``` [root@gpu1 ~]# nvidia-smi --query-gpu=name,fan.speed,utilization.gpu --format=csv,nounits name, fan.speed [%], utilization.gpu [%] Tesla P40, [Not Supported], 0 Tesla P40, [Not Supported], 0 Tesla P40, [Not Supported], 100...

Yep! It indeed works better :tada: But gpu2 don't : ``` { "gpu1": { "GPU": { "GPU-373e1376-924e-2bfc-1f62-064eaaccd10d": { "index": 3, "metrics": { "fan_speed": { "unit": "%", "value": null }, "mem_free":...

This issue is linked to this one : https://github.com/MIT-LCP/wfdb-python/issues/73 You should be able to open the file on any filesystem (local, remote S3, HDFS...) and read the contents of it...

- [ ] Handle slow_bpm_gap - [x] Add docstring to correct_peaks

Why is this function needed? It is if you want to get a peak position exactly on the R peak. Indeed, algorithms such as GQRS and Pan&Tompkins do not return...

This function also uses the find_peaks function from wfdb.processing.peaks that detect what I called "hard" and "soft" peaks. Those are really signal peaks, not QRS peaks:  Soft peaks are...

I wanted to rename min_gap and max_gap to slow_bpm_gap and fast_bpm_gapas it is more explicit. (min_gap->slow_bpm_gap & max_gap->fast_bpm_gap) The thing about slow_bpm_gap is that it is physiologically **possible** to see...

It not only shifts to local maxima, it also delete one peak when two are too close from each other. Spliting the concepts is a good idea! Yes sure ;)