Giter Club home page Giter Club logo

fastfouriertransform's Introduction

Fast Fourier Transform

Overall Description

Contains Serial and Parallel Version (openMPI) of the Fast Fourier Transform algorithm. Used to converts a signal from its original domain (often time or space) to a representation in the frequency domain and vice versa. A performance analysis was performed to show display execution time, speed-up, and efficiency.

Serial Code

Sequentially performs the FFT algorithm and records time. Execution time was recorded using the TimeSource.c and timer.h files.

*LOOK AT FFT-Serial Version.c

Parallel Code

Parallel implementation of the FFT written in C using openMPI. Execution time was recorded using MPI's time function MPI_Wtime().

*LOOK AT FFT-ParallelVersion.c

Master Process

The master process creates a table of real and imaginary numbers. The master process then distributes a portion of the table to each individual process. The master process then gathers all the calculated information from the slave processes. Then calculates the last part of the FFT which requires all the imaginary and real numbers to be summed. The master process is in charge of recording the execution time.

Slave Processes

The slaves processes recieves a portion of the table that hold imaginary and real values. The slave processes then perform the FFT algorithm on thier portion. This portion is later gathered by the master process.

Performance Analysis Breakdown

Execution Time

Execution time goes down with the more processors that are being utilized. The exeception is when number of processors is > 16. This is due to each node in the cluster that I used has 16 possible cores. When there is more than 16 processors the overhead of communication between nodes slows then execution down.

Speed-Up

Speedup is greatest when using the max amount of processes in a single node. In this case speedup is greatest using 16 proceses.

Efficiency

Efficiency decreases in these examples due to the relativly small size of the problem. In this case problem size never goes beyond 16384. Efficiency decreases due to each process spending more time waiting than computing. If the problem size was bigger then efficiency would increase due to each process spening more time computing than waiting.

fastfouriertransform's People

Contributors

brayzen403 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.