d4ed5c9a43 | 1 year ago | |
---|---|---|
.task/checksum | 2 years ago | |
cmd | 2 years ago | |
influxdb/startup | 2 years ago | |
internal | 1 year ago | |
wiki | 1 year ago | |
.dockerignore | 2 years ago | |
.env | 2 years ago | |
.gitignore | 2 years ago | |
Dockerfile.reactor | 2 years ago | |
Dockerfile.server | 2 years ago | |
README.md | 1 year ago | |
Taskfile.dist.yml | 1 year ago | |
build.sh | 2 years ago | |
docker-compose.yml | 2 years ago | |
go.mod | 1 year ago | |
go.sum | 1 year ago | |
gotest.py | 1 year ago | |
reactor_build.sh | 2 years ago | |
wc.sh | 2 years ago |
README.md
FRMS
ForeLight Reactor Management System
This branch will serve as the staging ground for adding unit tests and documentation in order to finalize v0.1.0-alpha
Table of Contents
Introduction
FRMS serves as both an internal framework for testing reactor designs as well as a scalable customer facing application for monitoring and control. The project makes heavy use of low-cost yet powerful embedded systems capable of running full Linux kernels. Examples include the BeagleBone Black which was heavily used in development of FRMS as well as the popular Raspberry Pi 4. For more information about the hardware used in the reactors see here.
In its current state, FRMS is very bare bones and exists mostly as a proof of concept. Quickly navigate to:
Getting Started
Development
FRMS was initially written almost entirely in Go with some bash/python helper scripts.
Go was used primarily for its emphasis on readable and maintainable code as well as its approach to concurrent applications.
Creating software capable of scaling up to many reactors made heavy use of Goroutines especially on the server.
To begin developing use git clone git@github.com:fl-src/FRMS.git
to clone the repository.