Skip to content
Snippets Groups Projects

Add a basic script to validate metadata content

2 unresolved threads

In the context of recent examples of inconsistencies in the in-file metadata content due to interference of jobs running in containers (ATLASG-2686, AFT-711), this MR adds a script to check the sanity of the metadata:

  • check if the number of events from EventStreamInfo equals to the number of entries in DataHeader
  • check if /TagInfo metadata contains inconsistent information
  • check presence of FileMetaData
  • check uniqueness of run/lumiblock/event number per event and against the summary in the FileMetaData

This is of course non-exhaustive, so I'm open to suggestions regarding other checks.

I've added this to run in one of the ART tests, please let me know if this is sufficient and correct.

/cc @gemmeren @amete

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
107 if (
108 len(
109 set(
110 item[5:6]
111 for item in tag_info["project_name"]
112 if item.startswith("data")
113 )
114 )
115 > 1
116 ):
117 logging.error("/TagInfo contains values from different data taking periods")
118 return 1
119 if (
120 "data_year" in tag_info
121 and isinstance(tag_info["data_year"], list)
122 and set(tag_info["data_year"]) > 1
  • Otherwise, it does not work.

  • mentioned in merge request !70717 (merged)

  • Please register or sign in to reply
    Loading