r

Over Christmas we moved our main site from Wordpress to Hugo & Netlify. The main benefits for us moving to Hugo were Security. We were always getting emails about various Wordpress plugins. As our site was essentially static, this was an additional maintenance task. Site-speed. Although Wordpress has lots of clever plugins for optimising site-speed (which then leads to the situation above); Wordpress is just “big”. Raw cost. By this I mean web-site fees.

This is part four of our four part series Part 1: Specifying the correct figure dimension in {knitr}. Part 2: What image format should you use for graphics. Part 3: Including external graphics in your document Part 4: Setting default {knitr} options (this post). As with many aspects of programming, when you are working by yourself you can be (slightly) more lax with styles and set-up. However, as you start working in a team, different styles can quickly become a hindrance and lead to errors.

We are currently developing a SAAS Shiny application. We have a prototype that is functional, but not ready for release. Your role will be to refactor the application, and push it towards public release. The core requirements for this role is Shiny experience, plus CSS and Javascript. If you have experience in deployment that’s great, but isn’t required. This Shiny application will be your main role, but not your only one.

This is part four of our four part series Part 1: Specifying the correct figure dimension in {knitr}. Part 2: What image format should you use for graphics. Part 3: Including external graphics in your document (this post). Part 4: Setting default {knitr} options. In this third post, we’ll look at including eternal images, such as figures and logos in HTML documents. This is relevant for all R markdown files, including fancy things like {bookdown}, {distill} and {pkgdown}.

This is part four of our four part series Part 1: Specifying the correct figure dimension in {knitr}. Part 2: What image format should you use for graphics (this post). Part 3: Including external graphics in your document. Part 4: Setting default {knitr} options. There are (at least) three file formats to choose from: JPEG, PNG and SVG. Attribute JPEG PNG SVG Type Raster Raster Vector Transparency No Yes Yes Animation No No Yes Lossy Yes No Yes Recommended Occasionally Yes Often If you are reading this via a syndication site, be sure to go the original post for updated links.

This is part four of our four part series Part 1: Specifying the correct figure dimension in {knitr} (this post). Part 2: What image format should you use for graphics. Part 3: Including external graphics in your document. Part 4: Setting default {knitr} options. At Jumping Rivers we recently moved our website from WordPress to Hugo. The main reason for the move was that since the team are all very comfortable with Git, continuous integration and continuous development using a static web-site generator made more sense than WordPress.

If you’ve been using R for a while, you’ve likely accumulated a hodgepodge of useful code along the way. Said hodgepodge might include functions you source into multiple projects; bits and bobs that you copy and paste where needed; or code that solved a particularly esoteric problem and will never be applicable elsewhere, but you still enjoy revisiting sometimes. We all do it. If you’re anything like me, your personal library of code has grown gradually and haphazardly.

We love supporting the community around the open source tools that we use on a daily basis. In the past, Jumping Rivers has helped useR user groups and SatRdays events to happen by enabling frictionless sponsorship for European groups. We believe that it is our duty to help grow the community that helps us. With that in mind, it is our honour to announce that we are proudly sponsoring a new season of events hosted by WhyR.

For the last few years we’ve offered automatic sponsorship for meet-ups and satRday events. However for obvious COVID related reasons, most (all?) meet-ups have meeting getting together virtually, so the need for extra Pizza money has diminished. As with most organisations, we’ve had to adapted to the new online-first environment. In particular, running primarily online training courses. We’ve always ran some, online events, but now we’re running in excess of ten days of training per month on topics ranging from R, Python, Git, Shiny and Stan.

Don’t we all miss 2019 (blame Covid for the long delay in this post). The days of going to work and seeing your work colleagues face to face - and for some of you, attending one of our on-site training courses! 2019 was a great year for us. Not only have we broken new boundaries, we have recruited new full-time staff which have furthermore contributed to the glowing success of the company.