Why Am I Here

1
Why Am I Here

• ODS collaborating with ESE in some initial BTeV
  projects
• Software for the test beam
• Software for the pixel module
• Trigger microcode
• Ongoing SVX Diagnostic Work with CDF and ESE
• Tools/architecture for debugging VME based boards
• Future
• Real time OS evaluations
• Interest in BteV DA
• Solicit Your Needs to Help Define Our Work
• What kind of software are people writing now?
• What tools are you using?
• Where do you need help?

2
(No Transcript)
3
Pixel Software Layout
Unix Node
VxWorks Node
4
Pixel Test Stand

• Where we were a a few years ago - written by
  Harvard for SVX Test Beam
• Will be used to test FPIX0 and FPIX1 chips
• VME Based using VxWorks
• Data read out across the VME backplane and sent
  up to a UNIX host via Ethernet using an RPC
  Protocol
• Control/monitoring over Ethernet
• Not particularly portable to other configurations
• not using standard software for vme accesses
• doesnt lend itself to adding new boards easily

5
Characterization of pixel module

• Using Labview
• GPIB bus - most device drivers already written
  for logic analyzers etc.

6
(No Transcript)
7
SVX Diagnostic Software Layout
Unix Node
NT Node
VxWorks Node
8
SVX Diagnostic Software

• Written by YALE, CDF, and ODS
• Data sent over ATM switch (in real DA)
• Control/monitoring still over Ethernet using
  Corba
• More portable because of standards
• uses Fision for VME accesses
• cdfvme for underlying test framework and vme
  board construct
• Development environment is unix and NT based
  using C (server code), Java (client), VxWorks
  (OS)
• Look and feel of software the same (show some
  pictures), but implementaion much different
• GUI is in java and jfc (swing).

9
SVX Diagnostic User Interface
10
SVX Diagnostic User Interface

11
SVX Diagnostic User Interface

12
SVX Diagnostic User Interface

13
CDFVME

• Software library and template for a generic VME
  test stand
• fell out of SVX diagnostic work, currently used
  by 10 different subsystems at CDF.
• Supports debugging n boards in m crates, although
  1 board in 1 crate is the normal case.
• Contains test manager software to run series of
  tests in batch
• Built on
• fision - for vme accesses
• robin for CORBA implementation
• java/jfc for client code
• Theoretically, client can run everywhere since
  Java based, but Robin isnt totally CORBA
  compliant.
• Robin compiler support on IRIX, SunOS, Linux, NT

14
CDFVME User Interface
15
CDFVME User Interface
16
CDFVME User Interface
17
Corba

• Can be thought of as rpc for objects. Software
  can create objects that really reside on a remote
  node.
• Corba is the standard, but there are many
  implementations.
• If the standard is adhered to, different programs
  can use different implementations and it should
  be transparent.
• IDL files describe objects. IDL compilers can
  generate c and/or java code depending on the
  implementation (c in rare cases).
• VxWorks implementations
• Robin - written by CDF. Generates c code on the
  server! Troublesome to support.
• Ace/Tao - free, but requires lots of memory
  (2.5M). Support is a question.
• Visibroker - commercial. Originally written by
  CLEO collaborator.

18
Fision

• CDF implementation of VISION, software standard
  for VME access
• vme mapping looks the same for all users
• Now supported by Computing Division
• Very hardware dependent - boards have different
  VME interface chips.
• Server supported under VxWorks 5.3 for mv162,
  mv167, mv2301, mv2603
• Client supported under SunOS, IRIX, Linux, NT

19
Camac

• Supporting Jorway 411S and 73a
• Ports now available for NT4, Linux, and IRIX6.5

20
Tools

• Java - v1_2 (or is it now v2_0?) on the verge.
• Swing is integrated in
• Will require several changes
• Slow
• Not yet available everywhere
• CVS - source version control.
• No reason not to start using at the very
  beginning.
• Great when many developers or even for a single
  developer working on more than one node
• Cygwin
• Freeware from cygnus
• Creates a bash window on NT
• ups/upd supported in this environment
• SRT runs in this environment
• Insure/insight
• Licensed debugging tool for IRIX
• Find problems at compile time and run time
  (memory leaks!)
• Purify
• Licensed debugging tool for IRIX
• Works on object that have been created by your
  favorite compiler

21
Operating Systems

• VxWorks
• the RT OS used at Fermilab and other HEP sites
  (US)
• currently supported (at Fermi) on mv162, mv167,
  mv2301, and mv2603
• expensive
• host platforms change - currently SunOS, NT, HP
• technical support less than spectacular
• Real Time Linux
• Start evaluating in another month or so
• Free!
• Sources distributed
• May still be too new
• Been ported to 68k and ppc processor boards
• QNX