Hello. Hi, so thanks for coming everyone. My name's Fergus, this is my colleague Shimon and we want to talk to you a bit today around some of the work we've been doing in the GreenSoft Health Foundation which is one of the foundations under the Linux Foundation umbrella. I'm the chair of one of the projects and Shimon is the co-chair of one of the projects so we're just going to kind of explain a little bit about what the GreenSoft rydych yn cyd-dweud ar gyfer o'r mwyaf o'r projektyn ydyn ni'n gofio, ac rydyn ni'n gan y gallu gwneud yn bwysig o'r ddweud ac yn ddweud. Yn y gweithio'r projektyn yma, mae'n gwneud am y cerddwyd gyda'r projektyn yma, yma'r un o'r parwysion yw'r cyfnodd Sdk, sy'n ddod i'r cyfeinio'r cyffredig, ac mae'r cyfnodd CICD pipeline, oherwydd rydyn ni'n fawr i'r cyfnodd ddweud. Beth angen dw i'w dwy'n cael ei wneud i'w Chymyn o'r reagent yma'n ymlaen?bod, ddwi'n dod wrth i'r wych ar wirbydd eich cyfrof guidance ar gyfroedd CSF, wedi cyfroedd CSF, ar gyfer cydaniaeth hynny. Yna mae fy mod i ddim yn ysbeth cos yn siwtio ar gyfer rydych chi. Ac mae'r cyfroedd CIS, i ddin yn ysbeth, neu y gallwn hynny yn cymru cyfroedd cyfroedd cyfroedd cyfroedd cyfroedd cyfroedd CIS, ac dros awdurdod yn ganlymwys y projello a muwg'r cyfynnwys iaith cyfnodi'r sgif . Rhaid i fi gilydd y ffordd y Gymraeth Gweithgaf nhw? Felly rydych yn fawr ei gweld iddyn nhw. Rhaid i fi'n gymryd Fardd Gweithgaf nhw yn oed yn ôl gweithio mewn cydweithio ymgyrchu yma gan fvargrifeni. today we will talk a little bit more about the tooling specifically some of the projects that we're running in order to generate the tooling that people can use to ensure that they're getting green software. I'm going to brush over these so we can get into the demo and things but there's a manifesto online which you can read if you just google green software foundation or green software dot foundation is the website you can read sy'n gwneud o tiesiol sy'n gweld fynd i'r ddechrau sydd o ysgolio a'r sgolio, ac oaf i'r prathau dechrau. Gwylwyr maen nhw'n gŷnol ar sydd eich gryffydd pern o gwybod gyda'r cyfrwyngau newydd er mwyn i gwrthu gen i maen nhw gwn gwirio ar gyfer y gwirio i gyrdoedd yma, a'r gyrddur ac yn gyrwbeth o fwrdd gwiswng gwirio ar gyfer gwirio? Mewn ysgrifennu bwrdd ei wneud o gweithredau One is sustainability within technology. Stud, sustainability within the technology that we're using. If you think about your laptop you got hardware, chips, software all sorts of carbon going into the manufacture but also the running of your laptop, the energy that it uses but also the energy in the cloud service it relies on. Also there is this idea sustainability with technology. This might be looking at how we can improve efficiency of processes Be tynnu o'r tynnu yn unigol, mae'nungsibu weld i'r byw, a'r cyfweld i chi eisiau cydyddio amiodedraethau, cymdeithasol iaith deimlo, unigol, gyfan systr yn iaith. Ynno, byddwn ei wneud yn cael eu cyfanyddiol임 yn cefnogaeth, fel y maes y plawdd enghreifftid yn datblygu, i'r cyfanyddiolydd a'r cyfanydd wedi yn ymddangos arnod yn cael eu cyfanydd. Yn rhaid i'n mynd i'ch cyfeidio'r accwr gwylliant what we're talking about today across green software. So we are talking about software, things like facilities management, and especially energy usage will come up quite a lot because that's where the majority of the carbon in using technology is going to come from. We do also consider embodied carbon, which is basically the carbon that it took to manufacture a chip or a computer or a server that is essentially trapped in that device until it's recycled or reused. We do ond there are some aspects of green software which have blurred out a little bit on the screen. Things like water usage. The amount of water it takes to produce a device you may have seen adverts around online around the amount of water it takes to produce a smartphone and why using a refurbished smartphone has a great impact on the environment just because of the water usage alone that goes into manufacturing smartphones. Also, things like single use ond mae'n cael ei gweisio arddangos a gynnig dechrau – dyna ond allan nhw ydych chi gael. Dyghodd, hwnnw nes yn fwy gwaith na sicrhau'n gwybod, gan ymweld o'r pryd Cymru a'ch ges proceedingau. Ioriad yn ymgyrch yn ddaeth yn bwysig rydym ni, ond rydym yn ei erioed, ond i wych yn bwysig bod hynny am mwy o gyflym siar. Ond y gallwn eitemigau'n cyffredinog, sy'n ei gael iawn. Mae'r iawn eitemigau cwestior ffnwyr i dduch yn ei hunain. Yn mynd i ddisgwetiau, yn ymgwych y rhai ffnwyr sy'n, yw'r hwn, ymlaen ar gyfer y system cyffredinog, beth ydy'r hynny mae'r effeithiaid yn yr cwestior hyffredinog, yn llai ei bwysig ar y cyfredinog, the hardware efficiency of that software and the the carbon awareness. So excuse me, so this is really a methodology for measuring the the carbon in software and the purpose is to help users and developers be more informed about their choices, about what they're developing, what they're deploying, and what technologies they are using so that they're more aware of the carbon impact in and around the basically what we're developing every day right. So what do you actually need to create an SCI score? Well we've come up with some some steps here. First is decide what you're actually measuring at any one point and we'll talk a little bit about this in the in both of the projects. So we call this the software boundary so which actual have a think about which actual components you are looking at in the in what you're trying to measure the SCI. The second thing which I'd like to call out as kind of specifically important is what we call the scale and this is essentially what you're measuring against. So the software carbon intensity per watt, if for example you're just creating an API that might be per API call, if you had a full website maybe per user it may be per per transaction there's lots of different ways you can measure that which is quite important but that needs to be stable for the software that you're measuring against and it needs to make sense for the use case. You then need to think about how you're actually measuring that what quantification methods you're actually using this is a big a big question mark around SCIs because that data source needs to be reliable we need to know how much energy a particular chipset is using or a particular data service is using so how you're actually measuring that and then quantifying that so for each every value within your boundary quantify the software carbon intensity and then the fifth and final one is report how you're actually thinking about reporting that back to the user back to the developer so they can actually make informed choices and we'll talk a little bit more about the type of choices they might make when we actually go through the projects themselves and then four and five I won't go into too much detail around the specifics of the software boundaries and the core characteristics but this is just the the full specification so so these slides are available so please do go through and have a look but just to like go back to the point of what the SCI is it's the this is a methodology for calculating the rate of carbon emissions for any software system so it doesn't actually matter what the software system is using these these five steps we can we can calculate the SCI and then use that as a baseline to compare against other applications other pieces of software and the aim is would essentially be to reduce the SCI the software carbon intensity of any piece of software or development that we are are building so I'll hand over to Simon now to go over the specifics for the carbon aware SDK thanks figures so before I introduce carbon awareness itself I have to do a quick intro to to what actually is carbon awareness and we will start off by just simply explaining what what it actually is so carbon awareness in principle is simply doing less when the electricity is dirty and doing more when it's clean and what do you understand by cleanness on dirtiness of energy if you look at the diagram here on the left basically energy is more clean when the composition of where the energy comes from is more focused on renewable energy so stuff like wind or solar then we can see that the carbon intensity so how much carbon is produced per kilowatt hour is smaller so that is well what actually mostly is about and how do we actually apply carbon awareness in software so how do we use it there are two main methods of doing that the first one is by doing time shifting so that's moving our shifting our load to different times of day because basically electricity might be cleaner at a different time of day maybe like at noon or something there is more sun so there is more solar in the grid and then there is a smaller carbon intensity so by time shifting we can take tasks that can be performed asynchronously so such things like training an AI model or maybe posting some invoices and doing it either later during the day or even at a completely different time and then the other option is by doing location shifting so location shifting it's a very similar principle but instead of moving it in time we are moving it in space so we are looking at what other locations the electricity might be cleaner so some tasks that aren't like region bound which for example the data doesn't need to be specifically in that region that can be moved anywhere at all we can move to a different location to produce this carbon and I'll touch upon some of the carbon aware pain points I won't dive into them too deeply because we want to get to the demo I think that's our main core of the presentation here but some of the most important carbon aware pain points is understanding the return of investment so why do we actually might want to care about carbon awareness what do we gain from it next one is disparate integration approaches this being a new thing there's a lot of different teams trying to achieve this at the same time and we want to prevent people from reinventing the wheel every single time so we don't create different approaches with different data sources because that's just it's going to be too hard to track what is actually the standard next thing is that teams are blocked without data providers so if we don't have access to carbon intensity data or other stuff there is no way of moving forwards auditability is another thing so we need to understand why certain business decisions are made why do we decide to actually shift some load to a different region what is the actual gain from it next one is the integrity of approaches so how can we actually be sure that we are not greenwashing stuff so how do we know that the data we're using the data on which we base our carbon aware decisions isn't isn't false or isn't skewed to cause us to make false decisions another thing is that there's oh you might notice as well that there's an increasing pressure in legislature and regulatory compliance from bodies like EU for example to push towards making greener software and businesses might want to get ahead of the problem and to address it before it becomes the problem and be ready for when carbon awareness is going to be the standard not the option and finally this all leads up to the need for a unified approach to have a single single tool to both to address and to create carbon aware products so why a carbon aware SDK we'll start off by showing what our the carbon aware SDK we at GST have developed so it is a piece of software that sits between your application which might be somewhere in the cloud or locally on your computer and the data providers so the data might be coming from data sources such as what time or electricity maps or it can be even your own data you've collected and you've used and what the SDK does is it gives you a single interface for incorporating carbon awareness into our applications for a single point for adding carbon optimization logic as well so if around through the business you have some already predefined options for calculating stuff around carbon or decisions that you make around carbon instead of making them repeating them for every single piece of software you can just have a single single point of action where you analyze the data and you just pull the SDK and you get all the data from from that single centralized point so just yeah and the other thing that's quite important is it gives you the option to measure the operation carbon intensity of your platform so what that means is it can let you check what is the carbon density at right now at this current point by checking the current carbon density data or even allows you to run hypothetical models so looking at future data and predicting how your software how your platform might do in the future and the next one some of these points are already repeated as well so i'll run through them quickly so we do want essentialized carbon awareness intelligence we do want a single spot where which which we access to to make our carbon carbon awareness decisions from we don't want to repeat this in every single piece of software you just want a single one um the SDK gives us the option to also abstract the data providers we don't have to have custom apis for each one of them we can just pull the single SDK or api um and still get the same results no matter if it's what time that's your data provider electricity maps or even your own data you've collected um once again it lets you abstract the carbon logic away from your software to a single spot um and gives you the option to also protect and manage secret keys secrets and keys uh for accessing those services um so you don't have to do that in your own software you have a single spot where you do it and i'll move on to the demo um i think i'll have to put away the microphone so hopefully you can still hear me fine without without it okay great and let me move jump to the demo so the demo is in a Jupiter notebook cos uh let's join us carbon awareness is also something that is quite important to uh data scientists as well and this being a tool that's often often used by them i decided to create a demo in in the uh in a notebook and uh we'll start off by just throwing a number to you generally what i've come to a conclusion after running through those calculations is that making carbon by making applications carbon aware we can decrease the carbon footprint of software by up to 76 percent so that's based on the data we are analysing later on in this slide in this uh in this notebook so that's pretty pretty a big quite a big improvement in my opinion um and we'll start off by simply showing off time shifting so as i mentioned before carbon awareness can be applied by two main principles like time shifting and location shifting so we start off with time shifting and the scenario is that we have a software engineer that is running some computationally intensive uh data processing job and he's running it at 8 55 p.m. every single day and the job is run in west central yes uh azure data center um and what they want want to do is they want to see if maybe running it at a different time of day um might produce less carbon emissions um because maybe there is more solar energy in that grid during the day so what they do is they can run the uh sdk so i'm not going to run through all of the cells but we can already see the results because i've pre-run them before this talk um what we want to focus on here is this section because this is just initialisation of the sdk and then this is actually what is pulling the sdk so what he does is he gets uh he he goes that gets emission data for location by time uh end point so maybe i should explain what's actually happening here because i haven't really introduced that what we have here we have is we have the sdk deployed as a web api somewhere in the cloud and uh what we are doing here in code is uh we're just configuring it because what we have is uh we have a client library that interacts with the sdk right um and what we can do now is we can simply pull the already deployed sdk and get data from it and this particular instance we we're using what time as the data provider um yep can just check the time okay we're still fine um so what the software engineer can do is they can pull it to see uh the time from from the beginning of the day until the end and they first they can check what is the well what is the current carbon intensity so at the time they're running it at 8.55 pm when they pull it we can see that it's 928.5 grams of 0 to per kilowatt hour so that's quite a bit and what they can do next is they can call a different uh end point so it's the emissions by locations best end point of the sdk what that end point gives you is um the best time and location uh with the lowest carbon intensity so they provide as input uh their region their sorry they're interested in the start time which is 12 am previous of that day until the end of that day and what they get in response after running this query is they get the region which they're interested in so that's the west central s but simply mapped to to the what time region so the data provider region and they get the carbon carbon rating of that so we can see that by just moving it from 8.55 pm to 11.55 pm so that's the time we receive the carbon footprint can be decreased by 47 percent and that's based on a single data point of a single day so what we can do now is we can do the same thing but looking at it on a 55 day scale so what would have happened if you did this 55 days ago the sdk also allows us to do that because it's audible it allows us to check how the data would have been some time ago so what we do now is once again pull the sdk and we get all of the data for 55 days and we sort it nicely using some python tricks to get only the data at 11.55 in that region we put it on a table and we can see in comparison for all the different days from 22nd of june this year up to the 15th of august for the 8.55 time and 11.55 at that region and if we plot it on a graph we can see that on average at 11.55 the carbon intensity here is much lower than at 8.55 and if we were to do some calculations and get the average percentage decrease overall over those 55 days ago if we did this shift 55 days ago we'd have a 38.76 percent decrease so it's a bit smaller smaller than on the day we looked at before but overall it's still quite a big a big big decrease sorry not an increase a big decrease in the carbon carbon emitted let me just check the time okay still good to go so this is time shifting next we're looking at is location shifting so let's say that the software engineer we're looking at he is currently restricted to only work in the US regions because that's his company policy and he cannot move outside that that's a fairly valid restriction so we're looking at those particular azure regions we're interested in and once again we're only looking at at the time that was of interest for us the time you found best for that job in that particular region so 11.55 and what we get is that the best region to do it for once again we determine the best region by pulling the emissions by locations best end point and we get that the best region is azps which maps to the azure region west us 3 and just by looking at the at the location shift on a single data point we already get a 30.3 percent decrease of carbon emissions so already another increase and that's on top of the previous one so that's not combined that's a further 30.3 percent decrease and what we can again do is do a little experiment by looking what would have happened if we did this 55 days ago um so how would we have how much would they have saved carbon if we did this 55 days ago are we still fine for time or okay lovely um so again we repeat the same thing as for the time but instead we look at the locations so we pull the emissions by locations end point what that end point gives us is the emission data for a list of locations in a particular time window and the locations we're interested in is the west central less so the one that where we originally performed that task and west us 3 and after sorting the data and putting it in a nice panda data frame we have all the data here where we can compare it um and we'll just move on to the plot so we can see it more visually and this blue line here is the new region we're looking at so the west us 3 region at 11 55 p.m and this is the west central us region at 11 55 so if you remember correctly before when we looked at west central rest there was uh we look at um was it eight eight fifty or something like that and that had an either higher carbon intensity index of all all of those days and we can see that this always is almost always be uh under west central yes so if you look at the average average decrease we can see that it isn't as good sorry miss clicking um it isn't as great as on that day um and we can even see that on the graph that this day was very lucky there was a very big dip but still on average it's a further 18.18 percent decrease over the 55 days so that's still a really good result and the last thing we're looking at is uh we're looking at the location shifts globally so something I only touched upon previously during the presentation about having fully mentioned is that if our company for example has a restriction for us to stick stick to only a certain regions to a certain country maybe we cannot move our data outside of our country for some reason uh because it's sensitive we can still look how how our carbon intensity carbon emissions would have changed if we could do it anywhere in the world and maybe build a business case to convince our our company to change this uh change this regulation so we can move it somewhere else so here we're looking globally we're looking at uh almost all of the azure regions that are supported um by what time and once again we are using the handy emissions by locations best endpoint and what we get here is that the best location to perform this task is actually France and it has a carbon rating of 257 grams and again here in this place we are only looking at the single day of data it's the same day we've looked at previously at 11 55 p.m and just by looking at that day we get a decrease from the original region which was uh i mean sorry we get a further decrease of 25.38% so let's confirm that by looking at the bigger batch of data and looking at 55 days so this is just repeated so i'm just going to scroll through it and get to the graph which is easier to to look at and more pleasant so once again we are only looking at 11 55 because we have decided that this is the best time in western Australia's region and we can again see that this was our initial location shift which gave us again a decrease and this if we could have moved it to France would have been yet another quite big carbon emission decrease so if we go down to it and look at the average we can see that the carbon intensity percentage so maybe i'll point here so the carbon intensity percentage decreased as a result of location shifting from west us 3 so from here to front central would have been 41% and the result of doing the location shift from the original region from west central west would have been 51.76% so as we can see carbon awareness definitely does play a big role in making our our software more green because just by being carbon aware and just by looking at location and time and not running it by default as a nightly build always at night because that's how it we always did or always at 8pm because yeah that's how we always did it for that project we can look at different times different locations and make our decisions more informed about the well the carbon produced okay and let me jump back to the presentation so we're gonna skip or maybe i'll just do a quick run through well once again we're visiting the end the pain points so what we get from the sdk is we actually have the ability to run hypothetical models and understanding well what is the impact of moving stuff of actually making our application carbon aware and how can we look at in the future or in the past as we saw in the demo we get a single unified approach to create a standardized tooling give the developers a single a single tool to you so they don't have to learn different ways how we can apply carbon awareness but just use a single tool and apply it for for everything something i haven't mentioned before is the the sdk gives you uses swagger and open api to generate sdks for well up to 50 languages supporting by open api so it's not limited to just to just a dotnet or which we develop it in but it can be almost any language many any mainstream language available um it is highly auditable so we have the ability as shown in the demo to replay understand why some decisions were made or why they weren't made so we can always look back at 55 days ago or how many days ago we wanted to and see if the decision was correct or what it could have been how it could have been different it has high integrity because all data sources we use are known and are confirmed to to give us good data so and well being an open source project anyone can always jump in and verify if it is or if it isn't and finally audibility by having centralized logging so similar to this we can always confirm the decision was correct or not and the final point i guess this is also with a bit of a shameless plug it's highly hackathonable so right now as gsf we are starting a carbon hack 2020 so i don't have a link here but i can share it with you later if you want or put it in the slides um and this is a hackathon running around carbon aware SDK for producing and and using carbon aware um software so if you are interested dark surprise involved as well but also can give you quite a good head start to to using um the the sdk and uh becoming a green software engineer as well and i'll hand off the focus now to to talk about the carbon side pipeline project great thank you so um shaman has perfectly explained um the benefit some of the benefits of of doing this location and time shifting uh to reduce your software carbon intensity um and i think the interesting thing to take away is looking back 55 days is useful for that audit process but it's it's not useful to reduce the carbon in those 55 days right so what what um we're also looking at in the green software foundation is the idea of putting these tools straight into your ci so you're in continuous integration pipeline um right now what does that look like what does continuous integration look like well we have these cycles of kind of code test build code test build and then test release and deploy um which are you know fairly standard processes uh they're well understood we have lots of tools to deal with those but the result really is that once we get to that deploy section um we just uh if we're talking about a cloud deployment for example we kind of throw a load of resources up into the cloud and then they're running they we know where they are we know what time of day they're running but we haven't measured the sci we haven't thought about this the impact on the environment from that software or any of the the elements that are running in there so when we do a measurement like using the carbon aware stk and we look at the sci we pretty usually get a bad measurement so one of those high graphs right um so is there a better way um because by using tools like the carbon aware stk we can do some of those location shifts we can do some of those time shifts we can even scale things like uh things down if we're not actually using them to get a better sci score but by this point it's already too late if you're made the changes 55 days 100 days whatever it is later you've already wasted uh energy and carbon so our idea with this new project is to put a new step into the continuous integration uh cycle which is assess so at each point uh at both points of your build and test cycle and your release and deploy you're actually assessing your sci before that deployment so you're actually getting a score for what your future carbon uh your software carbon intensity will be in the future so you can actually make the decisions about where to deploy things when to deploy things uh what elements you want to deploy before you actually click deploy and before they actually start generating carbon um so what do we need well uh shaman's thankfully already covered uh some of this this is just a screenshot of the electricity map api and this is a graphical representation of the carbon intensity of different electricity grids around europe so you can see uh from when this was taken france is coming up quite well that's why in the sdk suggests france quite often because they do a lot of nuclear energy often the nordics are very good because they have a lot of hydropower and other countries burning more coal and gas may come up as as red and uh countries to potentially avoid uh if they're not using as many renewable energies at any point the other thing we need to know is how much um how much energy our compute resources are actually using at any one time and this is uh you know an area where we need a lot of collaboration across different organizations to actually understand what chipsets are using different amounts of power and how that's going uh what's the last thing that we need is you so everyone everyone here at the linux foundation can join up to the green software foundation get involved in these projects start contributing to both the carbon aware stk so this is um the projects page on the green software foundation website so his shaman in the carbon aware stk and the carbon ti pipeline tooling is here as well we definitely need uh you know more developers more help with people who are interested in sustainability as well um i put the link here so it's green software dot foundation you can go there to to learn more um we do have a couple of minutes for questions if anybody has any questions in the room or online please do let us know we'll do the our best to answer them in the next couple of minutes yes i'll come over the microphone what is the input data is it a standard format or can it be different in other across many countries yeah that's a really good question um the tools that we've been looking at in terms of electricity map and what time are standardized across the the the globe in the regions that they have access to the data for which is really really helpful um what isn't standardized is the data and is more difficult to get i would say is the the data coming from different providers so if we have a you know an sql server for example running in azure if we have an sql running server running in aws we can figure out if we know how much electricity they use we can use tools like electricity map or what time to figure out how much carbon is related to the energy they use but we need to know from the providers how much energy is used and that's where there isn't a standardization right now so there is a project in the green software foundation to try and do that data standardization um that we would definitely invite you if you if you have an interest to sign up and and help with that because that's something we're actually working towards is getting to a point where we have a nice standardized data and a really good understanding of of what different resources are using different amounts of energy uh at any time but yeah so that's that's something we're actively working towards but isn't necessarily available um from every different provider good question um any other last questions maybe have one time or one more yeah so my question is just around is there any intention to possibly get this automated in the cloud service providers for example so getting them to do this as opposed to me forecasting and then deciding yeah that's a great question i think it depends on the cloud provider i don't know if you want to add anything but i would say it depends on the cloud provider i would say for uh it's definitely of of interest you know add like 20 seconds yeah i mean basically like at this point obviously we want we want the cloud providers to get interested and to actually care about this so i guess our approach is to start doing it and once they have a pressure from other people in other organizations to start doing it maybe then one of the providers will eventually decide hey this is something we're interested in maybe let's join in there for it and start doing it and once one follows hopefully others will as well awesome so i think we're out of time but so thank you so much for for coming um and asking questions if you have any more questions for us we'll be around after the event um but yeah please do visit the link uh have a look at some of the other projects as well this is just two of many projects under the green software foundation but thank you very much


