-
Notifications
You must be signed in to change notification settings - Fork 31
User-defined features #902
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
Draft
kecnry
wants to merge
35
commits into
phoebe-project:release-2.5
Choose a base branch
from
kecnry:user-defined-features
base: release-2.5
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1f2a352 to
a101841
Compare
6420a96 to
9507a2b
Compare
725206d to
0a9852a
Compare
8cb812a to
2ff5605
Compare
6ead7ab to
e150aae
Compare
e4ea7af to
9c6829f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for defining custom features in-line that can either modify models after they are computed (but before they are fitted) or modify component mesh quantities.
Current restrictions:
superis not allowed and will result in an error.DatasetFeature:
ComponentFeature:
Example of a
DatasetFeature(SinusoidalThirdLight):Example of a
ComponentFeature(SinusoidalIntensities):Example of a
ComponentFeature(DifferentialRotation):Example of a
ComponentFeatureinheriting from a built-inSpot(MigratingSpot):TODO:
DatasetFeatureto handle modifying the comparison data (ie detrending)? Or should we split intoDatasetFeatureandModelFeature?can we be more consistent between returning values inComponentFeaturevs modifying parameters inDatasetFeatureLightCurveAdditiveFeatureandLightCurveMultiplicativeFeaturewhich allows just defining the functional form and handlesmodify_data_for_estimatorsandmodify_modelget_parameterstoadd_featureor similar?proto_coordsto something more user-friendly (and document better)feature_code, if possiblecomponent.spot,dataset.gaussian_process, etc)feature_codethrough parameteradd_feature(..., overwrite=True, **b.get_feature(...)), or should we split into two input arguments (if callable is sent tokindthen create the parameters and create afeature_codeparameter which can also be sent as a kwarg).entries need to show up inlist_available_features(at least if using registration)