lesson

Hello,
In "Working with Files and Directories" under "Good names for files and directories" I think it would be good advice to suggest that file names contain only lower case letters. If nothing else, it would be worthwhile to emphasize the importance of being consistent with letter case when choosing file names.
My understanding is that Unix is always case sensitive, while Windows is not, an

In Episode 8: Collaborating, there are many gendered pronouns that should be changed to better fit with the model of inclusivity that the Carpentries has built.

To accept access to the Owner’s repo, the Collaborator needs to go to https://github.com/notifications. Once there she can accept access to the Owner’s repo.

• The s

Starting at line 135 the lesson uses view() to open the data in RStudio's Data Viewer.
I suggest adding to the note on line 141 that tibble::view() and utils::View() have similar functionality but are part of different packages which is why the function does not seem to be case sensitive.

For context, see swcarpentry/python-novice-inflammation#887

Maintainers would like to solicit contributions to update episode 1 with examples more relevant to the inflammation story.

The space between Work and flow in the title of the Work flow within RStudio chunk should be removed as workflow is a single word.

Also, in this same section, reference to a .R file occurs without explanation that this is reflective of the R scripts described above. This could potentially b

Admittedly, I'm not a pythonista, but I wonder whether there would be value in using bash versions of the three python scripts. For whatever reason, I'm running into problems with getting python installed correctly on my Mac. Once I got it pointed in the right direct, I ran into problems with installing numpy. It's quickly becoming a tutorial on installing python rather than make :)

I suspect the

• I felt like nunique was arbitrarily (re)introduced when it was necessary. It wouldn't be top-of-mind for students solving problems.
• The lesson answers need to be adjacent to the exercises.
• I like the pre-introduction of masks and then circling back around to explain them.
• I feel like Part 4 needs to be broken up and integrated across other lessons: it felt thin on its own.
• Horizo

Dear Community,

There is a typo in the section titled "The StringsAsFactors argument" after the second block of code that demonstrates the use of the str() function. Right after the code boxes is written "We can see that the $Color and $State columns are factors and $Speed is a numeric column", but the box shows that the $Color column is a vector of strings.

Regards,

Rodolfo

https://swcarpentry.github.io/python-novice-gapminder/01-run-quit/index.html
Update in wording

I would like to suggest improvement to the below opening paragraph, found at https://swcarpentry.github.io/python-novice-gapminder/01-run-quit/index.html

"Many software developers will often use an integrated development environment (IDE) or a text editor to create and edit their Python programs

Help Wanted to Fix:

• "Utilize" could be "use" throughout. (#353)
• Sometimes we emphasize terms with italics, sometimes with boldface. "The cloud" on 11-hpc-intro is bold, and "The cloud" on 12-cluster is italics. Any significance to the difference? Any preference on just using one?
• Should images be linked as "../fig/" instead of "fig/" ?
• Consistent use of "log in to

In episode _episodes_rmd/12-time-series-raster.Rmd

There is a big chunk of code that can probably be made to look nicer via dplyr:

# Plot RGB data for Julian day 133
 RGB_133 <- stack("data/NEON-DS-Landsat-NDVI/HARV/2011/RGB/133_HARV_landRGB.tif")
 RGB_133_df <- raster::as.data.frame(RGB_133, xy = TRUE)
 quantiles = c(0.02, 0.98)
 r <- quantile(RGB_133_df$X133_HARV_landRGB.1, q

As datacarpentry is aimed at researchers, citations are an important part of their job.
Therefore a page on Rmarkdown should mention citations.

Maybe just one sentence about it including a link that is a more up-to-date version of
https://www.rstudio.com/blog/rstudio-1-4-preview-citations/

It'd be great if by default geospatial plots did not truncate axis ticks.

In the meantime, there is an easy one liner to change a setting to display axis ticks without truncation: plt.ticklabel_format(style="plain")

I only found out about this later