Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator...

19
Simulation Standards and Interfacing Aims: Do we need this at all? Define the accelerator description format Interfacing procedure (bds- detector, linac-bds,etc.) Common ILC repository

Transcript of Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator...

Page 1: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

Simulation Standards and Interfacing

Aims:

● Do we need this at all?● Define the accelerator description format● Interfacing procedure (bds-detector, linac-bds,etc.)● Common ILC repository

Page 2: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

Agenda

● Introduction. Accelerator description format (Agapov)● ILC Repository (Glen White)● Tools and Modeling for Collimator Studies (Andre Sopczak)● Detector-IR interfacing (John Carter)● Discussion

Sopczak

Page 3: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

Motivation

● Simulation tools: GEANT,MARS,STRUCT,MERLIN, BDSIM, MAD,DIMAD,TURTLE,.....● Integration of international collimation and background studies● Integration of repositories

Page 4: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

Where we are

● Optics repository SLAC● Detector description (Mokka), Mokka-Geant interface● Software repository Zeuthen (not complete)● Simulation database (QMUL)● Need for common accelerator specification

Page 5: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

Accelerator description format requirments

● Standard elements: drift, sbend, etc.● Inherit MAD functionality● Geometry specification● Field specification● Beam (and background) distribution specification● Run control

Page 6: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

XML option

1. David Sagan's AML http://www.lns.cornell.edu/~dcs/aml/

2. Nick Walker's specification

Page 7: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

XML example<?xml version="1.0" encoding="utf-8"?>

<?xml-stylesheet type="text/xslt" href="Accelerator-ML.xsl"?>

<?DOCTYPE Accelerator SYSTEM="Accelerator-ML.dtd"?>

<!-- Lattice definition-->

<AcceleratorDescription>

<Section name="FODO" l="10m" tag="FODO Cell">

<QF type="QFA" l="1m" k="1" aperture="10cm" tilt="0.1deg"></QF>

<Drift l="1m"></Drift>

<QD type ="QDXX"></QD>

<Drift l="1m"></Drift>

<QF></QF>

</Section>

<Accelerator>

<Section></Section>

</Accelerator>

</AcceleratorDesctiption>

Page 8: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

XML dtd

<?xml version="1.0" encoding="utf-8"?><!-- ---------------------------------------------- Accelerator markup language DTD Draft, (C) Ilya Agapov [email protected] ----------------------------------------------------><!-- --------- Entities --------- --><!ENTITY % bool "(true|false)"> <!-- --------- Accelerator definition --------- --> <!-- The root element. --><!ELEMENT AcceleratorDefinition (BeamLine+,Element+)><!-- Accelerator attributes--><!ATTLIST AcceleratorDefinition Name CDATA #REQUIRED

Page 9: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

XML

Problems● Not yet defined● No parser● Need to convert existing decks

Page 10: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

GMAD format

● Preserve (possibly) the MAD (MAD-X) lattice description● Take out some control commands● Provide some additional geometry- and material-related stuff● Provide drivers to geometry and field description formats (CAD)● flex/bison parser● Implemented in BDSIM● Can be changed to XML

Page 11: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

GMAD specification

Elements:<name> : <type>,attribute=<attr_val>, attribute=<attr_val>,...;Commands:include <filename>;use,period=<name>;...Beam parameters:beam, attribute=<attr_val>,...;

Options:option, attribute=<attr_val>,...;

Page 12: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

GMAD specification

Element types:marker,drift, sbend,rbend,quadrupole,sextupole,octupole, solenoid,multipole,coord_transform, rcol,ecol,elementCommands:use, gas, beam, sample

Page 13: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

GMAD example (atf 2)

include atf_optics.gmad;

include options.gmad;

beam, particle="e-", energy=1.5405110 * GeV, nparticles=1e+10, distrType="gauss",

sigmaX=0.01*mm, sigmaY=0.01*mm, sigmaXp=0.001, sigmaYp=0.001;

use ,period=ext;

sample, range = startl;

!sample, range = endl;

option,turnInteractions=1,ngenerate=100;

Page 14: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

GMAD example (continued)! standard options for bdsim

option, beampipeRadius = 10 * cm,

boxSize = 1.9 * m,

tunnelRadius= 2.0 * m,

beampipeThickness = 1 * cm,

chordStepMinimum = 0.0000000001 * m,

deltaIntersection = 0.00000001 * m,

deltaChord = 0.001 * m,

lengthSafety = 0.00001 * m,

thresholdCutCharged = 1 * MeV,

thresholdCutPhotons = 1 * KeV;

option,turnInteractions=1;

option,ngenerate=10;

Page 15: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

GMAD example (continued)! kickers ;

akick := 0.0025 ;!half-angle ;

ke1x_1 : sbend, l=0.25, angle=akick, e1=0, fint=0.5, fintx=0 ;

ke1x_2 : sbend, l=0.25, angle=akick, e2=2*akick, fint=0, fintx=0.5 ;

ke2x_1 : sbend, l=0.25, angle=akick, e1=akick, fint=0.5, fintx=0 ;

ke2x_2 : sbend, l=0.25, angle=akick, e2=akick, fint=0, fintx=0.5 ;

* * *

! sextupoles ;

lfftbsextupole := 0.1 ;

S2 : sextupole, l=lfftbsextupole/2, aper=(2.13*0.0254)/2 ;

S1 : sextupole, l=lfftbsextupole/2, aper=(1.38*0.0254)/2 ;

Page 16: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

GMAD example (continued)

colli : element,l=1*m,geometry="gmad:colli.geo", bmap="gmad:e1.bmap";

file colli.geo :

Tubs {

x0=0, y0=0, z0=0,

rmin=6, rmax=600, z=400

material="Al",

phi0=0,

dphi=360,

temperature=300

}

Page 17: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

GMAD open issues

● Wakefields● Taylor maps● Acceleration (time-varying field specification)● Interfacing to CAD tools

Page 18: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

Grid update

● VO 'ilc' supported – RHUL, QMUL, DESY● Software packages have to be installed on all nodes - suggestions?

Page 19: Simulation Standards and Interfacing Aims: ● Do we need this at all? ● Define the accelerator description format ● Interfacing procedure (bds-detector,

Goals ?