I am working on a project that utilizes both Human UI and some of solvers like Galapagos/Opossum/Goat. The issue that I am having is that Human UI’s input value automatically return to its default values right after Opossum or Goat started. Strangely, there is no such an issue with Galapagos. It seems like solvers other than Galapagos trigger refreshing Human UI, and I wonder if there is anyway to avoid it.
Human UI does not support these solvers. Even using Galapagos in this way is likely not to work correctly - once a slider in the UI is established it should not be modified within the definition.
Andrew - Thanks for the quick reply. I understand that sliders in UI should not be modified with the solvers. But if you look at the definition, solvers do not change those sliders embedded in the UI - they only change values of independent sliders. I just put those sliders there to show some of those solvers refresh the interface no matter what, and wanted to know if there is any way to stop it refreshing…
ah, I see. The other two solvers are likely expiring the whole definition, whereas Galapagos only expires those components on which the fitness depends (or which depend on the sliders it is connected to). Nothing I can do about this one unfortunately…