Search results

Jump to navigation Jump to search

Page title matches

  • ...topologies and other characteristics. In terms of buffering and processing data in real or near time, they pose different requirements. ...logical background. Zero-suppression will lead to significant reduction of data volume and rates (the detector will appear "empty" for the most part).
    3 KB (432 words) - 19:57, 18 December 2017
  • Data is available from the 35t Prototype Detector. http://dune-data.fnal.gov/data/35t/testfiles/filelist.txt
    2 KB (345 words) - 18:30, 8 December 2017
  • ...ta that is shared by modules via the event data store and written to event data output files. == Simulation data classes ==
    25 KB (3,240 words) - 14:08, 12 December 2017

Page text matches

  • == Data Handling == ...science.iop.org/1742-6596/396/3/032023/pdf/1742-6596_396_3_032023.pdf LHCb Data Management]
    1 KB (155 words) - 00:24, 26 November 2014
  • * "SFO" means subfarm output processor. It's function is to receive event data which passed triggers of all levels and assemble it before committing to ma ...e [http://www.linux.org/threads/xfs-file-system.4364/ XFS file system] for data storage.
    3 KB (466 words) - 18:44, 15 June 2017
  • Data is available from the 35t Prototype Detector. http://dune-data.fnal.gov/data/35t/testfiles/filelist.txt
    2 KB (345 words) - 18:30, 8 December 2017
  • .... parallel trigger farm looks for nice muons in real time. Needs ZS of TPC data to work.|| --- ...ck.||This is a fallback option of there is bottleneck in either RCE or SSP data.
    2 KB (371 words) - 18:30, 8 December 2017
  • = external data = |data=nick=short_name,name=full_name,country=country,address=address
    1 KB (148 words) - 15:12, 6 January 2015
  • ...ibution network. This provides high-bandwidth, low-latency access to LBNE data. This is still under development. ...GPFS). So, it can be used for smallish files which can then be moved to a data disk.
    2 KB (318 words) - 15:43, 9 December 2014
  • ...l redirector" which allows xrootd services to locate a particular piece of data within the federation. ...ins how dCache storage at FNAL is equipped with a "xroot door" so that the data content of dCache is exposed to external clients.
    3 KB (444 words) - 01:20, 26 August 2016
  • gsiftp://fndca1.fnal.gov:2811/pnfs/fnal.gov/usr/lbne/test-data/lbne/raw/00/18/90/51/lbne_r006837_sr01_20160112T213253.root enstore:/pnfs/lbne/test-data/lbne/raw/00/18/90/51(602@vpe776)
    3 KB (364 words) - 18:54, 8 December 2017
  • Starting the xrootd daemon by itself is enough to serve data from a single node (i.e. without xrootd -c configFile.cfg /path/to/data &
    8 KB (1,411 words) - 01:34, 27 September 2016
  • ...from some people. This would effectively double the number (and weight) of data cable, impacting the number of connectors and flanges (or at least connecto
    2 KB (299 words) - 22:11, 20 December 2016
  • * pLAPPD ToF will be joined with the “normal” DAQ data stream * The fiber tracker data, other spill-relevant data, and ckov data will go into the BI DB
    4 KB (672 words) - 17:48, 6 February 2018
  • ....org:8080/cgi-bin/RetrieveFile?docid=1755&filename=HDR-192192-XX.PDF Cold Data Cable drawing ] [[Image:DataCable-signal-map.png|300px|Caption Cold Data Cable Signal Map]]
    5 KB (720 words) - 14:38, 3 November 2016
  • * [[35t Data]]
    743 bytes (111 words) - 18:31, 8 December 2017
  • ...ta that is shared by modules via the event data store and written to event data output files. == Simulation data classes ==
    25 KB (3,240 words) - 14:08, 12 December 2017
  • * where is a diagram showing all the parts of the DAQ data stream with their names (millislice, microblock, tick, "trigger", etc)? * what is the start/stop criteria that defines the highest level "chunk" of data (e.g. a "trigger")?
    7 KB (1,233 words) - 18:33, 8 December 2017
  • ...topologies and other characteristics. In terms of buffering and processing data in real or near time, they pose different requirements. ...logical background. Zero-suppression will lead to significant reduction of data volume and rates (the detector will appear "empty" for the most part).
    3 KB (432 words) - 19:57, 18 December 2017
  • * {{DocDB|9967|Raw Data File Name Discussion (v2)}} * t.b.d. "Proposed change to file metadata in support of 35t raw data"
    7 KB (1,096 words) - 14:45, 16 December 2014
  • ===CUC DATA and Control room=== [http://www.palazzani.it/public/TZX%20550%20(170)_USA100346.pdf Data Sheet for a small platform (1m wide) areal lift]
    6 KB (813 words) - 13:08, 5 September 2022
  • Note, the definitive source of data rate/volume numbers is in {{Doc|1086}}. The extracted numbers below may be ** Nominal data in spill: 13.5GB
    7 KB (1,094 words) - 17:12, 30 November 2017
  • at the CERN SPS accelerator complex. The rate and volume of data produced by these detectors will be substantial and will require =Expected Data Volume and Rates=
    14 KB (2,145 words) - 20:13, 19 December 2017

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)