|
1 | 1 | ---
|
2 |
| -title: "Tools for the revolution: developing scientific programming packages for archaeology" |
| 2 | +title: "Tools for the 'Third Science Revolution': developing scientific software packages for archaeology" |
3 | 3 | author:
|
4 | 4 | - Joe Roe <<[email protected]>>, University of Copenhagen
|
5 | 5 | - Martin Hinz <<[email protected]>>, University of Bern
|
6 |
| -- Clemens Schmid <<clemens@nevrome.de>>, MPI-SHH |
| 6 | +- Clemens Schmid <<[email protected].de>>, MPI-SHH |
7 | 7 | output: pdf_document
|
8 | 8 | bibliography: references.bib
|
| 9 | +geometry: "left=1.5cm,right=1.5cm,top=1cm,bottom=1cm" |
9 | 10 | ---
|
10 | 11 |
|
11 | 12 | Standard session proposal for CAA2021, Cyprus
|
12 | 13 | Convened on behalf of the *Scientific Scripting Languages in Archaeology* special interest group (SIG-SSLA)
|
13 | 14 |
|
14 | 15 | ## Abstract
|
15 | 16 |
|
16 |
| -The increasing use of scientific programming languages (e.g. R or Python) is transforming the practice of computational archaeology. |
17 |
| -This "tool-driven revolution" [@Schmidt2020] promises to greatly improve the accessibility, power, and reproducibility of quantitative analyses. |
18 |
| -But a tool-driven revolution needs tools. |
| 17 | +The increasing use of scientific programming languages (e.g. R or Python) is changing the way computational analysis are conducted in archaeology. |
| 18 | +This "tool-driven revolution" [@Schmidt2020] promises to greatly improve the accessibility, power, and reproducibility of quantitative analyses and thereby to permanently influence the field as a whole [@Kristiansen2014]. |
| 19 | + |
| 20 | +But a tool-driven revolution dies without versatile and sturdy tools. |
19 | 21 | As inveterate methodological borrowers, we can frequently rely on implementations in other fields, but the adoption of scripted analysis also reiterates the long-established need for methods designed specifically for archaeological data and archaeological problems [@Kintigh1987;@Aldenderfer1998].
|
20 |
| -As a result, recent years have seen a proliferation in packages developed by and for archaeologists (<<http://open-archaeo.info/>>). |
| 22 | +Recent years have seen a proliferation in packages developed by and for archaeologists (e.g. <<http://open-archaeo.info/>>). |
21 | 23 | An increasing number of computational archaeologists therefore find themselves not only in the role of analyst, but also that of a 'research software engineer' [@Baxter2012]; not just using tools, but making them.
|
22 | 24 | The distinct set of skills and practices this role demands has not yet been widely discussed within the field, but establishing what constitutes 'good' software engineering in archaeology is vital if we are to ensure that our new tools do what they say they do, work together, can be maintained over the long term, and are accessible to the broadest possible community of archaeological practitioners.
|
23 | 25 |
|
24 | 26 | This session, organised on behalf of the 'scientific scripting languages' special interest group, will survey the state of the art in archaeological packages for R, Python, and other scientific programming languages.
|
25 |
| -We invite technical or theoretical papers on new packages; |
26 |
| -significant updates to existing packages; |
27 |
| -general concepts in package development as applied to archaeology (e.g. user interface design, unit testing, continuous integration, software peer review); |
28 |
| -critical reviews of software support for specific domains of analysis; |
29 |
| -or discussions of future priorities for package development in archaeology. |
30 |
| -The session is aimed at both developers and users of scientific programming packages in archaeology, as well as prospective users or developers. |
| 27 | +We invite technical or theoretical papers on |
| 28 | + |
| 29 | +- new packages |
| 30 | +- significant updates to existing packages |
| 31 | +- general concepts in package development as applied to archaeology (e.g. user interface design, unit testing, continuous integration, software peer review) |
| 32 | +- critical reviews of software support for specific domains of analysis |
| 33 | +- discussions of future priorities for package development in archaeology |
| 34 | + |
| 35 | +The session is aimed at both developers and users of scientific software in archaeology, as well as prospective users or developers. |
31 | 36 | A companion workshop on package development for beginners is also planned.
|
32 | 37 |
|
33 | 38 | ## References
|
0 commit comments