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
In F3X/F3P cover records, the col_b_year field contains a 4-digit year value (e.g. 2025). FastFEC outputs this as 2025.00 (treating it as a float), while libfec correctly passes through the raw value 2025.
This is a FastFEC bug, not a libfec bug. The raw FEC data contains 2025 as a plain integer string, and libfec's passthrough is correct.
Documenting here for completeness since it causes a diff between the two tools.
Note
Much of this ticket was composed with Claude
In F3X/F3P cover records, the
col_b_yearfield contains a 4-digit year value (e.g.2025). FastFEC outputs this as2025.00(treating it as a float), while libfec correctly passes through the raw value2025.This is a FastFEC bug, not a libfec bug. The raw FEC data contains
2025as a plain integer string, and libfec's passthrough is correct.Documenting here for completeness since it causes a diff between the two tools.
Affected Filing
Filing ID: 1935668 (237KB, Chevron PAC F3XN filing)
Reproduction
Observe the Difference
Decision
No action needed on the libfec side - libfec's output is correct. This is a FastFEC quirk where it parses all numeric-looking values as floats.