Document running the Python listener on a second PC

Abierto
  • ¿Algo no está bien?
#264 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
70/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
documentation

Línea de trabajo

Read the root README section “Sending to iMotions and Python at the same time” and the relevant guidance in inference/README.md. Then follow the proposed two-PC setup on the lab PCs, checking the listener bind address, Windows Firewall access, and the IPv4 address entered in the relay. Done means the root README has a “Two PCs” subsection, inference/README.md points to it, and the first test's findings are recorded.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:docs area:ml area:relay documentation needs-triage

Problem

In the lab, X-Plane and the relay run on one PC and the ML pipeline runs on another. Every example in the READMEs uses 127.0.0.1:5001, and nobody has run the mirror between two PCs yet. Three things are needed that the docs do not mention:

  • live_groups and data_logger bind to 127.0.0.1 by default (--host), so a relay on another PC cannot reach them. Start them with --host 0.0.0.0, or with the ML PC's LAN address.
  • Windows Firewall on the ML PC blocks inbound TCP 5001 until a rule allows it, for example New-NetFirewallRule -DisplayName "PilotDataSync 5001" -Direction Inbound -Protocol TCP -LocalPort 5001 -Action Allow (admin).
  • The relay's mirror box needs the ML PC's IPv4 address (ipconfig), not 127.0.0.1.

Proposal

  • A "Two PCs" subsection under "Sending to iMotions and Python at the same time" in the root README, with a pointer from inference/README.md.
  • A first real test on the lab PCs, noting anything else that came up.
  • #258 can automate the firewall rule and print the address. This issue covers the docs and the first test.
Lenguaje dominante
Python
Estrellas
4
Forks
9
Merge medio
5 d 13 h
PR fusionados (30 d)
13

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de oss-slu/PilotDataSynchronization

Todos los issues de oss-slu/PilotDataSynchronization

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.