1 / 7

Remained Developments of the Pre-trigger system

Remained Developments of the Pre-trigger system. Ken Oyama Heidelberg. Items to be finalized in pre-trigger system. FPGA design Nearly done and now in maintenance phase A,C, FEB … Joerg, TLMU … Tobias & Rainer , B … Jochen Introducing BUSY line from GTU to be done [Jochen]

kaelem
Download Presentation

Remained Developments of the Pre-trigger system

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Remained Developments of the Pre-trigger system Ken Oyama Heidelberg Ken Oyama

  2. Items to be finalized in pre-trigger system FPGA design • Nearly done and now in maintenance phase • A,C, FEB … Joerg, TLMU … Tobias & Rainer , B … Jochen • Introducing BUSY line from GTU to be done [Jochen] • GTU BUSY is currently kept until end of data transmission to DAQ Configuration scheme and software • PTSS (front-end server on DCS boards) and PTFSMD operationalbut further improvements are needed (later pages) • Data base configuration is not yet touched (later pages) • FXS proxy and offline data base part is not yet touched(we finalize after configuration method and data format is fixed) PVSS • Counter publishing is working fine [Bastian] • Tag based run depending configuration is next step [see also Oliver’s talk] Raw Data readout • New PIMDDL project to be approved [see Joerg’s talk] Infrastructure • Power connection upgrade for C-side … during long LHC stop Ken Oyama

  3. Configuration Scheme as of Now Currently, there is no interaction between PTFSMD and PTSS/PTDIC • things are script based, and no data base, no connection to PHYSICS setup PVSS send script name send FSM command dim2shell ptfsmd exec shell scripts exec shell scripts call on linux human exec ptdic send (initial) command LUT, FPGA conf, etc (files) ptdic_process read CB CB CB CB CB CB CB CB CB PTSS C++lib and comand line tool on linux on DCS boards Ken Oyama

  4. Near Future Plan • Make the ptdic_process (dim client part) usable from ptfsmd as interface to PTSS • TAG based configuration straight forward from CTP level to hardware • Use DB for configuration storage • Works being done by Felix Reidt and Uwe Westerhof CTP Gives: Run type, trigger conf, detector participation from ACT, and fill scheme etc FSM command + TAG(s) human PVSS ptfsmd exec ptdic give tag Param/Conf (tag) ptdic_process config formatter CB CB CB CB Other files CB CB CB CB CB PTSS Ken Oyama

  5. PVSS Development • Done by Bastian and Oliver • Now behind is scripts called by dim2shell facility • to be upgraded to tag based configuration for stable setup • and adjustments through PTFSMD for run-by-run setup (such as BCMask) … interface will look same but all are tracked Ken Oyama

  6. Monitoring Counters on PVSS • All counters are visible now on PVSS panel and trending is kept [Bastian] • TLMU counters (576xN) will be somehow shown as soon as PTSS becomes ready [Felix and Bastian are working] • Alarm for counter values and ratios [Bastian, Oliver] Ken Oyama

  7. Othere Activities on Going • Introducing new trigger line (not only 0HWU) • Time sharing information between MB/RARE needed at higher  with many bunches run? • ALICE won’t go to higher  so far • Occasional crash of PTSS to be investigated • Debugging jtag configuration over DIM (Felix is investigating) • Sometimes fails for writing LUT on CB-C … being investigated by Joerg Ken Oyama

More Related