1 / 17

Agata construction DataBase

Review of progress on Agata Construction Database infrastructure including barcodes, actions, and object registration. Discussions on barcodes, actions, and policies.

vpreece
Download Presentation

Agata construction DataBase

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agata construction DataBase Infrastructure Meeting C.Aufranc,O.Stezowski, 21/05/08

  2. Outlines • What has been done? • Snapshots of BigBrother • A common policy for BarCodes • Principle of Actions • Discussions

  3. What has been done? • BigBrother: the official Agata construction DataBase • Lyon Computing Center as Database location: test, and production database • CMS tool: few adaptations for Agata purpose except for barcodes • Conversion alphanumeric of the barcodes: under development and test, should be finished for Agata Week • Objects to insert in the database: based on the document of Gilbert Duchêne

  4. Structure of objects in the BD

  5. Registration of an object

  6. Transfer: need also a barcode

  7. Inventory: history of objects

  8. Assembly of a Crystal in a capsule

  9. Connection between 2 objects

  10. Available actions for an object

  11. Report for a specific center

  12. Bar codes • Necessary for objects and transfers • Cables are objects in the database • First proposal: the first digits are related to the Gilbert’s groups (Infrastructure, Detector Module, Data Processing, DAQ, Ancillary Detectors, Data Analysis), the following digits rely on each sub-system policy

  13. Labeling Tests (Andres Gadea)

  14. Actions • Actions in DB = measures on objects • Composite actions can be created • Actions have a status flag (reference, valid, notvalid), implication on objects: a faulty object cannot be assembled • Sheet paper to help you to define your own actions in regards of the BD:

  15. Necessary informations to define an action: • Action: name, version • Object: name, type, version • Description : a short description of the action • Results of the action: name, type, unit • Action composite? Yes/No • Input conditions of the test: value, unit , description • Tool : tool used in a particular center • Operator: name of the operator

  16. Example: • Action: RESOLUTION122keV, 1 • Object: CRYSTAL, *, * • Description: Gives the resolution of a crystal and its 36 segments for 122 keV • Results: resCrystal float, resSegments Array of 36 floats • Action composite? No • Input: 122, keV, Energy in keV • Tool: test • Operator: Cecile

  17. Discussions Current Status Policy of Barcodes Principle of Actions

More Related