- Rating
- 1
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
For ECG compression, it is often difficult to decide the optimal compression ratio due to different compressibility of ECG signal. Hence, many works choose a conservative compression ratio in order to ensure signal fidelity for downstream tasks, which causes missing opportunities to achieve high compression ratio.
This paper’s main idea is that let the source to compress the signal as aggressive as possible, then decompress the signal and compare with it with the ground true signal at the source. If the decompressed signal meets beat detection criteria, the compressed signal can be sent, otherwise, the signal will be re-compressed with less aggressive compression ratio. The paper uses beat detection as a way of verification.
Critical strengths
None
Critical weaknesses
- The motivation, novelty, and achievements are overstated.
- Verification using “all beat preserved” is over simplified as a way for fidelity guarantee. ECG compression also requires clinically relevant waveform features are preserved.
- The evaluation protocol is not clearly presented. This causes concern if the comparison with baseline is fair.
- The memory requirements of the proposed encoder-side verification pipeline are insufficiently characterized.
- The battery-life estimation is not built on a sufficiently accurate energy model, hence, such analytical results are not sufficient for a top-conference like ICLR. I would suggest the authors to develop a prototype with a concrete hardware.
- It is not clear how much energy is used for performing compression, decompression, verification, and transmission.
Questions for authors
-
Does compression preserve clinically relevant waveform features?
-
Can the authors show how much energy is used for performing compression, decompression, verification, and transmission? As some decompressed signal cannot meet detection criteria, and it requires re-compression, how many signals on average require retries?
-
What is the runtime memory footprint of the compressor, compression, decompression, verification? What is the peak RAM and processing latency? In particular, for the worst cases that requires retries.