I should restructure the feedback code. Write now it's messy, duplicates work, and is difficult to debug.

Currently, it is written where there is completely separate logic for low feedback, medium, and high feedback, where the finding of "optimal" or "suboptimal" settings is repeated (poorly) within each of these feedback code blocks.

A better structure would be to have a single code block that finds every "optimal", "suboptimal", or "incorrect" to the finest degree, and stores these in a single "optimizations" array. Then, each of the low, medium, and high feedback blocks should pull from this as it wants.