DOCSLIB.ORG

Newsletter No

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Newsletter No International Committee for Future Accelerators Sponsored by the Particles and Fields Commission of IUPAP Beam Dynamics Newsletter No. 47 Issue Editor: I. S. Ko Editor in Chief: W. Chou December 2008 3 Contents 1 FOREWORD........................................................................................................11 1.1 FROM THE CHAIR ....................................................................................................11 1.2 FROM THE EDITOR ..................................................................................................12 2 LETTERS TO THE EDITOR – IN MEMORY OF ROBERT H. SIEMANN14 2.1 ROBERT H. SIEMANN – ENCOUNTERS AND ESSAYS ................................................14 2.1.1 Introduction ..................................................................................................14 2.1.2 Numerous Encounters ..................................................................................14 2.1.3 Memorial Essays ..........................................................................................17 2.1.4 References ....................................................................................................17 2.2 REMEMBERING BOB SIEMANN AS AN EARLY MENTOR ...........................................18 2.3 BOB SIEMANN AND MESON PRODUCTION BY POLARIZED PHOTONS .......................19 2.3.1 Introduction ..................................................................................................19 2.3.2 Polarization Dependence of Meson Photoproduction ..................................20 2.3.3 Construction, Characterization, and Use of the SLAC Polarized Photon Beamline.......................................................................................................22 2.3.4 References ....................................................................................................22 2.4 MEMORIES OF A MENTOR AND FRIEND – ROBERT H. SIEMANN ..............................23 2.4.1 Introduction ..................................................................................................23 2.4.2 Cornell Years................................................................................................23 2.4.3 Fermilab Sabbatical ......................................................................................25 2.4.4 Lasting Mentor and Friend ...........................................................................25 2.5 ROBERT H. SIEMANN: A PERSONAL TRIBUTE .........................................................26 2.6 IN MEMORY OF ROBERT SIEMANN..........................................................................29 2.7 SLC DAYS AT SLAC ..............................................................................................30 2.8 ESSAY FOR ROBERT H. SIEMANN............................................................................32 2.9 ROBERT H. SIEMANN AS LEADER OF AARD...........................................................33 2.9.1 Introduction ..................................................................................................33 2.9.2 Scientist, Colleague, and Collaborator .........................................................34 2.9.3 Professor .......................................................................................................34 2.9.4 Mentor .. .......................................................................................................35 2.9.5 Administrator................................................................................................35 2.9.6 Hobbyist .......................................................................................................35 2.9.7 Conclusion....................................................................................................36 4 2.10 SIEMANN TRIBUTE ..................................................................................................36 References ..............................................................................................................37 2.11 BOB SIEMANN’S CONTRIBUTIONS TO ADVANCED ACCELERATORS – A PERSONAL PERSPECTIVE...........................................................................................................38 References ..............................................................................................................40 2.12 BOB SIEMANN AND THE SPALLATION NEUTRON SOURCE: A REMEMBRANCE.........40 2.13 BOB SIEMANN AND PRST-AB ................................................................................42 2.14 HANDS ACROSS THE ATLANTIC ...............................................................................44 3 INTERNATIONAL LINEAR COLLIDER (ILC)............................................46 3.1 THIRD INTERNATIONAL ACCELERATOR SCHOOL FOR LINEAR COLLIDERS..............46 4 THEME SECTION: CONTROL SYSTEMS....................................................49 4.1 ACCELERATOR CONTROL SYSTEMS – A PERSONAL RECOLLECTION .......................49 4.1.1 Introduction...................................................................................................49 4.1.2 The TRIUMF Years......................................................................................49 4.1.3 A Community ...............................................................................................50 4.1.4 Collaboration - EPICS ..................................................................................51 4.1.5 The SSC ........................................................................................................52 4.1.6 The SNS........................................................................................................53 4.1.7 Conclusions...................................................................................................55 4.2 EPICS – EXPERIMENTAL PHYSICS AND INDUSTRIAL CONTROL SYSTEM.................56 4.2.1 Brief History .................................................................................................56 4.2.2 Architecture ..................................................................................................56 4.2.3 Process Database ..........................................................................................58 4.2.3.1 Record Processing..........................................................................58 4.2.3.2 Hardware Support ..........................................................................58 4.2.4 Software Interfaces .......................................................................................59 4.2.4.1 Driver Layer Interface....................................................................59 4.2.4.2 Record Type Support ......................................................................59 4.2.4.3 Channel Access Client Interface.....................................................60 4.2.4.4 Hardware Platforms.......................................................................60 4.2.5 Channel Access Clients and Operator Tools ................................................60 4.2.5.1 Services: Archiving.........................................................................61 4.2.5.2 Services: Alarming .........................................................................61 4.2.5.3 Services: Logging ...........................................................................61 4.2.5.4 Operator Tools: X-Window/Motif Based Applications ..................61 4.2.5.5 Operator Tools: Java Based Applications......................................61 4.2.6 Applications & Their Requirements.............................................................61 4.2.7 Robustness and Reliability ...........................................................................62 4.2.7.1 Robustness ......................................................................................62 4.2.7.2 Reliability........................................................................................63 5 4.2.7.3 Redundancy ....................................................................................63 4.2.8 Current Plans ................................................................................................63 4.2.8.1 EPICS Core: Java IOC ..................................................................63 4.2.8.2 New Directions in Channel Access ................................................64 4.2.8.3 Operator Tools ...............................................................................64 4.2.8.4 Web Based Applications.................................................................64 4.2.8.5 Services...........................................................................................65 4.2.9 Industrial Support .........................................................................................65 4.2.10 The EPICS Collaboration...............................................................65 4.2.11 Conclusions ....................................................................................66 4.2.12 References ......................................................................................66 4.3 THE TANGO CONTROL SYSTEM.....................................................................66 4.3.1 History ..........................................................................................................66 4.3.2 TANGO Philosophy .....................................................................................67 4.3.3 CORBA ........................................................................................................67
Load more

