 My name is Kristin Antelman. I'm the Associate Director for the Digital Library at North Carolina State University, and this is Morris York, head of IT for the NCSU Libraries. And we're here today to talk to you about the library building as a research platform. With the opportunity to build a new library at NC State, which we'll tell you a bit more about in a second, we were presented with the enviable opportunity to think deeply about what does a research library mean going forward. And kind of specifically, what is the physical research library going forward in the post-print environment? So I'm going to start with a little bit of the story of how we got to the vision, and then Morris will take it over and talk about the specific implementations of creating the research program and spaces and partnerships for the Hunt Library. Before I get off the starting slide here, I just wanted to mention that we did a student contest called My Hunt Library, where we asked students to take pictures of the new library, and we got over 1,700 submissions, and this was the winning photo. This was a student in front of our immersion theater. The site of the new Hunt Library is a Centennial Campus, which is a 1,000-acre research campus adjacent to NC State's main campus. Centennial exemplifies the vision of academic, corporate, and government partnership. It was significantly inspired by the Research Triangle Park model. And in fact, the former Governor James B. Hunt Jr., after whom our new library is named, was the person that secured the land for NC State 25 years ago when he was Governor of North Carolina. The library was funded by the legislature in 2007, which was actually very fortuitous because if it had been come up for funding the next year, it probably wouldn't ever have happened. So when the library started to engage with the campus community about the vision, we tried to explore the question of what is the value proposition for a new library on a science and engineering technology campus in the early 21st century. The entire College of Engineering, which NC State is the fourth largest college of engineering in the U.S., is located on this campus and will be eventually when the full campus is built out. So there were of course many threads that we could have drawn on here that emerged from these conversations with people, and so we're really just able to follow a few of those to their natural conclusion today. One is clearly that all of you know that data-driven science is clearly a core environmental context for research that libraries need to respond to. And many libraries have already done a lot of great work in defining how they can support data-driven science through building infrastructure and services to support data curation and so on. But not as many libraries have built physical infrastructure to support these new research methodologies. So we asked ourselves the question, do we want to limit ourselves to archiving the results of the research? Or do we have a role to play in creating the platform to support creation of the research itself? Back in 1998, which I guess is 15 years ago, David Lewis wrote this article which had an enormous impact on me at the time. And I still, it's kind of a touchstone for me and I'm thinking about libraries over the years. He asked this question posed by the title of this article, what if libraries are artifact-bound institutions? And he wrote at that time, I still think that this is a profound challenge to us and I think it actually has new resonance when we think of this question in the context of the future of the physical research library. He wrote then, libraries are artifact-bound institutions and as such will be replaced as the dominant technology for information communication. As the dominant technology for information communication moves from tangible objects to electronic bits on a network. As this transition occurs, it is important to understand not what libraries have done, but rather what they are for. They are the means through which organizations and communities subsidize the distribution of information to residents and members. And he further asked, as the library fades at the channel for the subsidy, it is critical that the subsidy itself is not lost. And I think this is very much a living question. I mean, clearly we're still subsidizing books and journals and collections. Taking that question into the present, are there resources connected with knowledge creation at the present time that were like books and journals in the past, for which the library is the logical entity to manage an institutional subsidy? So returning to the data-driven science core use case, that kind of shows where we were, right? We still pay $20,000 for those four journals. The university is also asking this question, of course, right? So looking at data-driven science, the university is looking at shared investments in resources that may not necessarily be the best housed in the library, right? Like, so very expensive microscopes, for instance. Universities are looking at how those can become shared resources to pool the investment for resources like that. But returning to the idea of data-driven science, that core use case, is a visual data analysis that is often associated with big research data. And it's a core tool for both analysis and exploration of data. And I think this is the one that we really decided to focus in on with the Heart Library. We're not alone in this, of course. We see that several other libraries are also engaged with this question, visualization spaces. And these examples are from Brown University, the recent issue of nature that featured Johns Hopkins. And this is the University of Calgary visualization spaces in libraries. Our friends down the road, Duke University, also have visualization spaces and programs. So we built on the visualization and collaboration as kind of the core anchors for the technology vision for Hunt. I mean, there's really a lot more than that. It's kind of a core anchor for our research program. And once we get into the detail of that story in a bit, I just want to take a slight diversion and talk about why I think NCSU Libraries was particularly well positioned to be fairly aggressive in the vision for this new library. Just 30 years ago, we were really not a research library at all. We were really a not very good college library. So we weren't even kind of leading in the scope in which we existed back in that time. And you can see by the budget growth that we've become a research library level funded library over over a really rapid period of short period of time. And I think what we really did is we bootstrapped our way into being a research library through the deliberate strategy to invest in new technologies. So that includes both collections and technology staff. I think that's a critical point. But on the electronic collections side, I just want, this is another little diversion, but back in 1990, John Unsworth was a faculty member in the Department of English at NC State. And he and a few colleagues approached the then and still director of our library, Susan Nutter, asking for assistance to start up this new journal. And that was, this was a time when there were really very few electronic scholarly journals, electronic only. And it was quite controversial. So what the library did is partner with the Department of English that didn't really have a lot of resources to support a venture like this. And it provided staff, provided some space and supplies and places to meet and assistance with copyright issues and things like that. And then subsequently partnered a conference to talk about the future of electronic journals. And I think that really helped gave a nice shot in the arm to this type of forward thinking in the area of digital collections. So this is just a little side light, but I think it's really part and parcel of where we are today. So fast forward 17 years, a new library has been funded. And through a competitive international competition process has selected the lead designer to Snow Heta. And I think Snow Heta was critical to our success with their vision and their willingness to kind of partner with us. And not, you know, have any pre come in with any preconceptions of what this library would be. You may know Snow Heta as the designers of the Library of Alexandria, as well as the Oslo award-winning Oslo Opera House project, which are pictured there. The local architect was PBCNL. And, you know, both PBCNL and Snow Heta will say that that collaboration was the best in their careers. They had never had such a productive and creative collaboration between them. Skanska was the construction firm. If any of you have done building projects, you know that they are a critical member of the design team, critical for success. And we worked with the sextant group as our AB consultants. And I really just want to say again before I go off the slide that without any one of these partners just really stepping to the table and willing to be creative and work with us, this project would never have been possible. So it pretty quickly became apparent back in 2007-2008 that we needed, before we could get to an actual technology plan for the building, we needed a technology vision statement. A pretty well elaborated upon vision statement early in the design phase. This document, which was provided to the internal leadership team as well as the design team, was critical for coalescing around the vision, especially internal conversations in the library, I have to say. It was really a starting point for our work with the AB consultants. It allowed us to really control that narrative rather than having them come in and tell us what kind of technology spaces they were going to build. We were working with them on guiding that conversation. The strategy that this document took was to carry the concepts and lessons that we had learned from our successful 2007 Learning Commons project into very new territory. Showing that we could build on what was widely acknowledged to be existing successes, especially internally, enabled us to significantly expand the program for technology at home. We were inspired by many, so this is the Learning Commons project at NC State. But taking that to kind of the next level, we were inspired by, particularly just focusing on the visualization area. This is the kind of material that that vision document contained. It contained examples with lots of visuals. It was full of visuals. We knew our core audience loved visuals, our core internal audience at least to start, and it ended up being a very effective strategy more broadly as well. We provided visuals like this. What could the library be? Two of these three are non-library spaces. Actually, all three are non-library spaces. The one in the lower left was probably kind of our Lynch PIN inspiration, the University of Sussex Creativity Zone. It really served as the driving force for much of what you see in the library. So these are the core principles that emerged and that were really our foundational talking points for all audiences during the design process. And we wrapped these principles under the overarching concept, the library as technology incubator. Each of these really has a dual meaning. It's both kind of pointed to the current. What we view as our current successes and our core cultural values as a library in the present, what the Learning Commons was already doing, but also I think somewhat subversively pointed to a very different future vision and one that was much more closely tied to the future and to the research library mission of the University than the Learning Commons have been. Our Learning Commons, like all Learning Commons, is really focused on undergraduate and study space and so on. So it's fast forward five more years and we had our grand opening yesterday. Morris and I actually ran out of the party to come to the airport to come here. It's quite exciting and what we see here is just some pictures from the opening itself yesterday. A few tweets about how students feel about the library. Even though we're not focusing on that aspect of it today, I think that it's fundamentally complementary to the success of the library research mission. And now I'm going to turn it over to Morris who's going to get into the actual details of what we did and show you some more pictures of the spaces. Okay, so some of these tweets are actually a really great launching off point into where we're going to go with what this becomes as a research platform, the core topic of the talk. The pictures that we saw, these tweets, really what people experience when they walk into this library is first and foremost an experience of awe. It's just incredibly beautiful and that really opens up their imaginations, which is what we wanted. It was like to walk into this library, people walk in here and see something that they had never seen before and really open up their conception of what a library could be and how they could interact with it. And we have evidence of that, right? So now we take that feeling of awe and wonder and inspiration and we dig down deep and say what can we do to actually take that and leverage it to promote the research enterprise at the university and how we augment that and provide something new of value. So what I'm going to talk about primarily is how we go about looking at the library building, not just putting research spaces into a library, not just putting learning spaces into a library, but turning the facility itself into an integrated holistic platform for research. So we'll talk a little bit about the infrastructure and then as well as some of our research use cases, the partners we've drawn into the space and how they're starting to use it today. So our core focus areas as we ask this question of what is the research library as a facility for these high tech disciplines, for the research that happens today primarily based in compute research, big data and things like that. The value we found we could provide was in large scale display, visualization, interactive computing. These were things that were not present on campus in any sort of organized way. There were pots and there were places that you could do large scale visualization and data work, primarily within colleges and places that were fairly restricted, things that you couldn't really get access to. So thinking about what could we provide in a central community place, a 24 hour facility that could really provide extraordinary value for the entire university as well as these disciplines. Large scale visualization and display was a clear niche where we could move into. And then the communications and collaboration particularly and then piloting and developing new technologies. This core idea of becoming a sandbox for technology and providing this facility where we can continually roll in the latest technologies for the students and faculty to work with. So the spaces that we designed within that building, particularly black box and white box spaces. So this went to the idea of sort of infinite flexibility in our spaces. I actually clearly remember the meeting where we sat down and Kristen and I had been lobbying for this. Everything has to be flexible. We need to change it around. And one of the architects kind of threw their papers on the table and said, you know, at some point we got to put down steel and we got to put concrete around it. There's no such thing as infinite flexibility. But these few spaces were really where we took that idea to its logical conclusion. So they're built like black box theaters for technology. The teaching in this lab is pictured here. You can see this is actually a shot from yesterday. We're standing inside of the Coliseum in Rome. So it has stereoscopic capabilities. It's 270 degree projection. We can create those kind of immersive 3D visual environments. And it also has 3D sound capabilities, which I'll talk about. But we can use these spaces to repurpose on a daily, a weekly basis for teaching research, the technology research and development, creating immersive environments for visualization. But we can also use that kind of black box environment no matter what technology throws at us. We know that it changes too fast for any of us to keep up with. The rooms themselves can adapt and we can roll in the latest technologies. This is our white box space. So what I mean by white box is basically take the same infrastructure principles, but steal some ideas from gallery spaces and from studios. This has movable whiteboard walls that 10 feet high and 4 feet wide. So you can actually reconfigure the physical interior of the room. It's got theater lighting kits, curtain wall system, projection on every wall. We got rid of all the screens that we could and actually just painted everything in projection quality paint. We can project on any wall, project on the floors. The students when they first took tours of these spaces started to affectionately to refer to them as the holodeck. So for all of us Trekkies, it was very gratifying to see that actually every piece of the building began to become associated with some part of the Starship Enterprise. So great for brainstorming, simulation, active collaboration. This is one side of the creativity studio and they're doing visualization work there. And this is the same side of that now converted into a maritime skills simulator for the Navy. So what they do up there is we're looking at a ship simulation. They can drive any ship in the fleet. So they change it from a battleship to aircraft carrier destroyer submarine and actually simulate the correct layout of any bridge on any of those ships and conduct ship simulations and training for their midship. And then to compliment those black box spaces are large scale interactive displays. So we have five giant display walls throughout the building, all of them running at four to eight times the resolution of your standard HDTV. I actually counted the other day and we have over 100 million pixels of display capability throughout the building. Your standard TV in your living room has two million pixels and that hundred million is not even counting all of the LCD and plasma screens we have all over the building. That's just high resolution display wall capability. And this is our game lab. The first one was our Emergent Theater. This is our game lab. This was specifically designed for the gaming research program at NC State, which is one of the top gaming programs in the country. The undergraduate program is focused on the entertainment gaming industry. The graduate program is focused on serious games, applications of gaming to artificial intelligence, medicine, data modeling and that sort of thing. And finally our display walls throughout the rest of the building. The talking about our teaching visualization wall on the right is the most unusual. It's built up into stripped displays. We really wanted to mix up, get out of the 1920 by 1080 box and work with all sorts of different resolutions, different aspect ratios, different configurations of displays to really work with concepts of how do we visualize the data world. How do we interact with the compute world and what are the different ways that we can start to see into that world. So as we make a transition from those physical spaces, so my, I guess you would call it a meme now, is that great physical research spaces require great virtual spaces behind them. Our conclusion with this building was it was not for, you know, half a dozen high profile researchers on campus. It was not for one specific college. These technologies in the spirit of a library actually had to be made available to everyone from your second week undergraduate all the way up to our most advanced researchers who had NSF grants and were working with the DoD and so forth, which meant that they had to be very accessible. You didn't have, you couldn't take, have to take a six month training course to get into these spaces and know the secret handshake and have talked to all of the right people. These are blown wide open. There's no limits to access. There's no restrictions, 24 hour spaces that anybody can use. In order to do that, we had to build the virtual and cloud infrastructure behind that. We had to make these sorts of large graphics applications, the tools to use them easily portable. You couldn't tell researchers that where they were doing their research out on the campus HPC, but in order to come in and use the VizLab, well, you've got to do it on our machines and you've got to start all over again. It had to integrate out into the campus research infrastructure, not only campus research infrastructure, but throughout the park. So going out to Duke, to UNC, throughout North Carolina and all the collaborations that we have across the nation and across the globe. So our focus was on graphics intensive applications of course. We're working with big visuals, rendering, you know, so we have a render farm which I'll talk a little bit about. But obviously if you're working with four and eight K graphics, which they call Ultra HD now, and asking students to create that level of intensive motion graphics, you can't just tell them, well, you know, that's going to take maybe two years to render out. So, you know, come back when you're a senior and we'll give you your passing grade for that. It's got to work very quickly. It's got to snap. So from the get go of the entire program of technology in the building to use those sorts of physical spaces was about virtualization. It was virtualize everything. Sink everything down into the data center. Have all of the computing, all the rendering, all of the graphics manipulation happen in the server room and they get pushed up the backbone. So we actually have, we removed about 95% of the equipment that would have been up on the floors and in the labs and sank that all down into the server room. And we just send visual results up the backbone. Once we sink everything down into the data center, it's all right next to each other. It's racks away and aisle away from each other. Now we can expand that out into the cloud environment. So creating that sort of central compute cloud, the new concept here was project cloud space. So creating a web interface where anybody could go in and say, you know, I need three desktops. I need two servers. I need a virtual network to connect them. I need, you know, 50 terabytes of storage for the project that I'm going to be doing. And I need that for three months, right? So now instead of checking out books or research materials, we're actually checking out compute power to them. And we can come back at the end of that lease and say, hey, do you want to save that off? Do you want to take your VMDK over to your own college infrastructure? Do you want us to just blow it away? Do you want us to archive that for you? And then we extend that out to external compute cloud providers. So people that are working with, you know, NetApp, Amazon, other sorts of cloud providers. And then extend all of that out through communications infrastructure. So through video conferencing, capture, broadcast, we actually, you know, completely blow the walls off the library. We can invite people from anywhere in the world into the space and allow them to be active collaborators with the research that's taking place in the building. So research infrastructure, as we put that sort of concept into place. The places that we really, well, okay, that happened too fast. I hope you caught all of that. Yeah. Okay. I'm going to talk fast. The private cloud, HPC and render farm display servers, any to any display conference and capture, high speed network and high performance storage on the network. In particular, we're working with a 40 gig internal backbone inside of the server room. And this is actually a schematic of that. So I'll just talk from this 40 gig internal backbone inside of the server room. 10 gig drops to all the major pieces of equipment. 10 gig backbone up the back of the building. And then 10 gig out to all the major of a pieces of equipment that are still upstairs. So ultra high speed bandwidth there. We actually have two networks in the building. One is a switched IP network. The other one is a dedicated fiber backbone just for pumping all of that graphical information because we wanted to remove that from the data stream. Moving over into the cloud infrastructure. That's housed down there as well. Creating that sort of dynamic cloud environment where we can allow people to create their own resources to check them out, where we can do the analysis of usage, work that down into the usage of the resources and reporting for grant purposes out on how many compute sources they used, how many cycles and put a monetary quantification on that. And then research computing itself. We do have a small HPC cluster in the building. We need to be campus HPC. We've got that. It's enough local computing power that they can bring their applications, their data and so forth into the building close to the graphics infrastructure and run their experiments, run their research in the visualization lab and resources like that. We have a render farm. So it's about 40 nodes of high performance computing altogether. 16 nodes of that is carved off just for rendering and another 24 for a traditional HPC stack. This is all graphics accelerated. So we're doing GPGPU. We're focusing on the graphics computing. Also have about 110 terabytes of very high performance research storage from EMC and Dell. And then all of our display workstations, everything that drives all the big walls are also down there in the basement as well. So you can be in there in Maya, creating your 3D environment, throw that to the render farm and then have the display servers pick that up and ship it up to the backbone all over that 40 gig network. So everything happens very fast. And then as we pipe that up to the high tech spaces upstairs, like I said, that's that 10 gig backbone and 10 gig drops to all of the rooms upstairs in the building. Just to take a little bit of a walk-through for use cases now about how we use that. So again, it's not just dropping research spaces into a library. And that is a holistic platform for research. So we're looking at life cycle. Research has many different aspects of a life cycle, as we know. It's not just walking up to that screen and throwing up the visualization. There's a whole process of work that goes behind that. And the building has to adapt to that entire life cycle. So everything from very early stages in somewhere like the creativity studio with lots of whiteboard walls, that kind of ideation, the brainstorming, a lot of that physical work that can go on with sketching out ideas to the VizLab, right? A closed space, locked the doors, black box, can do all sorts of that messy early work on the research, throw up lots of ideas and throw away 90% of it because it doesn't work. Going out to media production, now we're actually producing those graphics. We're working with that data. We're in a high performance using lots of different applications and manipulating all of that into presentation-worthy form. Interactive computing, we're actually putting those applications out for people to use. And then the graphics-intensive applications, we're taking that out more into public spaces, places where we want to do demonstration, where we're trying to teach with it, where we're trying to bring other people into the research process to get that feedback loop and finally to present the results of those research and broadcast them out to the community. So to take a specific instantiation of that with gaming. Like I mentioned, gaming is a huge cornerstone of what we're doing with the library. One, because gaming leads a lot of technology, it leads a lot of use cases, and it allows us to dig down into other aspects of research areas. So with gaming, right, so we can start with that concept development, ideation and design, move into the VizLab for that early prototyping and proof of concept work, come over into the media production labs for the cinematics, the graphics, the animations, and then go down into the game lab for that kind of critique, gameplay demonstration. And to show how the cloud environment leaves into that, all of that is backed by the cloud. You don't have to think about what room has the right computer in it, where the applications are installed, how do I get my data in there? You walk into any space, you log into the network and all of your stuff is just there. So it's really thinking about what space is the most appropriate for me and what application and what computer is driving it. So when we're talking about gaming, as I said, you have those graphics workstations, where you're doing a lot of that coding and creation, the render farm for producing the assets, development servers, we're hosting a lot of the code, the gameplay clients, code repository, and being able to push that out now to all of your mobile clients, your laptops, your devices. So finally now digging down into the research itself, what do we really mean by enabling research in the building? There's many different aspects of that, three primarily that I'll focus on. One is the platform research. So research on the building itself as a platform, how do we continuously keep that developing and keep the technology fresh? Applications research, how do we build the tools to allow people to use that platform? Just putting it out there isn't enough. They walk into the building, they get frustrated and they never come back again. We've got to give them the tools and then academic research. So these are the grants. This is coming in with your NSF grant, your DOD grant, your National Humanities grant, all of that that we really think of as traditional academic research. So the platform is really about, the research is about creating adaptable infrastructure and technology integration. When we get into the applications, we're trying to create an API for the building, essentially that extensible API, reusable frameworks for how the building functions. And then when you get into the academic research, that's a pure research knowledge advancement. And there's a specific area of investment associated with each of these, right? So we have to create new models of investment, new models of sustainability. The platform itself is about corporate investment. This is the spirit of Centennial Campus, academic and corporate partners working together. The extensible APIs come from community investment, asking our community to create those APIs that allow everybody else in the community to use the research platform. So this is the shared community investment. And finally, on the academic research inside the grant investment, bringing in those dollars, getting written into the grants, having the entire research community think about this building as an enabler for their grant work. So just quickly, I'll run through a couple of elements here, just as examples. So platform research, we're really talking about how does this facility function? How does the hardware function? What kind of technologies are we using? Just as an example, so we designed, traditional technology designed for a building of this scale is about two years behind the curve. They want to make sure this stuff works. You don't go out on the bleeding edge because then it doesn't work and, you know, it's kind of embarrassing. What we continuously pushed for throughout the design process was don't put us behind the curve. If we stuck two years behind the curve, we're way too far behind for a research platform. Research is always on the leading edge, so the facility itself has to be the latest, the most recently released, the cutting edge technologies. Now there's a cost to that, which is that some of the stuff that we plan to install of the building hasn't even been released yet, right? So we're still waiting a few months for some of the technologies to actually become available on the market so that we can put them in the building. But that's all in the spirit of it. That's exactly what we want, right? Now, there's a threshold if you get more than half of your technology is not even released yet, well, that's a little, a lot of sleepless nights, shall we say. But it's where we want to be. And these are some of the companies that we're working with. We have over 14 corporate partners on the table to invest in this idea with us. To use the building for their own platform for research as well. If you put these beta technologies, things that haven't been released or proven out into AT&T and you get it wrong, they could lose billions of dollars an hour. But if you put it into a safe research environment where the idea is when stuff breaks, that's how we learn, right? So this becomes a very compelling environment for these companies to work in. So for applications research, this was a student, a PhD student in computer science. This was a blog post that came out within the first week that the building was open in January. And I'll just read a couple of pieces of it, but what I would have loved to see is an API for Hunt Library itself. Okay, so the building opened and basically there was no technology in it, right? It was stunning, beautiful facility, lots of furniture, no computer anywhere, right? So what I would have loved to see is an API for Hunt Library itself. Imagine if students actually had an interface where they could write apps for the library, right? Give us the tools to add to the library. So they walked in immediately new that this was something different, right? This is something I should be able to create with, but I can't because I don't have the right tools. So give me the API. And that's essentially what we're doing with the applications research, right? Create the frameworks, create the reusable components. We don't do one-off projects for anyone, right? We have developers, we have designers, we have consultants. We won't take one faculty project and say, we'll build this for you and it only works for you, but it'll be great because you'll be able to finish your research, right? We pass those aside because it's not sustainable. We can't keep that up. So when we take on a project, we look for the things where we can create a framework, where they'll partner with us, they'll build something that's reusable, and then we have a nice faculty member that comes along. We can say, hey, someone already did that and we know exactly how to drop your stuff into it. Just to give you one example, actually I'll save it. I'll come to a really good example of that later on and in the interest of time, I'll just leave this one there. And then on the academic research side, so this is my transition, where we'll talk about a couple of our specific projects. Clearly with making this kind of technology and facility investment, you don't want to just walk out and then the first time someone asked the question of, okay, who would use that and what would they do with it? You've got to have something in your back pocket, right? Hopefully a couple of somethings. So they don't start asking, you know, that conversation could go on forever if you can't put the right stuff and then to prove why you did this in the first place, particularly at a state institution. So these are a couple of our core use cases, you know, creating big data harvesters and business analytics for the College of Management, maritime skills with the U.S. Naval Training. I showed you a picture of that one. Gaming design, AI, virtual crime scene investigation, which was one of the coolest. I'm sorry, I can't show you more of that. Creating virtual forestry environments and things of this nature. St. Paul's Cathedral, I'll talk about more in-depth right now. So like I said, as soon as we started creating this, the core use cases were engineering, computer science, textiles, which is actually an extraordinarily high-tech discipline these days. But it extends to the entire university. As soon as you create an environment like this, it actually, you walk out the door and you start tripping across people that could use this. So digital humanities was one, right? And that John Wall up in the corner working with Joshua Stevens and David Hill. This was a multidisciplinary effort to create a virtual reconstruction of St. Paul's Cathedral, which burned down in the London Fire, 1666. The research question was, what would it be like to stand in the courtyard of St. Paul's Cathedral in Paul's Cross and listen to John Dunn deliver a sermon? So they built the whole 3D environment. They did lots of cool stuff, like sonar plunging of the original foundations of the building, exploration of the original documents in the lower corner there, as one of the original sketches of the cathedral, and create a full 3D environment. And then don't stop there, but give that over to sound engineers who can now look at the reflection properties of the 3D environment, can look at the acoustical properties of that space would have been in 1622 in London, and actually recreate that sound environment. So then we can go into the visualization lab where I mentioned we have 3D audio capabilities as well as 3D visuals. And what all 3D audio means is the same acoustical environment that we walk around in every day on the street. So your traditional sound environment of what they call surround sound, there's kind of a sound on the left, right, 3D sound is I can get down to the level of creating a fly buzzing around your head and you can hear exactly where that is and you can turn your head in space and that sound shifts as you turn your head. So take that into a virtual forestry environment. Now we can change the shape of the room into a hilltop in North Carolina. We can place bird song half a mile away and have those birds migrate around through the trees and you can actually follow them and identify what species of bird song you're listening to. All without leaving that room. So we switch over to Paul's Cross and now you're in the courtyard of St. Paul's Cathedral. You're listening to John Dunn deliver a sermon. You can change the crowd size from 25 to 100 people. You can cue a flock of birds to fly overhead. You can stand in the back of the courtyard next to the apple cart and see what that was like or move right up next to Paul's Cross, the pulpit station itself and listen right in front of them. And finally, this is a last example of some of the academic research applications. On the upper right there, looking at 3D visualization, we have a faculty member who wants to move into that VizLab and use the 3D projection capabilities to look at plant cell component mobility through cell walls, which is apparently an extraordinary, difficult thing to explain, but putting in a visualization environment like that, now we can demonstrate it and skip a lot of that confusion and just difficulty in explaining what the environment is like. The innovation there is we put that visualization into the Unity game environment, so leveraging our gaming component and they can interact with it in a live gaming environment now. So to go back to the example of reusable frameworks, this is the concept for the VizLab. Anybody that has a 3D model or creating a Unity game environment that's tuned to the properties of that room can leverage the sound capabilities and all you have to do is give us your model and we can drop it in there and you magically have an instant visualization interactive environment. On the lower left there, 3D quantification. So not just working with, all visualization is sensory representation of data, so we can gain some new knowledge that we wouldn't have had if we just looked at raw numbers and data itself. So that happens not just in the visual world, but in the oral world as well. So Sina Barum, who was identified as one of the White House champions of change very recently, he is blind and so his research is how do we take data and represent it in a 3D sound environment so that you can experience data through 3D sound and interact with it in a 3D sound space. So you can imagine if you took that plant cell visualization and you were blind, it wouldn't do you any good. But if you could represent that through sound, now you have a very rich interactive environment where you can take that data and gain some new value from it. So finally, just to conclude to tie it all back in, this is how we envision this building as a research platform. It will take us a couple of years just to prove out this concept. It's entirely new. There aren't good models for this anywhere. We are trying to build a new model for what this kind of research platform looks like. At the same time, we are very conscious that there are many important applications of this kind of technology. And we want to acknowledge them all. That is the NCAA tournament. Unfortunately, we were kicked out in the first round. So I was standing here going, oh, the wolf pack is losing. That's terrible. But wait, that's really cool. So it was a conflicted sort of moment. But that's the Hunt Library and that's the research platform we're creating. Thank you.