Index of /~dlr/g-2/gm2/mytest/kicker_upgrade_evaluation/robyn/development9_linux/multibunch/files

[ICO]NameLast modifiedSizeDescription

[PARENTDIR]Parent Directory  -  
[   ]beam_def.in2015-08-05 09:52 490  
[   ]beamfield.data2015-05-24 19:23 654K 
[   ]beamfield_39924.data2015-06-04 10:15 654K 
[   ]beamfield_39959.dat2015-06-07 07:12 654K 
[   ]beamfield_40852.data2015-07-28 11:52 720K 
[   ]beamfield_40962.data2015-08-14 14:58 3.2M 
[   ]cta_2085mev_xr40m_20101215_bs.lat2015-06-18 13:56 21K 
[   ]cta_2085mev_xr40m_20101215_bs.lat.digested1562015-06-24 08:20 1.9M 
[   ]fort.122015-08-05 09:53 6.5M 
[   ]fort.152015-08-05 09:53 37K 
[   ]fort.262015-08-05 09:53 36K 
[DIR]layout/2019-10-10 12:38 -  
[   ]periodic.lat2014-01-28 17:27 658  
[   ]q.sh2015-06-18 15:45 1.7K 


July 28, 2015

Data files generated by Ecloud program
Generally found at
 /home/critten/ecloud/jobs/job#####/beamfield.data

Copied to this directory as 
beamfield_#####.data

There is a header line (giving the number of bunches as 20, for example)
Then 10780 sets of:
  -one line gibin bunch number, time slice number, gaussian charge weight along bunch, etc
  -and then 49 lines giving x,y,Ex,Ey

The time goes from 0.0345ns to 266.432 ns because there are 20 bunches spaced b 14ns.
The first time slice for which the field is recalculated is 0.0345 ns from the front of the bunch and the last one is 0.432ns from the front of the bunch.

The field values are to be multiplied by 5.7e-12(mass/charge=9.1e-31/1.6e-19 kg/Coulomb) to get V/m

Some of the jobs have the beam at x=0.4mm, y=0. (That is why there is n x=0: the grid is centered on the beam, at x=0.4mm, y=0)

----------------------------------------------------
Run test_ecloud_ele 
 In response to query
  Give the name of the file (i.e. beamfield_#####.data)
 and then then number of the bunch of interest. If you want to
 see what the fields look like that bunch <nb> will see, type <nb>

The TEST_ECLOUD_ELE program
 - writes the Efield data for the specified bunch to fort.15
    Columns in fort.15 are
      xstep, ystep, x, y, Ex, Ey
    For each of 11 time slices
    The slices are separated by spaces so that gnuplot can distinguish which slice to plot

 - computes Efield data over a range of x,y,z (to test ecloud_ele)
    and writes to fort.12