Jakob Jordan
Jakob Jordan
can confirm this. we've also encountered problems with 5g and SPORE (https://github.com/jakobj/nest-simulator/issues/74). @hakonsbm has already looked into this a bit. maybe the two of you could sit together to fix...
ping @HenrikMettler
i think i don't have any more pressing comments, besides squashing commits please and fixing tests :)
great, thanks! pls update this PR now that #357 is merged
thanks for working on this! :rocket: looks like the checks only broke because of formatting?
yes, i think that would be a good idea. `n_columns` may be difficult to understand without the option of adding rows :D
good catch that we can not just remove the configuration option for reorder while we support multiple rows. how do you feel about removing the possibility of setting `n_rows` and...
yes, i think you're right, `levels_back` can also be removed. :+1: could you please create a separate PR, removing `n_rows` and `levels_back`? after that has been merged, we can come...
good idea :) we should keep in mind use cases where more than one exit criterion is desired, for example currently we exit upon reaching a max number of generations...
> Should I change the name of 'fitness_is_None' to 'already_evaluated' or make a separate method named 'already_evaluated'? i would strongly suggest to replace the existing method in the long run....