Einstein @ Home

S5R3 Task Crunch Time Ready Reckoner V7C

Important Points To Read

  • All times are in seconds.
  • Predictions are designed for data from a single machine and a given application version only.
  • For data entry particularly :
    • Minumum two inputs, and generally the more the better.
    • Rigorous input checking applies to CSV input into left hand side text area/pane.
      • Three or four data values per line.
      • Values interpreted in order as FREQUENCY, SEQUENCE_NUMBER, RUNTIME and APP_VERSION respectively.
      • FREQUENCY interpreted as floating point.
      • SEQUENCE_NUMBER interpreted as integer.
      • RUNTIME interpreted as floating point.
      • if provided, APP_VERSION is accepted only if either
        • the word "mixed" ( lower case )
        • a floating point
      • Comma to separate each value.
      • No spaces within data values ( elsewhere trimming occurs ).
      • Abberant lines that do not parse as above will be discarded.
      • Each line represents a data point for analysis. There is no assumption of any ordering from one line and the next.
    • Choose a spread of task phases for a given frequency. Analysis ouput will be ascending sorted by levels of APP_VERSION, FREQUENCY and SEQUENCE_NUMBER.
    • An expected peak, average and trough runtimes plus variance and error is calculated given all qualifying tasks at each given frequency. This is subject to triage as regards fitness to predict ( complex ).
    • The right hand pane is editable. Any changes you make will be reflected when "Inputs and Outputs Summary" is selected.
    • If no error is quoted then none applies. Zero will be explicit.
  • NaN in a field indicates either an bad input somewhere earlier, or an unacceptable calculation result ( various causes ).
  • This an UNOFFICIAL toy. No warranties are implied or express whatsoever.
  • I would be very glad to receive any & all feedback ! ;-)

Cheers, Mike

For a sequence of tasks we will attempt an estimation of runtime parameters.
This depends upon the frequency F, sequence number S, running time T [ +/- application version V ] for as many entries as your runtime system can manage. There is no pre-programmed limit, and expect noticeable pauses for large data sets!