Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Need additional logic to detect WRF code downloaded as GitHub archive #72

Open
mgduda opened this issue Oct 1, 2018 · 1 comment
Open

Need additional logic to detect WRF code downloaded as GitHub archive #72

mgduda opened this issue Oct 1, 2018 · 1 comment

Comments

@mgduda
Copy link
Collaborator

mgduda commented Oct 1, 2018

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
@mgduda mgduda mentioned this issue Oct 2, 2018
Merged
@DonteRW DonteRW mentioned this issue Dec 6, 2018
Closed
@mgduda
Copy link
Collaborator Author

mgduda commented Feb 18, 2019

A little progress has been made with PR #102 , but a general solution has yet to be implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mgduda