Controls Software Migration Status

1
Controls Software Migration Status
2
From My Introductory Talk

• Whos doing what
• Are the keeper assignments appropriate?
• Scheduling
• In what order should the applications be
  migrated?
• Testing
• How much is needed for each application?
• We need your input to answer them
• We cant get started without answers

3
Phase I Status

• No known issues in clib and phase 1 user
  libraries (15-June)
• Completed except for recently discovered issues
• Desktop changes, e.g., backspace and console
  startup, ready for division-wide deployment
  (15-June)
• Done, except possibly for documentation and the
  training of local admins

4
Phase I Status (cont.)

• No known issues in phase I applications, e.g.,
  D80, and services, e.g., PLD (1-July)
• Completed except for recently discovered issues
• Phase II tools completed, i.e., importing script,
  automated changes, and dependency information
  (1-July)
• Completed except for recently discovered issues,
  with the exception the dependency information
  which is still under construction

5
Phase I Status (cont.)

• All controls applications compiled, linked, and
  ready for testing (1-August)
• In progress.
• 52.7 of files are compiled
• Duplex windows design agreed to and implemented
  (1-September)
• In progress (need more feedback)

6
Who is Doing What

• Suspect Keepers 108 Applications (1700 7/5)
• 10 Controls
• 3 Antiproton Source
• 36 Proton Source
• 7 External beams
• 8 Recycler
• 9 Main Injector
• 20 Tevatron
• 15 Multiple affiliations
• 190 applications have been flagged obsolete

7
Scheduling

• A database exists which attempts to identify
  connections between applications
• Calls to chgpgm
• FSHARE
• Other file sharing
• Entries are still dominated by noise
• E.g. 364 applications are currently directly or
  indirectly connected to each other through chgpgm
  alone
• File sharing entries are also being revisited

8
Application Testing

• No work has been done!
• Need to devote a meeting to hashing out ideas?