datastrategist / amitfuncs

Random Assortment Of Convenience Functions By Amit

Hi there, I'm Amit 👋

I'm a bicultural environmental engineer turned data director and data science educator and speaker. I use R for most things, sometimes even correctly! I believe in diversity and have spent my entire 20+ year career working to improve this world or the lives of the people that live in it.

• 🔭 I’m currently too busy for personal projects :( But the next one will be looking at land prices in the UK (wanna help?)
• 🌱 I’m currently learning better ETL tools (but really need to learn Baysian inference)
• 👯 I’m looking to collaborate on COVID-19 or #BlackLivesMatter initiatives. Contact me, I'm willing to volunteer!
• 💬 Ask me about United Nations, International Development, NGOs, charities, teaching and anything R!
• 📫 How to reach me: [email protected] or see other social networks below.
• 😄 Pronouns: He
• ⚡ Fun fact: I just heard that my love of analyzing movies and video games means I don't get to enjoy them :-\

Connect with me:

---

📕 Latest Blog Posts

• SDG Indicator Direction Estimation
• an R-user's guide to Python for data science
• 10 reasons why Random Forest is the only algorithm you will need
• How are SDG Indicators interconnected?
• Interactive COVID map by LSOA

---

📺 Latest YouTube Videos

• How to accept a pull request from Github on your R package
• London Crime Map Errors and all!
• London Crime Analysis Errors and all!
• How to create an R package using usethis, sinew, pkgdown and goodpractice
• Making International Development Data Not Useless EARL London 2017 Talk

---

amitfuncs's Issues

input comparer

check all the inputs and if they are the same input, compare if they have the same definition.

Dep parser should have options

• to be recursive or not, and to exclude certain folders or not

Increase visual size of dependancy_parser

Also... can we make it not visNetwork? igraph might be enough. Or one of the hand-drawn looking ones.

Test split creater

when testing a function, if we take inputs that have options listed, create an output where all of the input combinations are crossed. This will create an output suitable to create unit tests.

Hrm... mess w/ the idea of explicitly stating errors or not?

#' @param boom does x, Default: 'R', Options: c("1","4","6{X}")
#' @param matchingText PARAM_DESCRIPTION, Default: '.', Options: c("a", "bvb", NA{X})
#' @param other does y, Options: c("hello", "bye")

Would produce:

expand_grid(boom  = c("1","4","6{X}"), matchingText  = c("a", "bvb", "NA{X}"), other  = c("hello", "bye"))

and anything that has an X will create an expect_error expectation... else expect class as per output.

This is concise, but it does coerce everything to character. Maybe:

#' @param boom does x, Default: 'R', Options: c(1,4,6), FailureOn: 6