Available Documents

• The Requirements document:
  • HTML: [sectioned] or [one big page]
  • [PS]
  • [PDF]

• Status reports, To do list, Validation needs.

• Some useful files for analysis
  • data from inital proton beam running.
  • Recent beam sheet showing nominal locations
  • An spread sheet giving better measured positions for some devices
• Simple diagram of how I see the BeamData process fitting in to the general picture. Also includes mu/hadron control system (Christos). [EPS] and [PNG].

• The list of devices that will be read out in MS Excell 5.0/95 and Plain Text formats. The text file and one generated from it by this code is used directly by the Beam Data Process, so if a device isn't marked in this list, it isn't read out. See here for specifics of the beam line. In particular the ACNET device locations

• Instructions for installing Mary's JAS3 based prompt monitor display.

• Copy of spread sheet, maintained by Bob Ducar (ducar at fnal dot gov), of all primary beam devices. [XLS file]. (It is readable with gnumeric).
• Albert Erwin's initial list of monitors.
• Mary's list

• A console screen shot from Wally Kissel showing a device to use for testing array outputs.
• A console screen showing some devices for testing. From Tony Leveling via Gordon Koizujmi:

  AP1 line toroids - M:TOR105 and M:TOR109
  bpm's - see P60, protn, page 7
  AP1 loss monitors - see P60, protn, page 3
  		

• Some Java code from Jim Patrick that shows everything one needs to know to decode the output of the SWIC scanners. See the RawData/RawBeamSwicData for our implementation of this. And some more for new style beam profile monitors.

• Albert's test SWIC scanner: "Z_T1S1EV[]" device gives "sample", "start" and "stop" events for Albert's swic (Z:T1S1DS[]) (these are FE,02,FF). Using Z_T1S1ME[] gets a large block. The first elements give values like this (with Jim's explanation)

   1 - this block is defined
   2 - readout type; 2 means "slow"
   1 - gain
   100 - sampling duration in 0.1 ms units
   0 - threshold
   2 - prescaler
  		

  followed by a bunch of zeros, then similar for the second out-of-spill gate of the SWIC scanner (eg 1, 2, 1, 10000, ...). Albert confirms this is how he has the SWIC scanner set up. The Z:T1FF0D and Z:T1FF1D show the time delay from the trigger event to the start of each daq gate.

• SWIC paper.

• Debbie's Primary Beam Instrumentation page
• A table of ACNET events. Use as trigger via e,XX,s,0 where XX is the 2 digit hex value.
And another one.
• A guide to the DAE (data aq. engine)
• A page on IRMs, or Internet Rack Monitors, which are used by MiniBOONE to collect and buffer their 15 Hz data.

• Short description given at Ely '04 in [PS.GZ] and [PDF] formats.

Related software

• How to talk to the rotorooter and the rotorooter section of the user manual.

  Test with:

  rotorooter -p 9013 -e 
  

  and

  cd BeamData/python
  ./test-feed-rotorooter.py
  

• xmlrpc-1.2-b1.jar needed for JAS3 based displays.

Related links

• Some available APIs:
  • Simple query: http://www-bd.fnal.gov/xmlrpc/Accelerator
  • Register/callbacks:
    • General purpose: http://www-bd.fnal.gov/xmlrpc/Export
    • Modified version of above giving msec timestamps and variable forced callback timeouts http://www-bd.fnal.gov/xmlrpc-test/export
    • MINOS specific: http://www-bd.fnal.gov/minos
    • Access to data logger. http://www-bd.fnal.gov/xmlrpc/Datalogger
  • The current FNAL accelerator timeline. "9" are $29 events, "1" are fixed target cycles ($35)
  • XML-RPC for C/C++ will be used for the XML-RPC implementation.
  • Frontier::RPC, XML-RPC in Perl. May be used for initial connection process startup.
  • TCP Wrappers may be used for limiting which hosts access callback listener.

  Still to do

  Some things that still need to be done are:
  1. For the rotorooter connection, I am currently masquerading as the DCS. Changes to the rotorooter need to be done to fix this.

  2. Work needs to be done on the XML-RPC server end to allow for array-like devices to be read out (namely, the SWICs). Currenly only scalar-like devices can be read out.

  3. I still don't know the best way to get a useful timestamp into the data. I can always just take the system time, but it would be preferable to have a GPS time stamp with a known correlation.

  4. Testing with real beam devices, in particular, real triggering need to be done. I've been using things like outdoor temperature and a simple 1.89 sec recurring timer trigger.

  Misc. Notes

  To test running at BNL I must use SSH tunneling to negate BNL firewall and HTTP proxy. Two tunnels are used, one for calling into the XMLRPC server and one for callbacks from the XMLRPC "server".

  1. ssh -l minos -v -L 8888:www-bd.fnal.gov:80 minos-om.fnal.gov
     

     You'd then connect to, eg http://localhost:8888/xmlrpc/Accelerator

  2. ssh -l minos -v -R 19870:minos.phy.bnl.gov:19870 minos-om.fnal.gov
     

  The server on minos-om, in this case, needs "GatewayPorts yes" added to "/etc/ssh/sshd_config".

  ---

  Last Modified: $Date: 2005/10/20 16:17:27 $