Common Reject Guide

Rejects are part of truthful alpha behavior. A reject does not automatically mean a backend fault. It can mean the uploaded file is invalid, inconsistent, or numerically non-usable for the current evaluator path.

Common reject patterns

• Missing required freq_hz column.
• Mixed complex and mag/phase columns in the same file.
• NaNs, broken channel pairs, or partially empty channels.
• Non-monotonic or duplicated frequencies.
• Very weak / no-peaks spectral content that makes the current band non-usable.

What to do after a reject

1. Check that the file follows the official template exactly.
2. Confirm monotonic freq_hz and complete channels.
3. Remove mixed representations and empty columns.
4. Retry once after correcting the file.
5. If the same reject repeats, keep the request ID for follow-up.
6. If a clearly invalid or no-peaks file returns a server error instead of a reject, treat it as an alpha defect and keep the request ID.