Recommended publications
  • Development of the Software Tools Using Python for Epics-Based Control System T
    TPPA16 Proceedings of ICALEPCS07, Knoxville, Tennessee, USA DEVELOPMENT OF THE SOFTWARE TOOLS USING PYTHON FOR EPICS-BASED CONTROL SYSTEM T. T. Nakamura, K. Furukawa, J-I. Odagiri, N. Yamamoto, KEK, Tsukuba, Ibaraki, Japan Abstract Basic functions of CA are get, put, and monitor In the commissioning phase of accelerators, many operations. List 1 shows an example of get operation of application programs are built and modified frequently by Python-CA. Module name of Python-CA is “ca”, which nonexpert programmers. Scripting language such as appears in import statement. Python is suitable for such quick development. Since List 1: Example of Python-CA (get operation) EPICS Channel Access interface library in Python was import ca developed in KEKB accelerator control system, many programs has been written in Python. We have been chan = ca.channel("channel_name") developing, providing some tools and libraries for Python chan.wait_conn() programming. Some of the recent developments in KEK chan.get() are reported, and possible applications are also discussed. ca.pend_event(1.0) value = chan.val INTRODUCTION KEKB is an asymmetric electron-positron collider at 8 Simple-CA library × 3.5 GeV/c, which is dedicated to B-meson physics. Its While Python-CA provides powerful functions of CA operation was started in December 1998. The KEKB client library, most people still feels complexity for CA accelerators control system has been constructed based on programming. List 1 show that even for single get EPICS (Experimental Physics and Industrial Control operation it needs 4 function (or method) calls. System) tool kit [1]. EPICS provides core mechanism for We have also developed Simple-CA library, which is a the distributed control system.
    [Show full text]
  • Cornell Gets a New Chair
    PEOPLE APPOINTMENTS & AWARDS Cornell gets a new chair Two prominent accelerator physicists and Cornell alumni, Helen T Edwards and her husband, Donald A Edwards, have endowed a chair in accelerator physics at Cornell.The chair is named after Boyce D McDaniel, pro­ fessor emeritus at Cornell. The first holder of the new chair is David L Rubin, professor of physics and director of accelerator physics at Cornell.The donors David Rubin is the first incumbent of the new Boyce McDaniel Chair of Physics at Cornell, asked that the new professorship should be endowed by Helen and Donald Edwards. The chair is named after Boyce D McDaniel. Left awarded to a Cornell faculty member whose to right: Boyce McDaniel, Donald Edwards, David Rubin, Helen Edwards and Maury Tigner, discipline is particle-beam physics and who director of Cornell's Laboratory of Nuclear Studies. would teach both graduate and undergradu­ ate students in addition to doing research. McDaniel, a previous director of nuclear ingthe commissioning of the Main Ring at Helen Edwards is a 1957 graduate of science at Cornell, was Helen Edwards' thesis Fermilab and providing advice for numerous Cornell, where she also earned her PhD in adviser. Initially a graduate student at Cornell, accelerator projects throughout the US, in 1966. She works at Fermilab and at DESY in he left during the Second World War to join the addition to his notable contributions to the Germany. She played a prominent role in the Manhattan Project and returned to complete accelerator and elementary particle physics construction of Fermilab'sTevatron and has his PhD, joining the faculty in 1946.
    [Show full text]
  • Vol25-Issue6.Pdf
    Vancouver Accelerator Conference Michael Craddock, Chairman of the Conference, and Accelerator Research Division Head at the TRIUMF Laboratory gives the opening address at the 1985 Particle Accelerator Conference in Vancouver. He and his colleagues are to be congratulated on the very smooth organization of such a large gathering. Anyone who contends that particle physics is conducted in an ivory tower, not contributing to other fields of science or to humanity at large, should have attended the 1985 Particle Accelerator Confer­ ence in Vancouver. Over a thou­ sand participants contributed 781 papers and only a fraction were actually related to accelerators for nigh energy physics. The majority of present developments are in the service of other fields of science, for alternative power sources, for medicine, for industrial applica­ tions, etc. Nevertheless, it is the spur of high energy physics that has dri­ ven accelerator technology along. As Burt Richter pointed out, in some fifty years since the first Cockcroft-Walton accelerators were built, accelerator physicists have increased peak machine energies by a factor of a million and have reduced the cost per GeV by a factor of over ten thou­ larly the machine diameter. ing problems, good cooling and sand. Conference Chairman Mike Though there are variants - with straightforward \)raddock rejoiced in his opening such as two-in-one (both beam ap­ manufacturing processes. Address that the contributions of ertures in a single yoke) or one-in- Paul Reardon reported on the al­ the accelerator community had one designs - there are essentially ternative high field type for which been so significantly recognized at two basic magnet types now un­ the initially separate proposals of the end of the last year with the der consideration.
    [Show full text]
  • Pure Labview Implementation of EPICS Communication Protocol
    Pure LabVIEW Implementation of EPICS Communication Protocol Alexander Zhukov Spallation Neutron Source, ORNL NIWeek 2012 Managed by UT-Battelle for the Department of Energy What is EPICS Experimental Physics and Industrial Control System (EPICS) is a set of Open Source software tools, libraries and applications developed collaboratively and used worldwide to create distributed soft real-time control systems for scientific instruments such as a particle accelerators, telescopes and other large scientific experiments. Major collaborators – ANL – LANL – ORNL (SNS) – SLAC (SSRL, LCLS) – JLAB (CEBAF) – DESY – BESSY – PSI (SLS) – KEK Runs on variety of hardware/OS (Linux, VxWorks, Windows, Mac, RTEMS…) 2 Managed by UT-Battelle for the Department of Energy How EPICS works A network based fully distributed client/server model Client and server use Channel Access (CA) protocol to communicate Everything spins around process variables (PV) – an entity similar to LabVIEW network shared variable – A server (Input Output Controller – IOC) publishes data by updating PVs – PV corresponds to some value (measurement, setting, status etc) – Every PV has unique name – Client has ways to read PVs and update them over network – Client can subscribe to particular PV and monitor its value or state without polling it Standard EPICS server also has records processing mechanism – Control logic is programmed in records definition file – Allows perform routine tasks without explicitly programming in C – In addition to value every record has also status (OK,
    [Show full text]
  • EPICS Application Developer's Guide
    1 EPICS Application Developer’s Guide EPICS Base Release 3.15.0.2 17 October 2014 Andrew N. Johnson, Janet B. Anderson, Martin R. Kraimer (Argonne National Laboratory) W. Eric Norum (Lawrence Berkeley National Laboratory) Jeffrey O. Hill (Los Alamos National Laboratory) Ralph Lange, Benjamin Franksen (Helmholtz-Zentrum Berlin) Peter Denison (Diamond Light Source) 2 Contents EPICS Applications Developer’s Guide1 Table of Contents 7 1 Introduction 9 1.1 Overview.................................................9 1.2 Acknowledgments............................................ 11 2 Getting Started 13 2.1 Introduction................................................ 13 2.2 Example IOC Application........................................ 13 2.3 Channel Access Host Example...................................... 15 2.4 iocsh.................................................... 16 2.5 Building IOC components........................................ 16 2.6 makeBaseApp.pl............................................. 19 2.7 vxWorks boot parameters......................................... 22 2.8 RTEMS boot procedure.......................................... 23 3 EPICS Overview 25 3.1 What is EPICS?.............................................. 25 3.2 Basic Attributes.............................................. 26 3.3 IOC Software Components........................................ 26 3.4 Channel Access.............................................. 28 3.5 OPI Tools................................................. 30 3.6 EPICS Core Software..........................................
    [Show full text]
  • EPICS at Fermilab: Not Just D0 Anymore - Cavities, Cavities, Cavities
    EPICS at Fermilab: Not just D0 anymore - Cavities, Cavities, Cavities Geoff Savage for the Dzero and ILCTA controls groups Wed June 14, 2006 EPICS Collaboration Meeting Current EPICS Projects Run II Experiments D0 Controls. ILC Test Accelerator (ILCTA) @ FNAL Cavity testing in three facilities, maybe a fourth Horizontal Test Facility/Coupler conditioning (MDB) Run tests in August 2006 Vertical Test Facility (IB1) Getting started Beam test (NML) using photoinjector currently at A0 Preparing facility - cryo installed at the end of 2007 Other Proton Driver – EPICS only control system Nova – Seriously evaluating EPICS as control system for DAQ. Maybe also for controls itself? 6/14/2006 EPICS Collaboration Mtg 2 D0 Detector Increased luminosity in Run IIb Just finished detector upgrade Silicon layer 0 Enhanced triggering systems Goals for controls Support new field busses Remove 68k processors from system Move to EPICS 3.14.8.2 Controls - all EPICS all the time DAQ controls are independent 6/14/2006 EPICS Collaboration Mtg 3 D0 Controls Two new field buses CANbus driver wrapped in ASYN TPMC816 - dual channel PMC CANbus module Implements limited CANbus feature set Raw ethernet driver in ASYN Linux IOC connected via fiber to remote crate Trying to get to 3.14.8.2 Tested but not deployed Currently using 3.14.6 and 3.13.4 MVME5500 processors Remove remaining 68k processors ~ 25 Some problems - similar experiences? 6/14/2006 EPICS Collaboration Mtg 4 ILCTA Controls Systems ACNET (FNAL) Accelerator Division Drivers/interfaces for FNAL devices already written and in use at Fermilab in ILCTA (HRM) EPICS (ANL) Cryogenics interface for MDB and NML.
    [Show full text]
  • REALIZATION of LINUX PLATFORM in DISTRIBUTED CONTROL SYSTEM by EPICS at BEPCII Zhuo Zhao, C.H.Wang, Ge Lei, J.J.Zhao, K.J.Yue, Jia Liu, IHEP, Beijing, China
    Proceedings of ICALEPCS2003, Gyeongju, Korea REALIZATION OF LINUX PLATFORM IN DISTRIBUTED CONTROL SYSTEM BY EPICS AT BEPCII Zhuo Zhao, C.H.Wang, Ge Lei, J.J.Zhao, K.J.Yue, Jia Liu, IHEP, Beijing, China Abstract also has friendly operating interface and it supports IHEP will begin the BEPCII project that has been software transplanting. funded by the Chinese Government in order to further At present, Red Hat Linux has developed release 9. So I upgrade the BEPC (Beijing Electron Positron Collider) select the latest release-Red Hat Linux 9 as the operating which has operated since 1989 [1]. As a part of this system that is installed on PC [4]. updating project, control system is decided to use EPICS The installing of ftp server and downloading of [2]. EPICS IOCs can run on many kinds of operating systems [3], for example VxWorks, Unix, Linux, VxWorks kernel Windows, RTEMS and so on. Based on the idea of After the Red Hat Linux 9 has been installed on one creating EPICS OPI on Linux and downloading real-time PC, ftp server should be also installed and started. The ftp database to VME IOC target board, this article is mainly server that I select is vsftpd whose “.rpm” instalation file about how to setup EPICS base and EPICS extension on is included in the Red Hat Linux 9’s installation Linux operating system and furthermore how to finish CDROM. communication between server and Linux control The VxWorks boot file should be in the special platform. In order to come into being a friendly directory in order to download VxWorks kernel.
    [Show full text]
  • Building EPICS Software
    Building EPICS Software Andrew Johnson and Tim Mooney AES/SSG Outline ■ Build Base 3.14.12.5 ● Architectures: Linux, VxWorks ● Test by creating the makeBaseApp example ■ Build Extensions ● Build msi, MEDM, StripTool ■ Build Support Modules ● Sequencer, Asyn ■ Build synapps 5.8 ■ Build xxx as separate top 03/16/15 Base 3.14.12.5 ■ Actually Base 3.14.12.5-rc1 since the final release is not yet out ■ Website: http://www.aps.anl.gov/epics/base/R3-14/12.php ■ Download: http://www.aps.anl.gov/epics/download/base/baseR3.14.12.5-rc1.tar.gz ■ Prerequisites: GNU Make, Perl, C and C++ compilers (GCC) ● Many Linux distributions install these by default or as a single ● Optional: GNU readline developer package, recommended □ RPM: readline-devel DEB: libreadline-dev 03/16/15 Extensions ■ Extensions Configure files (R3.14) ● Website: http://www.aps.anl.gov/epics/extensions/configure/index.php ● Download: http://www.aps.anl.gov/epics/download/extensions/extensionsTop_20120904.tar.gz ● Prerequisites: EPICS Base ■ MSI – Macro Substitution and Include ● Website: http://www.aps.anl.gov/epics/extensions/msi/index.php ● Download: http://www.aps.anl.gov/epics/download/extensions/msi1-6.tar.gz ● Prerequisites: Extensions Configure 03/16/15 Extensions: Motif Clients ■ MEDM ● Website: http://www.aps.anl.gov/epics/extensions/medm/index.php ● Download: http://www.aps.anl.gov/epics/download/extensions/medm3_1_9.tar.gz ● Prerequisites: Developer packages for OpenMotif, libXmu, libXp, libXpm, libXext, libX11 □ DEB: libmotif-dev, x11proto-print-dev, libxmu-dev, libxp-dev,
    [Show full text]
  • Matlab Objects for Epics Channel Access
    Proceedings of ICALEPCS2013, San Francisco, CA, USA MOPPC146 MATLAB OBJECTS FOR EPICS CHANNEL ACCESS J. Chrin, Paul Scherrer Institut, 5232 Villigen PSI, Switzerland Abstract • Improved CA reconnection management to ensure With the substantial dependence on MATLAB for appli- stability and robustness in every eventuality. cation development at the SwissFEL Injector Test Facility • Compilation on 64-bit Linux architectures. (SITF), the requirement for a robust and more extensive EPICS (Experimental Physics and Industrial Controls Sys- In the meantime and per contra, a new C++ CA inter- tem) Channel Access (CA) interface became increasingly face library, CAFE [9], has recently been developed in- imperative. To this effect, a new MATLAB Executable house that provided the required underlying functionality. (MEX) file has been developed around an in-house C++ Since CAFE further sought to act as a CA host library to CA interface library (CAFE), which serves to expose com- scripting and domain-specific languages, the development prehensive control system functionality to within the MAT- of bindings to MATLAB presented itself as a natural exten- LAB framework. Immediate benefits include support for sion. To achieve this necessitated gaining knowledge and all MATLAB data types, a richer set of synchronous and experience in the use of the MATLAB C Application Pro- asynchronous methods, a further physics oriented abstrac- gramming Interface (API). A dynamically loadable MAT- tion layer that uses CA synchronous groups, and compila- LAB Executable (MEX) file could then be constructed that tion on 64-bit architectures. An account of the MOCHA would allow CAFE routines to be called from within the (MATLAB Objects for CHannel Access) interface is pre- MATLAB framework, in the same manner as MATLAB sented.
    [Show full text]
  • Argonne Slides
    Using APS iocappsTools Andrew Johnson, AES-SSG Outline ■ What are the iocappsTools ■ APS Accelerator IOC standards ● asdstd Support Module ● IRMIS and AOIs ■ Tools covered in this lecture ● iocHelp ● iocConsole ● capr and pvExist ● iocBoot, iocBootChange ● iocBsp, iocModules, iocFindSupport ● pvUsage ● iocNetwork ● iocErrorLog ● aoiExist and aoiMedm APS EPICS Training — 2015-03-27 — Using APS iocappsTools 2 The iocappsTools ■ EPICS Extension ■ Provides scripts for querying, configuring and interacting with IOCs ■ Most were designed for the APS Accelerator IOCs ● IOCs must use the asdStd module to provide data for the scripts to use ● Scripts rely on the /usr/local/iocapps file-system layout, IRMIS database etc. □ The file-system path can often be changed by setting an environment variable ● In most cases operations can cover multiple IOCs APS EPICS Training — 2015-03-27 — Using APS iocappsTools 3 iocHelp ■ Alias for iocappsHelp ■ Prints a summary list of the other scripts and what they do tux% iocHelp iocapps tools: aoiExist Print AOI names containing a specified string or AOI names of an EPICS record containing a specified string aoiMedm Execute and/or list top medm displays for a specified AOI or for the AOI of a specified EPICS record capr A channel access version of "dbpr" caclients Displays information about local CA clients ctllog Information on the e-mail list-server used as the Controls Group "Knowledge Base" iocappsHelp List all iocapps tools iocBoot Print bootparams and bootlog messages iocBootChange Change vxWorks bootstrap
    [Show full text]
  • World Year of Physics Opens with Paris Conference by Ernie Tretkoff the World Year of Physics Was Jose Luis Moran-Lopez, Director Developing Nations
    NEWS February 2005 Volume 14, No. 2 A Publication of The American Physical Society http://www.aps.org/apsnews World Year of Physics Opens with Paris Conference By Ernie Tretkoff The World Year of Physics was Jose Luis Moran-Lopez, director developing nations. In one session, officially launched at the conference of the ISTR San Luis Potosi in Mexico, Katepalli Sreenivasan of the Inter- “Physics for Tomorrow,” which took described a project called “Science national Center for Theoretical place in Paris at UNESCO headquar- for everyone,” a series of books writ- Physics in Trieste, Italy, talked about ters January 13-15. Speakers and ten by active Mexican scientists physics and development. He participants addressed issues such aimed at the high school and college pointed out some of the vast dif- as the public perception of physics level. There are also contests that in- ferences between the developed and how physics can help solve vite students to read one of the world and the developing nations, social and economic problems. books and do a project or report including the availability of About 1000 participants, includ- based on their reading, he said. internet access. Without access to ing approximately 500 students from Also during the round table the latest information, it is difficult over 70 countries, attended the con- discussion, Pierre Lena, vice presi- to practice science, he said. “We ference. Eight Nobel laureates spoke dent of the Association Bernard live in a connected world, but yet on a variety of topics ranging from Gregory, said that many students See WYP PARIS on page 10 biophysics to nanoscience to physics believe that science is out of reach education in lectures aimed at high- for them.
    [Show full text]
  • John W. Dewire
    John W. DeWire June 12, 1916 — September 17, 1990 John W. DeWire has left an indelible imprint on Cornell. Arriving in 1947, he became one of the most influential and respected members of the Physics Department. He was one of the earliest members of the Laboratory of Nuclear Studies and was instrumental in its development into international leadership in high energy physics. In 1983 he was appointed University Ombudsman, a position he filled with great distinction until 1988, two years after his retirement, when ill health forced his resignation. John was born in Milton, Pennsylvania in 1916, received a B.S. degree from Ursinus College in 1938 and a Ph.D. degree from Ohio State University in 1942. In 1979 he was awarded an honorary D.Sc. degree from Ursinus College. After receiving his doctoral degree, John worked on scientific projects connected with the war effort. He joined Robert R. Wilson at Princeton University on a uranium isotope separation project. In March 1943 he accompanied Wilson to Los Alamos where he measured various nuclear properties required for the design of nuclear weapons. One of the most important of these was the measurement of the neutron multiplication constant for neutron induced fission in uranium. He also participated in measuring the neutron growth rate in the first nuclear explosion at the Trinity test site in New Mexico. In 1946 John joined the newly established Laboratory of Nuclear Studies at Cornell as a research associate. In 1947 he was appointed to the Physics Department faculty. He was an active player in the life of the department.
    [Show full text]