Tasku

@euronion I've been a bit busy lately, so I don't know when I'll have the time to address your comments above. Hopefully within a few weeks, but I can't make...

@euronion Ok, I think I've addressed all of your previous comments. I also revised the example so that it doesn't display any unnecessary intermediate output, and included the outputs of...

@FabianHofmann can you clarify which part of the example code you're referring to? In the beginning, I clip the raw European population density raster with ```python finland_population_density = ( population_density.rio.clip(finland_3035.geometry,...

Ok, I revised the example to be a bit more dense *(and fixed a few typos)*. I also went through the pull request checklist again, but it seems that `pytest`...

@FabianHofmann I have no objections, it's your codebase after all 😉

I'm not especially experienced with investment optimisation, so I'm hardly the best person to comment on the formulation etc. I can comment on some aspects of the code and model...

@manuelma @DillonJ @jkiviluo If you want, I can spoil the surprise for next week 😄 Or you can spoil yourselves, as I've already uploaded my presentation with the initial results...

@manuelma @abelsiqueira Just a thought, but perhaps a relatively quick thing we could try to improve the performance of the indices _(e.g. #925)_ is to replace `Array`s with `Generators` and...

@manuelma True, I suppose. However, at the moment, each indexing function call returns an `Array`, and I think there might be a lot of time and memory wasted allocating memory...

@manuelma That's why it's just a thought 😅 I'm not very familiar with `Generator`s and `Iterator`s, so I don't know if they support all the logic we'd need them to...