Data ingress, storage, and egress functionality (AWS S3 bucket configurations)

[Michael-Lalime]

We will start with the first sketch below:

[Michael-Lalime]

@ZacharyWills @KatherinePowell-NOAA any updates on how the S3 bucket deployment is going?

[KatherinePowell-NOAA]

Zach created this Pull Request:#88

[breannalcv]

S3 data transfer and access

[KatherinePowell-NOAA]

Jason Ducker constructed .zarr extractions scripts for AORC, HRRR, CORA, ESTOFS, NWM retrospective channel output datasets, which would subset the datasets only for the SCHISM mesh for efficiency and allow users to extract data in a dask parallelized fashion.

[KatherinePowell-NOAA]

Jason constructed an ERA5 interim dataset extraction script that allows a user to extract hourly ERA5 interim data specifically for a given region off the ECMWF system. Also constructed regridding scripts to blend AORC data with either HRRR or ERA5 Interim data to fill the offshore data gap for the AORC domain encompassing the SCHISM mesh. These Python scripts utilize ESMF regridding methods and have also been parallelized for efficiency.
Jason also streamlined SCHISM forcing pre-processing scripts to ingest and construct the required forcing files for a given model execution based on the retrospective datasets available from this developed workflow (AORC blended data, NWM retrospective .zarr channel output data, and CORA/ESTOFS data)