Deprecate the FFT library in ck-libs in favor of Nikhil's new FFT library
Right now the libraries manual still points to the in-tree version of the FFT library. Anyone using this library should get a deprecation warning, and the manual should be updated to point to Nikhil's library at https://charm.cs.illinois.edu/gerrit/gitweb?p=libs%2Ffft.git;a=summary instead.
#2 Updated by Eric Bohm about 2 years ago
- Status changed from New to In Progress
- Estimated time set to 24.00 h
- % Done changed from 0 to 10
There are a few complications to accomplishing this in that Nikhil's fft library is not a drop in replacement for the prior version.
- Documentation is far from complete
- the current manual includes inline TODO items from a prior review
- the API is not completely described
- there is no functioning example in the manual
- the tests provided do not run correctly
- they either crash or hang
- the prior library provided both a Charm and AMPI API.
- no documentation is provided for using this library with AMPI
- this library is thought to be interoperable with MPI from publication history, but no documentation is provided.
- it is known to work in production for OpenAtom, but we lack production tests for any part of the API not in use by OpenAtom.
Might be a good summer project, but current state appear to be days (possibly more depending on how much functionality is necessary) of effort away from production level.
#6 Updated by Justin Szaday almost 2 years ago
- The prior library's documentation notes that the AMPI API was 'not in CVS,' was it ever actually released?
- Should I try to address the TODO's in the documentation? If so, I would like to have a discussion with the relevant people so I can get a better idea of what the goal of some of these todo's originally was (mostly due to my lack of familiarity with this library).
- "Thought to be interoperable with MPI," does this just mean we need to verify it can be run in interopt mode or is more thorough testing required?