Moving towards the right approach
The last few weeks have been a whirlwind of ideas, coding, and rethinking as we figured out the best way to build my dashboard project. Our First Idea: My initial plan seemed pretty logical. I was going to download all the raw data (the "event files"), process them into lightweight h5 files full of handy PNGs, and stick them all in an S3 bucket. The dashboard would just grab these pre-made files. It was a neat and tidy plan, but the more we thought about it, a static, deployed app . We decided to make something that a user could clone and run right on their own local machine. The Next Step: So, that's what we did. The new idea was to build a dashboard that anyone could just grab from a repository and run on their own computer. No big deployment , In this version, the user would download the source data they were interested in, and my dashboard would help them create the plots and data products right there on their machine. But that created a whole new problem: asking p...