Examples of Solver

choco.kernel.solver.Solver
com.cloudera.oryx.common.math.Solver
Encapsulates a {@link DecompositionSolver} from Commons Math.
com.hpctoday.fada.integersolver.Solver
driftingdroids.model.Solver
hu.u_szeged.nbo.res_alloc.main.Solver
jinngine.physics.solver.Solver
Solver for a non-linear complimentarity problem (NCP).
The contact force problem generated by Jinngine is ultimately a non-linear complementarity problem. In fact, when disregarding the coupling between friction forces and normal forces, the problem becomes a mixed linear complimentarity problem, or MLCP for short. The MLCP is on the form
Given the matrix A, the vector b, and the solution limit vectors l and u, Find x, such that
w = A x + b
where
if x_i=u_i then w_i<=0
if x_i in (l_i,u_i) then w_i = 0
if x_i=l_i then w_i>=0
A is the matrix J M^(-1) J^T which describes constraint relations, and b is the vector of desired change in velocities.
This problem class can model normal-component contact forces and various joint types. The reason why this becomes a NCP when contact friction is introduced, is that we allow u and l to depend on the magnitude of some x_i vales, namely the x_i's that represent normal contact forces, so
l_i = -|mu * x_j| and u_i = |mu*x_j|
where i is the index of a friction constraint, j is the index of the normal force, and mu is the friction coefficient. constraint to which the friction constraint is coupled. This coupling is done to model an approximation to Coulomb's law of friction.
kodkod.engine.Solver
A computational engine for solving relational formulae. A {@link kodkod.ast.Formula formula} is solved with respect to given {@link kodkod.instance.Bounds bounds} and {@link kodkod.engine.config.Options options}. @specfield options: Options @author Emina Torlak
net.myrrix.common.math.Solver
A solver for the system Ax = b, where A is an n x n matrix and x and b are n-element vectors. An implementation of this class encapsulates a solver which implicitly contains A. @author Sean Owen @since 1.0
net.sf.cpsolver.ifs.solver.Solver
net.sf.javailp.Solver
org.boblycat.abbots.Solver
org.drools.planner.core.Solver
A Solver solves planning problems.
Most methods are not thread-safe and should be called from the same thread.
org.drools.solver.core.Solver
org.jakstab.solver.Solver
A generic interface to SMT solvers, represents a logical context that can be updated with assertions and checked for satisfiability. @author Johannes Kinder
org.moxie.Solver
Solves transitive dependency chains, scoped classpaths, and linked projects.
Solver employs Maven 2 transitive dependency resolution based on "nearness" and declaration order using a 2-pass scheme. Pass one recursively retrieves all referenced POMs. Pass two analyzes each retrieved POM for a particular solving scope and builds a flat dependency list with ring scores.
Ring-0 is the project itself. Ring-1 are direct named dependencies. Ring > 1 are solved transitive dependencies. Dependency conflicts are resolved by choosing the dependency in the lowest ring OR the first declaration, if the rings are equal.
Linked projects are treated as source folders of the build project. Therefore the dependencies linked projects are assimilated into the build project's dependencies.
org.optaplanner.core.api.solver.Solver
A Solver solves a planning problem. Clients usually call {@link #solve(Solution)} and then {@link #getBestSolution()}.
These methods are not thread-safe and should be called from the same thread, except for the methods that are explicitly marked as thread-safe. Note that despite that {@link #solve(Solution)} is not thread-safe for clients of this class,that method is free to do multi-threading inside itself.
Build by a {@link SolverFactory}.
solver.Solver
The Solver is the header component of Constraint Programming. It embeds the list of Variable (and their Domain), the Constraint's network, and a IPropagationEngine to pilot the propagation.
Solver includes a AbstractSearchLoop to guide the search loop: apply decisions and propagate, run backups and rollbacks and store solutions. @author Xavier Lorca @author Charles Prud'homme @version 0.01, june 2010 @see solver.variables.Variable @see solver.constraints.Constraint @since 0.01
solvers.Solver
class to represent a solver * @author Hélène Collavizza @date June 2008

Examples of solver.Solver


    IntVar[] letters;


    @Override
    public void createSolver() {
        solver = new Solver("Alpha");
    }

View Full Code Here

Examples of solver.Solver


    IntVar[] vars;


    @Override
    public void createSolver() {
        solver = new Solver("AbsoluteEvaluation");
    }

View Full Code Here

Examples of solver.Solver

    BoolVar[] viols;
    IntVar violations;


    @Override
    public void createSolver() {
        solver = new Solver("Photo");
    }

View Full Code Here

Examples of solver.Solver

    IntVar objective;




    @Override
    public void createSolver() {
        solver = new Solver("Air plane landing");
    }

View Full Code Here

Examples of solver.Solver

     */
    public static Constraint mod(IntVar X, IntVar Y, IntVar Z) {
        int xl = Math.abs(X.getLB());
        int xu = Math.abs(X.getUB());
        int b = Math.max(xl, xu);
        Solver solver = X.getSolver();
        IntVar t1 = VariableFactory.bounded(StringUtils.randomName(), -b, b, solver);
        IntVar t2 = VariableFactory.bounded(StringUtils.randomName(), -b, b, solver);
        Constraint div = IntConstraintFactory.eucl_div(X, Y, t1);
        Constraint tim = IntConstraintFactory.times(t1, Y, t2);
        Constraint sum = IntConstraintFactory.sum(new IntVar[]{Z, t2}, X);

View Full Code Here

Examples of solvers.Solver

  
  /** A term CSP with a name and a solver*/ 
  public TermCSP(String n,int solverType,int f) {
    name = n;
    status = new SolverStatus(n);
    s = new Solver(solverType);
    setConstraintBlock(s);
    setIntVarBlock(s,f);
  }

View Full Code Here

0 1 2 3 4 5 6

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.