Black-box optimization for expensive evaluations

Run fewer expensive trials. Keep the evaluator in your environment.

Looptimum is a lightweight controller that uses previous results to select the next bounded trial, replacing broad sweeps and manual tuning with a sequential, resumable optimization loop.

suggest evaluate ingest

How the loop runs

Looptimum chooses the next candidate. You run it.

The controller maintains the optimization state and suggests what to try next. Your existing script, cluster, solver, experiment, or workflow executes the trial and returns a result or declared failure.

  1. 01

    Suggest

    Looptimum uses the campaign's completed results to select the next bounded candidate instead of scheduling a broad sweep.

  2. 02

    Evaluate

    Your evaluator runs where it already lives: cluster jobs, scripts, CI runners, solver hosts, or lab workflows.

  3. 03

    Ingest

    The result—or a declared failure—is recorded in local files so the campaign can resume after interruptions and preserve an auditable decision trail.

Campaign evidence examples

Bar chart comparing solver wall clock for the fine reference and validated coarse mesh

Validated engineering campaign

Fine-to-coarse simulation mesh search

A bounded engineering campaign paired its selected candidate with downstream solver and mesh-independence validation.

Read the case study
Normalized held-out loss across ten evaluations in an anonymized GPT training campaign

Anonymized ML campaign

Guided GPT training-recipe search

Ten bounded evaluations tested four generic recipe controls while the training evaluator remained externally owned.

Read the case study

Use cases

When Looptimum is useful.

The best early engagements have a real evaluation bottleneck, a bounded set of decision variables, and a team that can already run the underlying process inside its own environment.

Simulation and engineering

Mesh controls, solver tolerances, calibration knobs, and workflow parameters where every run costs serious compute or analyst time.

Infrastructure tuning

Concurrency, retry policy, memory limits, thread counts, cache TTLs, and resource controls with measurable cost or latency impact.

ML and evaluation loops

Training recipe knobs, evaluation thresholds, batch sizes, and runtime controls when experiments are slow and failures are expensive.

Operational process tuning

Lab workflows, ETL processes, and production runbooks where throughput, quality, and cost need to be balanced under guardrails.

Earlier-stage work

Some optimization problems begin before there is a stable loop.

The Looptimum Advanced Research Consortium works with ambitious, early technical projects where efficiency, optimization, or computational feasibility may shape the architecture and the path to implementation.

If you already have an expensive evaluator, core Looptimum may fit. If the system and its evidence pathway are still being designed, explore LARC.

Read about LARC

Continue

Is this a fit?

Start with the cost of one evaluation, the knobs you can bound, and the result you need to improve.

Portrait of David Y.

Meet the team

David Y.

Founder, Developer

David Y. is the founder and lead developer of Looptimum, where he works at the intersection of optimization, machine learning, scientific computing, and complex systems engineering. His technical work spans computational hemodynamics and medical-device research, physics- and data-informed modeling, Bayesian optimization, custom machine-learning pipelines, and applied language-model development. He has built and maintained research software for simulation, statistical analysis, model calibration, and experimental workflows, with a particular focus on problems where computational efficiency, model fidelity, and practical implementation are tightly coupled. Through Looptimum, he develops optimization-driven tools and research workflows intended to turn technically difficult, computationally constrained problems into tractable engineering and scientific systems.

View GitHub profile