typicalTYLER
typicalTYLER
Currently clustering is restartable, but doesn't add new positive cases to old clusters, just makes new clusters.
Possibly by grouping things into classes, using dunder method naming, etc.
I can't currently imagine exactly what the tests will look like, but we should write some.
I think due to some combination of SIGINT-ing processes and bugs, it's possible to collect a lot of imagery that isn't tracked in the database, therefore it would be helpful...
MapRoulette is pretty good as a verification tool for our task, but we could still try out other ones, including Tasking Manager 3. I've reached out to a couple people...
This will probably make deploying the code less fragile for contributors and simplify things.
Optimize slower parts of this code (I've tried to parallelize the inner grid calculation and persistence but after much effort it was still not working correctly)
Currently sessions are created for every method call to the solardb.py, which is probably too frequently, especially for methods that get called with higher frequency.
In the [DeepSolar supplemental information pdf](https://www.cell.com/cms/10.1016/j.joule.2018.11.021/attachment/b91312aa-483a-44ad-9d75-60f0762cf709/mmc1.pdf), they detail a method they used to filter search area to urban areas which is pretty clever. They used [Nasa nightlight imagery](https://www.nasa.gov/image-feature/new-full-hemisphere-views-of-earth-at-night) as a...