Skip to content
Snippets Groups Projects
  1. Jul 26, 2018
  2. Jul 16, 2018
  3. Jun 22, 2018
  4. Jun 21, 2018
  5. Jun 15, 2018
  6. Jun 13, 2018
  7. Jun 05, 2018
  8. Jun 04, 2018
  9. May 31, 2018
  10. May 02, 2018
  11. Apr 30, 2018
  12. Mar 10, 2018
  13. Mar 09, 2018
  14. Mar 08, 2018
  15. Mar 06, 2018
  16. Mar 02, 2018
  17. Mar 01, 2018
    • Alex Pearce's avatar
      Improve DST writer logic. · 0db7a67a
      Alex Pearce authored
      1. Only require the Turbo sequence passed if we're running in 'online'
      mode *and* we're not running on simulated data. Otherwise, we want to
      write out every event that's in the input.
      2. Because of 1., we can no longer require the existence of
      /Event/Turbo/Rec/Summary in the writer, because for events with no Turbo
      lines firing the writer will still run but the summary will not be
      made. This is a little unfortunate because we now have no run-time
      guarantee that this location will be created when a Turbo line *does*
      fire, as it should be, but I'm not sure of the alternatives.
      3. Always write out the juggled raw event in online mode, because there
      we always perform the juggling.
      0db7a67a
    • Alex Pearce's avatar
      Do not run the Tesla sequence if no Turbo line fires. · 4a274e79
      Alex Pearce authored
      For data this filter always passes, as Tesla only runs on the TURBO and
      TURCAL streams, in which every event passes a Turbo line by
      construction. In the simulation, however, this is not necessarily true,
      so we protect the sequence from finding missing locations etc. by
      filtering on Turbo decisions.
      4a274e79
  18. Feb 27, 2018
  19. Feb 26, 2018
  20. Feb 21, 2018
  21. Feb 15, 2018
Loading