Currently rdsa_utils has add_runlog_entry() which uses auto-incrementing integers for run IDs. We've built a run ID generator for TiG Local that produces human-readable IDs encoding a prefix and datetime: bbxx-yymmdd-hhmm.
Proposal: Add a generic version to rdsa_utils that any pipeline could use:
pythongenerate_run_id(prefix="bb26") # → "bb26-260706-1040"
generate_run_id(prefix="irt01") # → "irt01-260706-1040"
Along with validate_run_id() and parse_run_id() utilities. The functions are self-contained with no pipeline-specific dependencies.
Currently rdsa_utils has add_runlog_entry() which uses auto-incrementing integers for run IDs. We've built a run ID generator for TiG Local that produces human-readable IDs encoding a prefix and datetime: bbxx-yymmdd-hhmm.
Proposal: Add a generic version to rdsa_utils that any pipeline could use:
pythongenerate_run_id(prefix="bb26") # → "bb26-260706-1040"
generate_run_id(prefix="irt01") # → "irt01-260706-1040"
Along with validate_run_id() and parse_run_id() utilities. The functions are self-contained with no pipeline-specific dependencies.