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
When processing multiple CVR files from different source filepaths, the undeclared write-in labels in the input files may potentially vary (e.g., “uwi” in one file and “udwi” in another). This is especially true when dealing with multiple voting systems or multiple jurisdictions (e.g., a state-wide race that is administrated by multiple decentralized, local elections officials). While RCTab has no control over the labels used in the input CVR files, it does have control over the format of the output rctab_cvr.csv file. A consistent undeclared write-in label should be enforced in the final output, regardless of the input configuration.
Current Behavior:
When using CVR files from different sources with varying undeclared write-in labels, the rctab_cvr.csv output reflects the original labels, resulting in potential inconsistencies.
Example:
- cvr0.xlsx uses the label “uwi” for undeclared write-ins.
- cvr1.xlsx uses the label “udwi” for undeclared write-ins.
- The resulting rctab_cvr.csv includes both “uwi” and “udwi” labels.
Expected Behavior:
The rctab_cvr.csv file should have a single, consistent label for undeclared write-ins, regardless of the original labels in the input files. This ensures that the output is standardized and simplifies further processing and analysis.
Scope and Impact:
This issue was identified using the ES&S CVR provider, as specified in the provided configuration file. The solution should be applicable across all vendors and elections to ensure uniformity in the rctab_cvr.csv output for all RCTab-supported configurations.
Steps to Reproduce:
Configure RCTab with two or more CVR source filepaths that use different undeclared write-in labels.
Set up the config.json file to include these files.
Run the tabulation.
Inspect the resulting rctab_cvr.csv file for inconsistent undeclared write-in labels.
Proposed Solution:
Enforce a single consistent, human-readable undeclared write-in label in the rctab_cvr.csv file output, such as “undeclared_write-in.”
Environment and Files for Reference:
RCTab version: pre-2.0 release; current development branch (as of late September 2024)
When processing multiple CVR files from different source filepaths, the undeclared write-in labels in the input files may potentially vary (e.g., “uwi” in one file and “udwi” in another). This is especially true when dealing with multiple voting systems or multiple jurisdictions (e.g., a state-wide race that is administrated by multiple decentralized, local elections officials). While RCTab has no control over the labels used in the input CVR files, it does have control over the format of the output
rctab_cvr.csv
file. A consistent undeclared write-in label should be enforced in the final output, regardless of the input configuration.Current Behavior:
When using CVR files from different sources with varying undeclared write-in labels, the
rctab_cvr.csv
output reflects the original labels, resulting in potential inconsistencies.Expected Behavior:
The
rctab_cvr.csv
file should have a single, consistent label for undeclared write-ins, regardless of the original labels in the input files. This ensures that the output is standardized and simplifies further processing and analysis.Scope and Impact:
This issue was identified using the ES&S CVR provider, as specified in the provided configuration file. The solution should be applicable across all vendors and elections to ensure uniformity in the
rctab_cvr.csv
output for all RCTab-supported configurations.Steps to Reproduce:
config.json
file to include these files.rctab_cvr.csv
file for inconsistent undeclared write-in labels.Proposed Solution:
Enforce a single consistent, human-readable undeclared write-in label in the
rctab_cvr.csv
file output, such as “undeclared_write-in.”Environment and Files for Reference:
The text was updated successfully, but these errors were encountered: