Skip to main content

XINA Markers

  • Managing Marker IDs (aka primary and secondary IDs):

    • Having to manage a master marker list is prone to error
    • Takes a lot of work
    • Quickly creating new markers for ad hoc tests is slow, which can often result in markers not being created at all
  • Procs/scripts that abruptlyend end:early, either intentionally or due to error:
    • Leaves dangling open markers
    • Open markers had to be manually closed by knowing the primary and secondary ID of the open marker(s)...error prone
    • No immediate feedback on which markers are opened. Test conductors are unaware that markers are left open.
    • Added convention where an ID of 0 with close flag will close all open markers
      • Doesn't play nicely with long duration "wrapper" markers, since those will be accidentally closed
  • Tagging "bad" markers
    • On OCI we use the convention of having a "debug" metadata key. "yes" means the data should be ignored, else "no"
    • Does not work when the proc is automated since the proc will automatically close the marker
    • AddedThe convention10 whereminute animport IDfrequency ofmeans 0you have to wait to be able to tag a marker as "bad"
    • Not well integrated with closethe flagweb will close all open markersinterface
      • Doesn'tNeeds playeasy nicelyfilters withto long durationignore "wrapper"bad" markers
    • Display "bad" tag on markers
    • Need button to easily tag a "bad" marker
Back to top