-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
Incorporating given points into training #723
Incorporating given points into training #723
Conversation
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.
AI-Maintainer Review for PR - Initial commit of given_points_training
Title and Description ⚠️
Scope 👍
Testing ⚠️
Documentation ⚠️
inner_loss_DAE
generate_loss_DAE
GivenPointsTraining
get_loss_function
(withstrategy::GivenPointsTraining
argument)
These entities should have docstrings added to describe their behavior, arguments, and return values.
Suggested Changes
- Please revise the title and description to provide more clarity about the changes and their purpose.
- Please provide details about how the changes were tested.
- Please add docstrings to the
inner_loss_DAE
,generate_loss_DAE
,GivenPointsTraining
, andget_loss_function
(withstrategy::GivenPointsTraining
argument) functions, classes, or methods.
Reviewed with AI Maintainer
As mentioned in #644, tstops would be the right way to do this. Basically, This would be a lot more useful since only using the given points is likely never a good idea. The points should be changing and randomized so that just won't be possible with given points. But what we can do is do for example a QuadratureStrategy but, knowing the point of a discontinuity, add a few training points around this point that we know is going to be difficult. |
…ows us to add points to to ts of the current strategy
Ok got it, we do not want a separate training strategy, we want to add this functionality to each training strategy. I've written up some stuff so far, but there are some issues currently. It works well for |
You don't need to mutate or add to the loss function code of any strategy. Just append the values by adding the loss. |
…ration and into solve call
I think this is what you are referring to? I tested it with 3 training strategies and it turned a failing solver into a successful solver in all 3 cases |
This looks close, just needs the clean ups mentioned. |
Why make a separate test group? Does this one really take half an hour? |
It does not take half an hour, I just fixed that now and just made it run as part of 'All' |
All is not a test group. Please put it with the other nnode tests |
Fixed now, sorry for the confusion |
Test fails |
Weird, it was working on my end when I ran it, but I made some edits and accounted for the relative size of the tstops entry when calculating the total loss. This works much more consistently now. I am not sure if this is exactly what we were looking for with this idea but hopefully it does what we want |
No, read the CI... it was missing test imports. |
Oh maybe I misinterpreted what you said, I thought you meant it was failing the tests I wrote. But after reading the CI it says that its missing IntegralsCuba (which I never touched) and I haven't changed the manifest.toml or project.toml. |
No, it's saying |
Ok I removed it from the file, hopefully everything is good now |
oops, loaded now |
#644 This is working for the given example