accelerate-examples: Examples using the Accelerate library

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.

[maintain] [Publish]

Warnings:

'ghc-options: -O2' is rarely needed. Check that it is giving a real benefit and not just imposing longer compile times on your users.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.
'ghc-prof-options: -fprof*' profiling flags are typically not appropriate for a distributed library package. These flags are useful to profile this package, but when profiling other packages that use this one these flags clutter the profile output with excessive detail. If you think other packages really want to see cost centres from this package then use '-fprof-auto-exported' which puts cost centres only on exported functions. Alternatively, if you want to use this, make it conditional based on a Cabal configuration flag (with 'manual: True' and 'default: False') and enable that flag during development.

Example programs using the Accelerate library. The aim is for this package to evolve and be useful for both performance and regression testing.

Refer to the main Accelerate package for more information: http://hackage.haskell.org/package/accelerate

[Skip to Readme]

Properties

Versions	0.2.0.0, 0.2.0.1, 0.12.0.0, 0.12.1.0, 0.13.0.0, 0.14.0.0, 0.15.0.0, 0.15.1.0, 1.0.0.0, 1.1.0.0, 1.2.0.0, 1.2.0.1, 1.3.0.0, 1.3.0.0
Change log	None available
Dependencies	accelerate (>=1.3 && <1.4), accelerate-examples, accelerate-fft (>=1.3), accelerate-io (>=1.3), accelerate-io-bmp (>=0.1), accelerate-io-repa (>=0.1), accelerate-io-vector (>=0.1), accelerate-llvm-native (>=1.3), accelerate-llvm-ptx (>=1.3), aeson (>=0.8), ansi-wl-pprint (>=0.6), array (>=0.5.2), base (>=4.7 && <5), binary (>=0.7), bmp (>=1.2), bytestring (>=0.9), bytestring-lexing (>=0.5), cereal (>=0.3), colour-accelerate (>=0.1), containers (>=0.5), criterion (>=1.0), criterion-measurement (>=0.1), directory (>=1.1), fclabels (>=2.0), filepath (>=1.0), gloss (>=1.7), gloss-accelerate (>=2.0), gloss-raster-accelerate (>=2.0), gloss-rendering (>=1.9), HTTP (>=4000.2), http-types (>=0.8), HUnit (>=1.2), lens-accelerate (>=0.1), linear-accelerate (>=0.3), matrix-market-attoparsec (>=0.1), mwc-random (>=0.8), mwc-random-accelerate (>=0.1), network (>=2.5), normaldistribution, process (>=1.0), QuickCheck (>=2.7), random, repa (>=3.1), repa-io (>=3.1), scientific (>=0.3), statistics (>=0.13), template-haskell (>=2.2), test-framework (>=0.5), test-framework-hunit (>=0.3), test-framework-quickcheck2 (>=0.2), text (>=0.11), time (>=1.4), vector (>=0.7), vector-algorithms (>=0.4) [details]
License	BSD-3-Clause
Author	The Accelerate Team
Maintainer	Trevor L. McDonell <trevor.mcdonell@gmail.com>
Category	Accelerate
Home page	https://github.com/AccelerateHS/accelerate-examples
Bug tracker	https://github.com/AccelerateHS/accelerate/issues
Source repo	head: git clone https://github.com/AccelerateHS/accelerate-examples this: git clone https://github.com/AccelerateHS/accelerate-examples(tag v1.3.0.0)
Uploaded	by TrevorMcDonell at 2020-08-28T10:58:55Z

Modules

Data
- Array
  - Accelerate
    - Examples
      - Data.Array.Accelerate.Examples.Internal

Flags

Automatic Flags

Name	Description	Default
gui	Enable gloss-based GUIs, where applicable. If not enabled, the application always runs in benchmark mode.	Enabled
ekg	Enable EKG remote monitoring server at http://localhost:8000	Enabled
codespeed	Enable upload of results to benchmark server	Disabled
llvm-cpu	Enable the LLVM backend for multicore CPUs	Enabled
llvm-ptx	Enable the LLVM PTX backend for NVIDIA GPUs	Enabled
smvm	Sparse-matrix vector multiplication benchmark	Enabled
crystal	A visualisation of a sum of waves in a plane	Enabled
tunnel	The slit-scan effect creating a Doctor Who time vortex	Enabled
canny	Canny edge detection benchmark	Enabled
mandelbrot	A Mandelbrot fractal benchmark	Enabled
julia	An interactive julia-set simulator	Enabled
fluid	An interactive particle-based fluid simulation	Enabled
nbody	Simulation of gravitational attraction between solid particles	Enabled
smoothlife	A cellular automata simulation	Enabled
hashcat	A "password recovery" application for MD5 cracking	Enabled
fft	Simple FFT-based high/low-pass image filtering	Enabled
pagerank	Implementation of the PageRank algorithm	Enabled
quicksort	Implementation of the QuickSort algorithm	Enabled
ray	A simple real-time ray tracer	Enabled
kmeans	An implementation of k-means clustering in a plane	Enabled

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

accelerate-examples-1.3.0.0.tar.gz [browse] (Cabal source package)
Package description (as included in the package)

Maintainer's Corner

Package maintainers

ManuelChakravarty, TrevorMcDonell

For package maintainers and hackage trustees

edit package information

Readme for accelerate-examples-1.3.0.0

[back to package description]

Example programs using Accelerate

Example programs using the Accelerate library. The aim is for this package to evolve and be useful for both performance and regression testing.

Contributions and bug reports are welcome!
Please feel free to contact me through GitHub or gitter.im.

Installation

External dependencies

Installation of accelerate-examples and its dependencies requires several external packages. You may need to adjust the package names or versions slightly for your system.

Ubuntu/Debian (apt-get):
- llvm-9-dev
- freeglut3-dev
- libfftw3-dev
Mac OS (homebrew)
- fftw
- libffi
- llvm-hs/homebrew-llvm/llvm-9

If you want to use the CUDA GPU enabled backend accelerate-llvm-ptx, you will also need to install the CUDA toolkit for your system. You can find an installer on NVIDIA's website here:

https://developer.nvidia.com/cuda-downloads

Building: stack

For development, the recommend build method is via the stack tool. This will simplify pulling in dependencies not yet on Hackage. For example, to build using ghc-8.10:

ln -s stack-8.10.yaml stack.yaml    # only once
stack build                         # or, 'stack install' to install the executables globally

Before building, you may want to edit the stack.yaml file to change the build configuration. In particular, the flags section at the bottom can be used to enable or disable individual example programs and accelerate backends, as well as features such as monitoring and debug output.

Adding new backends

Adding support for new Accelerate backends should require only a few minor additions to the cabal file and the module 'Data.Array.Accelerate.Examples.Internal.Backend'.