Think about multiple GUIs

[matiasandina]

Initial comments of needs

• A feed on console (we already have this)
• Information about last event (with timestamp), and cumulative pellets per fed

[matiasandina]

We discussed many things, I'm adding an image of the options we are currently considering

There are 3 main paths. Purple things are needed for all paths. We have yellow = tkinter, teal = local shiny, orange = remote shiny

The data viz part would be minimally showing some stats (see #8 ). We can later click onto each fed to have larger timescale or some plot (number of active levers, cumulative pellets, IPI histogram, ...).

We are still thinking about getting data to bonsai in real time. Options for this are network based, maybe even through ethernet cable.

[matiasandina]

Tkinter version

Pros: we keep it simple Cons: it's not that simple, and it's ugly, and we need to VNC to all the Pis to see what's going on.

Local Shiny version

Pros: Matias can help here. Shiny is better than tkinter and dash for data wrangling and display. Potentially all data converges into one place. Cons: Less people know and can maintain R. IP of remote will change unless we make it fixed, annoying. I currently bypass this by sharing the IPs through SSH (for which I need to have one fixed IP).

Remote Shiny version

Pros: Same pros as local shiny + Better access options. Cons: Likely costs money. More difficult to maintain.

It's possible to run a local shiny server that has access through www, which can bypass all the "in network" problems More info here https://www.rstudio.com/products/shiny/shiny-server/