Papers › Is checking for sequential positivity violations getting you down? Try sPoRT!
Is checking for sequential positivity violations getting you down? Try sPoRT!
Arthur Chatton, Michael Schomaker, Miguel-Angel Luque-Fernandez, Robert W. Platt, Mireille E. Schnitzer
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
Background: Sequential positivity is often a necessary assumption for drawing causal inferences, such as through marginal structural modeling. Unfortunately, verification of this assumption can be challenging because it usually relies on multiple parametric propensity score models, unlikely all correctly specified. Therefore, we propose a new algorithm, called sequential Positivity Regression Tree (sPoRT), to overcome this issue and identify the subgroups found to be violating this assumption, allowing for insights about the nature of the violations and potential solutions. Methods: We present different versions of sPoRT based on either stratifying or pooling over time under static or dynamic treatment strategies. This methodological development was motivated by a real-life application of the impact of the timing of initiation of HIV treatment with and without smoothing over time, which we also use to demonstrate the method. Results: The illustration of sPoRT demonstrates its easy use and the interpretability of the results for applied epidemiologists. Furthermore, an R notebook showing how to use sPoRT in practice is available at github.com/ArthurChatton/sPoRT-notebook. Conclusions: The sPoRT algorithm provides interpretable subgroups violating the sequential positivity violation, allowing patterns and trends in the confounders to be easily identified. We finally provided practical implications and recommendations when positivity violations are identified.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections