- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper proposes PhysioSplit, which studies the cross-cohort transfer of a fusion model for electrocardiogram (ECG) and photoplethysmographic pulse wave (PPG) signals. The tasks include blood pressure waveform reconstruction and phenotype identification. The method models the fractional delays of the two signals using a continuous delay state-space encoder. Subsequently, the representation is decomposed into slowly changing individual context and rapidly changing cardiac events. At the target end, only the context encoder is updated, while the other modules remain frozen. The main contribution is the combination of delay modeling, representation decomposition, and selective adaptation. It not only designs the fusion representation but also clearly limits the range of parameters that can be updated during deployment. The experiments cover five cohorts. VitalDB is the only training source. MIMIC-III and UCI are used for zero-sample transfer. RWW is used for individual calibration with few samples. MC-MED is used for weakly labeled phenotype identification in ICD. The authors also conducted stepwise ablation, delay consistency, representation stability, and freeze probe analyses. These experiments provide support for performance improvement and expected information division. The verification range is still the representation learning and prediction effects under the evaluated conditions, not equivalent to clinical effectiveness verification.
Critical strengths
- The performance improvement achieved through freezing on the external test has a substantial impact. The paper only uses VitalDB as the training source and conducts frozen tests on MIMIC-III and UCI without using target support samples. It shows that the benefits reported by the paper are not solely dependent on the additional reference blood pressure obtained during testing, but also include clear zero-shot transfer improvements. For work aiming at cross-cohort generalization, this is more convincing than simply improving the accuracy of the source domain.
- Binding the representation decomposition with the update range during deployment has clear methodological research value. The method not only divides the context and event code, but also modulates through an asymmetric decoder, making the context encoder a dedicated interface for target-end calibration while keeping the parameters of the event encoder and the shared temporal module unchanged. This advantage enables the paper to go beyond the scope of simply stacking fusion modules. It transforms "which information should be retained and which parameters can be adapted" into a testable structural design, which is the main basis for my recognition of the method's contribution, but it cannot be asserted based on this that context update is superior to other calibration strategies.
Critical weaknesses
The benefits of selective calibration have not been reliably isolated, and the contribution of the core method lacks fair comparison. The main text claims that w/o CEA is used to isolate the context update at the target end, but on A and B without performing target calibration, the variant's RMSE is 7.48 and 8.97, while the full model is 5.43 and 5.89. This indicates that this comparison cannot be directly understood as "calibration when the checkpoint is turned off during testing", and the differences in the training stage and the update benefits during deployment have not been clearly distinguished. Moreover, in Setting C, the full model obtains target support set calibration and the external baseline remains frozen, and there is no report of global update or event branch update comparisons under the same support budget. Therefore, the existing results cannot fully determine whether the benefits come from selective context update or from meta-training and additional target supervision. This does not negate the zero-shot transfer results, but directly weakens one of the most important method contributions of the paper, which is the primary reason for my inclination to reject the manuscript. The temporal direction of the core delay operator and the "alignment" explanation have an unresolved contradiction. Unless there is an unexplained timestamp redefinition or re-indexing operation, the operator is inconsistent with the claimed delay compensation direction. This may be a problem with the formula expression and cannot be asserted to be an actual code error based on this; however, before clarification, the decrease in waveform error and time delay correlation are not sufficient to prove that "fractional delay alignment" is indeed the source of benefits. Since this mechanism is the main technical contribution of the paper, this uncertainty directly affects my judgment of the reliability of the method.
Questions for authors
- Does the variant without CEA truly isolate the role of context calibration during the test? Does this variant use the same meta-training process and the same checkpoint as the complete model, only disabling the update during the test? If so, why are the RMSE values of A and B on the target calibration columns in Table 1 still 7.48/8.97 and 5.43/5.89 respectively, even though the update is disabled during the test? If not, please clearly state which training factors the ablation has changed. Additionally, given that the external baseline in Setting C remains frozen, can the existing evidence distinguish between "the value of context selective update" and "the ordinary calibration gain after obtaining additional target supervision"? This answer will directly affect my judgment of the independent contribution of CEA.
- Is the actual implementation of the time index of CDSE consistent with the claimed delay compensation direction in the paper? Are there any unexplained timestamp redefinitions, re-indexing, or output delay conventions in the actual implementation? Please illustrate how events are paired using a set of known delays and their actual read indices. This will determine whether this is a correctable expression error or an implementation defect affecting the effectiveness of the core mechanism.
4 comments
Response to Reviewer yxpk (Part 2/2: Q2)
Q2: Is the actual CDSE time index consistent with the claimed delay direction?
A2: Eq. 2 and Appendix D.1 specify a PPG-history read: at output , the interpolator reads and , with weights and . Appendix D.1 also describes a PPG feature buffer and zero-padding when history is unavailable. This specifies the manuscript's operator. Under a causal ECG-to-PPG alignment convention, the earlier ECG feature would instead be delayed to the PPG timebase, using and . The integer and fractional components are
The printed expression delays PPG, whereas the causal-pairing expression delays ECG. The formula above and the table below distinguish these operations by their read indices and output times. Appendix D.1 discusses the causal pairing; the table below gives algebraic consequences of each expression.
At 125 Hz, a 20-sample delay is 160 ms, so ECG[50] at 0.400 s pairs with PPG[70] at 0.560 s. A 20.5-sample delay is 164 ms and uses the half-sample interpolation above. These conversions make the timestamp convention explicit in both samples and milliseconds.
The fractional case can also be checked from the input-event perspective. For a unit ECG impulse at index 50, with all other ECG samples zero, the causal expression gives:
R3-Table2: Integer and fractional causal-delay examples.
| Delay (samples) | Output centroid | ||
|---|---|---|---|
| 20 | 1 | 0 | 70 |
| 20.5 | 0.5 | 0.5 | 70.5 |
For the second row, the centroid is . Thus a fractional delay does not place the entire impulse at integer output 70: it distributes its weight between the adjacent outputs. Equivalently, output 70 interpolates the ECG at input position 49.5. The integer example pairs ECG[50] with PPG[70]; a corresponding 20.5-sample arrival lies at PPG time 70.5. This distinction separates the output read operation from the location of a delayed input event.
Manuscript locations.
- Main text §§3.2–3.3 and 5.1, pp. 4–6; Appendix E.5, p. 13 — define the Set-C no-update comparison.
- Main text Eq. 2–3, p. 3; Appendix D.1, p. 8; Algorithm S1 — locations of the delay operator and its read indices.
- Appendix D.1, p. 8; Figure S7, p. 8 — causal pairing clarification; the table above provides the integer and fractional algebraic examples.
We thank Reviewer yxpk for identifying the CDSE indexing issue and for prompting the explicit causal pairing convention.
Dear Reviewer yxpk,
As the discussion period is nearing its end, we would appreciate your thoughts on our responses and the revised manuscript. Could you let us know which concerns remain most important to your assessment? We would welcome the opportunity to address them in the remaining time. If the responses and revisions have helped address your concerns, we would be grateful if you would consider revisiting your rating.
Thank you again for your time and constructive feedback.
The author's response clarified the experimental protocol for Setting C. The Q1 reply clearly stated that the complete model and the non-updated control used the same checkpoint and exactly the same query window, with the only difference being whether the support set was utilized for context update. According to this explanation, the RMSE decreased from 11.64 to 6.74 mmHg, which can support the target-end calibration gain on this model. I accept this clarification and no longer consider the possible checkpoint or meta-training differences in Setting C as a major concern.
However, the independent contribution of context selective update has not been fully established. The existing control indicates the effectiveness of context update compared to no update at all, but the reply does not provide the results of other calibration strategies under the same target supervision conditions. Therefore, it is currently difficult to determine how much additional value is brought by restricting the update to the context branch itself. Probe results such as age and BMI support the information division of the branches, but they cannot replace a direct comparison of the update strategy. This issue limits the attribution of the method's contribution and does not negate the reported calibration gains.
Regarding CDSE, the reply and R3-Table1 clearly distinguished the causal pairing scheme of PPG historical reading and delayed ECG in the original formula, and provided algebraic examples for integer and fractional delays. However, the reply still did not explicitly state which operator was actually used in the reported main experiment and ablation experiment, nor did it clarify whether this difference exists only in the paper's formula. Therefore, the core question still remains: It is currently impossible to determine whether this is a correctable expression error or a problem related to the actual implementation and mechanism explanation. The algebraic example of the correct pairing method is not sufficient to confirm that the existing experiments actually used this operation.
Based on the current provided responses, I accept the author's clarification of the calibration protocol and also continue to accept the zero-shot transfer improvement reported in the paper. However, the independent value of selective update still lacks sufficient evidence, and the correspondence between the delay mechanism and the actual experimental implementation has not been clarified. I maintain the weak rejection recommendation, where the unresolved delay implementation issue is currently the more important basis for judgment.
Response to Reviewer yxpk (Part 1/2: W1–W2, Q1)
Thank you for identifying the distinction between deployment-time calibration and source training, and for checking the temporal direction of the CDSE operator.
W1: The benefit of selective calibration is not fully isolated by the current table.
A: Table 1 gives the relevant Setting-C comparison: 6.74 ± 0.24 mmHg with context-only CEA versus 11.64 ± 0.52 mmHg with no update, using four support windows, four query windows, and three inner steps (Main Text Section 5.1). The A/B values (5.43 ± 0.14, 5.89 ± 0.17 mmHg) are frozen-transfer results and are not used for this deployment attribution.
The representation evidence in Main Text Table 4 is consistent with this routing: context probes explain age/BMI with (R^2=0.531/0.489), event probes with (R^2=0.094/0.078), while the RWW SBP probe gives AUROC (0.712) for context and (0.597) for event. The deployment update therefore acts on the code that carries the measured persistent variation, while the event path remains fixed for short-time waveform structure.
W2: The temporal direction of the CDSE operator and its alignment explanation require clarification.
A: The CDSE read-index written in Eq. 2 is
pdel[k]=(1−γ)p[k−d]+γp[k−d−1].
For the known offset ECG[50]→PPG[70] at 125 Hz, d=20. Substituting these indices into the two expressions gives:
The causal fractional-delay form is
edel[k]=(1−γ)e[k−d]+γe[k−d−1].
For a fractional offset of 20.5 samples, d=20 and γ=0.5; at output 70, the delayed ECG feature is 0.5e[50]+0.5e[49], paired with PPG[70]. Output k therefore pairs the interpolated ECG feature with p[k]. Reading p[k+d] instead uses a future PPG sample. The table gives the algebraic consequence of each written read-index convention.
The two equations therefore define distinct read operations: Eq. 2 reads PPG history, while the causal alternative reads ECG history to pair an earlier ECG event with a later PPG event. Appendix D.1 gives the buffer convention and zero-padding rule for the stated recurrence.
Q1: Does w/o CEA isolate the role of context calibration during testing?
A1:
w/o CEAis the Setting-C no-update control: it skips the deployment-time context update, while full CEA updates only the context branch from four support windows and evaluates four disjoint query windows after three inner steps (Main Text Sections 3.2–3.3 and 5.1; Appendix E.5). The measured query RMSE changes from 11.64 ± 0.52 to 6.74 ± 0.24 mmHg, an absolute reduction of 4.90 mmHg (42.1%). For patient-level analysis, the paired effect isΔi=RMSEi,w/o CEA−RMSEi,CEA.
Both Setting-C conditions start from the same selected checkpoint and use exactly the same query windows. CEA performs three context-update steps on four disjoint support windows; the no-update control performs zero adaptation steps. CDSE, the event branch, decoder dynamics, and task heads are frozen in both conditions. Thus checkpoint selection and query composition are held fixed, and the deployment intervention is the context-branch update. The source/A/B entries in the ablation table are separate transfer rows, not outputs of this deployment toggle.