Closed burritobrittany closed 4 years ago
Decided on using different data set without rain. Will Close this pull request and create a new one.
@burritobrittany I agree, the code is cleaner not having D1 and D2 and being able to use the same grid.
I think I would suggest using data from a different day so we don't have the rain-drops, and also putting all of the cameras in there so it shows complete coastal coverage? I think that would be helpful to teach around as well. I think trying to find a day with some nice sandbar morphology - maybe crescentic bars (sort of like the data you have in the multi-Cam branch) would be nice.
I also think we should add some notes about while we are pulling the stacks out as an example, these stacks are just from timex images as opposed to sequential frames within a 30-minute collect, so aren't really a vbar, runup, or cbathy stack.
Removed the Hawaii Data and put Duck data in the multi camera demo instead. This allows D1 and D2 to be combined into a singular D since the data can share the same grid. I think this streamlines the code quite a bit.
For, D, G1 and G2, moved all of the multi-camera input into one Section (section numbers still need to be updated). This makes it easy for the user to find what to comment out etc to switch between demos.
For the data itself... I tried to pull argus data from the same day as the flight. Unfortunately on that day the images have lots of rain drops. Is it better to do a different day where it is clear?
I also played with using camera 5 instead of 1 to remove the number of frames with drops in it. However camera 2 still has a lot of drops...but it is a key image that overlaps with the UAS data so we are stuck with it.