-
Notifications
You must be signed in to change notification settings - Fork 9
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
Sprint16 kl projection #167
Conversation
Hi @jakobsj and @nabriis. I finished this KL projection pull request, but there is a general design/convention question: should we allow fun2par to be a projection or should it always be either exact or not supported. This functionality is very helpful for example in the heat1D problem where we want to look at the projected signal in the coefficient space (to get plot_ci for parameters for example). We can discuss in the stand-up. |
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.
After looking at it I think its OK to have this feature added. With the warning message there is no doubt that its not the full inverse.
update style Co-authored-by: Nicolai André Brogaard Riis <nabr@dtu.dk>
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.
Thank you @amal-ghamdi it looks good - I've requested some minor additions to the comments and tests.
Thank you @jakobsj for your very helpful feedback! I addressed your comments, please let me know if you have further suggestions for improvements |
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.
Thanks for adding the extra doc, looks good!
Closes #168