Changes between Version 3 and Version 4 of Piernik

Show
Ignore:
Timestamp:
03/09/13 11:50:33 (12 years ago)
Author:
mmamonski
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Piernik

    v3 v4  
    1111= The goal = 
    1212- couple using MUSCLE, why? 
    13  * the coupling is done one way (from MHD to MC), this brings a potential of introducing new level of parallelism (in curent code MHD and MC simulations are called one after another, sequentially) 
     13 * the coupling is done one way (from MHD to MC), this brings a potential of introducing new level of parallelism (in curent code MHD and MC simulations are called one after another, sequentially). TODO: figure 
    1414 * the MC is in process of GPU-enabling, one may want to run both modules on different heterogenous resources (i.e. MC on GPU cluster, base MHD code on Intel Nehalem cluster) 
    1515= Step By Step Guide = 
    … …  
    3939./setup mc_collisions_test -c gnufast -d HDF5,MUSCLE,MHD_KERNEL 
    4040}}} 
     41The `MUSCLE` and `MHD_KERNEL` stands for preprocessor defines as we want to keep the MUSCLE dependency conditional, we will use them later. 
     42= First Step - MUSCLE init = 
    4143