Skip to content
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

Feature: function to report the influence of a knot and plot the original, coarsened, and re-inserted control polygons #19

Closed
dewittpe opened this issue Nov 16, 2016 · 1 comment
Assignees

Comments

@dewittpe
Copy link
Owner

A very helpful graphic used to show the influence of a knot on a (uni-variable) spline function has been a plot of three control polygons:

  1. The original control polygon with ξ and θ
  2. The coarsened control polygon with ξ \ ξj and (WTW)-1 WT θ
  3. The control polygon after reinserting ξj, i.e., with ξ and W(WTW)-1 WT θ

The function influence_weights already exists for finding the influence weight. This function will need a good name, perhaps influence_of?.

Initial thoughts for the API is:

influence_of(x, j)

where x would be a cpr_cp object and j is the index of attr(x, "xi") to omit.

A warning should be given if j is the index of a boundary knot.

The return should be a graphic and some other information, the index j, the value of the knot (the abscissa), the influence weight and rank.

Perhaps a vector of indices can be passed and a facetted graphic will be returned with a table of information, the index, abscissa, and the influence weight, and rank.

@dewittpe dewittpe added this to the Long Term Objectives/Issues milestone Nov 16, 2016
@dewittpe dewittpe self-assigned this Nov 16, 2016
@dewittpe
Copy link
Owner Author

To make this a viable tool you'll need to reconsider how the spline data is used in plot.cpr_cp so that it can be extracted and used in plot.cpr_influence_of.

dewittpe added a commit that referenced this issue Nov 17, 2016
build the full data need and using functions within each layer to subset the
data.
dewittpe added a commit that referenced this issue Nov 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant