run-stata

To run a Stata do-file in batch mode, execute it through the project wrapper from the repository root. The wrapper captures the exit code, produces a consistent log, scans for r(<n>) runtime errors, and verifies expected output artifacts.

Stata log validation works by scanning the batch execution log for common runtime failure signatures, including r(<n>) error patterns and missing observations, confirming whether your econometric analysis script succeeded.

The best way to check for missing outputs is to verify expected artifacts referenced in the do-file's Outputs header after execution, ensuring all declared tables and figures were successfully created.

Yes, you need to validate declared inputs before execution. The workflow resolves the do-file path, confirms the file exists, and checks declared inputs in the do-file header to ensure deterministic econometric analysis.

Stata do-files can fail silently if logs are not properly parsed for r(<n>) error patterns or missing observations. Using a batch-mode runner that scans logs captures these failure signatures and reports them.