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

Avoiding data copies? #1060

Open
dakoop opened this issue Apr 15, 2015 · 2 comments
Open

Avoiding data copies? #1060

dakoop opened this issue Apr 15, 2015 · 2 comments

Comments

@dakoop
Copy link
Member

dakoop commented Apr 15, 2015

@tacaswell brought up the possibility of mutating numpy arrays instead of having the input array disjoint from the output array. Potential ideas involve enforcing cardinality=1 on output ports, or having some way to inform VisTrails that such mutated objects exist so caching, etc. can deal with this.

@tacaswell
Copy link
Contributor

attn @ericdill @giltis

@tacaswell
Copy link
Contributor

I think the cardinality constraint is a bit nastier, the input port which takes in an object that it will mutate needs to enforce that the cardinality on the output port that it is connected to is 1.

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

3 participants