Create LogStrategy object

[MichaelClerx]

Simplest version would just implement the current scheme of logging the first 3 iterations, and then every Nth iteration.
Having this strategy in a separate class would open the door to more complex schemes, e.g. setting N based on the time between log calls

Example:

log = Logger()
log_strategy = LogStrategy()

for i in iterations:
    ...
    if log_strategy.should_log():
        log.log(123)
        log_strategy.have_logged()

something along those lines

[MichaelClerx]

An alternative implementation would be to update the Logger class so that it's called on every iteration, but discards most of the data it gets (only logs selectively, following some strategy)

[MichaelClerx]

Another suggestion in #616 is to have some logging-capable class that controllers can extend