Uwe Krien

In my opinion the error message should be the section and then we can add a list with possible reasons: **ERROR-Optimization failed with status warning and terminal condition infeasible** The...

I still will be able to pass a label attribute to the flow but it will be ignored in the first step and label will be added automatically in the...

> Concerning the warning: I'd not only generate one but straight up raise an error. That's what I meant with "extra checks". :+1: You are right. Raising an error is...

I think `to_something` functions are really helpful and important for a results structure because everybody wants to store results. > One note: The results can only be pickled/accessed if the...

I think we should distinguish between `dump` functions that make it possible to reload the results in the same form and `export` functions that may drop some information. Let us...

I wrote a function to divide the columns into input and output. Now I think it might be better to pass the DataFrame and get back the part of the...

> Sometimes I think about having a result class, again. I think you did a good job with the new results API. Releasing v0.3 people can bring together their experience...

> Maybe then it would be nice to add a shortcut for that for the API? ```python node_data = views.node(my_results, 'my_node', split='output') node_data = views.node_outputs(my_results, 'my_node') or something like this.......

> Or did I miss something? This is defined by the main API: ```python my_results = processing.results(om) export.to_xls(my_results, 'my_file.xlsx) ``` ...but if you want to export views you need to...

> Actually I have some ideas for this but would prefer to discuss them next week. Dicussing it here is too exhausting and it won't take long ;-) Agree :+1: