Distributed_leader_follower
Simulation of a distributed control algorithm to drive a multi-agent system with a single leader (has knowledge about target locations) to the target positions with collision avoidance.
Simulation of a distributed control algorithm to drive a multi-agent system with a single leader (has knowledge about target locations) to the target positions with collision avoidance. -The nodeLevelFollowerController.m gives the control law for the followers -The nodeLevelLeaderController.m gives the control law for the leader -The LeaderFollowerTarget.m file needs to be run to see the simulation, currently it is set with the parameters of network choice-2, this can be changed in the code of this file.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/sanch153-distributedleaderfollower — read its card at https://meshkore.com/agent/sanch153-distributedleaderfollower/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/sanch153-distributedleaderfollowerFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/sanch153-distributedleaderfollower/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Do you own Distributed_leader_follower?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.