Fy enw i'r cymdeithasol yw'r cyfan. Yn y cyfryd yw'r dr Buck Bryd yn ymdweud o'r cyfrifodau o'r ddweud yma yw'r cyfrifodau yw'r cyfrifodau. Yn y cyfrifodau, yw'r cyfrifodau yw'r cyfrifodau yw'r gyfrifodau. Yn y cyfrifodau ar y dystod y dystod y dystod yng nghylch yn nodiwm, ac mae'n meddwl, eich argymeth, yn ymddangos gyrfa ynglyn â'r ddweud, sy'n gynhyrch mewn ddweud i'r ddweud i'r ddweud. Mae'n hwn yma'n ddweud i'r projECt gan gwybod i ddweud i'r ddweudio bai cyfnogaeth biologicol yn ystod. Yn eich cyflwynt, mae'n ymdangosio ario'u ddweud i'r ddweudio i ddweudio'r ddweud i'r ddweud i'r ddweud i ddweudio'r ddweud, a'r dysposol i ddim yn ddael ar gyfer thosei. Mae'r texbookau hefyd yn ei ddim yn gweithio'r texbookau a dwi'n ddiddorol i'r texbookau ar gyfer troll gwybodaeth a'r ddodol, rhai yn ysgrifennu rhaglen yma, a'r hyn yn ein gweithio gweithio'r resurs yw'r ysgrifennu erbyn i'r gweithio'r ysgrifennu. Rwan disasters yn gwneud eich maen nhw'n ddweud a bod o'r informacio i gael a gweithio'r ades, ac mae'n ddweud o'r ffordregau a'r adegau'n ddweud eich ddweud o ffad ar oed byw, wrth gwrs mae'n gweithio i Brathred i'r rhaglen gwneud yr oedd yng nghylched i'u hwyl ymddiol wedi'i meddwl o'r materiol o'r oceilogig. Mae'r 4,000 caelwyrs. Byddai'r clywed o'r ddod o'r ddod o'r bydwyr ymddiol, ond mae'n cael ei ffordd o'r ddod o'r ddod o'r ddod o'r ddod o'r ddod o'r ddod i'r cyfnod. So, rwy'n meddwl i'r dyfodol i'r ddod o'r ddod o'r ddod o'r hyfforddiad. Felly, we've been asked this evening, is it any one period that we're focused on, our collections span the Neolithic through the mid-19th century, so we are not specific to any one period. What this project was about was looking at the type specimens that give the information about chronic abuses of those literary and the skeleton. Most of the material is in partnership and collaboration with other institutions, museums such as the Noviom, as I mentioned. We run a dedicated MSc in human osteology, paleo pathology. We've ran short courses focused on these expertise that we have in Bradford based around the collections of pathological conditions. Mae'r bwysig iawn, a'n cael ei wneud i'r bwysig iawn, mae'n gweithio i'r ddweud o'r bwysig iawn, i'r sgol, a'r bwysig iawn. Ond oes, rwy'n cael ei wneud i chi'n gweld i'r gweithio. As a part in recognition of this project our dean who is an anatomist by training has actually very much got behind us. ac mae o'r rai o'r rai o'r cyfnod ar y ddechreuol a'r ei wneud o'r lleoli. O'r hyn o'r reisio sgwrs mae Joe yw'r cyflwyffydd. Mae'r projekty a genesys ar y projekty wedi'u cyfrwng yn Ymgyrchai'r Williamsburg ar gyfer y gwmdiannig. a we presented a couple of papers there, recognising the value of these collections, but also recognising the fragility of that material and how we might in the future wish to do the right thing by these collections in safeguarding them. Move forward to 2010, some 11 years later, and the technology was catching up with that idea, back to the future. And of course we were very lucky at that point in attracting funding from JISC, as you see here the UK's expert in digital technologies for education and research, and we ran a pilot project around the material that Anushka was curating the archives, the physical archive of, and we held the skeletons in our care for them. It's the material from St Mary and St James at Chichester, a medieval leprosarium. Originally the monograph identified some 75 individuals with lepros change. Because we've been able to explore that collection in far more detail, looking at that material in a very different way, using 3D technologies, we've actually extended that to some 84 individuals. We've also got a collection of historic radiographs, clinical radiographs of patients, modern patients from the 1970s, from India, from Africa, that were exposed to those chronic changes of leprosy, and we curate those. That's the Joss Anderson archive, but as part of that project we were able to tackle that. But more from Joe on that shortly. That was a pilot that showed JISC that we were capable of working with those 3D, with that content, using 3D digitisation methods to actually do the right thing by the collection in digitally documenting the type specimens. Only one other project, the British Geological Society's GB3D type fossils project, that was funded, that was working again in that 3D environment. Of course, as a visual subject, it's a logical next step for us. So we were lucky enough to secure, in fact if you add the University of Brantford's contribution, it's just short of a million pounds worth of public monies to safeguard the type specimens for use not just in teaching biological anthropologists and osteoarchaeologists, but also using that material for the benefit of training clinicians and medical historians. But focused on the examples of chronic disease effect in the skeleton for which many of the physical changes are not even readily observable within clinical practice. Something therefore that has that extended reach across disciplines. We were able, with our partners, and Joe will explain this in terms of the partners, the Royal College of Surgeons and Museum of London Archaeology. So over to Joe. OK, so one of the things that we did from cemetery to clinic was create 3D models of different bones from individuals suffering from leprosy and making them available over the internet. And we wanted to take this further. We're aware that particularly in teaching but also in research, most of the sources that we have to help us with our diagnosis of diseases in the past are 2D images. But the lesions that we're looking at and the bones that there are are extremely three-dimensional. So we wanted to take that further and digitise as many different elements as we could that really characterise the typical changes of as many different diseases as we could cover. So we worked and partnered with Museum of London Archaeology and the Royal College of Surgeons to basically get as many archaeological and historical examples of different pathologies, digitise them and make them widely available across the world. The reason we actually focused on the pathological specimens is because in terms of human skeletal remains, those bones often the most fragile because the different pathological processes can weaken bone and they are much more susceptible to damage during excavation, during storage and particularly during handling either by students learning from them or by researchers coming to access them. Of course, because they're pathological to many individuals, they're also regarded as the most interesting. So individuals like those from Chichester, which was known as a leprosarium, attracted a far higher number of researchers coming to access those collections and therefore increasing that rate of damage. So what we wanted to do was preserve them in some way and make them much more widely available. So we drew on all of our collections for the three project partners. So at the Biological Anthropology Research Centre ruled the bark, because that's less of a mouthful, we curate over 4,000 individuals. As Andy said, they date from the Neolithic right the way through to the 19th century, although the bulk of our collections date to the Romano-British period and later. Key collections within there is St James and St Mary Magdalene at Chichester, the medieval leprosarium. It later became an arms house at which point we're seeing a much wider variety of pathologies present in those skeletons. As I was discussing earlier with a couple of fellows, we also curate 36 individuals who died at the Battle of Tauton on Palm Sunday in 1461, a reputedly the bloodiest battle fought on British soil. Hereford Cathedral, we curate over 1,200 individuals dating from the entire duration of the medieval period, but significantly they include a large plague pit with Ysina Pestis being identified with DNA analysis securing that diagnosis of identification of the plague, because the plague doesn't affect the skeletons, you can't look for the direct evidence. The Royal College of Surgeons here in London has got two major collections of human remains in the Hunterian Museum and also the Welcombe Museum. Over 50,000 objects are recorded there from human remains through to notebooks and artefacts. We're really delighted to be able to work with both of those examples significantly because a lot of them are from a period when diagnosis was much more refined, particularly for the modern material, but where we actually have a known diagnosis that is done on people whilst they're still living. One of the complications of paleo pathology is that we don't know how somebody was feeling when they were ill, we just know what their bones looked like after they died, which adds some confusion and complications into our diagnosis. So, not only does the Royal College of Surgeons curate a large number of individual specimens of extremely rare conditions, but they also have known documented cases where we can say for certain what that pathology was, rather than it becoming an interpretation based on what we can see. Our third project partner was the Museum of London Archaeology. Over the years they've excavated over 17,000 individuals from London. When we started the project, they were part of the Museum of London and it sort of decoupled over the duration of the project. We worked extremely closely with the Centre of Human Bioarchaeology at the Museum of London, who were one of our lead associate partners in the project. Together they used the word database, the welcome osteological research database to record all of that material and make that available to researchers from around the world, but in this case without 3D images, just with the information about those remains. Of course from the outset we had to think about how we were actually going to present this to the public, so we decided the best thing we could do in terms of a website that was going to be made available is to actually come up with a way of grouping things together. We had to try and classify our diseases. There's actually ended up being one of the more problematic aspects of it because basically from the outset we couldn't really agree on what we were going to do. We had a wide-ranging advisory panel from medical clinicians, paleopathologists and archaeologists all working together trying to come to a consensus. Eventually we decided to go for something that was bespoke to our project because we needed something that divided material up enough that you could actually use it to navigate through a website. We tried to focus on the underlying cause of a disease. Are we looking at an infection? If we are looking at an infection, is it a bacterial infection? Is that bacterial infection specific? We know which pathogen caused it, or is it an infection that could have been caused by a number of different pathogens? We ended up with a tiered system, which we developed into the navigation menu on the website. Overall we have anything up to four levels of classification in there. You use this to navigate around the website. At each of these levels we have something known as a clinical synopsis which basically summarises what the disease is about, how it might affect an individual, how we might see it on a skeleton. Then you can drill down to look at specific examples and retext that describe a specific bone and then also see the 3D image and potentially also radiograph of specific bones for each of the categories. Another challenge was deciding exactly what we were going to scan. Essentially we started with the material we actually used for teaching on the basis that if we're using it for teaching it's got to be a really great example of what we're talking about. We worked through our teaching lists identifying as much material as we can and as we went along we were finding more and more pathologies that we could add in which was fantastic. We worked with a number of postdocs. Rebecca who is in the bottom corner was writing those pathological descriptions whereas Emma at the top was very busy helping us work out exactly which bones we were going to include. She actually took photographs of everything so we could rapidly pick what we wanted to do in project meetings and was also very active promoting the project through social media. Emma took these extremely fast photographs of everything and we graded each one on a category of A brilliant we'll have that be quite good we may use that down to X which was actually it's not right for this project. Either the material itself was too fragmented so it would become unrecognisable really to people who weren't used to working with it or it's an example of a pathology but it isn't typical or it isn't extreme enough to include. And then finally we also tried to think about how hard was this going to be to scan and this was very much a steep learning curve for all of us because we weren't sure what was going to scan successfully at the outset of the project and we learned as the project continued that extremely large and complicated specimens caused quite a significant problem in terms of computing power where smaller ones you could scan quite quickly but we needed to get the balance right between those different areas. So we worked very very closely with our project partners down in London basically they were focusing on the pathologies that we didn't have in Bradford because they were working alongside us at the same time they had access to larger collections so they were focusing on the things where we knew we didn't have an example of for example Ostea Malaysia in the Bradford collection and in particular the Royal College of Surgeons could offer us extremely unusual pathological cases and those were the documented case history which was very very useful. Whereas the bulk of the material we scanned was either curated in Bradford or with either the project partners in London we worked alongside a significant number of museums that became known as associate partners some of these such as the Novium and Gloucester City Museum actually have material on long term loan to us in Bradford so it's curated in Bradford on behalf of those institutions but other institutions we approached because we knew they had really fantastic examples of particular pathologies that we wanted to include within that and we were delighted that they all agreed for us to scan the material and include it on what is basically free access resource most significantly of those the Museum of London contributed enormous amount of data to the project and really do appreciate everything that these groups did. One of the things that we learnt as we went along was that actually not only were we creating a resource for other people to learn from but we were learning from the project as we went along by carefully looking at all of these different cases again with a different set of eyes with a different question in our mind we were beginning to identify further expressions of disease on the bones or revisit our diagnosis and perhaps go do you know what I think the original diagnosis from 20 years ago I think our knowledge has moved on and perhaps it's something different so we're re-diagnosing things and also we were beginning to identify quite unusual pathologies which we've not really thought of in the same way we just assumed it was something quite simple and when you looked into it in more detail we were picking up very very exciting cases and it was the luxury of being able to spend that time with the material was absolutely fantastic and we worked very very closely with colleagues across Bradford including our radiography department and then also we have Keith and Alan in the centre of the middle photograph Keith is a retired GP Alan is a retired dentist so we're bringing in all of their clinical knowledge into the project as we went along so what did we actually do in practice well having made those selections the process of 3D digitising each of those elements was down to a selection of an appropriate method where we could visualise sometimes quite complex objects you see here a toe which is a very small object but we were dealing with things like teeth as well each of which have their inherent problems even if they are showing normal morphology let alone the sort of problems of porosity that come about through pathological change so we were using something called a laser arm you can see that here we've got complementary methods now in Bradford such as structured light scanning but we started out with the laser arm which effectively works on the principle of trigonometry so it sends out a laser stripe and you've got a video camera that captures that information so the return of that laser and it's on an armature that moves around in 3D space and together it knows where it is the varied colour that you see down here at the bottom represents the fact that each scan is built up from successive passes of those laser stripes in practice what that means is we had a variety of different skill sets within the project team we had people that were doing the scanning and we trained up people in London to do complementary work to that in Bradford so we had a laser arm based in Bradford and a laser arm that we had based in London and as the image shows here each of these elements went through a number of researchers' hands because we had to describe the specimen of course there's no point in doing this work without that metadata the importance of why that specimen is relevant so the descriptions, the scanning the texture photography which was going on here which provides the contrast as you see in these images relative to the sort of grayscale image that you see at the bottom there we were able to provide photorealistic qualities to our images but no mint task of course we've got a nice quote later on from Forbes about the nature of our project as being a pioneer in this field but a lot of methodological challenges big data as Joe has spoken about problems of artefacts that we actually create through the scanning process based on the small size of some of these fragments based on the pitting, based on the edges some of which don't produce a very good laser return the fact that bone when broken exposing that trabeculi doesn't scan that well the fact that the enamel of teeth is quite shiny and if the deposition environment is such that we have changes in terms of colour that can be represented differently as well the value of it is of course it can move around an object but of course it can only see what you can point that laser at it can't see around corners it can't see into the undercut regions it's a very complex topography on those objects the photography and the texturing as I'll show you in a moment is really a major aspect of what we were trying to achieve in terms of explaining the relevance of these changes to these bones from normal but initially we were confined in that pilot project to just dealing with the grayscale image we had a trial viewer that used a proprietary format which was quite limiting in many respects we therefore complemented that with other approaches the use of object movies and the like but the texturing process was one borrowed from the discipline of visual computing we had two visual artists one experienced from the animation gaming field and even within and amongst those two visual artists they had varied skills in terms of their original training but what you can see in that top left image is one of the initial steps that they had to undertake based on the complexity of some of these bones the broken structure you can see that the laser return wasn't always providing complete coverage we needed to do something called whole filling to enable us to create an entire 3D model without any gaps those texture photographs that we showed earlier being caught were effectively then translated into these sort of flat surface models linking the photographs to that 3D geometry such that eventually they could be repainted back on the 3D model itself the process of texturing not the sort of texture that we're familiar with conventionally in archaeology for some of those objects it was just too complex and we had to use other methods such as object movies and the use of CT data which we'll explain in a little bit more detail in a moment but over to Jo again in terms of what we produced okay so at the outset we wanted to produce something that was quite ambitious and over the course of the project we actually scanned over 1600 bones or fragments of bones that could be pieced back together into 3D models and all of these were textured using that photographic technique we made these available over the internet and we're still uploading these models onto the internet as we speak onto a format that has fully open access it's got a commons copyright licence which basically means that people can use this in their own research and in their own teaching anywhere in the world as long as they don't modify it or print it out or anything like that and our idea was really initially that we wanted people to be able to use this in lectures with their students we were aware that we were blessed with this fantastic collection in Bradford but that many institutions did not have the ability to do that and we thought that for students it would be fantastic to actually have a 3D model that they could manipulate rather than just a 2D photograph in a book because it was on the internet students would then be able to use this in their own time to study and more importantly, researchers from around the world can also use these within their research so over the summer I was lucky enough to talk about the project to the Perminsa group which is the paleopathology association meeting in South America so I was over in Buenos Aires explaining this to colleagues over there and we're starting to talk about could we start to translate this into Spanish so that it has a global reach so essentially we've got a virtual learning environment that students and lecturers can use but it becomes a research base as well and suffice to say that even the oldest member of the project team was delighted when presented with the iPad and just using his finger he could turn that bone around and explore what was going on so one of the most happy photographs of Keith Manchester that I've ever captured or that Andy captured this one so we launched our website a couple of years ago and it's still being developed despite the project ended a while ago we've had continuation money from the university through a project known as Bradford Visualisation that has allowed us to continue working on this and update material as we go along our most recent addition is to the CT data that you can see on the front page of the website essentially what people can do is navigate through that system to pull up a single pathological specimen in this case you're looking at an Anglo-Saxon example of Pots disease of the spine evidence of tuberculosis this example is very very extreme I can't remember exactly how many numbers there are I remember that there are 10 vertebrae in total but the destruction of the pathology has actually taken away 4 or 5 of the vertebral bodies which are on this side so this should be much more straight it's causing it an anterior curvature so you can go online and you can pull up this 3D image and you can manipulate it online and a lower resolution information for having the description and the information regarding the age and the sex of the individual alongside it before you do that you actually have an option with the pathological description at the bottom very very often we have conditions or elements with more than one pathology presence with coexisting pathologies if you're looking somebody's teeth there's a reasonable chance that they're going to have dental cavities but they may also have another dental problem as well and a lot of these happen hand in hand but essentially you have the option to look at that model online or you can actually download it with a higher resolution version that you can actually manipulate on software known as MeshLab which is free to download the download files are quite large they're generally coming as zip files and we make sure that everybody is aware of A how they can cite the resource so that credit is due but also what they can and can't do it is free to use to anybody but we can't permit 3D printing and this is partly because of the importance of the ethical aspects of what we're doing particularly in relation to the more recent material that's curated by the Royal College of Surgeons that is less than 100 years old and falls under the Human Tissue Act so we need to think very carefully about what should and shouldn't be done with this data in terms of supplementing this we actually also scanned a whole post of radiographs initially in the from symmetry to clinic project we scanned the Joss Anderson archive of clinical radiographs of leprosy for digitised diseases we then scanned plain film radiographs that we had of pathological specimens and we took new radiographs to supplement that to aid in our diagnosis and our description as we went along and to also make those available to people in relation to the fact that of course some of those conditions go far deeper than the sort of superficial observations we can make of the outer cortex of the bone we also had collaborations with the local hospital at Pinderfields so Mid York's NHS trust but also our project partners down here in London were able to go and do the same at Chelsea and Westminster hospital so we had our outpatients visiting out of ours going through the CT scanners at these institutions and for the very fine detail I'll show you an example of that in a moment we also used a collaboration with Smith and Neffie in York using their micro CT before we were able to get micro CT in Bradford ourselves both techniques provide huge amounts of data which is available certainly from the CT from the medical sense in very specific formats that DICOM format which is used for medical imaging but we had the expertise of researchers very conversant with 3D data from archaeology so imagine the sort of geophysical prescription data that we also collect these days in three dimensions they were treating and handling the same CT data in a very similar sort of manner so they were converting it converting it into those 3D coordinates that we could then save in a variety of formats and produce either a surface model to visually reconstruct that element or to actually extract separate views from it and again using web based dissemination of that we've got a nice example here that shows why in relation to collections from the Royal College of Surgeons and if you can imagine the sort of bounding box here is actually a perspex box containing a wet specimen from the Royal College of Surgeons and it happens to be showing the soft tissue as well as the osceus material from an osteocondro... osteocondrosycoma of the knee where you can see again the value of this work using CT as well as a complementary technique to the surface scanning that we were doing elsewhere this is that example I mentioned that illustrates why the micro CT was particularly valuable to us you saw very early on an example of a near plastic condition a cancer in an individual from Wolverhampton from 19th century Wolverhampton this is a rib from that same individual and you can see those spicules of bone that very fine detail only picked up through the use of micro CT so we're trying to use complementary methods we're trying to use innovative methods that work with bone elements that work in reconstructing related elements and we have an example showing how of course you can reconstruct a a series of elements together in fact this is from the Royal London Hospital site excavated by a museum of London Archaeology you see portions here fragments of a mandible a lower jaw found that has certain discoloration to the surface this is a textured 3D scanned model that has then been virtually realigned we're able to match the saw of the fragments together the varied staining is because they come from different portions of that deposition environment from the Royal London Hospital so they show aspects of what this project is capable of doing and in fact a large part of that work with Mola was thinking about this content as part of wider stakeholder engagement so we're able to contribute some information to the online resource that sort of back story to the doctors dissection and resurrection then exhibition which was a big success at the museum of London but of course there are other project partner the Royal College of Surgeons had similar interest in working with us to present material to the wider public and this is an example of John Hunter's original collection an example showing the the changes relating to infection post ballistic trauma this is a very famous example of that ballistic trauma as you can see that John Hunter then later dissected as Joe mentioned it's very much an ongoing picture ongoing work initiating some of those elements ongoing work trying to ingest more content for that web delivery but it wasn't just the web delivery and the creation of that web GL based delivery that we were working on and although as Joe has rightly pointed out this was very much seen as a born digital resource ultimately we will be looking to one or two choice examples that we will allow people to 3D print and we did some innovative work and I'm very happy to allow people to pass these 3D prints around showing the sort of level of detail that we can capture from these surface scans that we can then turn into physical models again so it's that life cycle perpetuated yet again in terms of the importance of preserving these very fragile and very important specimens part of the legacy goes further and some of you may be familiar with this chap on the right hand side if you've been to the new Stonehenge visitor centre this is the chap that greets you he is from the Neolithic Winterborne Stoke Barrow as part of that Stonehenge landscape and Andy Holland one of the researchers on digitised diseases is shown there doing the initial 3D scanning which we then turned into a 3D print and Oscar Nielsen there in the centre did a facial reconstruction that you can now see as the general public so I'm going to let Joe say something about the sort of uptake as a teaching resource okay so we mentioned the right at the beginning that over the summer we've been very lucky to have a huge amount of investment into our area we actually moved across campus as a department in August and September and the Barlogic Anthropology Research Centre is part of an integrated learning centre that focuses around the human body from modern anatomy, pharmacy and right the way through to the archeological specimens just this morning what I should have been doing this morning when I sat on a train and thankfully my lovely colleague Julia Beaumont and did this for me was actually use some of the osteological examples that we have in Bradford to teach our physiotherapist students from the School of Health what conditions look like underneath the skin because they never get to see that return teaching with my students as part of that we've got a newly refurbished lab which is depicted here we actually took these photographs just yesterday afternoon that's a group of my master's students working on their skeletal material but we've been able to use a large touchscreen monitor to integrate the use of the website into our teaching and for the last few weeks I've been working with my undergraduate students teaching them the basics of paleo pathology and always after we've done the introduction there's a group of students manipulating different objects on the screen exploring far more specimens in that lab than I could ever get out of the store and enabling to look at those that I think are too fragile to actually bring out the teaching one of the most amazing things for us is actually looking at the scale of it so you can see me just holding a toe bone that's affected by gout next to the image that we've put on the screen so you're actually able to blow that up and look at it in much greater detail of course the bigger you go you do begin to lose resolution after a critical point but it does allow us to look at these in far greater detail and to manipulate them and turn them around and at the bottom I'm talking about this case with Jazz, one of my master's students last year she did a dissertation on gout and that's one of the specimens she actually included looking at evidence of gout in the medieval period but it's far more than what we can do in Bradford it's actually about what we can do for everybody else and we know that this resource has been used by researchers around the world and recently there was an article published in Forbes magazine by Christina Colgrove who actually said that we are doing the first and most extensive digitisation project in bioarchaeology to date just because of the sheer number of specimens that we're doing so rather than just doing one or two small focused specimens we've actually tried to get as much as we can into that project and we know that the uptake of this resource is global these are some of the statistics of use on the website we had over 13,000 unique visitors to the website in 2014 over 16,000 in 2013 I think a lot of that was around the launch of the project that those people first came in but it's continuing we're getting new people month on month and importantly for us is looking at the colour coding on that map on the far side of the slide the darker the colour the more hits we're getting on that resource and one of the big hotspots is North America where they have huge, huge bioanthropology programmes looking at human remains but very, very few skeletal collections to actually base that research on because much of the Native American material is being repatriated to Native American groups and often re-buried or not being used in the same way so although they have small amounts of teaching or they don't have the scale that we do so for them it's really benefitting what they can do with their students rather than rely on the traditional photographs just pass over back to Andy really just to sum up part of the reason that you've had this sort of comic double act here on stage this evening is of course the fact that it has been a huge project involving major project partners within the UK major contributions from associate partners but a very wide project team very large project team spanning quite a number of different disciplines from the visual computing end of things right through to the biological anthropology and all bringing complementary skills into the project so we were lucky midway through the project to get at least a large portion of that team together at in the crystal gallery as they call it at the Royal College of Surgeons for a bit of a meet and to share ideas but as I've alluded to it is something that is very much a part of what we like to do in Branford we've continued this as a legacy in other areas through other projects in continuing the work in biological anthropology but working with other animal heart tissues as well that sort of helps in terms of customs and border control where of course things like rhino horn or elephant ivory need to be characterised and so the legacy there really is building on a life's work of Dr Sonio O'Connor we've had a project which is now at it's halfway point called Fragmented Heritage a £2 million project funded by HRC where we've just launched our fossil finder website which is a crowdsourced piece of science working in Kenya working with three dimension dimensional landscape scale studies looking with Louise Leakey at material from the Takana Basin and trying to get the public involved and engaged in that material and as Joe mentioned the sort of unifying aspect of this work in three dimensions is something called Brown for Visualisation which receives some high funding through Hefke and allows us to continue this work so it's extending the range of skills and kits that we have available to these sorts of projects but once again it's a huge project and a testament to a huge amount of involvement from very many quarters to the wider sort of advisory team in terms of people like the late Don Orkner in whose name the project is now dedicated but also the funding bodies just with that foresight to include us in that 2011-2012 e-content programme as allowed this resource to become available what they're interested in is very much that level of open access that we get from throwing this open in that sort of creative commons licence so I think that's really what we wanted to share with you today if anyone is particularly interested in learning more about the website more about that resource or two of these little leaflets here but do get on and have a trial yourselves by visiting www.digitisediseases.org and do share that with your friends and colleagues many thanks for having us