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

Next generation steps identified by CHM #354

Closed
mohawk2 opened this issue May 6, 2019 · 1 comment
Closed

Next generation steps identified by CHM #354

mohawk2 opened this issue May 6, 2019 · 1 comment

Comments

@mohawk2
Copy link
Member

mohawk2 commented May 6, 2019

In an email in Dec 2015, Chris wrote things that could be incorporated in future PDL*:

ArrayFire GPGPU parallel computing:
http://www.arrayfire.com/docs/index.htm
This could give PDLng a quick start for
high performance using GPUs.

COS, the C Object System:
https://github.com/CObjectSystem/COS/blob/master/doc/cos-draft-dls09.pdf
https://github.com/CObjectSystem/COS
This could give PDLng an object oriented
interface that maintains a C FFI so that
PDLng could call or be called from other
languages. Matplotlib anyone?

HDF5 Attributes:
http://www.hdfgroup.org/HDF5/doc1.6/UG/13_Attributes.html
I was thinking that our PDLng implementation
should cover the bases from FITS, HDF5, named
dimensions,.. Ingo has already done some
work along these lines.

@mohawk2 mohawk2 transferred this issue from PDLPorters/pdla-core Nov 29, 2021
@mohawk2
Copy link
Member Author

mohawk2 commented Dec 31, 2021

Closing this to merge it into #349.

@mohawk2 mohawk2 closed this as completed Dec 31, 2021
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