because tick counter starts at 0, and is updated at the end of a cycle, it means any event happening during the first generation is record as happening at t0.
Which is weird because (a) it intuitively happens at t1 (b) we already have things happening at t0 (the introduction) so it creates conflicts with founding dates
There is a solution currently implemented in the model (basically running one cycle on empty) but I need to think about how this alters other aspects of the model (like what generations are actually saved) before validating it
because tick counter starts at 0, and is updated at the end of a cycle, it means any event happening during the first generation is record as happening at t0. Which is weird because (a) it intuitively happens at t1 (b) we already have things happening at t0 (the introduction) so it creates conflicts with founding dates
There is a solution currently implemented in the model (basically running one cycle on empty) but I need to think about how this alters other aspects of the model (like what generations are actually saved) before validating it