Giter Site home page Giter Site logo

plops's People

Watchers

 avatar  avatar

plops's Issues

Communicate via axcall

Research work being done in SerialPi project

swift run SerialPi call

This will fire up the axcall process, and simply print out information as it's received. Currently unable to send repeated commands, but progress is being made. PoC work for sending to another process is happening in the doRubyThing() method. So far, that method can send/receive text to a ruby script. Should be able to translate some of that work to doCallThing()

GPS view

We know when a runner left the prior station, we know their ETA for our station, we know the distance. In theory, we should be able to display a map with an estimated location.

Startup system

Ideally, a script that can be double-clicked or run in terminal to launch the system and connect it to the W100 system. It should:

[ ] Start any needed processes (database, ax.25 services, monitoring, etc.)
[ ] Get logging running
[ ] Bind any ports needed
[ ] Connect to system

Monitor incoming traffic from Pi

Work being done in SerialPi project

swift run SerialPi listen

This will fire up the axlisten process, and simply print out information as it's received. This will include all traffic though, so additional work would need to be done to filter out what we actually care about, and to cleanup the raw packets being received.

Aid station view

Simplified view that aid station workers can connect to in order to view incoming runners. Does not provide access to logging or other query info. should display current race time, as well as time data was last refreshed. ( In the event that a worker's device time is incorrect)

Display incoming runners, standings, temp info, etc. Station team members could connect their devices to this access point and have updated info in their pockets.

Store runner events

For every check-in/out, there needs to be an associated station, type, and timestamp.

CheckEvent {
runnerID:Int
station:StationEnum
time:Int
type:CheckEventType
}

enum CheckEventType {
in,
out
}

== OR ==

RunnerEvent {
runnerID:Int,
timestamp:Int,
station:StationEnum,
eventType:RunnerEventType
}

enum RunnerEventType {
checkIn,
checkOut,
dnf
}

Manual logging of runner events

Normally when using the UI to submit a runner event, the time should be logged automatically. However, there may be a need to manually enter a time for a runner with a custom time.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.