1 / 8

Enhancements in Dual-Use Data Access: Merging TEvent and TStore APIs for Efficient Processing

This document discusses the integration of the TEvent and TStore APIs, which combine the basic functionalities of StoreGate, TSelector, and OutputStream TStore into a transient-only data store. It examines the sharing capabilities of objects between the two APIs, potential merging strategies, and the use cases for private data stores. The focus is on improving algorithm execution, managing context-specific data, and offering alternatives for data organization. It also outlines the status of VarHandles and plans for future development to optimize these data access APIs.

vevina
Download Presentation

Enhancements in Dual-Use Data Access: Merging TEvent and TStore APIs for Efficient Processing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Access inDual-use Tools PC

  2. Data Access via TEvent/TStore TEvent: combines basic functionality of StoreGate, TSelector, OutputStream TStore: transient-only data store • Not sure why two very similar APIs • Objects can be shared(copied?) between the two, allowing to save TStore objects • How about merging them?

  3. Private Stores • Use Cases: • Train Carriages • One store per carriage • Systematics Variations • Multiple object versions • (HLT ROIs and Trigger Steps) • Event Views • Insulate execution of Algorithms/Tools • Slice event context • Allow both shared and context-specific data objects • Single context switch

  4. Common Theme: Inverted Lookup Photons Photons Electrons Electrons Private toEScale1Up Escale1Up Escale1Down Retrieve lookup Muons Photons Electrons Shared EventStore

  5. Design Alternatives SG Folders: • like TDS directories (or Trigger Elements) • Reverse “find”: 1st current dir, then up • Context-specific View Stores: • Shallow copy event store into context store • Record context-specific data objects

  6. VarHandles in Dual-Use Tools? • Declared and set as an AlgToolProperty • In .h • SG::RVar<EventInfo>m_r_evtInfo; • SG::WVar<int> m_w_int; • In .cxx declareProperty("EvtInfoHandle", m_r_evtInfo, “An EventInfo read handle"); Pointer-like syntax m_w_int = new int( m_r_evtInfo->event_number()) • Prototype in athena • a cross between DataLink and ToolHandle • replace record/retrieve • Interface not as rich as StoreGateSvc • Soon to use in athena • how to avoid split with dual-use tools

  7. Status of VarHandles Goal is to have them “tutorial-ready” for Sep (already presented in July LBL tutorial) Focus on interface, some tuning needed • Find better name :-) • How to connect to a non-default store • What is a valid handle? How to do • if (!contains(key)) record(dobj,key) • Optimize implementation later (follow DL) Recommend for athenaat Sep C&S week

  8. Summary • A lot remains to do for analysis data access APIs • Already some “legacy” design choices to deal with • No overarching development thread (that I can see) • Several common themes between Analysis, HLT, Concurrency

More Related