Lattice Function Database - Fermilab
Lattice Function Database
Table Definitions
Elliott McCrory
Friday, November 18, 2005
Introduction
The attached Excel spreadsheet defines the tables that are necessary to implement the lattice function database, as outlined in the requirements document, BeamDocs #1969. This document gives an informal definition of these tables.
Table: Lattices
This table contains the actual numbers for the lattice functions. One record corresponds to the following lattice function:
• One location (e.g., a BPM or a flying wire)
• One machine (e.g., the Tevatron at step N of the squeeze, or the Main Injector at 8 GeV, etc.)
• One time period (e.g., it is valid from 2004-Jan-01 through 2005-Mar-15)
• All lattice functions (e.g., X and Y) at that point.
• Full, coupled lattice functions.
There will be one record for every location, for every machine, for every time period that is of interest. To retrieve a record, you must provide the following information:
1. The location (see table NameTranslation),
2. the machine,
3. and the time.
Table: NameTranslation
The locations in the Lattices table must be unique for each machine. The preferred names that you may have probably do not correspond to the names given to the locations in the Lattices table. This table allows a specific client to create its own names for the records in the Lattices table. For example, it is imagined that one client would be “ACNET”, which would correspond to the ACNET names (“T:ABCDEF”) for the locations in table Lattices.
An SQL statement to retrieve the lattice function for the location you want might look like this:
SELECT BetaX1,Qx FROM Lattices,NameTranslation where Lattices.SlotNumber=NameTranslation.SlotNumber AND Client=”MyStuff” AND ClientName=”MyUniqueDeviceName_4223”;
There is also a column that will allow a client to define the type of device this location is. For example, a BPM or a dipole corrector could be specified in this manner. For example:
SELECT BetaX1,Qx from Lattices,NameTranslation where where Lattices.SlotNumber=NameTranslation.SlotNumber AND Client=”MyStuff” AND DeviceType=”BPM”
Table: Clients
This table simply provides ownership information on the clients that are specified in table NameTranslation.
Table: ChangeLog
This table provides a tracking mechanism for changes in the lattice database. It is assumed that the changes will be web-enabled, and the the ability to change a record or to add a new record will be authorized by a Kerberos Ticket, as described in A. Petrov’s BeamDocs #1502 and #1987.
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- data conversion plan template hhs
- osi issue and action item tracking process
- a survey of spreadsheet users
- lattice function database fermilab
- p7470 data governance documentation policy
- ict igcse practical paper 2 revision for database
- ms excel mcq quiz set 1
- database specifications template hud
- template for developing sewer collection system preventive
- user s manual template radford
Related searches
- function and function notation problems
- excel database function list
- database analyst vs database administrator
- function and function notation
- lattice fpga tutorial
- database developer vs database architect
- database engineer vs database administrator
- function keys function windows 10
- function of a function math
- function of a function calculator
- function inside a function python
- function not a function worksheet