Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WorkerSolver: Add API for using a custom worker #48

Open
gkjohnson opened this issue Oct 27, 2020 · 1 comment
Open

WorkerSolver: Add API for using a custom worker #48

gkjohnson opened this issue Oct 27, 2020 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@gkjohnson
Copy link
Owner

Something like an encapsulated class that can be instantiated in the worker that can listen to messages so users can write custom logic that listens to and modifies worker state manually.

class RemoteWorkerSolver extends Solver {

    consumeMessage( event );
    onDispatchMessage( event );

}
class WorkerSolver {

    constructor( roots, worker = new Worker( './WorkerSolver.worker.js' ) );

}

WorkerSolverRemote should also be able to use non synced joints so some joints can only live in the worker.

Open Questions

  • Should the solver automatically solve indefinitely until a non timeout result is hit? Or should it be up to the user worker to call solve?
@gkjohnson gkjohnson added the enhancement New feature or request label Oct 27, 2020
@gkjohnson gkjohnson modified the milestones: v0.0.3, v0.0.x Dec 29, 2020
@gkjohnson
Copy link
Owner Author

gkjohnson commented Dec 30, 2020

This may not exactly be needed. If required users can just pass the joint angles back to the main page to update something like the URDF model in the case they want to perform some kind of special solve in a Worker. A consistent and exposed way to serialize and deserialize the joint graph would be good, though. (Issue #66)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant