You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a reason there is no cross-validation equivalent for harmonica.EquivalentSources like there is for verde.SplineCV? I find myself quite often manually running cross-validations for the equivalent source parameters as shown in the Estimating damping and depth parameters user guide:
Also, related to this verde issue; I have an equivalent function for performing an optimization for the optimal equivalent source parameters, instead of a grid-search which would be done with the above cross-validation.
Are you willing to help implement and maintain this feature?
Yes if there is enough interest to justify doing this.
The text was updated successfully, but these errors were encountered:
Ok good to know, I'll see if I can find some time to make a PR for hm.EquivalentSourcesCV.
Any thoughts on the optimization aspect of this? Same idea as fatiando/verde#474 where instead of a grid-search CV, we use a hyperparameter optimization where the users defines the number of trials and the max/min values of damping/depth.
I guess we should first implement the simple CV and then consider adding the optimization.
Description of the desired feature:
Is there a reason there is no cross-validation equivalent for
harmonica.EquivalentSources
like there is forverde.SplineCV
? I find myself quite often manually running cross-validations for the equivalent source parameters as shown in the Estimating damping and depth parameters user guide:It would be great to be able to instead use
Also, related to this verde issue; I have an equivalent function for performing an optimization for the optimal equivalent source parameters, instead of a grid-search which would be done with the above cross-validation.
Are you willing to help implement and maintain this feature?
Yes if there is enough interest to justify doing this.
The text was updated successfully, but these errors were encountered: