EGU 2019 | Thu, 11 Apr, 08:30–10:15, Room -2.62
Sebastian Kreutzer is a Post-doc at Université Bordeaux Montaigne, working on landscape evolution, luminescence dating and data science.
Michael Dietze is a Post-doc at the GFZ Potsdam, working on the seismic signals emitted by Earth surface processes.
Structuring code and following good practice rules
You are looking for an introduction to R … sorry, bad luck!*
(*) Don't repeat yourself.
By the way, Hadley Wickham's Advanced R is a warm recommendation.
Working with packages simply saves time and brain cells
What do you think? What belongs to an R package?
A working examples (you don't want to rely on the documentation, only)
A set of further stuff that will be covered later
Title: Environmental seismology toolbox Description: A collection of functions to handle seismic data for the purpose of investigating the seismic signals emitted by Earth surface processes. The package supports inporting standard formats, data preparation and analysis techniques and data visualisation.
importFrom()
in the file NAMESPACE, instead.citation("PACKAGENAME")
to see how a package should be citedAuthors@R: person("First", "Last", email = "first.last@example.com", role = c("aut", "cre"))
CRAN supports ORCID
Authors@R: person(..., comment = c(ORCID = "0000-0002-9079-593X"))
License: file LICENSE
) or a keyword of standard licenses (read more):
They are more than just counters, they define dependency satisfactions
Make use of a NEWS file (e.g., NEWS.md) to announce history & changes.