Engineering topics

Himel, T

Publications and source records attributed to Himel, T.

3 records

DOE OSTI2011

Parameters for the PEP-II B-Factory at SLAC in 2008

The PEP-II B-Factory at SLAC (3.1 GeV e{sup +} x 9.0 GeV e{sup -}) operated from 1999 to 2008, delivering luminosity to the BaBar experiment. The design luminosity was reached after one and a half years of operation. In the end PEP-II surpassed, by four times, its design luminosity reaching 1.21 x 10{sup 34} cm{sup -2}s{sup -1}. It also set world stored beam current records of 2.1 A e{sup -} and 3.2 A e{sup +}. Continuous injection was implemented with BaBar successfully taking data. The total delivered luminosity to the BaBar detector was 557.4 fb{sup -1} spanning five upsilon resonances. PEP-II was constructed by SLAC, LBNL, and LLNL with help from BINP, IHEP, the BaBar collaboration, and the US DOE OHEP.

43 PARTICLE ACCELERATORS↗

DOE OSTI2011

Network Upgrade for the SLC: PEP II Network

The PEP-II control system required a new network to support the system functions. This network, called CTLnet, is an FDDI/Ethernet based network using only TCP/IP protocols. An upgrade of the SLC Control System micro communications to use TCP/IP and SLCNET would allow all PEP-II control system nodes to use TCP/IP. CTLnet is private and separate from the SLAC public network. Access to nodes and control system functions is provided by multi-homed application servers with connections to both the private CTLnet and the SLAC public network. Monitoring and diagnostics are provided using a dedicated system. Future plans and current status information is included.

43 PARTICLE ACCELERATORS↗

DOE OSTI2011

Network Upgrade for the SLC: Control System Modifications

Current communications between the SLAC Linear Collider control system central host and the SLCmicros is built upon the SLAC developed SLCNET communication hardware and protocols. We will describe how the Internet Suite of protocols (TCP/IP) are used to replace the SLCNET protocol interface. The major communication pathways and their individual requirements are described. A proxy server is used to reduce the number of total system TCP/IP connections. The SLCmicros were upgraded to use Ethernet and TCP/IP as well as SLCNET. Design choices and implementation experiences are addressed.

43 PARTICLE ACCELERATORS↗