fixing more conflicts in make_geogrid.py

wps/Readme.md

@@ -0,0 +1,113 @@
+![](https://ral.ucar.edu/sites/default/files/public/wrf_hydro_symbol_logo_2017_09_150pxby63px.png) WRF-HYDRO
+
+# Overview
+This container is used primarily to create geogrid files for a specified domain to be used with the WRF-Hydro modeling system.
+
+This container includes the following:
+
+* Ubuntu base image
+* WRF and WPS built with the GNU Fortran compiler ‘gfortran’
+* Python 3.6 command line utility for create WRF-Hydro geogrid files using the WPS geogrid.exe program.
+* WRF-WPS Geographical input data for the Continental United States.
+
+## Where to get help and/or post issues
+If you have general questions about Docker, there are ample online resources including the excellent Docker documentation at https://docs.docker.com/.
+
+The best place ask questions or post issues is via the Issues page of the GitHub repository at
+https://github.com/NCAR/wrf_hydro_docker/issues.
+
+## Data sources
+WRF Preprocessing System (WPS) geographical input data are one of the primary datasets used by the NoahMP Land Surface Model (LSM). These datasets can be obtained from the [WPS geographical input data download page](https://www2.mmm.ucar.edu/wrf/users/download/get_sources_wps_geog.html). However, these data are rather large (~50GB) and contain a number of datasets that are not used in most implementations of WRF-Hydro. We have reduced the data by removing various resolutions of the data that are not commonly used by WRF-Hydro. Furthermore, the dataset provided with this container has been subset to the Continental United States (CONUS). Thus, the dataset provided with this container is considerably smaller than the complete WRF-WPS dataset.
+
+## Creating the geo_em_d01.nc (geogrid) file
+### geogrid.exe
+The WPS program `geogrid.exe` is used to create the geo_em_d01.nc, hereafter referred to as the 'geogrid' file. The `geogrid.exe` program takes a fortran namelist (`namelist.wps`) and the [WPS geographical input data](https://www2.mmm.ucar.edu/wrf/users/download/get_sources_wps_geog.html) as inputs and creates the geogrid file. However, the `geogrid.exe.` program requires that WRF and WPS be built according to your system specification, and building WRF and WPS can be difficult on some systems. Additionally, much of the functionality of WRF and WPS is not utilized for creating a geogrid file for WRF-Hydro, and many of the options in the `namelist.wps` are not relevant to this process. Therefore, we have created a Docker container and Python command line utility to abstract much of the WRF/WPS complexity and simplify the process of creating a geogrid file for WRF-Hydro users. 
+
+We will cover the steps to create the geogrid file using this method in the section 'Usage and invocations'. For more non-standard, advanced usage please see the WRF-WPS documentation.
+
+### Defining domain boundaries
+WRF-Hydro uses domains boundaries defined by the `namelist.wps` input namelist to the geogrid.exe program. The first step to creating the geogrid file is to define our domain boundaries. The `geogrid.exe` program takes a centerpoint, x and y coordinates, and other projection information to define a bounding box for the domain. There are a number of resources available to assists users with defining this bounding box, including the NOAA supported [DomainWizard](https://esrl.noaa.gov/gsd/wrfportal/DomainWizard.html). If you have no knowledge of your coordinates, the [DomainWizard](https://esrl.noaa.gov/gsd/wrfportal/DomainWizard.html) is the best starting point. 
+
+### Exploring the abbreviated namelist.wps file
+The WPS `geogrid.exe` utility is controlled by options set in the `namelist.wps`. As previously stated, there are many options in the `namelist.wps` file that are not relevant to most WRF-Hydro users. Therefore, the Python command line utility supplied with this container accepts an abbreviated `namelist.wps` file.
+
+`namelist.wps`
+
+----------
+```
+&geogrid
+
+!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+! Define the extend in west-east (e_we) and south-north (e_sn) directions
+! Note: will create a domain of size (e_we-1) x (e_sn-1)
+!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+
+ e_we = 16,
+ e_sn = 17,
+
+!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+! Define the center point of your domain
+!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+
+ ref_lat = 41.47100
+ ref_lon = -73.74365
+
+!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+! Define the domain grid spacing (in meters)
+!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+
+ dx = 1000,
+ dy = 1000,
+
+!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+! Define the map projection
+!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+
+ map_proj = 'lambert',
+ truelat1 = 30.0,
+ truelat2 = 60.0,
+ stand_lon = -97.00
+
+/
+```
+----------
+
+### Usage
+
+** Step 1:** Create a directory to bind-mount to Docker for passing files between your system and docker
+
+```
+mkdir ~/dockerMount
+```
+
+**Step 2: Create a namelist.wps file for your domain using the above example as a starting point and save it in your mount directory from step 1.**
+
+**Step 3: Run Docker invoking the python make_geogrid.py utility with the required arguments.**
+
+**NOTE THE PATHS LISTED BELOW IN THE ARUGMENT LIST ARE FOR THE DOCKER FILESYSTEM**
+You most likely will only need to change the name of your namelist.wps file in the --namelist_path
+argument. 
+
+```
+docker run -v <path-to-your-local-mount-folder>:/home/docker/mount \
+ wrfhydro/wps \
+ --namelist_path /home/docker/mount/namelist.wps \
+ --output_dir /home/docker/mount/ \
+ --plot_only False
+```
+
+#### We will now dissect the pieces of this Docker command.
+
+-----------------
+
+`docker run -v <path-to-your-local-mount-folder>:/home/docker/mount...` - Run the container with the `-v` argument to bind mount a volume on your local system to a folder in the docker container. It is best to leave the folder in the docker container unchanged.
+
+`--namelist_path /home/docker/mount/namelist.wps \` - Path to your `namelist` file **ON THE DOCKER FILE SYSTEM**
+
+`--output_dir /home/docker/mount/ \` - Path to directory **ON THE DOCKER FILE SYSTEM** to hold output. It is easiest to have this be the mounted folder from the `-v` argument
+
+ `--plot_only False` - Only create a plot and do not run geogrid. Useful for making changes to the domain location and boundaries.
+
+**Note: You can access help on these arguments with the following command**
+
+`docker run wrfhydro/wps --help`

wps/gdrive_download.py

@@ -0,0 +1,51 @@
+import requests
+from argparse import ArgumentParser
+
+def download_file_from_google_drive(id, destination):
+ URL = "https://docs.google.com/uc?export=download"
+
+ session = requests.Session()
+
+ response = session.get(URL, params = { 'id' : id }, stream = True)
+ token = get_confirm_token(response)
+
+ if token:
+ params = { 'id' : id, 'confirm' : token }
+ response = session.get(URL, params = params, stream = True)
+
+ save_response_content(response, destination)
+
+def get_confirm_token(response):
+ for key, value in response.cookies.items():
+ if key.startswith('download_warning'):
+ return value
+
+ return None
+
+def save_response_content(response, destination):
+ CHUNK_SIZE = 32768
+
+ with open(destination, "wb") as f:
+ for chunk in response.iter_content(CHUNK_SIZE):
+ if chunk: # filter out keep-alive new chunks
+ f.write(chunk)
+
+def main():
+
+ parser = ArgumentParser()
+ parser.add_argument("--file_id",
+ dest="file_id",
+ help="Google drive file ID. Get from shareable link")
+ parser.add_argument("--dest_file",
+ dest="dest_file",
+ help="Full path including filename for downloaded file.")
+
+ args = parser.parse_args()
+ file_id = args.file_id
+ dest_file = args.dest_file
+
+ download_file_from_google_drive(file_id, dest_file)
+
+
+if __name__ == "__main__":
+ main()

wps/namelist.wps_orig

@@ -0,0 +1,53 @@
+&share
+ wrf_core = 'ARW',
+ max_dom = 1,
+ start_date = '2006-08-16_12:00:00',
+ end_date = '2006-08-16_18:00:00',
+ interval_seconds = 21600
+ io_form_geogrid = 2,
+/
+
+&geogrid
+ parent_id = 1,
+ parent_grid_ratio = 1,
+ i_parent_start = 1,
+ j_parent_start = 1,
+ e_we = 74,
+ e_sn = 61,
+ !
+ !!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORTANT NOTE !!!!!!!!!!!!!!!!!!!!!!!!!!!!
+ ! The default datasets used to produce the HGT_M, GREENFRAC, 
+ ! and LU_INDEX/LANDUSEF fields have changed in WPS v3.8. The HGT_M field
+ ! is now interpolated from 30-arc-second USGS GMTED2010, the GREENFRAC 
+ ! field is interpolated from MODIS FPAR, and the LU_INDEX/LANDUSEF fields 
+ ! are interpolated from 21-class MODIS.
+ !
+ ! To match the output given by the default namelist.wps in WPS v3.7.1, 
+ ! the following setting for geog_data_res may be used:
+ !
+ ! geog_data_res = 'gtopo_10m+usgs_10m+nesdis_greenfrac+10m','gtopo_2m+usgs_2m+nesdis_greenfrac+2m',
+ !
+ !!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORTANT NOTE !!!!!!!!!!!!!!!!!!!!!!!!!!!!
+ !
+ dx = 30000,
+ dy = 30000,
+ map_proj = 'lambert',
+ ref_lat = 34.83,
+ ref_lon = -81.03,
+ truelat1 = 30.0,
+ truelat2 = 60.0,
+ stand_lon = -98.0,
+
+ geog_data_res = 'default',
+ geog_data_path = '/home/docker/WRF_WPS/utilities/geog_conus'
+/
+
+&ungrib
+ out_format = 'WPS',
+ prefix = 'FILE',
+/
+
+&metgrid
+ fg_name = 'FILE'
+ io_form_metgrid = 2, 
+/