XINA Markers

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

• Procs/scripts that abruptly end:
  • 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.
• 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
  • Added convention where an ID of 0 with close flag will close all open markers
    • Doesn't play nicely with long duration "wrapper" markers