Coder Social home page Coder Social logo

impact's Introduction

IMPACT

Multiphysics application coupling toolkit

Version

Version 2.1.3

IMPACT follows semantic versioning. The version will be major.minor.patch. We will:

  • Increase the version for bug fixes, security fixes, and code documentation. Backwards compatible; no breaking changes.
  • Increase the minor version for new features and additions to the library’s interface. Backwards compatible; no breaking changes.
  • Increase the major version for breaking changes to the library’s interface or breaking changes to behavior.

Getting Started

To acquire IMPACT, you can clone it with the following command:

$ git clone https://github.com/IllinoisRocstar/IMPACT.git

Build Instructions

Dependencies

Make sure to apt install following before you start

  • build-essential
  • cmake
  • liblapack-dev
  • libblas-dev
  • libjpeg-dev
  • EITHER mpich OR openmpi
  • EITHER libcgns-dev OR libhdf4-dev

all of these can be obtained using linux apt-get install command.

Build IMPACT

NOTE Currently IMPACT is only tested with MPI compilers. Serial build is not recommended.

In the following, we assume $IMPACT_PROJECT_PATH is the path to the IMPACT directory, and $IMPACT_INSTALL_PATH is the desired installation location. Start the build process by executing:

$ cd $IMPACT_PROJECT_PATH
$ mkdir build && cd build
$ cmake -DCMAKE_INSTALL_PREFIX=$IMPACT_INSTALL_PATH .. 
$ make -j$(nproc)
$ make install

Executing the commands above will build all libraries and executables.

NOTE The CMake variables can also be set by using ccmake . from the build directory.

Testing IMPACT

To perform testing, be sure to turn on the ENABLE_TESTS CMake variable. This can be done by adding -DENABLE_TESTS=ON to the cmake command listed above, or by using the ccmake GUI. After enabling tests be sure to recompile and execute the following in the build directory:

$ make test

Currently most of the tests rely on CGNS input files, so only a fraction of the tests will run if IO_FORMAT=HDF4. The output of tests are captured in $IMPACT_PROJECT_PATH/build/testing/data. The testing framework also keeps a log of the test outputs in $IMPACT_PROJECT_PATH/build/Testing/Temporary directory. If tests fail seek output log in this directory for more details.

impact's People

Contributors

msafdari1234 avatar mtcam avatar agondolo avatar cswear avatar mjandersonir avatar michaelanthonyp96 avatar brianweisrocstar avatar

Watchers

James Cloos avatar  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.