If users download the WRF source code as a GitHub "archive" file from https://github.com/wrf-model/WRF/releases , the unpacked source directory will not be named WRF, but will have a name like WRF-4.0.
Somehow, we need to be able to find this WRF directory when configuring the WPS so that the path to the WRF I/O API can be added in the WPS configure.wps file.
Suggestions that have been offered:
Have the user type in the path to the WRF source code (or the name of the directory) when running the WPS configure script
If users download the WRF source code as a GitHub "archive" file from https://github.com/wrf-model/WRF/releases , the unpacked source directory will not be named
WRF
, but will have a name likeWRF-4.0
.Somehow, we need to be able to find this WRF directory when configuring the WPS so that the path to the WRF I/O API can be added in the WPS
configure.wps
file.Suggestions that have been offered:
configure
script