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

Make adaptive transform a Vcat instead of a cached vector? #76

Open
dlfivefifty opened this issue Sep 24, 2021 · 0 comments
Open

Make adaptive transform a Vcat instead of a cached vector? #76

dlfivefifty opened this issue Sep 24, 2021 · 0 comments

Comments

@dlfivefifty
Copy link
Member

Sometimes we use the transform to build operators, and the bandwidth is determined by the number of non-zeros. In this case, cached vectors are not so useful as anytime we access them they grow, and the bandwidth of the operators grows.

But is there any reason we would need coefficient vectors to be mutable (in their zeros) by default? A user could call Base.copymutable(P \ f) if they really wanted to mutate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant