WEBVTT

00:00:00.000 --> 00:00:02.000
All right. Well, I think we can desert. With the next section which will contain two flash talks. The first one should be from Sam Erickson. I also see him connected. I don't know if you'd like to share some slides or…

00:00:02.000 --> 00:00:15.000
Very nice picture.

00:00:15.000 --> 00:00:20.000
I remain a cow. There we go. I'm not always a cow.

00:00:20.000 --> 00:00:24.000
Okay, the cow is gone.

00:00:24.000 --> 00:00:30.000
All right. Yeah. Thank you. Just go ahead.

00:00:30.000 --> 00:00:49.000
Okay, good stuff. Right. So yeah, I'm going to talk about what uh we've done with the LZ collaboration in terms of sustainability. Before I do that, I'll do the obligatory introduction slides to what LZ is. We're a direct dark matter experiment.

00:00:49.000 --> 00:00:57.000
Based in South Dakota in an old gold mine. We've been running for four years now.

00:00:57.000 --> 00:01:02.000
And we'll probably keep taking data for at least another four years.

00:01:02.000 --> 00:01:14.000
There's about 250 of us primarily in Europe and in europe and US, but we've also got people in Asia now, so we're quite spread around the world.

00:01:14.000 --> 00:01:30.000
So what's sustainability in LZ? Well, we actually started up a working group late last year with the goals of quantifying what the environmental impact of running our experiment was and explore ways to reduce this.

00:01:30.000 --> 00:01:37.000
And I'll come to later. Let's do beyond LZ how this helps.

00:01:37.000 --> 00:01:53.000
But within LZ, we essentially broke this down into three sections we've got the operations, so the actual detector running. Then we've got the computing, so analyzing our data. And then we've got the in-person meetings.

00:01:53.000 --> 00:02:03.000
So this isn't exhaustive but we have taken these to be the big three.

00:02:03.000 --> 00:02:22.000
So since we started up started looking at all of these with the first one we tried to tackle being operations so The hard thing with this was when we built the experiment. We didn't really think about energy usage all that much. We just gave an initial number for

00:02:22.000 --> 00:02:28.000
This will be the peak load. We don't care about all the steady state we use is.

00:02:28.000 --> 00:02:36.000
So actually getting this number has been incredibly difficult. And it's a bit of a fudge.

00:02:36.000 --> 00:02:50.000
So in what we're considering here, we only look at our steady state contributions So the stuff which is on all the time, we don't consider high energy calibration sources and whatnot.

00:02:50.000 --> 00:03:01.000
But essentially, this gives us numbers in the range of 44 to 66 kilowatts. And this is just on 24-7, 365 days.

00:03:01.000 --> 00:03:07.000
And where possible, we validate this with whatever monitoring we have.

00:03:07.000 --> 00:03:21.000
Then in our computing, we actually use two computing centers. We use NERSC in the US, which is our primary one, and then we have a secondary one, which is based on the Great.

00:03:21.000 --> 00:03:37.000
And we've monitored how much we're using here based on essentially monitoring jobs. So all the ones in the US use Slurm's the batch system, and we're able to monitor the amount of energy used by each job I know how much storage we're using.

00:03:37.000 --> 00:03:54.000
And so we've been able to work out what the energy usage is running there. Similar story in the UK, apart from it's done on a site basis and then we just take what fraction of jobs and storage we have there.

00:03:54.000 --> 00:03:59.000
And this gives us some numbers which I'll come to later.

00:03:59.000 --> 00:04:08.000
And then for meetings, we typically host two meetings for the whole collaboration a year, which we alternate between the US and the UK.

00:04:08.000 --> 00:04:26.000
And essentially, since we started this working group we've started properly recording you know who's gone and how they got there And so for our two most recent ones, we had one in UCLA where all of the 50 people who weren't reported.

00:04:26.000 --> 00:04:30.000
And we were able to track their flights and work out how they got there.

00:04:30.000 --> 00:04:35.000
And for the one before, which was at Brown University, also in the US.

00:04:35.000 --> 00:04:47.000
Where we didn't have full reporting, so we had to make some estimates but it's about equivalent. So, you know, nearly 90 tons of CO2 for these meetups.

00:04:47.000 --> 00:04:50.000
So we put all of that into a summary. That's what we've got here.

00:04:50.000 --> 00:05:08.000
And we've translated these into our tons of co2 equivalents so we're equivalents around 500 tons a year is what we're putting out based on different scenarios, which I'll let people read in to on their own time.

00:05:08.000 --> 00:05:27.000
But the point of having this number is we can now start to think about how to mitigate certain bits. So I'm only going to briefly show one, which is this which is experimenting with different types of meetings. So for the ucla one

00:05:27.000 --> 00:05:45.000
What we did as a trial was we looked at when some other meetings that people in our collaboration want to go to And we've got our collaboration meeting around that. So we put it after a dark matter conference and before one of the giant us ones and we calculated that saved about 12 tons

00:05:45.000 --> 00:06:01.000
Another thing we're looking at is this hubs model where you go to somewhere local And so just to summarize this we're about two tons of CO2 per year per author.

00:06:01.000 --> 00:06:07.000
With operating the sector being largest and the second largest on flights.

00:06:07.000 --> 00:06:22.000
All of this will be used and taken into account for the next experiment, which we're planning now, which is XLZD, because that if it's in the UK we've got the target of being net zero in operations. So everything we learn here

00:06:22.000 --> 00:06:26.000
We can take food there. So it would be easier to adapt now.

00:06:26.000 --> 00:06:30.000
Essentially. Thank you.

00:06:30.000 --> 00:06:45.000
Thank you so much, Sam. There are also any questions? So have a look.

00:06:45.000 --> 00:06:59.000
I will have one otherwise Since you're talking a lot about flights, do you think this is easy to reduce given the fact that you're a collaboration?

00:06:59.000 --> 00:07:18.000
Mixed. Depends who you ask. We've kind of find it goes in waves The younger you are, the more keen you are to travel. And then there's like a plateau period where you're happy not suddenly you ramp up and want to hang out with your old mate again.

00:07:18.000 --> 00:07:29.000
Um so We think it's definitely realistic to get down to one international one a year.

00:07:29.000 --> 00:07:36.000
Which is what we're pushing for now. And beyond that, go for a hubs model.

00:07:36.000 --> 00:07:41.000
Okay. I see also Greg has raised his hand.

00:07:41.000 --> 00:07:52.000
Yeah, I have a question about the carbon footprint of the xenon itself because xenon is only present at 10 to the minus 8 in the atmosphere. And if you need new xenon.

00:07:52.000 --> 00:08:02.000
The distillation cost is probably quite high. I mean, I know the same distillation process makes liquid oxygen liquid nitrogen, but Is that factored in?

00:08:02.000 --> 00:08:03.000
Into your numbers at all.

00:08:03.000 --> 00:08:23.000
Not in this. But for XLZD, we've started doing full carbon life cycle assessments. And for that we are talking to the people who we buy xenon from to get those numbers.

00:08:23.000 --> 00:08:27.000
Okay, thanks.

00:08:27.000 --> 00:08:30.000
Thank you. Then with that, I think we can also move on.

00:08:30.000 --> 00:08:37.000
Flesh stock. So Martin, if you're around, you could start sharing.

