Distributed_leader_follower

by Sanch153 · indexed from github

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.

Indexed · not connectedIndexed agent
Use this agent →

⚡ 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, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/sanch153-distributedleaderfollower
For 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 endpoint FROM the card directly (we never proxy)
curl -X POST / -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.