Papers › Building a Framework for Predictive Science

Building a Framework for Predictive Science

6 Feb 2012arXiv:1202.1056links table onlyarchive 2025-07-28

Michael M. McKerns, Leif Strand, Tim Sullivan, Alta Fang, Michael A. G. Aivazis

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.

Key questions that scientists and engineers typically want to address can be formulated in terms of predictive science. Questions such as: "How well does my computational model represent reality?", "What are the most important parameters in the problem?", and "What is the best next experiment to perform?" are fundamental in solving scientific problems. Mystic is a framework for massively-parallel optimization and rigorous sensitivity analysis that enables these motivating questions to be addressed quantitatively as global optimization problems. Often realistic physics, engineering, and materials models may have hundreds of input parameters, hundreds of constraints, and may require execution times of seconds or longer. In more extreme cases, realistic models may be multi-scale, and require the use of high-performance computing clusters for their evaluation. Predictive calculations, formulated as a global optimization over a potential surface in design parameter space, may require an already prohibitively large simulation to be performed hundreds, if not thousands, of times. The need to prepare, schedule, and monitor thousands of model evaluations, and dynamically explore and analyze results, is a challenging problem that requires a software infrastructure capable of distributing and managing computations on large-scale heterogeneous resources. In this paper, we present the design behind an optimization framework, and also a framework for heterogeneous computing, that when utilized together, can make computationally intractable sensitivity and optimization problems much more tractable.

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 23 code samples harvested from 3 repositories linked to this paper: 21 ran (of which 0 constructed an object rather than computing a result; 21 with no instrument failure: 0 honoured, 1 violated, 20 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 23 samples from 3 repositories, 21 ran (21 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-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

14 repositories listed; official and paper-mentioned ones first.

avitabayan/dill-master mentioned on GitHubNOASSERTIONSyntology: not harvested report
lilys01/woltka-multiprocessing mentioned on GitHubSyntology: not harvested report
seung-lab/kimimaro mentioned on GitHubGPL-3.0Syntology: not harvested report
seungbin79/pathos mentioned on GitHubNOASSERTIONSyntology: not harvested report
uqfoundation/dill mentioned on GitHubNOASSERTIONSyntology: not harvested report
uqfoundation/klepto mentioned on GitHubNOASSERTIONSyntology: not harvested report
uqfoundation/multiprocess mentioned on GitHubNOASSERTIONSyntology: not harvested report
uqfoundation/mystic mentioned on GitHubSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
uqfoundation/pathos mentioned on GitHubNOASSERTIONSyntology: not harvested report
uqfoundation/pox mentioned on GitHubNOASSERTIONSyntology: not harvested report
uqfoundation/ppft mentioned on GitHubNOASSERTIONSyntology: not harvested report
uqfoundation/pyina mentioned on GitHubNOASSERTIONSyntology: not harvested report
vdods/heisenberg mentioned on GitHubMITSyntology: 9 samples, 9 ran (0 instrument-failed) · 0 unverified report
vdods/vorpy mentioned on GitHubpytorchMITSyntology: 13 samples, 11 ran (0 instrument-failed) · 2 unverified 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

23 samples harvested: 21 ran (of which 0 constructed an object rather than computing a result; 21 with no instrument failure: 0 honoured, 1 violated, 20 with no contract checked; 0 where Syntology's instrument failed) · 2 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.

1ran · violated contract
20ran
2unverified

Licence: 1 of the 23 samples is 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; 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.

uqfoundation/mystic community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
objective in 14 papers examples2/constrained_scipy.py ran · violated contract fingerprinted licence not identified · pointer only · 621cc5bb1ecdb5d1 · report fixture: signature x:Tensor/1/float · returned Tensor · level recorded 2026-09-22
vdods/heisenberg community (archive-listed) 9 samples, 9 ran (0 instrument-failed) · 0 unverified
csv_as_ndarray heisenberg/util.py ran MIT (permissive) · 1c135cea54770762 · report fixture: signature string:str/0/str, dtype:callable/0/? · returned ndarray · level recorded 2026-09-26
hamiltonian attic/library/heisenberg_dynamics.py ran fingerprinted MIT (permissive) · d0e2fb0b867a239c · report fixture: signature X:Tensor/1/float · returned Tensor · level recorded 2026-09-26
hamiltonian_vector_field attic/library/heisenberg_dynamics.py ran fingerprinted MIT (permissive) · de0e9a6c7e0f92c8 · report fixture: signature X:ndarray/1/float, t:float/0/float · returned ndarray · level recorded 2026-09-26
heisenberg_dynamics_context__embedding_1_0 lambdified_cache/heisenberg_dynamics_context__embedding_1_0.py ran fingerprinted MIT (permissive) · 93d7dc17151046ff · report fixture: signature X:ndarray/1/float · returned ndarray · level recorded 2026-09-26
heisenberg_dynamics_context__embedding_1_1 lambdified_cache/heisenberg_dynamics_context__embedding_1_1.py ran fingerprinted MIT (permissive) · 60ae50961fbe9267 · report fixture: signature X:ndarray/1/float · returned ndarray · level recorded 2026-09-26
heisenberg_dynamics_context__embedding_2_0 lambdified_cache/heisenberg_dynamics_context__embedding_2_0.py ran fingerprinted MIT (permissive) · ca1643492eaa417c · report fixture: signature X:ndarray/1/float · returned ndarray · level recorded 2026-09-26
heisenberg_dynamics_context__embedding_2_1 lambdified_cache/heisenberg_dynamics_context__embedding_2_1.py ran fingerprinted MIT (permissive) · fcf09d70696222db · report fixture: signature X:ndarray/1/float · returned ndarray · level recorded 2026-09-26
pop_brackets_off_of heisenberg/util.py ran MIT (permissive) · 009088ea0d602631 · report fixture: signature string:str/0/str · returned str · level recorded 2026-09-26
random_embedding2_point heisenberg/util.py ran MIT (permissive) · ae238d4fff59e4aa · report fixture: signature rng:RandomState/0/? · returned ndarray · level recorded 2026-09-26
vdods/vorpy community (archive-listed) 13 samples, 11 ran (0 instrument-failed) · 2 unverified
index_map_inverse vorpy/index_map.py ran MIT (permissive) · db4b3e16f9fcba46 · report fixture: signature index_map_v:ndarray/1/int, index_count:int/0/int · returned ndarray · level recorded 2026-09-26
is_nondecreasing_sequence vorpy/index_map.py ran fingerprinted MIT (permissive) · 624b7ae3fa81dc0d · report fixture: signature seq:list/1/int · returned bool · level recorded 2026-09-26
is_shape vorpy/tensor.py ran fingerprinted MIT (permissive) · e716c46533206f3b · report fixture: signature tup:tuple/1/int · returned bool · level recorded 2026-09-26
is_subsequence_of_nondecreasing_sequence vorpy/index_map.py ran MIT (permissive) · 5d40b8b4fe617dbd · report fixture: signature subseq:list/1/int, seq:list/1/int · returned bool · level recorded 2026-09-26
multiindex_iterator vorpy/symbolic.py ran MIT (permissive) · 89ce97793aebab44 · report fixture: signature shape:tuple/1/int, melt_1_tuple:bool/0/bool · returned product · level recorded 2026-09-26
order_of_shape vorpy/tensor.py ran MIT (permissive) · afed75e84204d77c · report fixture: signature sh:tuple/1/empty · returned int · level recorded 2026-09-26
prefixed_symbolic_tensor vorpy/experimental/coordinates.py ran MIT (permissive) · 7fd7f3e024b88362 · report fixture: signature prefix:str/0/str, symbol__t:ndarray/2/object · returned ndarray · level recorded 2026-09-26
shape in 15 papers vorpy/tensor.py ran MIT (permissive) · 962f703d7a53bdd9 · report fixture: signature tn:ndarray/3/int · returned tuple · level recorded 2026-09-26
simplified vorpy/experimental/coordinates.py ran MIT (permissive) · 2042cfb3e3d52015 · report fixture: signature arg:ndarray/2/object, preserve_shape:bool/0/bool · returned ndarray · level recorded 2026-09-26
tensor in 8 papers vorpy/symbolic.py ran MIT (permissive) · 995101d37cdc8bb5 · report fixture: signature name:str/0/str, shape:tuple/1/int · returned ndarray · level recorded 2026-09-26
variable in 12 papers vorpy/symbolic.py ran MIT (permissive) · df5dbaf5fee7d5c4 · report fixture: signature name:str/0/str · returned Symbol · level recorded 2026-09-26
apply_along_axes vorpy/apply_along_axes.py unverified MIT (permissive) · 3a51985cf6ab2abf · report
substitution vorpy/experimental/coordinates.py unverified MIT (permissive) · 44b2e3b39c7acb7c · 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