At the moment there is no proper postprocessing interface to analyze the data. We achieve this by custom python scripts tailored to the optimization case we are running.
Having said that we could host a minimal postrocessing class that could be used to scrape designs.json, get the constraints, objectives, parameters etc, and provide them to the user for plotting. I think it would reduce the amount of duplicate work, if we had that simple interface already implemented.
This is of course low priority, but I am opening this issue for further discussion.
At the moment there is no proper postprocessing interface to analyze the data. We achieve this by custom python scripts tailored to the optimization case we are running.
Having said that we could host a minimal postrocessing class that could be used to scrape designs.json, get the constraints, objectives, parameters etc, and provide them to the user for plotting. I think it would reduce the amount of duplicate work, if we had that simple interface already implemented.
This is of course low priority, but I am opening this issue for further discussion.