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

Move away from stl vector in primal #83

Open
davidgunderman opened this issue Aug 26, 2019 · 4 comments
Open

Move away from stl vector in primal #83

davidgunderman opened this issue Aug 26, 2019 · 4 comments
Assignees
Labels
Primal Issues related to Axom's 'primal component Reviewed

Comments

@davidgunderman
Copy link
Contributor

davidgunderman commented Aug 26, 2019

George @gzagaris suggested looking into using numerics::Matrix or axom::Array instead of std::vector in BezierCurve and associated classes.

@gzagaris gzagaris added the Primal Issues related to Axom's 'primal component label Aug 29, 2019
@kennyweiss kennyweiss added this to the FY22 Development milestone Nov 1, 2021
@kennyweiss
Copy link
Member

I think our axom::Array implementation is sufficiently advanced at this point for us to start chipping away at this ticket

@kennyweiss
Copy link
Member

@rhornung67
Copy link
Member

If there is a systematic way to do this incrementally, instead of one big change, it would be good to describe it here. Possibly with a checkbox task list?

@rhornung67
Copy link
Member

@kennyweiss @bmhan12 what is the status of this? do we want to move away from stl::vector in Primal completely? I assume code that has been ported to run on GPUs already has switched to Axom array view, or similar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Primal Issues related to Axom's 'primal component Reviewed
Projects
None yet
Development

No branches or pull requests

4 participants