Michael Duda

Working on Derecho and choosing options `1`, `n`, `n`, I get the following error: ``` -- The C compiler identification is Intel 2021.10.0.20230609 -- Cray Programming Environment 2.7.23 C --...

The last commit resolves the issue I was seeing. Actually, my intent wasn't to only compile ungrib, so perhaps I'm misunderstanding the option: ``` [EXT] Build external? Default [N] [y/N]...

I think it would be nice if users didn't need to specify the path to the compiled WRF code. I can appreciate that the situation is a bit different when...

I would also propose that the default for ``` [DM] Use MPI? Default [Y] [Y/n] : ``` be `n`, as we most often build the WPS executables without MPI. It's...

What we do currently is: 1) If the `WRF_DIR` environment variable is defined, use it to determine the location of the compiled WRF code 2) Otherwise, look in `../WRF` (or...

Agreed regarding no failure if `--no-wrf` is specified and no WRF directory is found. Also, I think it would be fine to prompt for something like `Detect compiled WRF (needed...

@islas This prompt seems a bit cryptic: ``` [EXT] Build external? Default [N] [y/N] : ``` Since its intent is to determine whether we build the GRIB2 libraries from source,...

As a suggestion for ``` [WRF] Try to find WRF for metgrid/geogrid? Requires WRF path set or ../WRF or ../wrf to exist. Valid input paths are WRF_ROOT or WRF_DIR, set...

Thanks for the additional explanation. I have a few proposals regarding the detection and use of compiled WRF: 1. There should be only one name for the environment variable and...

@islas That looks good to me!