JOpt.Solve: The Engine Gets a Face

For years JOpt has been an engine: vehicles, stops, time windows, constraints in, an optimized solution out. Powerful, headless, and about as visual as a stack trace.

JOpt.Solve is the front end it deserves: the first high-end GUI built for JOpt natively, designed to support every feature the engine offers. Not a wrapper around a subset. The whole thing.

The JOpt.Solve interface: an optimized two-vehicle route across Hamburg on a map, with a stop list and a Gantt schedule. — An early look at JOpt.Solve: map, stops, and schedule in one place.

Built for production, not just demos. Model a fleet directly in the interface, or pull data straight from the APIs already in use. Load a scenario, optimize, and watch the routes resolve on the map: inspect the geometry, read the schedule, see where the cost went.

No date yet.