Minimum value thresholding and megaFIPS aggregation for low counts #361
Labels
Engineering
Used to filter issues when synching with Asana
refactor
Long-term projects to revise existing machinery
Just wanted to track the conversation that started here. There is code that zeros out signals when the sample sizes are low due to privacy. It would be good to be clear about where these decisions are made and be uniform about them. A possibility is creating a separate step in the pipeline that provides this functionality. I have not looked at enough indicators to see where this occurs, so maybe it's not a big deal, but wanted to have a record of these concerns.
The text was updated successfully, but these errors were encountered: