-
Notifications
You must be signed in to change notification settings - Fork 30
Parameterize model validation and comparison #168
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
Conversation
@MoLi7 can you clarify how I go about testing these scripts? Are they supposed to be built in to model development? |
@bl-young you should always run/knit I consider them internal QAs (and/or preliminary analyses) but not essential model components that will be exposed to users. |
@MoLi7 I get this error (and a similar one on Compare...render.rmd)
|
Do you not have ValidateModel.Rmd in inst/doc/? |
I do...which is strange. I'm on the param_val branch and the file is there. Something about the path is not working for me locally. |
@MoLi7 ok the issue was that by default it was knitting based on the document directoyr not the project directory. now it works. sorry! |
Looks good to me, except I can't complete comparison of 2.0 and 2.1
|
I guess you haven't downloaded |
No I have that file and can build 2.1 just fine |
Sorry that I assumed you did not have it. It should be due to flow differences in 2.0 and 2.1 - that's why the error message is about |
1dd1154 enables comparison between models that have different flows and prints out what the flows are. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't realize this one was waiting on me. It's good sorry,
The idea is to create a standard process to validate and compare models, then parameterize the process based on modelname to render model-specific validation and comparison reports.
The reports will be forced to
md
format for version control purpose and can be later converted to PDF or other formats to meet different requirements.This PR is intended to resolve issue #165.