yoda is hosted by Hepforge, IPPP Durham
close Warning: Can't synchronize with repository "(default)" (Repository path '/hepforge/hg/yoda/public/yoda' does not exist.). Look in the Trac log for more information.

Changes between Version 1 and Version 2 of DataFormat


Ignore:
Timestamp:
Jul 17, 2008, 6:31:07 PM (16 years ago)
Author:
buckley
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DataFormat

    v1 v2  
    1111 * The hash sign ({{{#}}}) is to be interpreted as a comment character in the manner of Python. '''Need some way to declare that a comment is actually a header?'''
    1212 * An arbitrary number of headers may be present on each object. We recommend that these headers are escaped by a prefix {{{#}}} character, for compatibility with gnuplot
    13  * For compatibility with gnuplot, the first 6 '''???''' data columns of records must be compatible with the gnuplot "plot with xyerrors" format, namely: x, y, xlow, xhigh, ylow, yhigh
     13 * For compatibility with gnuplot, the first 6 '''???''' data columns of records must be compatible with the gnuplot "plot with xyerrors" format, namely:
     14{{{
     15x, y, xlow, xhigh, ylow, yhigh
     16}}}
    1417
    1518=== HISTOGRAM ===
     
    2023=== COUNTER ===
    2124
     25A Counter class is not yet confirmed for inclusion in YODA, but seems useful (and is usually overlooked)
     26
     27{{{
     28sumw, sumw2
     29}}}
     30
     31(only one line)
     32
    2233=== DBN1D ===
     34
     35An extension of Counter which is used for internally managing the x data of Histo1D bins and the content of Profile1D bins. Not yet confirmed for public use.
     36
     37{{{
     38xmean, xerr, sumw, sumw2, sumwx
     39}}}
     40
     41(only one line)
    2342
    2443=== BAR1D ===
    2544
     45Bar plots are like histograms, but the x axis is discrete. Hence, there is no meaning to the x-spread data, and y-heights should be displayed without a width scaling. Not yet confirmed for use in YODA, but the confusion over histogram height scaling (and the mess of HepData records) suggests that we could do with an explicit type for this. '''How to deal with integral distributions? Convert from Histo1D -> ???'''
     46
     47{{{
     48barname, <Counter>
     49}}}
     50
     51(multiple lines - one per bar)
     52
    2653=== HISTO1D ===
    2754
     55The main data type.
     56
     57{{{
     58xcenter, ycenter, xlow, xhigh, ylow, yhigh, sumw, sumw2, sumwx
     59}}}
     60
     61(multiple lines - one per bin)
     62
    2863=== PROFILE1D ===
     64
     65{{{
     66xcenter, ycenter, xlow, xhigh, ylow, yhigh, sumw, sumw2, sumwx, sumwy
     67}}}
     68
     69(multiple lines - one per bin)
     70
     71=== SCATTER1D ===
     72
     73{{{
     74
     75}}}
     76
     77(multiple lines - one per point)
     78
     79=== SCATTER2D ===
     80
     81
     82{{{
     83
     84}}}
     85
     86(multiple lines - one per point)