%TOC{title="Pixel Service Connectivity"

Connectivity Tables

The overall layout of the Pixel Connectivity is defined in a series of excell spreadsheets. They are inter-related, and changes to one will propogate the changes to the subsequent connectivity. It should be made clear that this can cause problems in that versioning is hard to track, as such, I include the 'version' in the title of the spreadsheets, and make explicit links to each. The versioned tables are in EDMS, and if in doubt, download a fresh set from EDMS and update them as you open. If you have an incorrect set (mis-matched versions) this update process will fail. The most important document is the Module to PP0 connectivity table (ATL-IP-ES-0092). This one table drives several others by way of a look-up table, specifically it drives ATL-IP-0093, ATL-IP-ES-0094, and ATL-IP-ES-0102, all of which can be uniquely mapped to PP0 postions thus are driven by ATL-IP-ES-0092. ATL-IP-ES-0104 is driven by '0094 (PP1 Type II Cables).

Modularity and Layout

The services of the Pixel Detector become rather complicated because of various system modularities. The goal of the layouts here is to help verify the above connectivity tables, and that they are routed to appropriate destinations. This also tries to take into account the installation order of the services, as to allow best access to various crates in racks. Currently, I'd like people to only verify that the services are going to the correct racks--crate layouts within the racks will be optimized later. Please feel free to add comments here, or mail them to me directly.

* DESTINATIONS.ppt: Work in Progress of Service Layout/Modularity

-- EricAnderssen - 09 Jun 2006