KOPYA NG SALIN 🔗
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 7/6/2024 5:18:40 PM
Duration: 2975.175
Channels: 1
1
00:00:00.080 --> 00:00:05.220
Today, I'm interviewing Sean Graham about his work on the Eimeline Digital Archaeology textbook.
2
00:00:18.119 --> 00:00:22.699
Hello, and welcome to podcast dot in it, the podcast about Python and the people who make it great.
3
00:00:23.000 --> 00:00:29.685
When you're ready to launch your next app or want to try a project you hear about on the show, you'll need somewhere to deploy it. So say hi to our friends over at Linode.
4
00:00:30.145 --> 00:00:40.110
With 200 gigabit private networking, scalable shared block storage, node balancers, and a 40 gigabit public network, all controlled by a brand new API, you've got everything you need to scale up.
5
00:00:40.489 --> 00:00:41.230
Go to pythonpodcast.com/linode,
6
00:00:43.665 --> 00:00:51.445
l I n o d e, to get a $20 credit and launch a new server in under a minute. And don't forget to thank them for their continued support of this show.
7
00:00:52.530 --> 00:00:57.110
And if you're like me, then you need a simple and easy to use tool to keep track of all of your projects.
8
00:00:57.490 --> 00:01:06.125
Some project management platforms are too flexible, leading to confusion of workflows and days' worth of setup, and others are so minimal that they aren't worth the cost of admission.
9
00:01:06.985 --> 00:01:10.609
After using Clubhouse for a few days, I was impressed by the intuitive flow.
10
00:01:10.909 --> 00:01:19.305
Going from adding the various projects that I work on to defining the high level epics that I need to stay on top of and creating the various tasks that need to happen only took a few minutes.
11
00:01:19.925 --> 00:01:22.025
I was also pleased by the presence of subtasks,
12
00:01:22.460 --> 00:01:28.320
seamless navigation, and the ability to create issue and bug templates to ensure that you never miss capturing essential details.
13
00:01:29.180 --> 00:01:34.424
Listeners of this show will get a full 2 months for free on any plan when you sign up at python podcast.com/clubhouse.
14
00:01:36.244 --> 00:01:39.384
So help support the show and help yourself get organized today.
15
00:01:40.260 --> 00:01:42.280
And don't forget to visit the site at pythonpodcast.com
16
00:01:43.299 --> 00:01:50.185
to subscribe to the show, sign up for the mailing list, and read the show notes. And don't forget to keep the conversation going at python podcast.com/chat.
17
00:01:51.765 --> 00:02:09.515
Registration for PyCon US, the largest annual gathering across the community, is open now. So don't forget to get your ticket, and I'll see you there. Your host as usual is Tobias Macy. And today, I'm interviewing Sean Graham about his work on the online digital archaeology text book. So, Sean, could you start by introducing yourself?
18
00:02:10.135 --> 00:02:17.110
Hi. I'm Sean Graham. I'm an associate professor of digital humanities in the history department at Carleton University in Ottawa, Canada.
19
00:02:17.970 --> 00:02:20.310
And do you remember how you first got introduced to Python?
20
00:02:21.410 --> 00:02:21.910
I
21
00:02:23.245 --> 00:02:26.305
I think what happened was when I first started
22
00:02:26.844 --> 00:02:27.584
at Carlton,
23
00:02:28.125 --> 00:02:28.625
I
24
00:02:29.325 --> 00:02:30.465
my my computational
25
00:02:30.765 --> 00:02:34.340
background was in simulation modeling in agent based modeling.
26
00:02:34.880 --> 00:02:38.420
And I I'm not particularly good at any of this stuff.
27
00:02:38.720 --> 00:02:49.754
And I was using a platform called Metlogo, which was originally developed to teach high school students about complex systems and complexity theory and and that sort of thing.
28
00:02:50.349 --> 00:02:53.250
And when I joined the history department
29
00:02:53.870 --> 00:02:56.450
as an archaeologist, I felt like a bit of an imposter,
30
00:02:57.230 --> 00:02:57.730
and
31
00:02:58.269 --> 00:02:58.769
I
32
00:02:59.805 --> 00:03:01.105
needed to quickly
33
00:03:01.485 --> 00:03:09.890
learn everything that was going on in other facets of history and archaeology and to figure out how I could fit into everything that was going on here.
34
00:03:10.590 --> 00:03:12.610
And a little bit of googling
35
00:03:12.910 --> 00:03:13.970
around later,
36
00:03:14.270 --> 00:03:15.330
I came across
37
00:03:16.015 --> 00:03:22.995
version 1 of the programming historian, which was an online textbook in series of tutorials by Bill Turkel at Western
38
00:03:23.450 --> 00:03:26.190
at the University of Western Ontario and Adam Krimbill.
39
00:03:26.730 --> 00:03:29.629
And he had a sequence of
40
00:03:31.095 --> 00:03:34.315
common tasks that a historian might want to do programmatically,
41
00:03:35.095 --> 00:03:40.520
and they were all written in Python. So I sat down and worked my way through those, and
42
00:03:41.240 --> 00:03:41.880
it's been,
43
00:03:43.000 --> 00:03:44.540
you know, how fast can I
44
00:03:44.920 --> 00:03:46.700
search for something on Stack Overflow?
45
00:03:47.000 --> 00:03:50.805
But it was very much courtesy of of Bill and Adam's
46
00:03:51.585 --> 00:03:54.325
original work, which came out in about
47
00:03:54.785 --> 00:03:55.285
2, 008,
48
00:03:55.905 --> 00:03:56.485
I think.
49
00:03:56.865 --> 00:03:58.805
So I started here in 2010.
50
00:04:00.830 --> 00:04:01.470
Well, it's,
51
00:04:02.190 --> 00:04:03.410
opportune happenstance
52
00:04:03.710 --> 00:04:08.370
that Python has continued to grow in popularity and use, which I'm sure has
53
00:04:08.735 --> 00:04:11.635
simplified some of your ongoing efforts to apply
54
00:04:12.015 --> 00:04:12.995
programming practices
55
00:04:13.295 --> 00:04:18.620
to your work in the archaeology department and or, sorry, in the history department as an archaeologist?
56
00:04:19.800 --> 00:04:21.820
Oh, yeah. Very much. And
57
00:04:22.360 --> 00:04:24.199
it's it's
Load full transcript
interesting because everything
58
00:04:24.705 --> 00:04:30.165
you know, there are fashions in everything, and there are fashions in history as well as in archaeology.
59
00:04:30.545 --> 00:04:31.045
And
60
00:04:31.425 --> 00:04:38.710
there there's been a lot of interest in in mapping and web mapping and historical GIS.
61
00:04:40.130 --> 00:04:40.630
And
62
00:04:41.090 --> 00:04:42.229
things like ArcGIS
63
00:04:42.935 --> 00:04:44.474
have rather expensive
64
00:04:44.775 --> 00:04:45.275
licenses.
65
00:04:45.895 --> 00:04:46.395
So
66
00:04:46.854 --> 00:04:51.035
open GIS software, things like QGIS, which has a lot of
67
00:04:51.490 --> 00:04:55.510
modularity built into it and and can be scripted in Python and so
68
00:04:55.890 --> 00:05:02.215
on, means that trying to stay 1 step ahead of where my students are interested keeps pushing me to to learn new things.
69
00:05:03.794 --> 00:05:05.814
Yeah. I've had occasion to use QGIS
70
00:05:06.115 --> 00:05:06.615
myself
71
00:05:06.995 --> 00:05:14.120
for some physical installations of IoT sensors in a past job, and it was definitely useful for being able
72
00:05:14.820 --> 00:05:22.544
to have a open and accessible platform to tinker with and build up maps of where the different sensors were and try to create overlays
73
00:05:22.845 --> 00:05:25.745
of what the, network paths were.
74
00:05:26.685 --> 00:05:27.985
Absolutely. And
75
00:05:28.340 --> 00:05:32.040
the the intersection of Python with all sorts of different open source
76
00:05:32.580 --> 00:05:35.620
platforms has been a real boom for me because I can't
77
00:05:36.335 --> 00:05:38.035
I'm not allowed to,
78
00:05:39.215 --> 00:05:44.355
assign a particular software package as a required purchase to students.
79
00:05:44.840 --> 00:05:48.940
I can I can put down, you know, purchase this $200 textbook
80
00:05:49.320 --> 00:05:53.740
without issue? But if I say you you have to buy a $20 subscription to something,
81
00:05:54.475 --> 00:05:59.535
that I'm not allowed to do. So we we need to do some catching up. But in the meantime,
82
00:06:00.315 --> 00:06:08.080
it pushes me to use a lot of open source stuff, which is great because then the students learn how to fend for themselves and figure out
83
00:06:08.780 --> 00:06:15.455
how to find the packages or the software or the platforms or whatever that can help them reach their research goals.
84
00:06:16.555 --> 00:06:22.014
1 of the few cases where the unintended side effects of bureaucracy ends up being positive.
85
00:06:22.639 --> 00:06:23.860
Absolutely. Yeah.
86
00:06:25.120 --> 00:06:28.340
And so as part of your work as a professor
87
00:06:28.800 --> 00:06:29.699
in archeology
88
00:06:30.080 --> 00:06:37.915
and in the history department, you have collaborated on this online digital archaeology textbook or Odate for short.
89
00:06:38.295 --> 00:06:41.035
So can you start by giving a bit of an explanation
90
00:06:41.880 --> 00:06:45.500
of at least how you see the definition of digital archaeology?
91
00:06:46.840 --> 00:06:47.340
Sure.
92
00:06:47.800 --> 00:06:49.180
For me, digital archaeology
93
00:06:49.480 --> 00:06:51.419
is not just about using
94
00:06:52.745 --> 00:06:53.245
computational
95
00:06:53.625 --> 00:06:59.725
power to ask archeological questions or to answer archeological questions. It also involves
96
00:07:00.230 --> 00:07:02.090
thinking through what these tools
97
00:07:02.550 --> 00:07:03.370
and approaches
98
00:07:03.670 --> 00:07:06.890
do to how I understand or conceive the past
99
00:07:07.350 --> 00:07:08.010
as well.
100
00:07:08.435 --> 00:07:10.775
So in the Open Digital Archaeology textbook,
101
00:07:11.715 --> 00:07:13.574
we have a lot of
102
00:07:14.835 --> 00:07:17.890
support, I suppose, for using digital
103
00:07:18.270 --> 00:07:18.770
tools
104
00:07:19.710 --> 00:07:20.690
to deform
105
00:07:21.230 --> 00:07:21.970
our archaeological
106
00:07:22.350 --> 00:07:24.370
material or deform our perspective
107
00:07:25.145 --> 00:07:29.645
on what we're looking at, to think through creative uses, so computational creativity
108
00:07:30.105 --> 00:07:30.845
as well
109
00:07:31.625 --> 00:07:32.525
as straightforward,
110
00:07:33.940 --> 00:07:40.120
you know, spatial statistics or or what have you. So it sits in a broader digital humanities
111
00:07:40.580 --> 00:07:41.080
framework.
112
00:07:41.595 --> 00:07:44.335
Archaeology has been using things like GIS for
113
00:07:44.794 --> 00:07:45.695
40 years
114
00:07:46.315 --> 00:07:49.855
and there's any amount of support for teaching GIS,
115
00:07:50.930 --> 00:07:54.310
but there's much less support out there for
116
00:07:55.729 --> 00:07:56.550
trying to
117
00:07:57.090 --> 00:07:58.710
say you're interested in how
118
00:07:59.445 --> 00:08:02.985
visitor impacts on an archaeological site in a national park
119
00:08:03.285 --> 00:08:07.225
and maybe what you wanna be doing is scraping Instagram and studying
120
00:08:08.090 --> 00:08:16.270
comments for what people are attending to and what what they find is important or or meaningful. So that's the kind of thing you can also learn
121
00:08:16.664 --> 00:08:19.645
courtesy of of our textbook.
122
00:08:20.504 --> 00:08:26.125
And in teaching or trying to teach these kinds of methods in my own classes, I end up wasting
123
00:08:26.810 --> 00:08:29.790
2, 3 weeks on tech support and getting everybody
124
00:08:30.490 --> 00:08:31.710
on the same page.
125
00:08:32.410 --> 00:08:39.775
I have to rely very much on my students bringing their own device, but I can't be supporting 3 different flavors of Windows
126
00:08:40.315 --> 00:08:40.815
and
127
00:08:41.675 --> 00:08:49.269
machines that might have 2 gigs of RAM and or 7 gigs or or the odd person with a Linux box or,
128
00:08:49.649 --> 00:08:52.149
you know, Mac machines from
129
00:08:52.610 --> 00:08:54.230
4 or 5 years of
130
00:08:54.769 --> 00:08:55.509
of of different
131
00:08:56.055 --> 00:08:56.555
specs.
132
00:08:57.015 --> 00:08:58.714
So with Odate, we
133
00:08:59.015 --> 00:08:59.515
also
134
00:09:00.535 --> 00:09:03.274
the the original vision was to have an entire
135
00:09:04.210 --> 00:09:09.910
virtual machine that could be installed with 1 click, and the textbook would be inside the virtual machine as well.
136
00:09:10.450 --> 00:09:17.465
That proved to be really difficult because of the security implications and the university not wanting to open
137
00:09:18.650 --> 00:09:21.870
ports to to anybody to be running
138
00:09:22.330 --> 00:09:24.190
code on our servers.
139
00:09:25.305 --> 00:09:31.405
I was developing all of this and proposing all of this right in the middle of a ransomware attack at our university.
140
00:09:32.025 --> 00:09:32.425
So,
141
00:09:32.985 --> 00:09:34.285
you can imagine how
142
00:09:34.940 --> 00:09:37.760
nervous what I was proposing was was making people.
143
00:09:38.380 --> 00:09:43.680
But it was around about that time that Tim Sherritt, who is a digital historian in Australia,
144
00:09:44.355 --> 00:09:45.014
sent me
145
00:09:46.035 --> 00:09:48.774
a direct message on Twitter saying, have you seen this binder
146
00:09:49.394 --> 00:09:49.894
service?
147
00:09:50.754 --> 00:09:52.375
And that that
148
00:09:53.220 --> 00:09:56.680
really enabled everything to take right off because I could just
149
00:09:57.140 --> 00:09:57.960
package up
150
00:09:58.340 --> 00:09:58.840
targeted
151
00:09:59.220 --> 00:10:00.680
exercises or packages
152
00:10:01.060 --> 00:10:03.584
or or, Jupyter Notebooks
153
00:10:04.285 --> 00:10:05.425
in a single repo,
154
00:10:05.964 --> 00:10:10.944
1 click, boom, binder, virtual environment, and we were off to the races.
155
00:10:11.710 --> 00:10:12.190
So it's,
156
00:10:14.670 --> 00:10:18.930
it it was very much different what I ended up building than what I initially
157
00:10:19.310 --> 00:10:19.810
proposed.
158
00:10:20.750 --> 00:10:21.250
And
159
00:10:22.324 --> 00:10:25.305
this was funded by an outfit called Ecampus Ontario,
160
00:10:25.685 --> 00:10:26.824
which is a
161
00:10:27.764 --> 00:10:30.505
an agency of the Ontario Provincial Government
162
00:10:30.885 --> 00:10:31.385
that
163
00:10:32.000 --> 00:10:32.720
wanted to,
164
00:10:34.080 --> 00:10:36.420
wants to support Open Educational Resources.
165
00:10:37.200 --> 00:10:38.420
And in their
166
00:10:39.385 --> 00:10:39.885
initial,
167
00:10:40.745 --> 00:10:44.205
description of the call for proposals it was clear that they imagined
168
00:10:44.825 --> 00:10:47.965
digital textbooks as being basically PDFs
169
00:10:48.709 --> 00:10:50.009
that a person could download
170
00:10:50.629 --> 00:10:54.889
and and maybe print out and put into a course pack. So
171
00:10:55.885 --> 00:10:58.545
an online digital textbook with Jupyter
172
00:10:59.005 --> 00:11:01.105
notebooks and binder powered
173
00:11:01.565 --> 00:11:02.065
environments,
174
00:11:03.325 --> 00:11:03.825
really
175
00:11:04.470 --> 00:11:06.410
pushed the envelope for what they were imagining.
176
00:11:07.350 --> 00:11:17.245
And in the end result, it ends up being much easier to keep things relevant and up to date as well because you don't have this static asset of a PDF,
177
00:11:17.625 --> 00:11:26.339
for instance, that somebody might download and can quickly have issues with various different versions floating around or not knowing
178
00:11:26.775 --> 00:11:37.060
how up to date something is, or if new versions of packages come out and you're having source code embedded within the PDF that might not actually be accurate anymore versus this
179
00:11:37.440 --> 00:11:49.134
binder environment that is hosted, that is always going to be consistent for everybody who accesses it within a given time frame. So I imagine that has greatly simplified your
180
00:11:49.435 --> 00:11:53.269
process of teaching these systems as well. Oh, yeah. Absolutely.
181
00:11:53.810 --> 00:11:55.589
And and it's great too because,
182
00:11:56.209 --> 00:12:12.430
you know, when we revealed this to the world, I said, and I identified Twitter and via my blog, you know, I said, look, this is there's gonna be rough edges. There's gonna be things that don't work. There's gonna be things that get dated or packages are gonna change. That's okay. That's part of the learning. That's part of what we want you all to understand.
183
00:12:13.130 --> 00:12:21.035
Here's how you can contribute. Here's how you can suggest changes. Here's how you can tell us when things are broken, this is how we can fix it. And so it becomes
184
00:12:21.415 --> 00:12:27.540
becomes very much a living document. And we've already had some poll requests from people external to the project improving,
185
00:12:28.480 --> 00:12:30.820
our section on databases, for instance,
186
00:12:31.529 --> 00:12:32.029
adding
187
00:12:32.345 --> 00:12:34.205
adding sections on graph databases.
188
00:12:35.225 --> 00:12:38.765
But even 1 of my even 1 of the Jupyter Notebooks that we built
189
00:12:39.145 --> 00:12:51.665
for our initial launch, it was, it was using or it was trying to teach about principles of linked open data and how to do sparkle queries and so on. On. And we were using the endpoint from the British Museum.
190
00:12:52.365 --> 00:12:53.425
The British Museum
191
00:12:53.964 --> 00:12:56.704
totally pulled the plug on all of that
192
00:12:58.120 --> 00:13:01.820
the people who'd been supporting it and and championing it
193
00:13:02.360 --> 00:13:05.020
at, at their institution. And so that endpoint
194
00:13:05.835 --> 00:13:08.975
went down and is no longer supported. So,
195
00:13:09.355 --> 00:13:12.015
you know, things change quickly in
196
00:13:12.690 --> 00:13:14.950
in the the world of museums and
197
00:13:15.650 --> 00:13:16.710
and, cultural
198
00:13:17.170 --> 00:13:20.470
institutions as far as their their online stuff goes.
199
00:13:20.850 --> 00:13:21.350
So
200
00:13:22.485 --> 00:13:28.425
if if we were building things in a static sense, that would be an enormous disaster for us. But because
201
00:13:29.420 --> 00:13:37.440
we anticipate, we expect this kind of stuff to happen in the first place, the totally, the repos and notebooks and binders,
202
00:13:38.385 --> 00:13:39.285
turns it into
203
00:13:39.745 --> 00:13:43.765
a a learning experience for everybody. So it's it's authentic. It's real.
204
00:13:44.625 --> 00:13:45.125
And
205
00:13:45.790 --> 00:13:51.250
1 thing that I found interesting in the process of reading about the textbook
206
00:13:51.630 --> 00:13:52.130
and
207
00:13:52.485 --> 00:13:59.225
some of your blog posts on the matter and looking through the material is the concept of a perpetual beta that you are
208
00:13:59.660 --> 00:14:01.440
supporting for this work,
209
00:14:01.820 --> 00:14:19.130
which means that there as you said, you decided to go ahead and launch it, even though it wasn't necessarily perfect in your mind, but recognizing that it will never reach that state of perfection, especially if you never release it to the world. So wondering if you can talk a bit about your philosophies
210
00:14:19.590 --> 00:14:20.090
of
211
00:14:20.470 --> 00:14:23.450
how you view the textbook as this living entity
212
00:14:23.945 --> 00:14:32.525
and some of your hopes for how the community will engage with it both in terms of the software community and the broader academic community?
213
00:14:33.160 --> 00:14:33.660
Yeah.
214
00:14:34.040 --> 00:14:36.940
Well, the part of the advantage of a perpetual
215
00:14:37.400 --> 00:14:38.780
beta framework is
216
00:14:39.240 --> 00:14:44.335
I'm I'm not expert in every single thing that we've covered in the in the volume,
217
00:14:44.715 --> 00:14:49.455
and I never could be. I have I have deep experience in a extremely narrow
218
00:14:51.040 --> 00:14:53.140
aspect of of all of this. So
219
00:14:53.520 --> 00:14:58.980
I I don't think we could ever reach the kind of perfection that you would want for
220
00:14:59.575 --> 00:15:08.230
or that we have been trained to expect for print publications. Right? You you put something out in prints and you never revisit it.
221
00:15:08.550 --> 00:15:10.889
By by focusing it or
222
00:15:11.990 --> 00:15:17.290
branding it, maybe that's a better word, but by saying to people, look, it's perpetual beta
223
00:15:18.055 --> 00:15:18.555
means
224
00:15:19.735 --> 00:15:29.060
that my hope is that when people encounter things that are a bit wonky or not as clearly explained as we might want, that they'll take it in the spirit in which it is offered
225
00:15:30.880 --> 00:15:33.220
and try to to improve things.
226
00:15:34.745 --> 00:15:38.045
And in that sense, if people fork it and
227
00:15:38.904 --> 00:15:47.520
it ends up going in in many different directions, that's that's good. I I don't wanna be prescriptive about what digital archaeology
228
00:15:47.980 --> 00:15:49.280
is or could be,
229
00:15:49.635 --> 00:15:54.215
but rather the people who who need it or who want it and take it forward
230
00:15:54.675 --> 00:15:57.895
become in the driver's seat. And I know that it's it's gonna
231
00:15:58.660 --> 00:16:01.959
mean that I have to always keep an eye on what's going on,
232
00:16:02.420 --> 00:16:12.475
and, eventually, maybe I'll be able to handle the the official reins to somebody else. But it also opens up teaching opportunities for me too with my my graduate students, my undergraduates,
233
00:16:13.335 --> 00:16:20.820
about what it means to to build community or to to try and keep something like this as current as possible.
234
00:16:21.839 --> 00:16:23.460
So Perpetual Beta,
235
00:16:24.125 --> 00:16:28.225
in 1 sense it's a bit me covering my ass and recognizing that
236
00:16:29.485 --> 00:16:32.305
I couldn't hope to put out something that
237
00:16:33.830 --> 00:16:38.089
covers all the bases and is perfect the first time.
238
00:16:38.630 --> 00:16:39.850
But I,
239
00:16:40.875 --> 00:16:41.855
more seriously,
240
00:16:42.795 --> 00:16:44.495
I I regard it as an open invitation,
241
00:16:45.755 --> 00:16:47.375
and I hope that people will,
242
00:16:48.019 --> 00:16:51.160
you know, will accept it in the in the spirit in which it is offered.
243
00:16:51.940 --> 00:16:55.800
And in terms of the subject matter that you cover within the textbooks
244
00:16:56.395 --> 00:17:06.890
and the notebooks that go with it, I'm curious what you have found to be some of the most critical lessons for your students in order to help them be effective and successful
245
00:17:07.750 --> 00:17:08.250
archaeologists?
246
00:17:09.110 --> 00:17:09.510
The,
247
00:17:10.550 --> 00:17:13.050
the the idea about failing productively
248
00:17:13.750 --> 00:17:15.290
and and how to
249
00:17:15.924 --> 00:17:16.664
to recover
250
00:17:17.044 --> 00:17:18.424
from things that don't work
251
00:17:19.044 --> 00:17:21.144
or things that collapse on you.
252
00:17:22.620 --> 00:17:26.720
My my students coming at me in the history department and to a lesser degree in archaeology,
253
00:17:28.700 --> 00:17:31.840
they they have been trained for years to just accept
254
00:17:32.284 --> 00:17:34.145
what the computer gives them
255
00:17:34.525 --> 00:17:38.385
and to open the hood and try and get it to do something else to,
256
00:17:38.924 --> 00:17:50.885
you know, the kind of things that we, you know, growing up in the eighties, you sit down at a Commodore 64 and you turn it on and it says ready and it just blinks and it does nothing unless you start telling it what to do.
257
00:17:51.685 --> 00:17:52.185
The
258
00:17:53.765 --> 00:17:57.625
my students, at the very least, come with a huge degree of anxiety
259
00:17:58.245 --> 00:17:58.745
about
260
00:17:59.720 --> 00:18:02.300
about trying anything other than what
261
00:18:04.040 --> 00:18:09.715
the software already gives them. So they very much live inside the boxes that are are provided.
262
00:18:10.735 --> 00:18:11.715
Teaching people
263
00:18:12.175 --> 00:18:17.780
that it is okay to open the hood, that it's okay to take control of of your machine and to push back
264
00:18:18.160 --> 00:18:21.220
against the decisions that other people have made in their code
265
00:18:21.760 --> 00:18:23.940
so that you can do your research
266
00:18:24.695 --> 00:18:25.435
more honestly
267
00:18:26.295 --> 00:18:27.435
or more effectively
268
00:18:27.815 --> 00:18:29.035
or in new directions.
269
00:18:29.495 --> 00:18:31.755
That's that's a really hard thing to teach.
270
00:18:32.429 --> 00:18:32.929
So
271
00:18:34.030 --> 00:18:37.170
in the in the textbook, we put a lot of effort into
272
00:18:38.590 --> 00:18:39.570
talking about
273
00:18:40.030 --> 00:18:41.809
a productive fail mindsets,
274
00:18:42.465 --> 00:18:45.764
about open and reproducible code, about sharing
275
00:18:46.304 --> 00:18:47.445
your code for
276
00:18:48.304 --> 00:18:48.804
replicability
277
00:18:49.264 --> 00:18:50.085
and reproducibility.
278
00:18:51.860 --> 00:18:54.840
These are things that we don't normally teach in
279
00:18:55.380 --> 00:18:58.920
at least on the humanity side of the, of the quad.
280
00:18:59.460 --> 00:18:59.960
So
281
00:19:01.135 --> 00:19:03.155
the tech will always be changing.
282
00:19:04.175 --> 00:19:08.195
But if you've got that good mindset from the outset, you'll be able to
283
00:19:08.750 --> 00:19:13.890
figure out what it is you need out of the tech and where to find answers and how to roll with it.
284
00:19:14.270 --> 00:19:17.330
And that, I think, is probably the single most useful
285
00:19:17.955 --> 00:19:20.294
thing that comes out of this whole experience.
286
00:19:21.554 --> 00:19:24.375
In terms of their experience once they graduate
287
00:19:24.755 --> 00:19:29.740
and get involved in actually doing archaeological research or field work,
288
00:19:30.040 --> 00:19:30.700
I'm wondering
289
00:19:31.000 --> 00:19:35.785
what you view as being the level of necessity of that computational
290
00:19:36.485 --> 00:19:37.865
comfort and experience
291
00:19:38.405 --> 00:19:40.185
as they progress throughout their careers?
292
00:19:41.045 --> 00:19:43.110
I think it's only gotta be to the good.
293
00:19:44.230 --> 00:19:46.809
If we can teach people how to
294
00:19:48.470 --> 00:19:52.970
figure out what they need to know, when they need to know it, and where to go
295
00:19:53.335 --> 00:19:59.115
in order to get the solutions. I mean, I spend huge amounts of time on Stack Overflow. Thank you to those folks.
296
00:19:59.735 --> 00:20:00.235
Then
297
00:20:01.850 --> 00:20:08.110
just getting in the habits of thought and understanding how code works and how to read it and and what to
298
00:20:08.985 --> 00:20:11.405
where to troubleshoot. Like, those are the things that,
299
00:20:13.465 --> 00:20:17.885
to my mind, are are more
valuable than experience with any particular
300
00:20:19.419 --> 00:20:22.720
package at a time. Right? Like, it's it's the problem of
301
00:20:23.419 --> 00:20:28.685
of GUI based software packages in the first place. If the the GUI changes, then you don't know what to do anymore.
302
00:20:29.245 --> 00:20:29.745
So
303
00:20:30.285 --> 00:20:31.905
does does that answer that question?
304
00:20:32.925 --> 00:20:37.100
It does in part, but I was also curious in the broader sense of the
305
00:20:37.480 --> 00:20:37.980
amount
306
00:20:38.440 --> 00:20:39.260
of crossover
307
00:20:39.640 --> 00:20:40.140
of
308
00:20:40.600 --> 00:20:41.500
the computational
309
00:20:41.800 --> 00:20:44.700
tools that are required for doing archaeological
310
00:20:45.080 --> 00:20:45.580
research
311
00:20:46.115 --> 00:20:47.335
and field exploration
312
00:20:48.275 --> 00:20:54.455
for people who are engaged in that in a professional context both now and as you see it progressing into the future?
313
00:20:55.570 --> 00:20:56.070
Crossover
314
00:20:56.450 --> 00:20:56.950
from
315
00:20:57.410 --> 00:20:59.830
what we're teaching to their professional lives?
316
00:21:00.290 --> 00:21:05.125
Just in terms of archaeological research, I'm just curious, like, how prevalent
317
00:21:05.585 --> 00:21:07.285
using software packages
318
00:21:08.305 --> 00:21:09.845
and computational techniques
319
00:21:10.225 --> 00:21:11.925
is applied versus
320
00:21:12.520 --> 00:21:14.300
spending time digging up artifacts
321
00:21:15.320 --> 00:21:18.780
or researching physical structures, things like that. Right. Right.
322
00:21:19.160 --> 00:21:21.100
Well, in in commercial archaeology
323
00:21:22.415 --> 00:21:23.075
right now
324
00:21:23.695 --> 00:21:28.835
and I and I mean I have to be honest, I haven't worked in commercial archaeology in quite some time.
325
00:21:30.080 --> 00:21:33.540
I actually have very little experience in commercial
326
00:21:34.080 --> 00:21:38.180
work but there's computational work happening all the time
327
00:21:38.525 --> 00:21:39.025
Databases,
328
00:21:39.565 --> 00:21:40.625
mapping, GIS,
329
00:21:41.325 --> 00:21:42.304
public outreach
330
00:21:43.165 --> 00:21:47.425
for all of it. I'd say the the computational work is more
331
00:21:48.610 --> 00:21:51.430
more the bread and butter than the the actual
332
00:21:52.130 --> 00:21:55.990
field work as it were because as the field work happens,
333
00:21:56.965 --> 00:21:58.745
the the material is being digitized
334
00:21:59.684 --> 00:22:00.825
as the field work
335
00:22:01.205 --> 00:22:03.225
goes on. Right? Things are being excavated,
336
00:22:03.684 --> 00:22:06.139
things get recorded into various databases,
337
00:22:06.840 --> 00:22:07.740
the the whole
338
00:22:08.440 --> 00:22:09.980
analytical side that happens
339
00:22:10.519 --> 00:22:14.860
the field work is you know maybe 1 third of what goes on
340
00:22:15.424 --> 00:22:18.705
and it's all the behind the scenes stuff, the,
341
00:22:19.745 --> 00:22:24.485
the assessments that happen before field work goes on, the predictive work, the
342
00:22:25.010 --> 00:22:26.710
the archival work to,
343
00:22:27.810 --> 00:22:28.870
work out the probabilities
344
00:22:29.170 --> 00:22:35.195
of what kinds of materials you might reasonably expect. Like, that sort of work is very computational
345
00:22:36.535 --> 00:22:37.115
and probably
346
00:22:38.695 --> 00:22:39.195
occupies
347
00:22:39.655 --> 00:22:44.270
far more of the the working life of of people in commercial work than
348
00:22:44.809 --> 00:22:46.590
than than field work does.
349
00:22:47.450 --> 00:22:49.390
And in terms of the
350
00:22:49.845 --> 00:22:52.184
data sources and data formats
351
00:22:52.645 --> 00:22:54.585
that would commonly be encountered,
352
00:22:54.885 --> 00:22:56.345
you mentioned some of these
353
00:22:56.860 --> 00:22:59.280
geographical surveys and GIS information,
354
00:23:00.059 --> 00:23:00.559
digitization
355
00:23:01.100 --> 00:23:03.280
of some of the artifacts that might be recovered,
356
00:23:03.660 --> 00:23:07.804
whatever formats that might take, and then also recording of metadata.
357
00:23:08.265 --> 00:23:08.765
And,
358
00:23:09.304 --> 00:23:12.045
I'm sure there are time aspects to
359
00:23:12.430 --> 00:23:19.330
when the artifacts are recorded or when the observations are taken. So I'm just wondering if you can talk through those different types of
360
00:23:19.845 --> 00:23:25.065
data and the sources and locations that they might be found for people who are engaged in
361
00:23:25.445 --> 00:23:28.585
performing these computational analysis of all of that information.
362
00:23:29.010 --> 00:23:30.630
Right. Well, it's,
363
00:23:31.090 --> 00:23:33.270
it's it's a god awful mess.
364
00:23:33.650 --> 00:23:34.789
There is material
365
00:23:35.250 --> 00:23:37.350
trapped in image based PDFs.
366
00:23:37.809 --> 00:23:38.789
There's stuff
367
00:23:39.235 --> 00:23:40.855
in old versions of Excel.
368
00:23:41.554 --> 00:23:42.534
There are XML,
369
00:23:43.075 --> 00:23:43.575
JSON,
370
00:23:43.875 --> 00:23:44.375
CSV,
371
00:23:45.955 --> 00:23:46.455
FileMaker,
372
00:23:47.399 --> 00:23:49.340
God help us all, Word documents.
373
00:23:52.919 --> 00:23:55.179
There there's there's no there
374
00:23:56.335 --> 00:23:57.395
there are archaeological
375
00:23:57.775 --> 00:24:00.995
repositories for digital work, and it's not necessary
376
00:24:01.375 --> 00:24:02.275
not necessarily
377
00:24:03.455 --> 00:24:05.075
true that every
378
00:24:05.670 --> 00:24:10.410
academic archaeologist or every commercial archaeologist is putting materials into these repositories.
379
00:24:12.310 --> 00:24:14.170
Some of the bigger ones are
380
00:24:14.545 --> 00:24:15.285
open context,
381
00:24:15.585 --> 00:24:17.125
open context dot org,
382
00:24:18.065 --> 00:24:20.965
which tends to have everything represented in
JSON.
383
00:24:21.345 --> 00:24:27.010
Then there's TIDAR, which is out of Arizona State University, I believe, and they are more of
384
00:24:28.429 --> 00:24:33.165
a they they will take your documentation in all sorts of different formats, whereas OpenContacts
385
00:24:33.625 --> 00:24:35.325
works with you as a data publisher
386
00:24:35.785 --> 00:24:39.085
to get your data into a format that can be exposed through
387
00:24:39.550 --> 00:24:40.290
their API
388
00:24:40.670 --> 00:24:44.610
and can be recombined and reused with other stuff. There's the archaeological
389
00:24:44.990 --> 00:24:48.770
data service in the UK, which again will take
390
00:24:49.545 --> 00:24:53.405
materials in lots of different formats, everything from
391
00:24:53.865 --> 00:24:55.725
field notes to to tables.
392
00:24:57.040 --> 00:25:00.240
So you you have you know, 1 of the things that we,
393
00:25:00.800 --> 00:25:03.220
1 of the binders that we have in Ode
394
00:25:03.775 --> 00:25:06.195
uses an R package called Tabulizer
395
00:25:07.055 --> 00:25:07.535
to,
396
00:25:07.935 --> 00:25:08.915
to try and,
397
00:25:10.655 --> 00:25:11.635
when you encounter
398
00:25:12.250 --> 00:25:12.750
data
399
00:25:13.130 --> 00:25:17.310
locked in a PDF to to get it into a data frame that you can then use.
400
00:25:17.770 --> 00:25:18.510
So there's
401
00:25:19.165 --> 00:25:21.825
there's some folks are using graph databases.
402
00:25:22.845 --> 00:25:24.305
Some people are using,
403
00:25:27.170 --> 00:25:29.990
all sorts of different schemas. It's,
404
00:25:30.690 --> 00:25:34.950
you you can you can encounter data in all sorts of different formats.
405
00:25:35.465 --> 00:25:36.424
A friend of mine who's,
406
00:25:37.304 --> 00:25:40.424
I forget what the the proper title is, but it is states
407
00:25:40.905 --> 00:25:44.765
a state archaeologist responsible for a lot of the data management of things.
408
00:25:45.750 --> 00:25:46.890
She encounters
409
00:25:48.470 --> 00:25:50.490
material kept in word files,
410
00:25:50.950 --> 00:25:53.450
material kept in old shoe boxes. It's
411
00:25:56.335 --> 00:25:58.515
it's a wild west of data.
412
00:25:59.295 --> 00:26:02.270
And in terms of the notebooks that,
413
00:26:02.750 --> 00:26:03.810
you and your collaborators
414
00:26:04.190 --> 00:26:06.690
have created to accompany the textbook,
415
00:26:07.150 --> 00:26:08.290
there's a
416
00:26:08.750 --> 00:26:10.445
fairly even mix year
417
00:26:10.745 --> 00:26:15.644
of R and Python code. So I'm wondering what you have found to be your personal guidelines
418
00:26:15.945 --> 00:26:19.164
for when to use each language to its greatest benefit.
419
00:26:19.950 --> 00:26:24.450
I'm not sure that I have anything really useful to say on that because I'm
420
00:26:24.910 --> 00:26:26.130
I'm a bit of a magpie
421
00:26:26.430 --> 00:26:28.475
when it comes to to code.
422
00:26:29.095 --> 00:26:37.260
If if I can get it to work and it does roughly what it is I need it to do, then that ends up being the the language or approach that I I end up using.
423
00:26:38.220 --> 00:26:38.720
So
424
00:26:39.580 --> 00:26:41.840
I got into using R
425
00:26:42.300 --> 00:26:42.800
via
426
00:26:43.580 --> 00:26:44.400
text analysis
427
00:26:45.020 --> 00:26:47.625
and topic modeling and that sort of thing.
428
00:26:48.405 --> 00:26:50.745
A lot of archaeologists are more
429
00:26:51.365 --> 00:26:54.105
comfortable with Python than they are with R.
430
00:26:54.405 --> 00:26:55.225
That said,
431
00:26:55.820 --> 00:26:58.559
Ben Marwick at, Washington State University
432
00:26:59.340 --> 00:26:59.840
has
433
00:27:00.220 --> 00:27:04.159
a huge compilation of R packages that are
434
00:27:04.675 --> 00:27:06.695
useful for archaeology. Matt Harris,
435
00:27:07.475 --> 00:27:12.535
is another 1 who's very, very handy with our can do all sorts of interesting things with it.
436
00:27:12.915 --> 00:27:13.415
So,
437
00:27:14.340 --> 00:27:18.200
really, if it does the job you needed to do, then that's the package you use.
438
00:27:19.620 --> 00:27:20.120
Yeah.
439
00:27:20.740 --> 00:27:22.760
Not the most helpful approach, I suppose.
440
00:27:23.634 --> 00:27:29.654
But as long as your code is is well commented out and you understand what it's doing, then
441
00:27:30.355 --> 00:27:31.575
either or, I suppose.
442
00:27:33.150 --> 00:27:39.890
Yeah. And I think that just in the broader sense of software, once you have enough of a foundational understanding
443
00:27:40.270 --> 00:27:41.410
of what's happening,
444
00:27:41.905 --> 00:27:42.565
then the syntax
445
00:27:43.265 --> 00:27:51.750
to some degree starts to melt away, and it's much better to be pragmatic than dogmatic in your approach to when to use which tool.
446
00:27:52.450 --> 00:27:56.210
Absolutely. Absolutely. I'm in I'm entirely self taught. I,
447
00:27:57.304 --> 00:27:59.725
I screw up and make errors all the time. So
448
00:28:00.025 --> 00:28:03.485
I really appreciate people who put out packages that
449
00:28:04.240 --> 00:28:11.220
are are cleanly explained and and commented and have examples that I can work through and think, okay.
450
00:28:11.585 --> 00:28:17.845
I see it. This is how their data is organized. I can get my data organized like that. I can use their sample code.
451
00:28:18.225 --> 00:28:25.230
Now what can I plug this in with to get to the next stage that I need it to be at? So the the IR OpenSci
452
00:28:25.850 --> 00:28:29.550
folks, they they're they've got lots of really great packages, and
453
00:28:30.715 --> 00:28:33.615
and I really appreciate what they're up to as well.
454
00:28:33.995 --> 00:28:34.975
Yeah. And particularly
455
00:28:35.275 --> 00:28:40.690
in recent years, there has been a lot more work done to ease the interoperability
456
00:28:41.390 --> 00:28:51.125
between R and Python in the data analytics space with things like the arrow project to make data frames
interoperable between R and Pandas, and
457
00:28:51.425 --> 00:28:53.525
just a a general approach within the
458
00:28:53.985 --> 00:28:55.125
community of,
459
00:28:55.720 --> 00:28:59.020
academics and scientists and data scientists to
460
00:28:59.400 --> 00:29:01.820
lower the friction and just make collaboration
461
00:29:02.120 --> 00:29:05.100
easier regardless of the language community?
462
00:29:06.505 --> 00:29:07.005
Absolutely.
463
00:29:07.385 --> 00:29:11.965
And I'm I haven't I haven't explored that project very much yet, but that's
464
00:29:12.825 --> 00:29:13.965
that kind of work
465
00:29:14.309 --> 00:29:17.690
is is really important, but it still requires an interpreter
466
00:29:18.070 --> 00:29:22.045
to get it down to the level of where so many of our students are.
467
00:29:22.605 --> 00:29:25.985
So that's something I'm gonna have to put on the agenda for
468
00:29:26.845 --> 00:29:29.265
future updates to, to Odate.
469
00:29:30.210 --> 00:29:33.590
And in terms of your overall experience
470
00:29:33.970 --> 00:29:39.030
and career, I'm curious how the skills and tools and
471
00:29:39.575 --> 00:29:48.760
thought models of software engineering have influenced your views and approaches to the way that you conduct research and education in in the realm of archaeology
472
00:29:49.060 --> 00:29:49.880
and history?
473
00:29:51.140 --> 00:29:55.080
Well, I I feel in some senses, I feel like I'm 1 step removed
474
00:29:55.460 --> 00:29:56.440
because I'm
475
00:29:57.815 --> 00:30:03.115
I'm very much influenced by people like Carl Boetticher, and I'm not entirely sure I pronounced that correctly,
476
00:30:03.815 --> 00:30:04.315
who
477
00:30:05.710 --> 00:30:08.610
was big on open notebook science and and
478
00:30:09.470 --> 00:30:14.690
and Ben Marwick, who's an archaeologist, or Caleb McDaniel, who's a historian of
479
00:30:16.575 --> 00:30:19.955
these these ideas of replicable code chunks and
480
00:30:21.294 --> 00:30:23.394
and being open about our processes
481
00:30:23.774 --> 00:30:24.274
entirely
482
00:30:25.220 --> 00:30:26.440
as academics.
483
00:30:26.900 --> 00:30:27.400
So,
484
00:30:28.420 --> 00:30:29.720
the degree to which
485
00:30:30.660 --> 00:30:32.600
the actual software community
486
00:30:33.515 --> 00:30:37.294
influences. I'm sure it does. I I'm sure it is because I'm,
487
00:30:37.835 --> 00:30:38.575
you know, I'm
488
00:30:38.875 --> 00:30:44.260
picking over carefully through people's blogs and Stack Overflow posts and trying to
489
00:30:45.040 --> 00:30:46.900
figure out my own immediate concerns.
490
00:30:47.680 --> 00:30:51.040
And I expect I I'm picking it up through osmosis, but I'm not
491
00:30:52.075 --> 00:30:55.855
I don't know that I could point to any single individual or
492
00:30:56.555 --> 00:30:58.655
or group of of people.
493
00:30:59.820 --> 00:31:03.520
And in terms of the ways that,
494
00:31:05.100 --> 00:31:05.600
software
495
00:31:05.980 --> 00:31:06.960
and analysis
496
00:31:07.340 --> 00:31:08.080
and computational
497
00:31:08.575 --> 00:31:09.075
capacity
498
00:31:09.375 --> 00:31:11.715
are applied to the field of archaeology.
499
00:31:12.735 --> 00:31:18.720
What have you found to be some of the most novel or engaging ways to make use of that?
500
00:31:19.899 --> 00:31:22.480
Well, I'm really interested in neural networks,
501
00:31:23.100 --> 00:31:25.279
for computer vision at the moment,
502
00:31:25.804 --> 00:31:27.025
and I
503
00:31:27.485 --> 00:31:30.065
I'm fascinated by things like generative
504
00:31:30.365 --> 00:31:30.865
adversarial
505
00:31:31.405 --> 00:31:34.304
networks and people exploring the the kind of latent
506
00:31:34.700 --> 00:31:35.760
space of images.
507
00:31:36.780 --> 00:31:37.280
And
508
00:31:38.220 --> 00:31:38.720
I'm
509
00:31:39.340 --> 00:31:43.440
I I have a research project on at the moment that looks at
510
00:31:44.145 --> 00:31:46.565
people who buy and sell human remains
511
00:31:47.184 --> 00:31:48.625
and trade them on,
512
00:31:49.345 --> 00:31:50.485
via social media
513
00:31:51.510 --> 00:31:54.170
and using computer vision to try and
514
00:31:55.110 --> 00:31:56.250
work out some of
515
00:31:56.870 --> 00:31:57.530
the rhetorical
516
00:31:58.070 --> 00:31:59.290
tropes of
517
00:31:59.804 --> 00:32:03.085
the visual composition of these images. Like, what is it that people are
518
00:32:04.285 --> 00:32:07.345
how are they signaling that things are for sale or
519
00:32:08.045 --> 00:32:09.265
what kinds of
520
00:32:10.120 --> 00:32:10.840
ideas that have
521
00:32:11.799 --> 00:32:18.139
you know, 1 1 thing that we're starting to notice is how when people are trying to signal something's for sale, but not actually
522
00:32:18.575 --> 00:32:20.435
stayed as much in terms of the comments,
523
00:32:21.135 --> 00:32:23.235
the the images end up being composed
524
00:32:23.935 --> 00:32:24.755
rather like
525
00:32:25.520 --> 00:32:28.020
how we would imagine a museum
526
00:32:28.640 --> 00:32:33.460
would display human remains of the, like, the 19 thirties or forties.
527
00:32:33.865 --> 00:32:36.765
So sort of an Indiana Jones visual motif,
528
00:32:37.705 --> 00:32:40.285
coming through in the images, which,
529
00:32:40.960 --> 00:32:47.460
you know, you might pick up on if you were staring at pictures all day. But when we do it at scale with
530
00:32:48.080 --> 00:32:48.580
convolutional
531
00:32:48.960 --> 00:32:52.605
neural network, it it stands out an an awful lot more.
532
00:32:53.784 --> 00:32:55.245
So that kind of thing is,
533
00:32:57.065 --> 00:33:02.190
you know, where I'm at at the moment. Other people are using them to pick
534
00:33:02.650 --> 00:33:03.230
out features
535
00:33:03.610 --> 00:33:04.110
in,
536
00:33:05.450 --> 00:33:06.510
field photographs.
537
00:33:07.325 --> 00:33:09.745
So as you're excavating you're taking photos
538
00:33:10.365 --> 00:33:12.145
of each level or
feature
539
00:33:12.525 --> 00:33:18.480
or context as you dig down. So every event that happens in the formation of a site is a context
540
00:33:18.860 --> 00:33:25.115
and you can peel these back like layers of onion or and the way that they intersect is a sort of three-dimensional,
541
00:33:25.495 --> 00:33:26.715
4 dimensional puzzle.
542
00:33:27.255 --> 00:33:29.115
And there are some folks who
543
00:33:29.815 --> 00:33:30.955
are feeding
544
00:33:32.130 --> 00:33:34.710
100 or 1000 of these kinds of photographs
545
00:33:35.090 --> 00:33:35.590
into
546
00:33:35.890 --> 00:33:37.590
neural networks to see
547
00:33:38.370 --> 00:33:38.770
what,
548
00:33:39.875 --> 00:33:46.455
what can we pick up when we let the computer do the looking rather than us. So, you know, interesting things like that.
549
00:33:46.970 --> 00:33:47.710
And another
550
00:33:48.490 --> 00:33:48.990
piece
551
00:33:49.370 --> 00:33:54.625
that I saw referenced as I was preparing for this show is the concept of archeogaming.
552
00:33:54.925 --> 00:33:59.665
So I'm wondering if you can talk a bit about what that is and some of the ways that it's applied.
553
00:34:00.285 --> 00:34:01.985
Right. So so archeogaming
554
00:34:02.950 --> 00:34:05.289
as a term was coined by Andrew Reinhart,
555
00:34:05.909 --> 00:34:07.770
who is a classical archaeologist
556
00:34:08.470 --> 00:34:08.970
and,
557
00:34:09.670 --> 00:34:10.730
archaeological publisher.
558
00:34:11.455 --> 00:34:16.195
And he was also involved with Bill Caraher and a few others in the Alamogordo
559
00:34:16.495 --> 00:34:18.720
excavations of the Atari burial ground.
560
00:34:19.119 --> 00:34:20.900
So if you've seen the game over
561
00:34:21.599 --> 00:34:22.900
documentary on Netflix
562
00:34:23.440 --> 00:34:26.340
about those excavations, you will have seen Andrew Reinhart.
563
00:34:26.955 --> 00:34:30.095
And he's actually doing a PhD in this at the moment,
564
00:34:30.715 --> 00:34:32.095
which is quite exciting.
565
00:34:32.555 --> 00:34:37.839
And he and I and a number of others for a couple of years have been exploring ideas of
566
00:34:38.380 --> 00:34:40.079
what does it mean for
567
00:34:40.380 --> 00:34:44.079
humans when so much of our culture these days is digitally mediated
568
00:34:44.655 --> 00:34:46.755
or takes place within digital spaces.
569
00:34:47.935 --> 00:34:53.875
And archaeology is about the material expression of human culture whether it's in the remote past or the current
570
00:34:54.600 --> 00:34:55.420
current day.
571
00:34:57.320 --> 00:34:58.700
So if we do archaeology
572
00:34:59.000 --> 00:35:04.115
inside these digital spaces, what does that look like? How do we translate the methods and perspectives
573
00:35:04.735 --> 00:35:06.355
of dealing with material culture
574
00:35:06.735 --> 00:35:07.235
into,
575
00:35:08.095 --> 00:35:09.475
into digital culture?
576
00:35:09.775 --> 00:35:10.675
So archaeogaming
577
00:35:10.975 --> 00:35:14.880
can be the application of archaeological perspectives within
578
00:35:15.740 --> 00:35:18.160
constructed digital spaces. It can be
579
00:35:18.780 --> 00:35:20.240
looking at the representation
580
00:35:20.620 --> 00:35:24.115
of human past or material culture through video games.
581
00:35:24.655 --> 00:35:25.155
So
582
00:35:25.615 --> 00:35:26.434
1 aspect
583
00:35:27.375 --> 00:35:30.275
of archeo gaming also intersects with archeological
584
00:35:30.710 --> 00:35:35.450
ethics when you think about loot looting mechanics and loot boxes and,
585
00:35:36.869 --> 00:35:39.225
archaeological tropes within video games.
586
00:35:39.625 --> 00:35:42.445
There's a there's another group at the University of Leiden
587
00:35:43.225 --> 00:35:46.125
who have been doing a lot of work in
588
00:35:47.599 --> 00:35:50.820
in ArQube Gaming and they run an annual conference called the,
589
00:35:51.760 --> 00:35:53.619
the interactive pasts conference.
590
00:35:54.845 --> 00:35:57.425
So it's, it's kind of an exciting
591
00:35:57.725 --> 00:35:59.585
field. Right? Because it's a new
592
00:36:00.205 --> 00:36:02.225
new avenue for for human,
593
00:36:03.330 --> 00:36:04.150
for archaeology
594
00:36:04.610 --> 00:36:06.790
to try and understand the human condition.
595
00:36:07.090 --> 00:36:10.015
Yeah. Humans have been making virtual worlds since
596
00:36:10.815 --> 00:36:14.115
the the Neolithic. Right? You look at the caves of Lascaux, you look at,
597
00:36:14.575 --> 00:36:18.275
you know, all the way up to Disneyland, that's another virtual world. So now it's
598
00:36:18.750 --> 00:36:19.810
moving into these,
599
00:36:20.510 --> 00:36:24.530
crafted virtual worlds that we interact with through the screen.
600
00:36:25.310 --> 00:36:27.275
Yeah. It's definitely a very fascinating
601
00:36:27.895 --> 00:36:28.555
area and
602
00:36:29.095 --> 00:36:33.355
just the concepts of archaeology are something that I've always found interesting
603
00:36:34.460 --> 00:36:47.785
on my own as just sort of a layperson to the field. So it's definitely great to see new techniques for trying to bring more people into it and get them starting to think about these different
604
00:36:48.484 --> 00:36:51.280
problems that are useful to explore
605
00:36:51.980 --> 00:36:54.560
for humanity as a species, both for exploring
606
00:36:54.860 --> 00:37:04.805
our cultural pasts, but also our cultural present. Right. And and 1 of the neat things of of some of Andrew's work is that he's been looking at a lot of procedural content generation
607
00:37:05.369 --> 00:37:08.270
and asking what does it mean to have machine made culture.
608
00:37:09.369 --> 00:37:14.830
And, so he's he's done things like lead expeditions into No Man's Sky or
609
00:37:16.214 --> 00:37:16.934
he he's,
610
00:37:18.055 --> 00:37:23.194
he's been doing code exegesis on the colossal cave adventure, which of course is 1 of the,
611
00:37:23.770 --> 00:37:26.110
if not the first, 1 of the first
612
00:37:26.570 --> 00:37:30.510
of these immersive worlds, just a text based mediated 1.
613
00:37:30.875 --> 00:37:31.755
So there's
614
00:37:32.235 --> 00:37:36.815
it's, ArQule Gaming is only gonna grow. I think it's going to become a a really neat,
615
00:37:38.155 --> 00:37:39.695
vector that unites,
616
00:37:40.240 --> 00:37:41.860
you know, humanities research,
617
00:37:42.320 --> 00:37:43.940
technological research, software,
618
00:37:44.960 --> 00:37:50.744
game design, game the game industry more generally. It'll be exciting to see how it how it plays
619
00:37:51.045 --> 00:37:54.585
out. And another interesting area of ways
620
00:37:54.885 --> 00:38:00.400
that digital and computational capacity are being leveraged in the field of archaeology
621
00:38:01.500 --> 00:38:03.680
is in the space of doing
622
00:38:03.980 --> 00:38:04.960
3 d scans
623
00:38:05.260 --> 00:38:06.720
of existing structures
624
00:38:07.099 --> 00:38:12.875
as a means of trying to preserve them against areas of conflict or,
625
00:38:14.214 --> 00:38:14.714
environmental
626
00:38:15.174 --> 00:38:23.170
hazards, such as acid rain or earthquakes, things like that. So I don't know if you have any experience of dealing with any of that types of information
627
00:38:23.550 --> 00:38:27.575
or, just that general field of archaeological preservation?
628
00:38:28.994 --> 00:38:30.375
Yeah. So 3 d modeling
629
00:38:30.755 --> 00:38:31.494
and photogrammetry
630
00:38:31.954 --> 00:38:37.400
and and and model building that way is it's important work. Right? Because you we're getting
631
00:38:38.020 --> 00:38:44.360
you're getting better and better resolution. And if you've got laser scanners, that's the the best resolution going.
632
00:38:44.725 --> 00:38:48.505
And it can help guide things like restoration work. We,
633
00:38:49.285 --> 00:38:53.305
there's a a gentleman here at Carlton, Steve Fye, who's using
634
00:38:53.765 --> 00:38:54.799
laser scanning
635
00:38:55.260 --> 00:38:57.119
on, a lot of the architectural
636
00:38:57.660 --> 00:39:00.000
elements of the houses of parliament
637
00:39:00.700 --> 00:39:03.200
for their for their restoration work and,
638
00:39:03.855 --> 00:39:08.435
because, you know, years of acid rain and and so on has worn them right away.
639
00:39:09.135 --> 00:39:09.295
The
640
00:39:10.690 --> 00:39:12.470
we don't talk about photographs
641
00:39:13.010 --> 00:39:14.070
as being preservation.
642
00:39:15.089 --> 00:39:20.390
And so I don't know that we should necessarily talk about digital 3 d models as being a kind of preservation because, you know, so much depends on the
643
00:39:27.955 --> 00:39:28.455
the
644
00:39:28.950 --> 00:39:30.550
And then you get things like the,
645
00:39:31.830 --> 00:39:34.089
the palm Palmyrene Arch
646
00:39:35.109 --> 00:39:36.330
episode where
647
00:39:38.415 --> 00:39:40.115
the so this in in Palmyra,
648
00:39:40.415 --> 00:39:43.875
there's this triumphal
arch that was blown up by ISIS,
649
00:39:44.415 --> 00:39:48.600
and it had been turned into a 3 d model a few years earlier,
650
00:39:48.900 --> 00:39:52.680
but that 3 d model certainly didn't have the resolution or the detail
651
00:39:53.220 --> 00:39:55.160
that is capable now. And
652
00:39:55.745 --> 00:39:59.845
it was used to mill blocks of stone to create a,
653
00:40:00.225 --> 00:40:02.965
you know, a 1 third or 2 third scale
654
00:40:03.750 --> 00:40:07.770
model, and everybody said, yay. We've got we've preserved this,
655
00:40:08.230 --> 00:40:09.930
but the the model
656
00:40:10.795 --> 00:40:13.375
had a lot less of the the the detail.
657
00:40:13.755 --> 00:40:22.920
And then we then people were putting this model up in places like Trafalgar Square to say, yay. We've we've preserved this and and take that Isis.
658
00:40:23.380 --> 00:40:25.435
But here it sits in the middle of
659
00:40:26.475 --> 00:40:33.855
empire. Right? Trafalgar Square is the center and heart of British Empire, and it's at diminished scale
660
00:40:34.480 --> 00:40:38.980
in that context. So looking at it, what kind of message are people meant to to understand
661
00:40:39.599 --> 00:40:42.180
here? Right? It's certainly not for the Syrians,
662
00:40:42.880 --> 00:40:43.380
and
663
00:40:45.375 --> 00:40:46.595
it really kind of,
664
00:40:48.015 --> 00:40:52.835
you know, takes that Western colonial gaze again and and brings it,
665
00:40:53.839 --> 00:40:56.339
really illustrates how a lot of our digital technologies
666
00:40:57.280 --> 00:40:58.099
do reproduce
667
00:40:59.040 --> 00:41:00.580
a lot of the ways of looking
668
00:41:01.724 --> 00:41:10.704
in the west that are so problematic. I mean, the the arch was then taken down and was displayed in Washington in the center of the mall, I think it was. So
669
00:41:12.080 --> 00:41:12.980
digital preservation,
670
00:41:13.840 --> 00:41:15.300
taking these 3 d models,
671
00:41:16.080 --> 00:41:16.820
I think
672
00:41:17.520 --> 00:41:20.980
can be really useful and powerful when there's a really good research
673
00:41:21.664 --> 00:41:23.204
case behind it.
674
00:41:23.984 --> 00:41:31.020
And sometimes, you know, sometimes these 3 d models might be all that we can make. When you look at the museum fire in Rio,
675
00:41:31.480 --> 00:41:36.700
you can stitch together models from tourist photos if you've got enough of them.
676
00:41:37.515 --> 00:41:40.414
Gives us a sense of what has been lost, but it's never
677
00:41:40.954 --> 00:41:42.734
it's always going to be lesser.
678
00:41:43.595 --> 00:41:44.474
I don't know. It's
679
00:41:45.400 --> 00:41:47.339
there's a lot of debate in archaeology
680
00:41:48.039 --> 00:41:48.539
about
681
00:41:49.799 --> 00:42:02.205
the value of of this kind of work in terms of things like preservation and and so on. I mean, archaeology destroys what it excavates. Right? So the record that exists in our archive
682
00:42:03.279 --> 00:42:04.579
is the only representation
683
00:42:04.880 --> 00:42:05.779
of this material
684
00:42:06.480 --> 00:42:08.819
left. So in a way, archaeology creates
685
00:42:09.119 --> 00:42:12.755
its own subject matter, but it also destroys the physical stuff.
686
00:42:13.535 --> 00:42:17.475
Yeah. I'm just thinking out loud and and riffing on on different thoughts, but
687
00:42:19.790 --> 00:42:26.210
it's we I think we have to be careful if we equate 3 d model building with preservation.
688
00:42:28.030 --> 00:42:28.530
It's
689
00:42:29.715 --> 00:42:35.235
it's important work. It can be very useful. But if we we think about it in preservation, then we gotta
690
00:42:35.955 --> 00:42:36.935
we get into
691
00:42:37.235 --> 00:42:38.950
questions of, well, who does it belong
692
00:42:39.430 --> 00:42:40.250
to? Ownership
693
00:42:40.710 --> 00:42:41.210
and
694
00:42:42.150 --> 00:42:43.930
empower and control, which
695
00:42:44.550 --> 00:42:46.010
archaeology has a really
696
00:42:47.255 --> 00:42:49.355
dirty backstory in terms of colonialism
697
00:42:49.974 --> 00:42:50.635
and and
698
00:42:54.190 --> 00:42:56.130
taking and stealing materials that
699
00:42:56.670 --> 00:42:58.290
don't necessarily belong to
700
00:42:58.750 --> 00:43:00.290
us, western white folk.
701
00:43:01.070 --> 00:43:01.570
So,
702
00:43:02.464 --> 00:43:06.325
you know, archaeology is always about the present as much as it is about the past.
703
00:43:07.905 --> 00:43:10.244
Yeah. I really appreciate that context and perspective as somebody who is not as continuously steeped
704
00:43:18.420 --> 00:43:18.920
your
705
00:43:19.464 --> 00:43:21.325
point about ethics also
706
00:43:21.865 --> 00:43:26.525
brings an interesting parallel in terms of the discussions that are happening in the areas
707
00:43:26.825 --> 00:43:29.900
of software engineering and data science of trying to determine
708
00:43:30.520 --> 00:43:32.220
what are the ethical responsibilities
709
00:43:32.600 --> 00:43:33.340
of practitioners
710
00:43:33.640 --> 00:43:38.555
in those fields in terms of particularly with data, trying to account
711
00:43:39.434 --> 00:43:46.575
for bias that's inherent to the data and the ways that the algorithms are applied, or software engineering, the ways that the
712
00:43:47.140 --> 00:43:47.640
interfaces
713
00:43:48.100 --> 00:43:49.000
are created
714
00:43:49.300 --> 00:43:51.240
and the ways that the,
715
00:43:51.860 --> 00:44:00.525
information is used within these systems and the ways that it can support or subvert or create various power structures
716
00:44:00.985 --> 00:44:02.605
and create disparities
717
00:44:02.985 --> 00:44:03.485
in
718
00:44:04.000 --> 00:44:07.940
opportunity or equality. So, this is Exactly. Yeah.
719
00:44:08.319 --> 00:44:10.980
Yeah. The first question has to always be,
720
00:44:11.359 --> 00:44:12.579
who can this hurt?
721
00:44:13.265 --> 00:44:16.965
Right? Because that's that's the fundamental function of the
computer
722
00:44:17.265 --> 00:44:21.445
is to copy, is to replicate. Right? So the decisions that we take
723
00:44:22.110 --> 00:44:28.370
on their own, 1 decision, 2 decisions, might not have too much impact. But then when we build that into our systems
724
00:44:28.805 --> 00:44:32.505
and the systems replicate and they they intersect with other systems,
725
00:44:33.204 --> 00:44:36.505
the the unintended consequences or the emerging consequences
726
00:44:37.125 --> 00:44:38.345
can be very
727
00:44:38.710 --> 00:44:41.130
dangerous indeed. So absolutely. We,
728
00:44:41.830 --> 00:44:45.210
when we sit down and especially when we're dealing with human
729
00:44:48.955 --> 00:44:55.135
with whatever data. Right? You gotta the first question has to be, who can this hurt? How can this hurt somebody?
730
00:44:55.570 --> 00:45:00.710
And if you can't answer that question, then you gotta go ask somebody else because it could. It always can.
731
00:45:01.490 --> 00:45:06.204
And with that, I'm curious, what are your goals and aspirations
732
00:45:06.585 --> 00:45:09.724
for the Odate project as you continue
733
00:45:10.184 --> 00:45:10.845
to use
734
00:45:11.280 --> 00:45:14.980
and improve and evolve it? Well, I hope it doesn't hurt anybody.
735
00:45:17.119 --> 00:45:23.244
But my my hope is that people will take it to pieces and find the bits that
736
00:45:23.625 --> 00:45:26.445
are useful for them in their context, in their teaching,
737
00:45:27.145 --> 00:45:28.365
and that it
738
00:45:28.880 --> 00:45:33.460
it smooths the way for more people to be engaged with this stuff
739
00:45:33.920 --> 00:45:38.645
and and and brings more eyes to to these different problems. Because
740
00:45:39.585 --> 00:45:41.925
if if we can increase
741
00:45:42.785 --> 00:45:43.765
people's literacy
742
00:45:44.465 --> 00:45:45.925
about how these,
743
00:45:46.609 --> 00:45:49.430
you know, computational approaches and the the consequences,
744
00:45:50.289 --> 00:45:56.745
you know, as a society, that's all to the good and and it's critical and I think we need that. But in terms of archaeology and history,
745
00:45:57.125 --> 00:46:01.065
I think we would be doing better history, better archaeology too.
746
00:46:01.410 --> 00:46:06.150
So, yeah, big ambitions, big dreams. I want to improve everything for everyone always,
747
00:46:06.770 --> 00:46:10.070
but I would be pleased if people started using it in their undergraduate
748
00:46:10.555 --> 00:46:12.015
1st year courses.
749
00:46:12.955 --> 00:46:15.135
I also think that it's a useful resource,
750
00:46:15.675 --> 00:46:17.775
particularly given the openness
751
00:46:18.075 --> 00:46:18.735
of it
752
00:46:19.050 --> 00:46:21.950
for anybody who is curious in exploring
753
00:46:22.490 --> 00:46:23.390
what archaeology
754
00:46:23.930 --> 00:46:24.910
can provide
755
00:46:25.610 --> 00:46:26.305
in terms
756
00:46:26.704 --> 00:46:30.565
of cultural understanding and knowledge and
just ways for people to experiment
757
00:46:30.865 --> 00:46:33.845
and engage with the field even just as a layperson?
758
00:46:34.930 --> 00:46:36.789
Well, absolutely. I
759
00:46:37.089 --> 00:46:37.589
I'm
760
00:46:39.650 --> 00:46:49.295
I I also teach in the the public history program here, and so I kind of regard my teaching as a as an extension of that as well. The
761
00:46:49.595 --> 00:46:54.710
the teaching that we do has to spill out beyond our walls if we want people to actually
762
00:46:55.090 --> 00:46:57.030
understand and value what goes on
763
00:46:57.490 --> 00:46:58.869
in our work.
764
00:46:59.935 --> 00:47:01.795
Are there any other aspects
765
00:47:02.095 --> 00:47:03.235
of digital archaeology
766
00:47:03.695 --> 00:47:05.075
or traditional archaeology
767
00:47:05.535 --> 00:47:11.300
or your work with the Odate project that we didn't cover yet which you think we should discuss before we close out the show?
768
00:47:12.000 --> 00:47:15.780
I I think we've covered a lot of ground, a lot of territory.
769
00:47:18.355 --> 00:47:22.935
I I enjoy doing this. I get a huge kick out of people reusing my stuff and
770
00:47:23.315 --> 00:47:24.375
and when it
771
00:47:24.869 --> 00:47:29.369
triggers new ideas or or it opens up doors for people. So
772
00:47:29.990 --> 00:47:33.050
I, you know, I welcome your listeners to
773
00:47:33.515 --> 00:47:35.835
take a look at it and and,
774
00:47:36.735 --> 00:47:39.455
and join us in pushing it forward.
775
00:47:41.619 --> 00:47:46.279
And for anybody who wants to follow-up with you or get in touch directly,
776
00:47:46.660 --> 00:47:52.755
I'll have you add your preferred contact information to the show notes. And so with that, I'll move us on into the picks.
777
00:47:53.214 --> 00:47:57.635
And this week, I'm going to pick a set of headphones that I got recently.
778
00:47:58.015 --> 00:47:58.835
They're a
779
00:47:59.170 --> 00:48:02.470
pair of noise cancelling earbuds that were fairly inexpensive,
780
00:48:03.170 --> 00:48:14.345
and I commute in on the train every day. So it's nice to be able to have that additional level of background noise reduction as I'm just sort of making my way to and from work. So
781
00:48:14.690 --> 00:48:17.030
they're, they're by a company called Dautronics.
782
00:48:17.970 --> 00:48:22.845
I'll add the link to the show notes. And so with that, I'll pass it to you, Sean. Do you have any picks this week?
783
00:48:23.325 --> 00:48:26.785
I've just started reading the latest Ian Rankin
784
00:48:27.085 --> 00:48:28.145
novels. So,
785
00:48:28.845 --> 00:48:31.370
if you don't know Ian Rankin's work it's
786
00:48:31.830 --> 00:48:33.930
detective novels police procedurals
787
00:48:34.470 --> 00:48:34.970
featuring
788
00:48:35.270 --> 00:48:37.690
a Scottish policeman named John Rebus
789
00:48:38.225 --> 00:48:39.445
mostly set in Edinburgh.
790
00:48:39.985 --> 00:48:41.925
Great stuff, atmospheric stuff.
791
00:48:42.305 --> 00:48:42.705
Just,
792
00:48:43.265 --> 00:48:44.485
can't put it down.
793
00:48:45.570 --> 00:48:46.070
Alright.
794
00:48:47.010 --> 00:48:55.015
Well, thank you for taking the time today to join me and discuss your work and experience with the Odate and with digital archaeology.
795
00:48:55.475 --> 00:48:57.575
It's been an interesting discussion, and
796
00:48:57.955 --> 00:49:06.860
I hope that it opens some doors for people as you mentioned. So thank you for that, and I hope you enjoy the rest of day. Oh, thank you for the opportunity. I've enjoyed it.