(GUI and API) Merge xnimbus implementation

[giomara-larraga]

I solved some of the conflicts, but please check that everything else is running correctly.

[gialmisi]

Thanks! I will be checking this.

[gialmisi]

@giomara-larraga

I have now extracted the XNIMBUS methods and its core functionalities. I limited this to getting the method working in the framework. I deliberately did not include some of the experiment specific features. These can be extracted as well, if deemed generally useful, just let me know which ones you would like to have. You can check commit 4f95b2c for the changes.

[giomara-larraga]

@gialmisi

I checked the master branch, and some changes were not merged. As a reference, I attached a screenshot of how the interface looks in my branch:

The following changes are not reflected in the master branch:

• The updated order of components in the preference sidebar
• Instructions on how to set preferences
• The help button explaining the use of the horizontal bars
• The method name displayed in the top bar
• The legend in the parallel coordinates plot
• The quick start button
• Updated objective names in the river pollution problem
• The revised layout of the visualization panel
• The help message shown when the iterate button is disabled (clarifying what constitutes a valid classification)

Since these changes reflect design decisions we have iterated on multiple times, it would be good to have them included in the master branch to avoid reimplementation later.

Please let me know if you need any clarification or additional details.

[gialmisi]

@giomara-larraga

Thank you for this list. I wanted to discuss about the merge in this week's technical meeting, but I could not make it. I am happy you brought this up, because I indeed limited the first commit to just the core functionalities of the method. I can bring these into the merge as well as soon as I have time.

Something I wanted to ask was about modifications to some of the components that are used in other methods as well. Should we update the general components, or have XNIMBUS specific ones? If the changes are result of iterative design and deemed beneficial in general, then my guess is that we should update the general components.

(And since I am bringing these changes to a new branch in their own commits, which is just easier for me than merging existing branches in this case; I will add you as an author to these commits as well before the actual PR, otherwise it looks like this is my work, which it is not. I hope that is ok!)

[giomara-larraga]

@gialmisi
I forgot to mention this during the technical meeting today. Since these changes are not XNIMBUS-specific, I think we should update the general components so they can be used more broadly and keep things consistent.