Glast Database in Pisa
A practical solution
based on MSAccess
Luca Latronico
INFN Pisa
INFN-Pisa
Requirements and conventions
Requirements
from Proposal of conceptual design of the GLAST Tracker Construction Database
(UCSC – SLAC – INFN Pi – Hiroshima Un.) soon in CyberDocs
•
•
•
•
•
local independent DBs at various institutions
central SLAC DB for higher level data (i.e. production monitoring during construction)
interface between local DBs
local DB take care of data flow from local suppliers
web read-only access to local DBs
Naming Conventions
from Naming Convention for GLAST Tracker Construction and Tray Orientation in Tracker Tower – UCSC
• for each part unique ID + location
Part
Strip
Detector
Ladder
Tray
---
ID
S0123
DH00012
L0001
T123
---
location (example)
--• include ManID in ladders, trays
[A-D]
(L0001B) • enrich tray coding to include
[F0-B3]
(T123B2) type (superglast, top, bottom)
[G1tr0-G16tr18] (G03tr18)
--INFN-Pisa
MS Access
Pros
• availability (institutes, manufacturers)
• runs on Windows (manufacturers)
• built-in import/export of Office docs (e.g. Excel worksheets)
• familiar “look” (manufacturer)
• no extra cost (manufacturer)
• lots of wizards and predefined macros to speed up
programming and reporting
• SQL compliant
Cons
• limited workflow control (mandatory fields)
• limited web access
• web I/O possible in principle but ……
• forced to program in VB and ASP for web scripts
• very little insight into core of db
• no automatic backup
• no user access/action log file
evaluation prototype in use and under development
INFN-Pisa
System properties
• relational DB engine : MS Jet Access
• distributed on local NT network
• security : NT accounts/permissions + project accounts
• one data repository (back-end DB)
• distributed user interfaces (replicated)
• data and interface backups (replicated)
• manual backup by replicas synchronization tool
• web interface (queries/reports) connected to a data
server copy through ODBC DSN
• ASP scripts running on a test PWS (unstable)
• core data repository upgradeable to SQL Server for real
client/server architecture, if needed
INFN-Pisa
System architecture
Central repository
backup
DB Interface
Data
Production
and quality
monitoring
Web
client
data server
Data
Local replicas
DB Interface
Clean room
I/O
Data
DB Interface
Users offices
I/O
DB Interface
DB Interface
ODBC
ASP
(read-only)
INFN-Pisa
Data Transfer
Local Institute/Manufacturer
local
DB
export
SQL query
exchange
table
Pisa
Pisa
DB
exchange
DB
exchange
link
table
exchange
DB
ftp
exchange
table
import
SQL query
requests for manufacturers:
requests for institutes:
• MSAccess2000
• local DB supporting SQL and ODBC
• run export query
• set up a server (Pisa, SLAC)
• upload Pisa server
two working examples using Access as local DB:
• ladder assembly from local supplier
• TMCM from UCSC
INFN-Pisa
Relationship
INFN-Pisa
Main DB mask
INFN-Pisa
Example queries for SSD selection
test/production date selection
relevant parameters sort
example
V depletion selection
INFN-Pisa
Example Report I
Selected time
SSD statistics
INFN-Pisa
Example Report II
Ladders statistics
report content can be
exported to Excel for
further analysis
INFN-Pisa
Plans
• finalize data queries and periodic reports for monitoring
• translate queries and reports into scripts for remote
production monitoring
• install a full-functioning web server
• test web interface
• get feedback from users:
• improve interface
• check speed with much data
• write and test data queries for selection
• get feedback from tracker community
• agree on data transfer protocol
… local copy available on laptop …
INFN-Pisa