You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
KeeganForelight 9086b80994 purged websocket garbage, just going to use web grpc 1 year ago
.task/checksum purged websocket garbage, just going to use web grpc 1 year ago
cmd purged websocket garbage, just going to use web grpc 1 year ago
docker moved docker files to sub directory and cleaned up task file 1 year ago
internal purged websocket garbage, just going to use web grpc 1 year ago
wiki moved docker files to sub directory and cleaned up task file 1 year ago
.dockerignore Added more config methods for server interface and started working on docker compose. Need to finish influx startup and grafana provisioning 2 years ago
.gitignore moved docker files to sub directory and cleaned up task file 1 year ago
README.md moved docker files to sub directory and cleaned up task file 1 year ago
Taskfile.dist.yml moved docker files to sub directory and cleaned up task file 1 year ago
go.mod python testing helper with colors 1 year ago
go.sum python testing helper with colors 1 year 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

For specific information about decisions made in development see here.

Installation

The project uses a make alternative called task written in go for building and testing. After using git clone git@github.com:fl-src/FRMS.git to clone the repository, you can then build binaries of the two commands server and reactor for testing. The binaries will be put into the bin/ folder and will be labeled with the platform and architecture they were built for.

WARNING: The reactor binary currently relies on the Linux i2c-tools to interact with the i2c bus. This may cause undefined behavior when run on a device without the tools installed. More information about this design choice can be found here

Usage

Technical Information

Overview

Reactor

Networking

GUI

API

Future Work