1. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN Status of Gain Mapping at Duke

2. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN Status  Certification  Module M2.15 and M3.14 were used for Duke mapper certification.  Two sets of data were taken from each module and compared.  The detail results were reported (DUKHEP03-04-15, and DUKHEP03-06-10)  Slope correction is ~1% for M2.15 and ~1.5% for M3.14. The sign of the slope correction is opposite for unknown reason.  (dG 1 -dG 2 ) distribution is fitted and sigma of ~0.5% is obtained => repeatability: ~0.5%  Wirelist is consistent from one measurement to the other.  Data  PAW based (Linux or PC operating system)  All relevant HBOOK files and kumac files are at Duke ATLAS web page – download the files and run PAW  Detail plots can be easily made with kumac files

3. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN  Passport  Necessary plots can be easily produced including the required wirelist.  Data Base  We are working to simulate Hampton data structure in EDMS.

4. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN  M2.15 M3.14 1 st (left) and 2 nd (right) measurement1 st (*) and 2 nd (dashed) Gain variation (M2.15,M3.14)

5. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN dG 1 -dG 2

6. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN dG 1.vs. dG 2

7. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN Plan/Summary  We are ready to scan Type II and Type III modules.  M2.15 and M3.14 can be sent to CERN.  Can scan 2 modules/week  No immediate plan to scan modules at Duke, but…  What are our long range goal?  Need a well define procedure for the wirelist  Who, How?

8. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN Module Quality Assurance

9. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN Define Goal  The modules should not fail after assembly  Are we doing the right tests?  Revisit the procedures, specs. Are specs latest/attainable? –Module leak rate: 1 mb/b/min –Purging volume leak rate: 1 mb/min at 5 mb –Current draw: < 50nA/HV feed –No arcing –Number of dead straws: < 1% –Wirelist Is 8% cut for dG/G good enough? Should we restring the hung wires with dG/G > 5% (~250 micron offset)  Are the assembly procedures ‘safe’?  Meeting the assembly schedule  Assembly would start early 04 and ends early 05 based on the BSS and electronics schedule.

10. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN Offset.vs. dG/G F.Kaioumov, K.Kruger, S.Mouraviev, L.Vassilieva

11. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN

12. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN Readiness  Initial acceptance at Duke/IU  Very important for the rest  Slow but on track  Gain mapping  Picking up speed  Is producing the wirelist well defined? Who? How?  154 status  Fixtures are not complete  ~50% are ready –HV tester, MGM, and may have to duplicate some fixtures –data base  Not enough experts  Re-inventing wheels  No realistic time estimation in processing a module –Initial checking: 1 day –Tension test: 1 day –HV test (initial/final):1 day –Gain map (partial) & rework : 2 day –Leak Test:1 day –Contingency : 3 days  ~10 days/module

13. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN  Thoughts on 154  Bring up all necessary fixtures and exercise ASAP  Send experts and train  Get a written procedure for processing modules and test the procedure.  Good tracking mechanism of each module –Done-list, to-do-list  Any arriving trained person should be productive right away  Accommodate the travel limitation  Send modules in bulk  Set up a (web) schedule that people can sign up

14. Seog Oh/ Duke University/June, 2003 TRT/ ATLAS week at CERN How we proceed from here  Need to see the big picture including assembly  Many unknowns for assembly  Assembly is likely in “crunch” mode due to electronics and BSS schedule  Need contingency.. schedule/resources… the more, the better  Proceed with module processing in gain map and in 154 fast by concentrating resources  After September, there will be “freed resources” ->gain mapping and in 154  Let us concentrate resources in assembly  Proposal  Gain map at Hampton and Duke – 12 modules/month minimum  Increase resources in 154 after September to process >12/month