Papers › MAYONNAISE: a morphological components analysis pipeline for circumstellar disks and...
MAYONNAISE: a morphological components analysis pipeline for circumstellar disks and exoplanets imaging in the near infrared
Benoît Pairet, Faustine Cantalloube, Laurent Jacques
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.
Imaging circumstellar disks in the near-infrared provides unprecedented information about the formation and evolution of planetary systems. However, current post-processing techniques for high-contrast imaging using ground-based telescopes have a limited sensitivity to extended signals and their morphology is often plagued with strong morphological distortions. Moreover, it is challenging to disentangle planetary signals from the disk when the two components are close or intertwined. We propose a pipeline that is capable of detecting a wide variety of disks and preserving their shapes and flux distributions. By construction, our approach separates planets from disks. After analyzing the distortions induced by the current angular differential imaging (ADI) post-processing techniques, we establish a direct model of the different components constituting a temporal sequence of high-contrast images. In an inverse problem framework, we jointly estimate the starlight residuals and the potential extended sources and point sources hidden in the images, using low-complexity priors for each signal. To verify and estimate the performance of our approach, we tested it on VLT/SPHERE-IRDIS data, in which we injected synthetic disks and planets. We also applied our approach on observations containing real disks. Our technique makes it possible to detect disks from ADI datasets of a contrast above 3×10⁻⁶ with respect to the host star. As no specific shape of the disks is assumed, we are capable of extracting a wide diversity of disks, including face-on disks. The intensity distribution of the detected disk is accurately preserved and point sources are distinguished, even close to the disk.
In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2008.05170")
Code
Syntology Ran 5 of 5 code samples harvested from 3 repositories linked to this paper; 0 have no recorded run. Of those that ran: 1 ran · our draft was wrong; 4 ran · fixture could not drive it.
By repository: official repository: 1 sample from 1 repository, 1 ran; community (archive-listed): 4 samples from 2 repositories, 4 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
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
5 samples harvested; 5 ran; 0 honoured the contract we drafted; 0 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.
Licence: 5 of the 5 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from 3 repositories linked to this paper, official or community; each sample names its own and says which. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.
Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
d1654db15038f233 · report
0c6ad3aff620201c · report
6fc105432485399e · report
9fb372a42b87e6a5 · report
64ac3ab8776767a5 · report
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