Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't use NaNs in tables when the value simply hasn't been recorded #2

Open
jimc101 opened this issue Jun 14, 2024 · 0 comments
Open

Comments

@jimc101
Copy link
Member

jimc101 commented Jun 14, 2024

In several instances, NaNs are recorded in statistical tables. This is often simply because the value wasn't calculated for some reason (e.g., the was no information for a given region).

In these instance, I recommend not using NaNs. Simply put a "-" or similar to indicate the value wasn't calculated. NaNs should be reserved for instances where a NaN was calculated in a given mathematical operation (e.g., division by zero), as this will assist debugging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant