You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test in #177 checks if FORM can produce a simple file for a simple case.
The test need to be followed by a verification step that checks that the file has the expected structure and has the expected values.
This can be closed. The verification step requested here now exists for both ROOT_TTREE and ROOT_RNTUPLE.
Expected values — test/form/writer.cpp writes a checksum file alongside the output; test/form/reader.cpp loads it and compares per-(event, segment) and per-event, reporting VERIFY FAIL and exiting non-zero on any mismatch (ReadVector_${TECH}).
Expected structure — several tests now check the file layout rather than just its existence:
form_navigation_${TECH} — navigation tables, layer columns, one row per data cell, and a cross-check of each navigation row against the per-creator index
dune_example_navigation_dump_${TECH} — the same checks on a multi-hierarchy, multi-creator DUNE-shaped file
form_root_schema_write/read_${TECH} plus check_root_schema_evolution_${TECH} — schema evolution, verified by comparing write and read logs
form_dune_outputs_*_check — reads each (file, technology) output of a job back and confirms its products
All are registered in test/form/CMakeLists.txt. Nothing further is needed here.
Activity
wwuoneway commentedon Oct 1, 2026
This can be closed. The verification step requested here now exists for both
ROOT_TTREEandROOT_RNTUPLE.Expected values —
test/form/writer.cppwrites a checksum file alongside the output;test/form/reader.cpploads it and compares per-(event, segment)and per-event, reportingVERIFY FAILand exiting non-zero on any mismatch (ReadVector_${TECH}).Expected structure — several tests now check the file layout rather than just its existence:
form_navigation_${TECH}— navigation tables, layer columns, one row per data cell, and a cross-check of each navigation row against the per-creator indexdune_example_navigation_dump_${TECH}— the same checks on a multi-hierarchy, multi-creator DUNE-shaped fileform_root_schema_write/read_${TECH}pluscheck_root_schema_evolution_${TECH}— schema evolution, verified by comparing write and read logsform_dune_outputs_*_check— reads each(file, technology)output of a job back and confirms its productsAll are registered in
test/form/CMakeLists.txt. Nothing further is needed here.