Simon Blanke

> No matter how we group them, I think we should give classes unique names Agreed If we order by algorithm, this would be my preference: ```python # in the...

We order by algorithm, as you suggested. The package abbreviations make the class names short and the classes are unique. This should work out fine, agreed?

V5 is released and a solution was found.

> so, going back to the hyperactive.opt.gfo folder structure? This is an "intermediate" commit for testing stuff out and to see it in practice. The fact, that we provide the...

Hello @Wassaf001, I already [added doc strings some time ago](https://github.com/SimonBlanke/Hyperactive/blob/master/src/hyperactive/hyperactive.py). Forgot to close this issue. I am currently working on a [new API for v5](https://github.com/SimonBlanke/Hyperactive/pull/101). This would require some new...

Hello @fkiraly, I took some time to understand these changes you are proposing. I will show you how interpreted them, so please correct me if I misunderstood something. It appears,...

> I think there is a small degree of miscommunication - would you like me to write a design document, or a draft PR (for demo purpose only)? That would...

Relevant comment: https://github.com/SimonBlanke/Hyperactive/issues/85#issuecomment-2454119030

This issue was solved during the development of v5.

Am currently working on some corrections of this notebook (for general usage): https://github.com/SimonBlanke/hyperactive-tutorials/blob/main/notebooks/hyperactive_tutorial.ipynb