-mesh define(STPSZE, eval(InnerRadius/15)) spacing= STPSZE pxlow= eval(-1.1*OuterRadius) pylow= eval(-1.1*OuterRadius) pzlow = eval(-(GapLength/2+TaperLength+9e-2)) pxhigh= 0 pyhigh= 0 pzhigh= eval( (GapLength/2+TaperLength+9e-2))For the linecharge, we have to specify its total charge, its length, and the (x,y)-position where it shall travel. We also have to say that we do not want to compute eigenvalues, but we want to perform a time domain computation. We specify that at the lower and upper z-planes absorbing boundary conditions shall be applied. In the section
-time
, we specify that we want to have saved
the fields at 90 equidistant times between the time that the line charge
has traveled 0.1 m and it has traveled 1 m.
We edit our inputfile, such that the end of it looks as:
-eigenvalues solutions= 15 estimation= 2e9 # the estimated highest frequency # doit -fdtd -lcharge charge= 1e-12 sigma= eval(4*STPSZE) xposition= 0, yposition= 0 shigh= 1.5 showdata= yes return -ports name= beamlow , plane= zlow, modes= 3, npml= 40, doit name= beamhigh, plane= zhigh, modes= 3, npml= 40, doit return -time firstsaved= eval(0.1/@clight) lastsaved= eval(1/@clight) distancesaved= eval(0.01/@clight) return doitThe so edited inputfile can be found as "/usr/local/gd1/Tutorial-SRRC/doris05-wake.gdf". We start the computation by feeding gd1 the inputfile:
gd1 < doris05-wake.gdf | tee outThe computation only takes some minutes, since we compute a short range wake. When the time domain iteration starts, gd1 detects that the specified wake path is tangential to two magnetic walls. gd1 spits out:
## I am iterating Yee's algorithm.. ################### # wake-computation: # (x,y)-position of the line charge: # specified (x,y)-position : ( 0.00000000 , 0.00000000 ) # used (x,y)-position : ( 17.34723476e-18, 17.34723476e-18) # ix, iy : 60, 60 # min. distances : 17.34723476e-18 .. 17.34723476e-18 ############ I am checking the beam-path.. #-- charge travels at upper x-plane. #-- charge travels at upper y-plane. ######################### # Wake computation: # Since the charge travels along one or two symmetry-planes, # only 25 % of the charge is considered traveling through # the computational volume. # The excited fields in the subvolume will be the same as if # you where computing without the symmetry planes. # The lossfactors as computed by the post-processor will be # the same also. #########################The end of the output of gd1 (on a fast machine) is:
## I cannot find an excited port.. is this a wake computation? timestep= 800, simulated time= 6.2061e-09 s cpu time/sec: used: 97.81, since last call: 8.80, MFLOPs/s: 56.93 Wall clock time: 113.00 s, MFLOPs/s: 49.28 ## I cannot find an excited port.. is this a wake computation? timestep= 900, simulated time= 6.9819e-09 s cpu time/sec: used: 106.71, since last call: 8.90, MFLOPs/s: 58.71 Wall clock time: 122.00 s, MFLOPs/s: 51.35 ## I cannot find an excited port.. is this a wake computation? The highest simulation time is reached .., I am stopping ################################ # cpu-seconds for FDTD : 110 # start time : 12:15:38 # end time : 12:19:26 # date : 16/09/99 ## This is the normal end. Don't worry. ## Start the postprocessor to look at the results. stop FDTDLoop