Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

issue with missing values in Exercise 25 in chapter 5

Open
#526 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
r
Domain
documentation

Research direction

Open exercises/_05-ex-explore-numerical.qmd around lines 572-573 and inspect Exercise 25. Check how zero values are handled and render or preview the exercise; done means the transformation and accompanying wording consistently account for counties with zero values.

Written by the indexing model from the issue text.

Description

I suspect that the counties with 0 hispanic_2017 are getting silently elided when log(hispanic_2017) is run.

I wonder if the code https://github.com/OpenIntroStat/ims/blob/7227c6e2f90b9f1cb804aa013f40ae1eba41fae3/exercises/_05-ex-explore-numerical.qmd#L572C5-L573C47 might be updated to log(1 + hispanic_2017) and the text slightly revised: logs of one plus these values.

suppressPackageStartupMessages(library(openintro))
suppressPackageStartupMessages(library(tidyverse))
county_complete |>
  select(fips, name, state, hispanic_2017) |> 
  arrange(hispanic_2017) |>
  head()
#>    fips             name        state hispanic_2017
#> 1 28061    Jasper County  Mississippi             0
#> 2 30069 Petroleum County      Montana             0
#> 3 31005    Arthur County     Nebraska             0
#> 4 31009    Blaine County     Nebraska             0
#> 5 31115      Loup County     Nebraska             0
#> 6 46061    Hanson County South Dakota             0

Created on 2026-02-13 with reprex v2.1.1

This doesn't directly relate to #525 except both are the same exercise.

Dominant language
JavaScript
Stars
948
Forks
211
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenIntroStat/ims

All issues in OpenIntroStat/ims

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.