mockr: Mocking in R

Canonical link: https://rscholar.com/pkg/mockr

Kirill Müller • View description and downloads View dependencies GitHub project

2017 Published

0 Citations

1 Authors

3 Revisions

0.2.2 Version

MIT License

Referenced by ⇅	Year
dosearch: Causal Effect Identification from Multiple Incomplete Data Sources (Version 1.0.12)	2019
gptstudio: Use Large Language Models Directly in your Development Environment (Version 0.4.0)	2023
amerifluxr: Interface to 'AmeriFlux' Data Services (Version 1.0.0)	2022
shiny.benchmark: Benchmark the Performance of 'shiny' Applications (Version 0.1.1)	2023
ROCaggregator: Aggregate Multiple ROC Curves into One Global ROC (Version 1.0.1)	2021
corehunter: Multi-Purpose Core Subset Selection (Version 3.2.3)	2016
coursekata: Packages and Functions for 'CourseKata' Courses (Version 0.19.0)	2023
dosearch Sources: (Version )	0
gluedown: Wrap Vectors in Markdown Formatting (Version 1.0.9)	2019
gptstudio Environment: (Version )	0
knitrProgressBar: Provides Progress Bars in 'knitr' (Version 1.1.1)	2018
mctq: Tools to Process the Munich ChronoType Questionnaire (MCTQ) (Version 0.3.2)	2021
metro: Washington Metropolitan Area Transit Authority API (Version 0.9.3)	2021
miniCRAN: Create a Mini Version of CRAN Containing Only Selected Packages (Version 0.3.1)	2014
onetime: Run Code Only Once (Version 0.2.0)	2022
passport: Travel Smoothly Between Country Name and Code Formats (Version 0.3.0)	2017
pestr: Interface to Download Data on Pests and Hosts from 'EPPO' (Version 0.8.4)	2021
storr: Simple Key Value Stores (Version 1.2.6)	2016
tidyhte: Tidy Estimation of Heterogeneous Treatment Effects (Version 1.0.4)	2023
tidysq: Tidy Processing and Analysis of Biological Sequences (Version 1.2.3)	2021
tidyverse: Easily Install and Load the 'Tidyverse' (Version 2.0.0)	2016

RPKG Scholar presents a tabulation of an author's contribution in the development of R packages stored in the Comprehensive R Archive Network (CRAN). Within this site, we consider package dependencies (suggests,imports,depends,enhances) as citations because we believe that using one's package to develop another is tantamount to citing the author of the package being imported, suggested or enhanced.