Currently it is possible for the user to specify start and end times that don’t download enough data. We should automatically calculate the duration of data required and add that to the user’s requested start and end time. Not sure if it should be a standalone helper function, or if it should be built in to the data gathering scripts… leaning towards the former. Input would need to be coordinates of all stations and grid center / dimensions though, so tricky to decide where this belongs.
This is fairly critical since it’s easy to screw up / zero out the stack function if not enough data is downloaded.
Original report by me.
Currently it is possible for the user to specify start and end times that don’t download enough data. We should automatically calculate the duration of data required and add that to the user’s requested start and end time. Not sure if it should be a standalone helper function, or if it should be built in to the data gathering scripts… leaning towards the former. Input would need to be coordinates of all stations and grid center / dimensions though, so tricky to decide where this belongs.
This is fairly critical since it’s easy to screw up / zero out the stack function if not enough data is downloaded.