CodingTrain / CodingTrain/Suggestion-Box

Kalman Filtering / SLAM

Ouverte
#930 0 commentaires 1 réaction 0 personnes assignées Voir sur GitHub
Langage dominant
Aucune donnée de langage
Étoiles
570
Forks
85
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

If you know a robot's initial position, and the instructions you are giving it, you should be able to predict its location at a later time. However, things can interfere with the robot perfectly executing the task (there might be a gust of wind, or the wheels might slip etc.) This is called _process noise_. Over time, you have less and less confidence in the robot's position.
You can try to fix this by using sensors on your robot which can give updates about its current position. However, these might be noisy themselves (_measurement noise_). Also, your sensors might not give full information about your environment (for example, it might be a laser that only gives the distance to the closest wall).
A Kalman Filter is one common way of working out how much to trust your model of where you are vs where your sensors are telling you you are. It can be extended to solve the problem of Simultaneous Localization and Mapping (SLAM), building a map of the environment while also working out your position in it.
A linear Kalman Filter might be a good topic for a coding challenge or series. For example, you could build agents like in challenge 69, Evolutionary Steering Behaviours, and intentionally corrupt the sensing inputs that the agents are receiving and/or add random gusts of wind etc., then design an algorithm to help them understand where they are despite corrupted or limited senses. Or you could have a set of landmarks in the environment and try to build a map of the environment from only the information the agents are receiving.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

Commencez par examiner le sujet proposé sur le filtre de Kalman linéaire et Challenge 69, Evolutionary Steering Behaviours. Clarifiez la portée d’un coding challenge ou d’une série, notamment s’il doit couvrir la détection bruitée, le bruit de processus ou SLAM. Le travail sera considéré comme terminé lorsqu’une définition du challenge et un périmètre d’implémentation auront été convenus.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Domaine
robotics
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.