Tutorial 2
==========

1)  I-Desk demo
    =========== 
    Interactive Visualization of live 
    Cactus simulation running

    Meghan Thornton

2) Compiling and running on parallel machines
   ==========================================

    --- multi processor runs on Origin, NT Cluster, 
        Linux cluster

        Compile the Cactus WaveToy applications in
        parallel, and run on multiprocessors on the
        different architectures (origin, NT cluster
        and Linux cluster). The notes in the folders
        describe how to access and use these machines.

        Remember to checkout and compile only those
        thorns that you need, to reduce time. To 
        checkout the flesh use

        cvs -d :pserver:cvs_anon@cvs.cactuscode.org:/cactus login
	> anon

        cvs -z9 -d :pserver:cvs_anon@cvs.cactuscode.org:/cactus 
			checkout Cactus

        to checkout the thorns use the gmake script in
        the Cactus home directory

        gmake checkout

        and select all the wavetoy applications, that is
        select <applications> and then 1-3

        Run the testsuite to verify the code on each 
        architecture

    --- scaling studies on parallel configurations
 
	Run any parameter file from the wavetoy application 
        using different numbers of processors (check the load 
        first!), and different grid sizes (change the parameters
        driver::global_nx , driver::global_ny and
        driver::global_nz in the parameter file). Time the
        runs to see how changes to the grid size and/or the
        number of processors affect the run time. 
        Here you should be aware that the WaveToy application 
        is not computationally intensive.
 
3) Elliptic Solvers
   ================
 
    Checkout the packages CactusElliptic, CactusWave, 
    CactusPUGH, CactusPUGHIO and CactusBase using 

    gmake checkout     

    If PETSc or HDF5 are not available on your machine 
    remove them from the ThornList at compile time.

    Compile the code and run the parameter file in 
    CactusWave/IDScalarWaveElliptic/par to generate
    initial data for the wave equation from an elliptic
    equation. Edit the source code in 

    CactusWave/IDScalarWaveElliptic/src/SourceData.F77

    to change the tolerances and/or to use the petsc
    solver if it is available. These should be in 
    the thorn as parameters, but aren't at the moment.

4) Use of advanced tools
   =====================

   Adding thorn isosurfacer for live remote viewing
   and adding thorn http for remote login to running Cactus simulation

1. go to some empty directory, e.g.

  cd /tmp
  mkdir mydir
  cd mydir

2. get cactus (comment: cvs doesn't run on impact*.ncsa....)

impact15:/tmp/mydir $ setenv PATH /afs/ncsa/packages/.link/IRIX_6.2/bin:$PATH

impact15:/tmp/mydir $ cvs -d :pserver:cvs_anon@cvs.cactuscode.org:/cactus login

  (Logging in to cvs_anon@cvs.cactuscode.org)
   CVS password:  anon

impact15:/tmp/mydir $ cvs -d :pserver:cvs_anon@cvs.cactuscode.org:/cactus 
		    checkout Cactus


(from: http://www.cactuscode.org/Documentation/UsersGuide_html/node6.html )

3. go into newly created Cactus dir

impact15:/tmp/mydir $ cd Cactus

4. checkout cactus thorns

impact15:/tmp/mydir/Cactus $ gmake checkout

Checkout applications, arrangements or thorns? [arrangements] : arrangements

Available arrangements: 
  [1] CactusBase 
  [2] CactusEinstein 
  [3] CactusPUGH 
  [4] CactusPUGHIO 
  [5] CactusWave 
  [6] CactusElliptic (dev)
  [7] CactusNet (dev)
  [8] external (dev)

Checkout arrangements [1-8] : 1,3,4,5,7,8


Quit or checkout more applications, arrangements or thorns [quit] : 
All done!
impact15:/tmp/mydir/Cactus $ 

5. Create configuration

impact15:/tmp/mydir/Cactus $   gmake myconfig CC=cc CXX=CC
  
 Setup configuration myconfig (no)? 
yes


7. Compile cactus

impact15:/tmp/mydir/Cactus $ gmake myconfig   



===XXXXXXXXXXXXXXXXX===


8. Test thorn_http:

 Launch cactus with example parameter file:

impact15:/tmp/mydir/Cactus $ exe/cactus_myconfig arrangements/CactusNet/http/par/web.par 

And point Web Browser to

    http://impact15:7050/


9. Test thorn_Isosurfacer

Optional: (a) Launch Cactus from Amira
          (b) Launch Cactus manually and connect from Amira later

(a) 1. start Amira with cactus parameter file

  /afs/ncsa/packages/amira/current/bin/start arrangements/CactusPUGHIO/IsoSurfacer/
								par/isosurfacer.par

    2. Click on `isosurfacer.par' icon and add launch information,
       here: `Cactus Binary':

       /tmp/mydir/Cactus/exe/cactus_myconfig

    3. Launch! 

    4. Choose `IsosurfaceConnection' from context menu of `isosurfacer.par' file

    5. Click `Connect' button from the `IsosurfaceConnection'

    6. Choose `SurfaceView' from `IsosurfaceConnection' context menu

    7. enjoy!


    Note: 4. and 6. can be done before 3. and 5., too, but 3. must always precede 5.


(b) 1. Manual cactus startup with:

impact15:/tmp/mydir/Cactus $ exe/cactus_myconfig arrangements/CactusPUGHIO/IsoSurfacer/par/isosurfacer.par

    2. start Amira

   /afs/ncsa/packages/amira/current/bin/start 

    3. Create Amira Connection

    Edit --> Create --> "Connect to Isosurface"

    4. Click on object `IsosurfaceConnection'

    5. Connect

    6. Activate `SurfaceView' from Contextmenu of `IsosurfaceConnection' object

    7. enjoy!


    Note: 6. can be done before 5., too. 
          7. can be done always.