'));
// trim code
$('pre>code').each(function(i, val) {
$(this).html($.trim($(this).html()));
});
// move posts-container right before article
$('.posts-container').insertBefore($('.d-article'));
$('body').addClass('downlevel');
on_load_complete();
}
function init_common() {
// jquery plugin to change element types
(function($) {
$.fn.changeElementType = function(newType) {
var attrs = {};
$.each(this[0].attributes, function(idx, attr) {
attrs[attr.nodeName] = attr.nodeValue;
});
this.replaceWith(function() {
return $("<" + newType + "/>", attrs).append($(this).contents());
});
};
})(jQuery);
// prevent underline for linked images
$('a > img').parent().css({'border-bottom' : 'none'});
// mark non-body figures created by knitr chunks as 100% width
$('.layout-chunk').each(function(i, val) {
var figures = $(this).find('img, .html-widget');
// ignore leaflet img layers (#106)
figures = figures.filter(':not(img[class*="leaflet"])')
if ($(this).attr('data-layout') !== "l-body") {
figures.css('width', '100%');
} else {
figures.css('max-width', '100%');
figures.filter("[width]").each(function(i, val) {
var fig = $(this);
fig.css('width', fig.attr('width') + 'px');
});
}
});
// auto-append index.html to post-preview links in file: protocol
// and in rstudio ide preview
$('.post-preview').each(function(i, val) {
if (window.location.protocol === "file:")
$(this).attr('href', $(this).attr('href') + "index.html");
});
// get rid of index.html references in header
if (window.location.protocol !== "file:") {
$('.distill-site-header a[href]').each(function(i,val) {
$(this).attr('href', $(this).attr('href').replace(/^index[.]html/, "./"));
});
}
// add class to pandoc style tables
$('tr.header').parent('thead').parent('table').addClass('pandoc-table');
$('.kable-table').children('table').addClass('pandoc-table');
// add figcaption style to table captions
$('caption').parent('table').addClass("figcaption");
// initialize posts list
if (window.init_posts_list)
window.init_posts_list();
// implmement disqus comment link
$('.disqus-comment-count').click(function() {
window.headroom_prevent_pin = true;
$('#disqus_thread').toggleClass('hidden');
if (!$('#disqus_thread').hasClass('hidden')) {
var offset = $(this).offset();
$(window).resize();
$('html, body').animate({
scrollTop: offset.top - 35
});
}
});
}
document.addEventListener('DOMContentLoaded', function() {
if (is_downlevel_browser())
init_downlevel();
else
window.addEventListener('WebComponentsReady', init_distill);
});
Overview
The R Journal is a peer-reviewed, open-access scientific journal, published by The R Foundation. It features short- to medium-length articles (up to 20 pages) covering topics of interest to users and developers of R. For example, description and implementation details of R packages, surveys or reviews of R software related to a particular area, applications of R software or descriptions of teaching resources related to R.
All submissions must primarily be about R packages and R programming. Submissions that involve R calling other software will be considered provided: (a) the other software is open source and free to use; (b) is widely used; and (c) there is a clear justification for using it rather than a native R implementation. Occasional exceptions may be made if (a) is not satisfied, provided there is no viable open source alternative.
The R Journal reaches a wide audience and has a thorough review process. It has a generally increasing SJR impact factor. Papers are expected to be concise, clearly written, not too technical, clearly related to R, and follow reproducible practices. Additional technical details and examples could be included as supplementary material. Authors of refereed articles should take care to:
- put their contribution in context, in particular discuss related R functions or packages;
- explain the motivation for their contribution;
- provide code to reproduce the material in the paper.
Article types
The R Journal accepts a variety of article topics including:
- Packages: Details of contributed R packages that are available on CRAN or Bioconductor, that go beyond a package vignette. This includes providing the broader context, implementation details, applications or examples of use, with the purpose being to make the work relevant to a wider readership than only the package users. The paper might explain the novelty in implementation and use of R, introduce new data structures or general architectures that could be re-usable for other R projects. Note that both the paper and the code will be reviewed. See our guidelines for papers about R packages.
- Reviews and proposals: surveying and discussing challenges and opportunities of potential importance for the broader R community, including proposals and proof-of-concept implementations.
- Comparisons and benchmarking: of implementations in base-R and contributed packages with each other, and where relevant with implementations in other software systems.
- Applications: demonstrating how new or existing techniques can be applied in an area of current interest using R, providing a fresh view of such analyses in R that is of benefit beyond the specific application.
- Special issue articles: papers associated with a conference like R Medicine, or possibly a collection of papers on a particular topic of interest.
History
The R Journal was established in 2009, superseding the R News. For historical purposes it also includes a news section, that includes items from R Core, updates from CRAN and Bioconductor, foRwards activities and conference reports.
R Journal article summaries, for the last four years
The R Journal receives a large number of submissions, currently around 150 a year, and processing times and especially review times are highly variable. The summaries below shows that for published articles, the time from first submission to accept averages at under a year.
For published articles in the years 2022, 2023, 2024, 2025, the boxplots show time from submission to accept by year of publication. Median number of days to accept is under a year. The barchart on the right refers to articles submitted in the years 2022, 2023, 2024, 2025, and reports the status as rejected, in progress or accepted/published. Papers labelled ‘in progress’ are under review or awaiting revisions.
Overview
The R Journal is a peer-reviewed, open-access scientific journal, published by The R Foundation. It features short- to medium-length articles (up to 20 pages) covering topics of interest to users and developers of R. For example, description and implementation details of R packages, surveys or reviews of R software related to a particular area, applications of R software or descriptions of teaching resources related to R.
All submissions must primarily be about R packages and R programming. Submissions that involve R calling other software will be considered provided: (a) the other software is open source and free to use; (b) is widely used; and (c) there is a clear justification for using it rather than a native R implementation. Occasional exceptions may be made if (a) is not satisfied, provided there is no viable open source alternative.
The R Journal reaches a wide audience and has a thorough review process. It has a generally increasing SJR impact factor. Papers are expected to be concise, clearly written, not too technical, clearly related to R, and follow reproducible practices. Additional technical details and examples could be included as supplementary material. Authors of refereed articles should take care to:
- put their contribution in context, in particular discuss related R functions or packages;
- explain the motivation for their contribution;
- provide code to reproduce the material in the paper.
Article types
The R Journal accepts a variety of article topics including:
- Packages: Details of contributed R packages that are available on CRAN or Bioconductor, that go beyond a package vignette. This includes providing the broader context, implementation details, applications or examples of use, with the purpose being to make the work relevant to a wider readership than only the package users. The paper might explain the novelty in implementation and use of R, introduce new data structures or general architectures that could be re-usable for other R projects. Note that both the paper and the code will be reviewed. See our guidelines for papers about R packages.
- Reviews and proposals: surveying and discussing challenges and opportunities of potential importance for the broader R community, including proposals and proof-of-concept implementations.
- Comparisons and benchmarking: of implementations in base-R and contributed packages with each other, and where relevant with implementations in other software systems.
- Applications: demonstrating how new or existing techniques can be applied in an area of current interest using R, providing a fresh view of such analyses in R that is of benefit beyond the specific application.
- Special issue articles: papers associated with a conference like R Medicine, or possibly a collection of papers on a particular topic of interest.
History
The R Journal was established in 2009, superseding the R News. For historical purposes it also includes a news section, that includes items from R Core, updates from CRAN and Bioconductor, foRwards activities and conference reports.
R Journal article summaries, for the last four years
The R Journal receives a large number of submissions, currently around 150 a year, and processing times and especially review times are highly variable. The summaries below shows that for published articles, the time from first submission to accept averages at under a year.
For published articles in the years 2022, 2023, 2024, 2025, the boxplots show time from submission to accept by year of publication. Median number of days to accept is under a year. The barchart on the right refers to articles submitted in the years 2022, 2023, 2024, 2025, and reports the status as rejected, in progress or accepted/published. Papers labelled ‘in progress’ are under review or awaiting revisions.