-
Notifications
You must be signed in to change notification settings - Fork 33
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
Update TEM configuration #279
Conversation
Move each TEM configuration into case and baseline sections of config file
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.
Looks good, but did have some questions and a few change requests.
@nusbaume I think I addressed your comments/suggestions. Thanks for looking this over, the changes are in when you get a chance to review it again. Thanks! |
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.
Super close! Just one last question.
@nusbaume There was also a bug for the TEM plots if the file exists and redo plot is false, it created an empty plot and saved that to the web. I've tested this with model vs model and model vs obs. If you don't mind just looking at these two changes again that'd be great. |
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.
Everything looks good to me now. Thanks @justin-richling!
It seems like it might make more sense to move the TEM configuration into the case subsections as requested by @cecilehannay.
This will move each TEM configuration into case and baseline sections of config file and will update the TEM files to account for the configuration change.