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.

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

Revert "Change name of metadata directory" #36

Merged
merged 2 commits into from
Jan 13, 2021
Merged

Conversation

mdpiper
Copy link
Member

@mdpiper mdpiper commented Jan 12, 2021

This reverts commit 88220cf, which fixes #35.

This statement gives the location of the installed model metadata. Changing it here in the babelizer causes problems downstream--it confuses the model_metadata package, which raises an exception from within pymt. I didn't fully understand the consequences of this change when I made it.

This reverts commit 88220cf.

I made this change without fulling understanding it. This sets where
the model_metadata package looks for the installed model metadata, so
it shouldn't be changed.
@mcflugen
Copy link
Member

@mdpiper sorry, I should have caught this.

As part of this pull request, would it be possible for you to add a test that checks that metadata files are installed correctly?

@mdpiper
Copy link
Member Author

mdpiper commented Jan 12, 2021

@mcflugen I shouldn't have messed up! I'll make a test.

@mdpiper
Copy link
Member Author

mdpiper commented Jan 13, 2021

@mcflugen Added test code. It's ugly, though; any suggestions for improvement are welcome.

@mdpiper mdpiper merged commit 05431d9 into develop Jan 13, 2021
@mdpiper mdpiper deleted the mdpiper/fix-35 branch January 13, 2021 21:06
mdpiper added a commit to pymt-lab/pymt_gridmet that referenced this pull request Jan 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

model_metadata can't find model metadata
2 participants