There were at least two attempts to create a GUI for Cadet (at least it seems like so based on the Github Repositories). Since Cadet Process aims at connecting unit operations and Knime does support such connections naturally, it might be a good match.
The ParameterArray class in Knime seems to support adding additional parameters (like components) and Knime would allow to ship/deploy models, scientists to create different configurations without coding. I think it is worth thinking about this combination.
Did you already discussed this option? Anyone who would like to join forces to prototype a forward simulation workflow, assuming Cadet Process runs on the same instance?
2 Likes
Hi Moritz,
Welcome to the forum!
I am currently the lead developer of the CADET-GUI. Although the repository has not seen much visible activity for some time, development is ongoing and we aim to complete the project this year. Last year was quite busy 
.
I would be interested to hear what you mean in by the second attempt. Are you referring to CADET-Web?
I am not familiar with KNIME, but I will discuss this with my colleagues and get back to you. We would need to better understand the proposed interface to assess whether this could be a suitable integration. Thank you for taking the initiative.
Best regards,
Hannah
Hi Hannah, thank you for the quick response. I can imagine that the last year was a busy one. Yes, I am referring to Cadet Web as the first attempt.
The idea with Knime has some uncertainties because it would mean, everything has to be built around the workflows in Knime but this might also be a strength (e.g. it could provide a very flexible way of creating a process or adding data or a plot to inlets or outlets). On the other hand, if you already have a roadmap for a GUI, it might be better to stick to it. Nevertheless, it would be interesting to know about your thoughts when comes to Cadet Process and Knime.