Skip to content

Commit 66e43e1

Browse files
nevromenevrome
committed
Merge branch 'master' of github.com:sslarch/sslarch.github.io
2 parents 915f69a + a472535 commit 66e43e1

File tree

5 files changed

+108
-4
lines changed

5 files changed

+108
-4
lines changed

‎content/members/martinhinz.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,7 @@
11
---
22
title: "Martin Hinz"
3-
role: "Convener"
4-
group: "Steering Committee"
3+
group: "Members"
54
github: "MartinHinz"
65
orcid: "0000-0002-9904-6548"
76
languages: "R, Ruby"
8-
weight: 1
97
---

‎content/members/matteotomasini.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
---
22
title: "Matteo Tomasini"
3-
group: "Members"
3+
role: "Convener"
4+
group: "Steering Committee"
45
github: "mtomasini"
56
orcid: "0000-0003-2776-9998"
67
languages: "Python, R, Stan, (C++), (Vue.js)"
8+
weight: 1
79
---

‎content/members/nickhall.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
title: "Nick Hall"
3+
group: "Members"
4+
github: "nicksgoodusername"
5+
orcid: "0009-0005-5818-0264"
6+
languages: "Python"
7+
---

‎content/sessions/caa2026_workshop_R.md‎

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
title: "From Zero to Plotting: R for Anyone"
3+
sessionType: workshop
4+
date: 2026-03-31
5+
publishDate: 2026-03-20
6+
conference: CAA 2026, Vienna
7+
conferenceUrl: https://2026.caaconference.org
8+
sessionCode: "-"
9+
organisers:
10+
- Petr Pajdla
11+
- Peter Tkáč
12+
- Vít Kozák
13+
---
14+
15+
**When:** 2026-03-31, 9:00 - 16:30 CET
16+
**Where:** In person, TU Wien, room AC 04 - 1 (Karlplatz 13, 1040 Vienna)
17+
**Format:** Full-day workshop
18+
19+
> *We will close your brackets and find all your missing commas!*
20+
21+
## Description
22+
23+
Intimidated by R? You’re not alone. Whether you’ve never written a line of code or struggled through previous attempts, this workshop is designed for you. We’ll demystify R and show you that data analysis and visualization aren’t just possible for archaeologists‚ they’re powerful tools that will transform how you work.
24+
25+
Over this hands-on session, we’ll guide you through the complete workflow: installing essential packages, reading, transforming and plotting data and ultimately understanding why R matters for reproducible research. We’ll use archaeological data, clean it up, organize it the “tidy” way, transform it to answer your questions, and create publication-ready plots.
26+
27+
We want you to leave the workshop with confidence to keep on coding!
28+
29+
### What You’ll Learn
30+
31+
- Starting R and R Studio for the first time
32+
- Installing packages
33+
- Working in scripts and projects
34+
- Reading your data with readr package
35+
- Data cleaning and organizing them the tidy way with tidyr package
36+
- Transforming and summarizing data with dplyr package
37+
- Creating compelling visualizations in ggplot2 package
38+
39+
### Who Should Apply
40+
41+
- Complete beginners with no coding experience
42+
- People who’ve tried R before and found it frustrating
43+
- Archaeologists wanting to improve data analysis and visualization skills
44+
- Anyone curious about reproducible research workflows
45+
46+
No prior programming experience necessary.
47+
Just bring your laptop (with R (https://cran.rstudio.com/) and RStudio (https://posit.co/download/rstudio-desktop/)installed) and willingness to learn.
48+
49+
### Format
50+
51+
Hands-on coding workshop with guided examples, archaeological datasets, and time to practice. We’ll troubleshoot together and emphasize learning over perfection
52+
53+
## Attendee requirements
54+
55+
- Laptop
56+
- R (https://cran.rstudio.com/) installed
57+
- RStudio (https://posit.co/download/rstudio-desktop/) installed, use this guide if needed: https://rstudio-education.github.io/hopr/starting.html
58+
59+
## Links
60+
61+
* [GitHub repository](https://github.com/petrpajdla/intRo)

‎content/sessions/caa2026_workshop_code .md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
title: "Code review and best practices in programming"
3+
sessionType: workshop
4+
date: 2026-03-31
5+
publishDate: 2026-03-20
6+
conference: CAA 2026, Vienna
7+
conferenceUrl: https://2026.caaconference.org
8+
sessionCode: "-"
9+
organisers:
10+
- Matteo Tomasini
11+
---
12+
13+
**When:** 2026-03-31, 13:30 - 16:30 CET
14+
**Where:** In person, TU Wien, room AC 02 - 2 (Karlplatz 13, 1040 Vienna)
15+
**Format:** Half-day workshop
16+
17+
18+
## Description
19+
20+
With the introduction of more and more digital tools in archaeology, most journals made it mandatory to publish software on a public repository such as Zenodo or Github, even when said software is not the central topic of a paper. However, during the process of peer review after submitting a paper, only a few journals requires of their reviewers to review a software. Additionally, in many cases the review does not follow a specific protocol to ensure that the code is running and functional. In other words, ensuring the correctness of code review is up to the reviewer’s time, capability and willingness.
21+
22+
On the contrary of code review performed in business software development settings – which aims at functionality as well as at uniforming a code base written by several individuals – the process of scientific code review aims at making sure that a code functions correctly, but it also aims at making it more readable by external individuals, and more usable in the future both as its own piece of software, or for further development. The consequence of lack of software review is that a lot of software becomes unavailable a few months after publication – either because it was not written nor assessed to ensure maintainability, or because the original developers left the building and nobody is able to pick up the obscure code.
23+
24+
A simple way to decrease the amount of published unusable software, is to perform code review on each piece of software that see the light of day on a journal. However, code review requires the collaboration of developers who are tasked with writing code better. This is why it is paramount to spread good practices in archaeological programming: these include code documentation (e.g. comments in the code), unit testing, proper software design and good stylistic writing. Learning these principles makes of us better software developers, but also contributes to making review of software easier on reviewers.
25+
26+
In this workshop, we will learn about software design principles and best practices in programming through a look at scientific code review. A short presentation will be followed by some hands-on work.
27+
28+
## Attendee requirements
29+
30+
- laptop
31+
- at least a little bit of experience in coding
32+
- a Github profile would be useful, but not required
33+
34+
Attendees are encouraged to find by themselves the code that they want to review during the hands-on part of the workshop. Being able to run code written in one of Python, R or NetLogo (or any other common language out there) will be necessary for the hands-on part: it would be beneficial to install all the necessary components for one or more of these languages before the workshop.
35+
36+

0 commit comments

Comments
 (0)