This is the result of what started as a 1-day hacking session with the team.
Our approach to AI is basically using it as an assistant to help you explore the data. In Marple, AI can do two things:
1. Generate relevant plots
2. Generate SQL to run on datasets
Have fun playing around with it, it's part our our free trial.
Thanks for the feedback, hope you enjoyed reading it.
Looks like you have a process engineering background, I am not familiar with a ratio controller actually, good to know.
Maybe for our next article I should dive in deeper how to avoid overshoot and what methods there are (eg. posicast, simple speed damper, ..)
We are making a series of more technical articles with Marple at the moment. This time it was my time to shine!
We often see engineers struggle to get some PID controllers working. We know a thing or two about it, so we want to share it with the world! I wrote a short 4 step guide on how I think you can tune a simple PID controller and also shared some thoughts.
You make a valid point, there is a completely free version actually, but you can also try the paid version 14-days for free. After signing-in you can choose the free plan or the trial, but I get your point, you might feel like you are running in some sort of trap. Maybe we could make a link to the pricing page there to make it more clear.
(other co-founder) Thanks a lot! Great to hear these positive reactions. You make some very valid points. We are indeed trying to focus on a certain use case, which we encountered our self in the past.
Thanks :D We're working on an export feature to quickly share or paste in a ppt etc..
But for now you'll have to rely on your printscreen or snipping tool skills.
Very close, it uses Electron! Front-end is written in ReactJs. The plot library is react-vis currently, but we're replacing that soon. All the zoom/pan logic we implemented ourselves. Backend is a completely separate process.
We've chosen for this architecture as it gives us the flexibility to easily change from desktop product to a web/server product, if we feel like that would be a better fit :)
Target users can be very broad and is something we are still figuring out, but at the moment we see that engineers that have to deal with data from tests or simulations are a good fit for Marple.
This is a beta version, the goal of the trial is to gather feedback and find interested parties. Pricing and pricing model is not set in stone yet and will depend on what we see is feasible. Feel free to contact us in private to discuss more in detail! :)
