Papers › Fast and scalable Gaussian process modeling with applications to astronomical time series

Fast and scalable Gaussian process modeling with applications to astronomical time series

28 Mar 2017arXiv:1703.09710links table onlyarchive 2025-07-28

Daniel Foreman-Mackey, Eric Agol, Sivaram Ambikasaran, Ruth Angus

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.

The growing field of large-scale time domain astronomy requires methods for probabilistic data analysis that are computationally tractable, even with large datasets. Gaussian Processes are a popular class of models used for this purpose but, since the computational cost scales, in general, as the cube of the number of data points, their application has been limited to small datasets. In this paper, we present a novel method for Gaussian Process modeling in one-dimension where the computational requirements scale linearly with the size of the dataset. We demonstrate the method by applying it to simulated and real astronomical time series datasets. These demonstrations are examples of probabilistic inference of stellar rotation periods, asteroseismic oscillation spectra, and transiting planet parameters. The method exploits structure in the problem when the covariance function is expressed as a mixture of complex exponentials, without requiring evenly spaced observations or uniform noise. This form of covariance arises naturally when the process is a mixture of stochastically-driven damped harmonic oscillators -- providing a physical motivation for and interpretation of this choice -- but we also demonstrate that it can be a useful effective model in some other cases. We present a mathematical description of the method and compare it to existing scalable Gaussian Process methods. The method is fast and interpretable, with a range of potential applications within astronomical data analysis and beyond. We provide well-tested and documented open-source implementations of this method in C++, Python, and Julia.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 14 code samples harvested from 2 repositories linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 10 samples from 1 repository, 7 ran (7 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 4 samples from 1 repository, 1 ran (1 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-25 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

dfm/celerite officialmentioned in papermentioned on GitHubMITSyntology: 10 samples, 7 ran (0 instrument-failed) · 3 unverified report
dfm/celerite2 mentioned on GitHubjaxMITSyntology: 4 samples, 1 ran (0 instrument-failed) · 3 unverified report
exoplanet-dev/celerite2 mentioned on GitHubjaxMITSyntology: not harvested report

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

14 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

8ran
6unverified

Licence: 0 of the 14 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (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 are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. 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 six 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; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. 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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

dfm/celerite official repository 10 samples, 7 ran (0 instrument-failed) · 3 unverified
band_e paper/figures/matrix.py ran MIT (permissive) · 1cb463502f2fb2ea · report fixture: signature l:int/0/int, u:int/0/int, mat_full:ndarray/2/int · returned ndarray · level recorded 2026-09-25
benchmark in 19 papers celerite/timer.py ran MIT (permissive) · 89742dd28562c866 · report fixture: signature stmt:str/0/str, setup:str/0/str · returned float · level recorded 2026-09-25
get_figsize in 5 papers celerite/plot_setup.py ran fingerprinted MIT (permissive) · d286cc7c36eef825 · report fixture: signature rows:int/0/int, cols:int/0/int · returned tuple · level recorded 2026-09-25
lorentz_psd paper/figures/sho.py ran fingerprinted MIT (permissive) · d03bfd8ea027807c · report fixture: signature Q:float/0/float, x:ndarray/1/float · returned ndarray · level recorded 2026-09-25
rename in 5 papers paper/publish.py ran fingerprinted MIT (permissive) · 8a0c509170cc3245 · report fixture: signature fn:str/0/str · returned tuple · level recorded 2026-09-25
sho_acf paper/figures/sho.py ran fingerprinted MIT (permissive) · d760887b0c3739aa · report fixture: signature Q:float/0/float, tau:ndarray/1/float · returned ndarray · level recorded 2026-09-25
sho_psd paper/figures/sho.py ran fingerprinted MIT (permissive) · 318e4a66a868c0f3 · report fixture: signature Q:float/0/float, x:ndarray/1/float · returned ndarray · level recorded 2026-09-25
cpp_flag celerite/build.py unverified MIT (permissive) · 06632162048ffe78 · report
has_flag celerite/build.py unverified MIT (permissive) · 4831b0942e89543f · report
has_library celerite/build.py unverified MIT (permissive) · b8eff7fd0c0117a6 · report
dfm/celerite2 community (archive-listed) 4 samples, 1 ran (0 instrument-failed) · 3 unverified
allclose python/celerite2/testing.py ran MIT (permissive) · 31a82fde8c05f918 · report fixture: signature a:ndarray/2/float, b:ndarray/2/float · returned bool · level recorded 2026-09-26
factor python/celerite2/jax/ops.py unverified MIT (permissive) · 27a32807adc7aa37 · report
solve_lower python/celerite2/jax/ops.py unverified MIT (permissive) · 7da09b9ffb483935 · report
solve_upper python/celerite2/jax/ops.py unverified MIT (permissive) · 60b73af5b84ae6f8 · 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