So what's the session going to be about? So we're going to talk about what does the Kubernetes steering committee steer? I'm Navarone. And I'm supposed to be Bob Killen? But hey, you're Tim, no? So here are the members of the committee. So we are a seven-member committee where Bob, Tim, Carlos, Christoph, Benjamin, Stephen, and I will talk more about how is the committee staffed in a way. So let's see some stats about the Kubernetes project and why are we relevant. Kubernetes is a big project. In its whole lifetime, we have had almost 80,000 contributors. I think we're having 10% year-on-year growth, 10% or 15%. There are around 1,800 org members and 345 repositories across four GitHub organizations. During 2022, it was the sixth largest open source project by developer activity and fifth largest by number of PRs. And in the past, I think in 2021 or 2022, we were number two in terms of project velocity, which was just behind Linux itself. Needless to say, it's quite large. And in order to manage the technical aspects of the project with these many people contributing to the project, we have to put a lot into how we structure ourselves. What kind of groups on what areas of code? We have 345 repos, so we need maintainers for all of them. How do you potentially resolve conflict between groups or inside groups themselves? How do you know the groups are healthy? They're not burning out or they need more maintainers or how do you actually ensure that they continue state of the over time? Or maybe sometimes groups are formed for certain reason and after achieving what they want to do, they may not be relevant anymore. And we have to make a decision on if they're still needed. And these are the project governing things that we do and which makes us relevant. And where we come into the picture. Now, here's a picture of what are our community groups and how we are organizationally structured. I would encourage you all to check out the link at some point in time. But I'll give you a TLDR. We have this picture as well as a document detailing what each group does and what kind of groups we have and what they're supposed to do or what should be the scope of each group. TLDR is we have three types of groups, special interest groups are SIGs, working groups are WGs and committees. So special interest groups make up the majority of our community groups. They essentially own code. For example, you might have used kubectl. So six CLI maintains that area of the code. We have working groups, which are transient groups. They're supposed to achieve a certain use case. For example, very recently yesterday we had conversations around long-term support. So working group LTS was one of the groups set up sometime back and they achieved some amount of LTS capabilities and then they grabbed up. Now, because there is more interest we are bringing that group up. So just to give an example of what is the working group. And then we have committees, which is what we are. There are two more committees. One is the security response committee who handle any sort of CVs, security disclosures. If anyone wants to reach out, like, hey, I found a vulnerability in your code, that they are the people who handle it. And then we have code of conduct committee. That's really important because they ensure that the code of conduct of our community it remains enforced and they handle any kind of conflicts arising in the community. So the steering committee is essentially the top-level governance body within the project. So what does the steering do? It is basically a synopsis of the formal definition of what we are supposed to do. We are the governing body of the project. We provide decision-making and oversight into activities of the project and what other groups are supposed to do. We also do provide financial planning. For example, like, if someone wants funding for certain things, we try to redirect that to whoever is supposed to fund that. For example, FCNCF is the right authority. And very importantly, we define the project values and the structure of the project. Now, these are our direct responsibilities. We do a lot of this. I would basically go on next and let's try to understand holistically what do we really do. So whatever we do comes up to this thing that we want to protect the long-term sustainability of the community. How do we protect our contributors? How do we encourage a leadership pipeline? How do we ensure that people grow in the community? We don't have any area of the community lagging behind or we have less amount of maintainers in an area. And if we look at such a big project and a big community, we also do want to engage with commercial contributors, people or companies or vendors or end users. How do we promote them to put in resources or people to this project to ensure that people are funded to work on Kubernetes and hence its sustenance? With that, I'm going to hand it over to Tim. So bear with me since Bob was unable to make it. I'm filling in for Bob. I should know all of this stuff, but he has really awesome detailed speaker notes. And I want to actually make sure I touch on the things that he says. So first, this idea of supporting and protecting contributors and the breakout of the SIGs, the working groups, the committees, the different reasons these entities exist. One thing maybe that everyone didn't say explicitly is that a steering committee, you might think of us as the overarching, like in that 80,000 people in the 300 repos and that sort of funnel as being a hierarchy up to the top, the hierarchy of importance or something like that. And we try to be the opposite. We try to make sure that the vast majority of things are delegated out to proper topical owners. But then there are some unusual things that come up. So a couple of examples of these recently. So I've been a member of a variety of nonprofit boards. I do volunteering and things like that. And through some unfortunate experiences, one of the things I've learned when I volunteer for something is to ask because I'm an American and we're a litigious society, what type of liability insurance do you offer your volunteers? If I do something and something goes wrong and somebody decides to sue me, what happens? And this is a question that's been coming up more and more in open source. And in particular for a project the size of Kubernetes. We've had this come up in multiple different areas. So we've been trying to figure out how we established some sort of a framework to give protections to our open source contributors. It's tricky. We have lawyers involved, we're looking at different options but we've been trying to force this issue as we've recognized at our level within the project that there isn't, we don't have a SIG legal for example. So we are sort of a place where an unusual thing like this bubbles up and we don't necessarily have this exactly resolved yet, I don't feel like, but we're actually making some progress and the ecosystem is starting to realize this is something we need to think about and do. Another angle of this is increasingly perhaps you've seen talk of regulation both in Europe and in North America, there's talk of regulating the way software is developed and distributed and that has impacts on open source. So those are perhaps some places where we might put our voice in and represent the project and our developers. A similar area of where we sort of might weigh in on something is providing visa support to our contributors. I'm very privileged as an American, I have a passport that allows me to more or less travel the world and I don't have to think about it but very commonly we have contributors who are major contributors in the projects in this space, they work up some really interesting thing, describe it in a potential presentation for a conference, get it accepted to the conference and then the hosting country of the conference says, oh, you need to do paperwork to improve why you're coming to our country and there is a sort of senior body within the organization, it comes to us to write that letter of support for those individuals to help them be able to come and share their experiences and lead within the project. So those are maybe not something that you exactly see in the details of the charter but things that kind of escalate up to us where we're supporting our community. Another big area is project health. So it's really easy I think to be deceived perhaps by the 10,000 people who are here this week. It is, I've been in this project for quite a while and it continues to overwhelm me each one of these conferences, the growth but despite the outward appearances, we're hurting and most of open sources between the pandemic, unusual geopolitics, economic pressures, a lot of companies who would maybe previously been more actively supporting open source and open source developers are supporting in different ways and or individuals who are doing things on a volunteer basis or having to focus on earning a paycheck or different things like that have led to a more recent decrease in the actual number of contributions. So this is a chart that Sophia Vargas at Google created to show that you might think that everything's going great but over the last couple of years actually we've seen some decrease and that's hurting, we have less active, we have a smaller number of active people in aggregate and that leads to more of the people who are active carrying more load and then we run into problems of burnout. So we've definitely been experiencing attrition and our contributor experience SIG has been working to bring new contributors but this takes time, it's difficult and then perhaps at our level we can be advocating out to member companies of the CNCF or others in the ecosystem or as a great example I think Don Foster's keynote at the beginning, at the end of this morning's beginning keynotes, talking about what it means to be contributing to the humans in open source, making sure that that message gets out there as something that we try to support because we need that for our developers and then more simple conceptually types of programs making sure that we've got mentoring cohorts working through our project and that we're inviting to new people so that they can show up and contribute. So with that you have something like a leadership pipeline. We have a variety of sort of titled or named roles within the project and we've been working to evolve that across time. We want to encourage individuals to do the important work and sometimes that requires having some structure. So we used to just have a very simple flat scenario where we had SIG leads or SIG chairs and that was that but there's a lot of responsibility that falls on that person. Everything from recording a meeting on Zoom, uploading that Zoom meeting to YouTube, keeping the calendar up to date, the agenda but also the code, doing code reviews and approvals and things like that mentoring of new people coming into the SIG. So we've worked to split that out more so that there's a separation of chair duties and tech lead responsibilities so that we can maybe have more people come in and have a specific responsibility. The ambiguity in the past was confusing both to new contributors and to the existing folks in leadership. So with these separations and also we can have maybe more formalized sub-project leaderships. That's not something that's officially merged as a process and I guess I should mention there that when I talk about merging process we literally do that. Our processes are written and marked down they merge into get of their public and known. They go through the normal open source review process as we iterate as a project body towards making decisions on how we're gonna run but we as a body try to instigate change in leadership on those things. So we're working on some evolution there. So on the employer's topic then we need to engage the organizations who are here effectively at KubeCon. The keynote this morning they talked about 300 some odd end user companies are members of CNCF 800 companies total. We need those companies valuing the humans doing work also in these projects giving those employees an incentive hopefully to participate and contribute to these projects. So our steering committee also works to interface with some of those companies and we talk to our own employers and some of the big groups, the Googles and Amazons and make sure that we're advocating and helping them understand the business value. This is one of the weird things for me as an engineer having to learn through my career to advocate for business value. It's not just about code and checking does the thing compile and run functionally correctly but we also have to think about the business size. So this is something that our steering committee does and not just with the big cloud providers the Googles, Amazon, the VMware sorts of companies but also end user companies, the Mercedes or Shopify or Apple type of companies helping them understand that they also as a consumer of this open source stuff even if they're not making money directly off of it it might make sense for them to be contributing to the long-term sustainability of the project. So let's say we succeed in that message. We've convinced somebody like, hey, I'm gonna start dedicating an engineer's time in part or in whole to these projects. Those people need a way to come in and understand where help is needed, where they could apply their labor. So one of the things that we've been doing over the last few years is an annual report process. Each of the SIGs writes up a document describing where they've been the past year and giving some roadmap information for the coming year and shining a light a bit on areas of help needed. So that hopefully if somebody is looking they see the progress of the project and kind of can project where it's going and maybe get on board and contribute. So we have 30 some odd SIGs so you can imagine 30 times five to 10 pages of documentation like there's hundreds of pages of where we are as a project. Steering consolidates that into a shorter report around 20 pages and we use that as something for collateral that we can try to start conversations around where we are, where we're going and hopefully get more people involved with the long-term sustaining on the project. And that is our last slide. We're on 20 minutes ish in. We've got a bit of time for Q and A. We'll pass the mic around and then there's just some links which I'll leave up while we chat on where to find us, where to get more information on what we do. Yeah, so any questions? Are you ready for dinner? So how easy or hard are you finding people that wanna volunteer at the time to be part of the steering committee and are you facing burnout with the existing members of it? So did we say explicitly that we're an elected body? So members of our community have voted for us to represent them. We also had to either be nominated by somebody in the community or self-nominate. So in the case where somebody is nominated, we have a checkpoint to say like, are you sure you wanna do this? Do you have the time? Can you do this? But basically those of us who are on steering have been on steering have chosen to contribute our time to this. Burnout is real though. There are weird things that come up. One week you may do almost zero hours of steering related work and here and there, it will be a full-time job for a week because something has come up. It's relatively unpredictable. Unfortunately, I think that leads to a situation where it biases towards employees of larger companies. This is effectively my job. I'm in a position where I kind of define my job. So I have that flexibility. But if I were in a different role, I couldn't just tell my boss like, oh, our production service with Kubernetes that I'm responsible for running. I'm not gonna be doing that for this week. I've got this community stuff I need to do. So I think that that makes it a little less approachable than it should be and that's a challenge. So we're trying to figure out how to do better on that but I don't know that we have a great answer. Something else we do publicly, like all of our elections, the results of them are on GitHub. So you can see we've had lots of people put their name in the hat. So I think we are getting volunteers but then we still have the problem of burnout. And it's a two-year term that we sign up for. It's really hard to project where you're gonna be as an individual or in a career two years out. So it's tricky. Just a couple of minutes ago, I was actually twisting somebody's arm to put their name in the hat this fall that they should consider being one of the volunteers to do this. So if any of you are interested, if hopefully we haven't scared you away, like these sorts of governance roles are important, an important place to contribute to the overall health of projects. So think about how you might do something yourselves. Thank you. Just a question about like things like which seems pretty clear, like can be handled by like a steering committee but things like what you mentioned, the legal issues is not like super clear because I know like things that might have their own like legal teams for that. So I'm just curious about like the boundary of the responsibilities which handled by the steering committee and handled by CNCF. Thank you. That's another area where things are kind of fuzzy. Again, despite the impression you might get from this massive conference, like I literally don't know what the budget of this thing is, like this is a big deal that the CNCF puts on. They are consummate professionals putting on an event like this. But not necessarily all of the details of how the interactions between that entity and all of the hundreds of projects that are related to CNCF. Those are things that are all emerging and being developed right now. The CNCF similarly has a GitHub repo where these processes are defined and they're actively in the process of definition. Yesterday I was commenting on something for an emerging process that would better clarify where the Kubernetes Code of Conduct Committee is versus the CNCF Code of Conduct Committee. Those are things that are regularly coming up and partly a surprise sort of fashion like, oh, you're doing that, we're doing that. Let's be open source, let's collaborate, let's figure out who should do it and how we can do it together well or if you should do it or me do it. And there are not necessarily clear boundaries but in that open, transparent way. We work really closely with the CNCF and try to figure out what's the best way to go. The CNCF is a corporation, they have a governing board and there's a technical oversight committee as well and we interface with those bodies regularly and things that we're seeing will bring up as sort of emerging patterns, ask if they're seeing. And then also this gentleman here who quietly asked a question, he works on OpenStack, they also have a foundation. We chat with them periodically, try to cross-pollinate ideas and challenges and figure out the best way to solve things together even though there aren't necessarily clear lines or we're totally separate different things but that doesn't mean we can't work together. Thank you. It was really good to see you guys are thinking about how to organize the leadership of the SIGs a little better. And I don't mean this to be a leading question, I'm actually really curious what you think. You're an elected leader, but the SIG leads nominate the replacements. Do you think that's the best way to have that process work? Have you thought of any alternatives? So this is somewhere where I failed because this was very clearly in the real Bob's speaker notes. He mentioned a couple of things on this. So some of those changes in governance that we have so you can't see the speaker notes I guess but we have the ability for SIGs now to define new roles. If a particular SIG things like we need a such and such that SIG can write it up, describe what that's gonna be, get it into their charter and do it. If a SIG wants to have an election, they can do it. So if a SIG wants to operate a particular way that makes the most sense for them, they can. Then the other thing is I was talking about breaking out the chair and the tech lead role. One of the things that we've discussed there is, do we have, and this is maybe, I don't know if you're referring to this, I don't think of it as a contentious thing personally but some people find it contentious. I think we can find a harmonious way to move forward with these things but we've been talking about whether we can or should have terms for leads. And I think that is a really positive thing personally because the term is just to say like every second year at a particular time, I should pause and reflect and be introspective. How is my SIG doing? How am I doing? Does it still make sense for me to lead? Is there somebody I could pull up to hand the reins to? I think that's a very positive process to do and it doesn't mean that you must fade off into the background. It's not removing anything from you. It's a positive, additive, non-zero-sum game way to view the world. The next step of the conversation though is well, if we have terms, should we have term limits? You can only be a lead for two terms or whatever the magic N number is. Three terms, one term, six terms, I don't know. That starts getting more contentious. I don't know that there's a right answer. On the one hand, you want to bring in new people. Have less burnout maybe, spread the load, encourage newcomers. On the other hand, maybe you have somebody who's the excellent professional doing the job perfectly. Everybody wants and has them. And if you have a process that says they must fade away, that doesn't feel right either. So there's an inherent conflict on that. And we don't have an answer. We're just talking about it at this point and we'll see what evolves. I think to your question of elections, elections make sense when there are like, there are a lot of people in the fray who are right for doing their job, but you want to choose between someone. Like let's say you want to choose two out of five people, but you don't have consensus on how do you want to nominate them. I think in those cases, elections make a lot of sense. Unfortunately in our community, when we want to like do succession of chairs or technical leads, we have very few people who are willing to do that job day in and day out because it literally takes a lot of time, bandwidth, and the knowledge to be gained over years to even do that job. So, but I would really love to see like some of our community groups try out elections. I think, code of conduct, staring, and I'm not sure if anyone else has tried elections recently but Quantarybacks does maintain Electo. So, if you want to have an anonymous election mechanism using some GitHub artifacts you can. Thanks for the great talk. I have a question. What's the future of Kubernetes? So, I think looking at the chart, I saw it's okay. It looks quite stable and maybe that's also one of the reasons why people are not joining so much anymore but I don't know, it's just a theory. Thanks. Maybe Kubernetes 2.0, time for it. I can speak to this, I guess. So, I've made my career an open source. I first bumped into open source in 1995. So, I'm coming up on 30 years.  You look at these numbers, I think it's hard to say like there's, as much as I said, like we have a problem. Like this is in many ways a good problem to have compared to a lot of projects. At open source often you have a sole maintainer who is burning out. We do have a lot of people but also then this other picture, there's a decline that could be a worrying thing. The way I'm choosing to positively see this and talk about this, I think it is true, I guess in time we'll see, I could well be wrong but in other large, rapidly growing open source projects, I've seen this massive influx and hype and money and interest and need to stabilize and add features and improve and then at some point it kind of gets good enough. A few years ago we were all joking like the goal is to make Kubernetes boring. Maybe we're starting to get there and it collapses down, not in a fatal way but it collapses down into a stable core. I think that you could look at the project and see the signs of that starting to happen and say, oh, this is a healthy evolution. I think technically like one of the reasons that we see some amount of decline in metrics is also because we have made Kubernetes so pluggable that a lot of entry development has now moved out of tree. For example, cloud providers, storage interfaces, networking, we've made it so modular that people can now develop out of tree and plug it in into a compliant Kubernetes cluster which makes it really stable and like just want to make things boring and maybe release once a year. Don't quote me on this. Any more questions? I think we're on time but can take a couple more questions. Cool then. Thank you so much. Thank you.


Hello, and welcome to this presentation of the STM32 Cube Firmware Package for the STM32 U5 series. The STM32 Cube Embedded Software for the STM32 U5 series is the richest firmware package released on web at product mass market launch. It is published on GitHub in addition to www.st.com for faster propagations of improvements and bug fixes. It is open for pull requests and issues to facilitate user contributions and direct feedback. It highlights all features of the STM32 U5 product with a particular focus on the low-power features through dedicated examples and the first in a kind provision of a helper utility driver for LP-BAM subsystem. Security features are represented by trust zone support, TFM stack integration, and dedicated SBS FU applications. This firmware package is the first to natively support Microsoft, Azure, RTOS, Middleware, USBX, FileX, LevelX, ThreadX, and NetX Duo, inducing the full cohabitation of USBX and USB PD. Amongst other in-house Middleware support such as Touch Sensing Library and Network Library, the STM32 Cube U5 Firmware Package also supports the open bootloader. IoT and connectivity are also part of this firmware package through wireless communication, which relies on external baseband and RF devices, MXChip for Wi-Fi, and ST32WB for BLE, supported by the BU585I IoT02A Discovery Board. For each board, a set of examples and Middleware applications are provided with pre-configured projects for EW ARM, MDK ARM, and STM32 Cube IDE tool chains. And improved documentation, thanks to the new HTML readme files present in the various firmware directories. See the figure on the right. The STM32 U5 series features the low power background autonomous mode subsystem, which allows peripherals to be functional and autonomous, regardless of the power modes, and without any software running. It can chain diverse operations through DMA linked list transfers. The LP BAM utility is a set of modular drivers located in the Utilities folder of the STM32 Cube U5 Firmware Package. It provides two levels of abstraction to the user, basic and advanced levels. The LP BAM utility is based on layers. The first level of abstraction is a hardware agnostic layer called the basic LP BAM layer. It gives users full granularity of scenario creation via transversal APIs. The second level of abstraction is a hardware agnostic layer called the advanced LP BAM layer. It provides a predefined scenario that can be customized and concatenated to build an end user application. The platform layer contains device specific constants to be used by the applicative side. The low level LP BAM layer is used by the basic and advanced LP BAM layers. It contains the device specific mechanisms for each supported peripheral. Nine applicative use cases developed on Nucleo U575ZIQ enable users to become familiar with this new class of drivers. Additional dedicated modules are available in the STM32 U575EV out-of-box demo, signal generator, and sensor acquisition. In addition to LP BAM, multiple examples implement the various low power features offered by the STM32 U5. ARM Trusted Firmware M or TFM is the reference implementation of the ARM Platform Security Architecture or PSA for TrustZone. Two different examples are provided in the STM32Cube U5 MCU package. The first is a complete implementation of TFM. A second application implementing only the secure boot and secure firmware update functionalities of TFM called STM32Cube U5 SB SFU is also available. The TFM reference implementation provides secure boot and secure firmware update services based on open source MCU boot and a set of secure services available at runtime for the user application. The table indicates the main features of the secure boot and secure firmware update application. Dynamic firmware update is supported with two slots and swap capability. In a mutable standalone local loader is in charge of downloading the possibly encrypted image. Two levels of isolation are implemented, secure versus non-secure and privileged versus non-privileged. Secure services are secure storage service, attestation, crypto service, TFM audit log, platform service. Seven dedicated TrustZone examples and applications are available for three IDEs, IAR, Keel and STM32Cube IDE. The STM32Cube U5 software suite is complemented with Microsoft Azure RTOS middleware that includes Azure RTOS Thread X Real-Time Operating System, Azure RTOS File XFAT File System Fault Tolerant, Azure RTOS NetX and NetX Duo TCPIP stacks, Azure RTOS USB X USB stack host and device and cohabitation with USB PD. The list of features supported by Azure RTOS middleware is provided in the table on the right. Azure is natively supported by STM32Cube U5. The additional key benefits that Azure RTOS brings to the well-known STM32Cube software suite are fast performance, complete consistent solution, industry certification. The USB Type-C connector enables traditional USB communication between the host and peripheral concurrently with the power delivery protocol. The STM32U5 embeds both a power delivery interface and a host device, USB 2.0 interface. The STM32Cube U5 is the first firmware package in which USB X and USB PD are fully integrated. USB X includes host and device stacks that come with many classes. The two following applications are provided in the firmware package. USB PD SyncU X device, HID CDC ACM, USB PD Type-C consumer and USB device using the Azure RTOS USB X stack on the STM32U585XX board. USB PD SRCU X host MSC provides an example of Azure RTOS USB X stack usage. It shows how to develop USB host mass storage capable of enumerating and communicating with a removable USB flash disk. Full validation and pre-certification tests facilitate the design of USB data and power delivery applications. An important requirement for most flash memory-based systems is the ability to update firmware once installed in the final product. This ability is referred to as in-application programming or IAP. Open Bootloader is an IAP that is provided in the STM32Cube firmware package and GitHub. This is an example that can be used by any customer that wants to build their own bootloader. Its main task is to download the application program to the internal user memory. Flash SRAM or OTP without the need for a debugger by using one of the available communication interfaces. Usart I2C SPI USB-DFU or FD-CAN. Regarding the USB boot interface, STM32U5 is the first MCU to support the integration of Azure USB X and ThreadX RTOS. Open Bootloader provides services to the host application such as STM32Cube programmer to download firmware to the device via an interface link and install this firmware into the required user memory. Open Bootloader relies on the STM32Cube firmware HAL and LL drivers for hardware system initialization such as the different clocks and the interface configurations. Open Bootloader is executed by the Cortex-M processor in the non-secure domain. The list of commands that are passed to the STM32 through the selected communication link is indicated on the right-hand side of the slide. In this implementation only, one instance of each protocol is used and for each of these protocols, one set of default pins is used. It is then up to the user to change the instance or pins if desired. This figure sums up the features of Open Bootloader. The objective of Open Bootloader is to provide an open source boot program with exactly the same features as the STM32 system bootloader and with exactly the same ecosystem. Open Bootloader is compliant with the STM32Cube firmware architecture based on the same drivers and middleware. Compatibility with the official ST Bootloader host, STM32Cube programmer is assured. By providing the source code, customers can adapt the boot program to their specific needs. Open Bootloader will progressively replace the IAP application in STM32Cube package. This slide describes the module that provides Wi-Fi connectivity to the STM32U5. The EMW30-80B device made by MXChip is an embedded wireless internet connectivity device. The module uses either the SPI or the UART interface to communicate with the MCU. The EMW30-80B module is directly soldered on the BU5-85IIOT02A board as highlighted in the top view of the board. It can also be present on a separate board. The EXTAT3080 shield to connect to any STM32 board via an Arduino connector. The MB1400 shield to connect to any STM32 board via an STMOD plus connector. The Wi-Fi module requires no operating system and has a completely integrated TCPIP stack that only requires AT commands to establish connectivity. The software architecture relies on the MX Wi-Fi driver that communicates with the EMW30-80B module. Test applications developed by MXChip and network library and applications developed by ST can be used on top of the driver. Seven middleware applications and one demo allow to get familiar with this Wi-Fi module. This slide describes the module that brings Bluetooth low energy connectivity to the STM32U5. The innovative architecture of STM32WB MCU's is based on two totally independent cores, optimized for real-time execution and enables flexible resource use as well as power management. This module is embedded in the BU5-85IIOT02A board. Communication with the STM32U5 is based on AT commands transferred over a UART link. The following application is available to demonstrate the capabilities of the BLE module. Heart rate sensor, point-to-point server. Once connected to the STBLE sensor application installed on a smartphone, the user can use LEDs and the button to verify the communication between the module and the smartphone. The instructions and commands that are transferred are displayed on the STM32U5 console. See the capture. The Wi-Fi web server demonstration is described in this slide. This demonstration firmware is part of the STM32CUBU5 MCU package. It shows how to use the MXChip module to perform HTTP requests using STM32CUBHAL. The MXChip module and a web browser, Google Chrome browser in this case, are used to create a web server. This web page supports PC and phone usage. The BU5-85IIOT02A board is the HTTP server in this demonstration. It contains the web page resources sent after each client request. The BU5-85IIOT02A board can decode, treat, and respond to client requests. Web page resource requests such as HTML pages, CSS files, and JS files. Sensor value requests, temperature, pressure, and humidity values. The user can start surfing a web page by copying the server IP address provided after the network interface process and pasting it in their browser. The web page will be loaded on the client's server. The web page contains four main menus. Home menu contains the product and the web page description. Temperature menu, pressure menu, humidity menu. Finally, the user can choose any menu and start or stop the different sensors' acquisitions. Standalone, HTML, Readme files are available in the directories containing examples and applications. They indicate the objectives of the program and expected results and useful notes so that users can easily understand the program and quickly develop their own projects. Thank you for attending this presentation.


There is not a high risk of transmitting HIV through oral sex. There's a very low risk. If precom or semen go into your mouth, you're either swallowing it and digesting it which kills the virus or spitting it out. And if you're worried, you can use mouthwash or rinse your mouth with water a few times. Using mouthwash after oral sex does not protect you from viruses or bacteria. There's no evidence to suggest mouthwash kills viruses or bacteria.  It just doesn't work. Secondly, ingesting viruses or bacteria doesn't kill them. They grow inside our body. Saliva, gastric secretions do not kill them or digest them. Just use your common sense. People suffer from viral diarrhea. Related to adenovirus, rotavirus, we have severe diarrhea. It's a disease, an infection. So same goes for HIV. If you swallow it, it grows inside your body. It doesn't get killed. So again, use protection.


Google was put on sale in 1999? In 1999, Yahoo and Excite held the top spots in search engine popularity. Larry Page pitched a sale of Google to Excite CEO George Bell. Page wanted 750,001% of Excite to let go of his fledgling search engine. At the time, Bell considered the offer competitive except for one detail. Page wanted Excite to ditch its search engine technology and adopt Google's system. Bell declined the offer and threw himself into internet lore. In 2022, most people don't know the name Excite, but everyone knows and uses Google. The company is now worth over $300 billion, and now you know.


just how in sync did you feel early on in this one yeah yeah I felt good I felt like I had every single pitch working we're using all four really well to every different part of the plate you know I felt good I felt good the whole time me and Higgy were rolling pretty well and the offense spotted us a lead so it allowed us to be pretty aggressive there for a few innings and keep the pitch count in check when you do get a lead like that just is it how much of a luxury is it to be able to be aggressive and not to have to be so fine and worry about every single pitch yeah yeah I mean it allows you to have an inning like the sixth where the mistakes can err on the side of aggression and attacking guys as opposed to like falling behind guys and walking guys and stuff like that so you know that six-thinning kind of got off the rails a little bit but at the same time when you have a lead like that I mean I'll take living on the aggressive side and making them beat us by putting the ball in play over you know the alternative any day you seem just about as frustrated as we've ever seen you when you came out in that sixth inning and and sat in the dugout what was it about the way things transpired that frustrated you so much yeah it was probably just because I felt so good tonight and I thought the first five and a third innings went so well you know I thought tonight was a night where I probably could have pitched into the eighth you know I felt that that kind of way tonight so to have it end at five and a third was pretty frustrating you know but after having some time to reflect and stuff I went back and watch the pitches and you know there's not really much I would change especially with the six-run lead so it is what it is go next to Greg Joyce James they just checking what when you caught that pop-up in the sixth where you find physically from that or did that take any kind of a toll yeah I know I was fine it got a little awkward just because I saw it at the corner of my eye Tyler Wade sprint that mean we all know he can run extremely fast so I didn't really feel like having him kind of take my legs out so I dove a little bit but yeah I mean that was a pretty easy play and something I expect to make every time anyone else for James and Brian Clark go ahead and James and just what did you notice over these seven games that the team as a whole was doing really well there's a lot of things I feel like every night it kind of changes a little bit there's nights where the starting pitching has been extremely dominant there's nights where the bullpen comes in and picks us up there's nights where the offense just scratches and claws and gets us enough and then there's nights like tonight where they put you know get the starter out of the game early and put up a big crooked number so I actually I don't know I feel like it's been a lot of different things and I I think that's a sign of a good team is when you can win in a bunch of different ways like we don't have to blow you out to win we can win the close games we can also slug we can put up runs we can have the starting pitching the bullpen and the defense so I feel like it's kind of just been a little bit of a mix and match


Now, we are going to talk about water logging. What are the problems? See, when the land gets degraded, it can get degraded because of the soil salinity, salt is added to the system so that the salt intake by the plant is reduced and nutrient intake is reduced and crop production goes into vary. Another problem is the water logging. Water logging is nothing but it is a drainage problem, so whatever the water is not getting moved out from the root zone fast enough so that it is able to intake better facilities. Now, water logging is the water table which raises up that means the water which is being percolated is not moving to the source further down or on the sideways or one situation. Another situation water which is gets percolated elsewhere they come try to come and then come out of the root zone areas so causing a circulation problem so that is what the water logging problems. And it is normally happens in the alluvial areas in the close to the alluvial areas whether the inflow from the river or inflow from the adjoining areas they try to make the water table to the closest thing. So, other reasons are that over irrigation that means before the water goes down the gout out of the root zone areas you irrigate it or inadequate drainages or management of poor irrigation management whatever the drainage which is happening natural drainages subsurface natural drainages which happens that is blocked due to so many construction activities in the nearby areas and or the water is happening is if it is a land which is a bubble type of geomorphology where the land is locked and water does not have any outlet to move away. These are all the major crosses for the water logging problems. And what are the effects which can happen on this is you may have to delay cultivation operations as well as aquatic weeds are likely to grow in those areas. If the aquatic weeds then that will be fertilizer sharing issues they come into picture instead of crops the weeds they eat away the consumed majority of the fertilizers and either or it could be a plants will be leading to diseased crops some physiological changes could happen and decay of roots can happen. And if it is in the cash crops and only few crops could come up and the rest of it is gets stuck in the system and low yield which is the major cause for the irrigation or cultivation for activities or agriculture activities. Now having seen the what are the different logging water logging conditions causes and effects on the crops now there are causes it could be a natural crosses. It could be a human induced crosses or it could be a permanent activity. It could be a when during the rainfall days you must be seeing then what water logging water accumulations they take place and when it is immediately after the rainfall this type of water logging moves away to other places. So that is what we call it as a temporary or it is a water logging which is a permanent like what you call all along the coastal area you have marshy land. So that is what the permanent water logging areas or it could be the sources of water which causes this thing could be either it could be a rain fed rain fed sources direct rainfall there is no much of drainages. So again water logs or excess irrigation in this area that causes the problem. Many of them happens on a agriculture land or it could be in a other utility land built up areas which happens this type of water logging. It is not only meant only for the agriculture land or it can happen in the built up areas also there will be a water logging will be there and there will be a dampness in the building and there will be other related issues will come up in the urban areas because it is manipulated the surface is manipulated very heavily in the urban areas whereas it is minimum in the agriculture except for ploughing conditions. Now what are the multiple stresses which can happen because of that is one thing is non availability of water that is what the drought we call it then the soil salinity which has gets improved or it could be a water salinity water salinity is nothing but ground water salinity or the water the surface water passes through the area where the salt content in the surfaces can get dissolved and then move up or it could be a water logging water logging means the water does not have any place to move around drainage is poor so or that could be some element concentration is possible. So these are all the different stresses and the reasons for the different kind of stresses which can happen to the crops. So how these things could be used is make a baseline information and then try to get all those areas marked and then do a practices and how best it is removed after few years of time that is how the GIS could be brought into picture even a smaller area or on a larger area because these water movement and salinity water logging and all those things they are of regional nature not of a smaller scale activities. So that is what we wanted to show that agriculture practices are affected by drought water logging salinity concentration of a particular minerals. So these are all the probable things which can affect a agriculture crops that needs not only the observations monitoring and updation of the information is possible but so that we will be able to take a better management practices to recline the degraded agriculture land back into the system. Thank you.


So, we have been looking at static lift generation and we have been looking at its variation with various parameters. So, there is one section still remaining from that portion. There is one section still remaining from that portion which is basically the calculation of the parameters with change in altitude and also pressure altitude. But I thought it was becoming too numerical. So, I wanted to take a break. Therefore, today we will take up a topic which is supposed to be have taken next time but I am just switching it just to allow a little bit of variety. So, today we look at the properties of material of the envelope. So, as you all know envelope is the most important component of an LTA system and therefore, it is very important for us to understand its properties. Now, some properties of an envelope are desirable because they help in the system meeting its professed requirements. Not in order of any specific preference, I would like to list down the various properties which are desirable in the material of an LTA envelope. High strength because especially in a non-rigid airship which is the most common airship being used nowadays, the entire load coming on the envelope is taken by the envelope itself. There is no internal structure. So, all the shear loading which will come on the envelope everything has to be sustained by the material itself and hence high strength is important. But this strength is measured in a very interesting fashion. There are two directions of a fabric. There is a warp direction and then there is a weft direction. We will see that in more detail. So, strength is determined in both directions and it need not be the same. So, one should keep in mind that in general the LTA materials are an isotropic. They are not isotropic. In fact, they are isotropic. They will have material properties different in different directions. Second thing is we would like this material to be able to take the load but at the least possible self-weight because the self-weight is going to deduct from the gross lift to give us the net lift. So, therefore, if there is a fabric which is very good in taking the load but if it is very heavy then it is of not much use in LTA systems. So, the challenge is to make it load carrying but with low self-weight. A major task of the envelope is to contain the lighter than air gas inside. So, permeability of gas is very important. Permeability is needed to be good for either hydrogen or helium or both depending on which gas is planned to be used. So, for passenger carrying airships we know that as per the legal requirements we cannot use hydrogen. So, the next best gas is helium. So, in those cases helium permeability is the prime requirement but in remotely controlled airships or in unmanned aerostats are mostly unmanned. There you might deploy them with hydrogen or helium depending on the application. So, you need to have good permeability for both these gases. The next required property is creep. The creep resistance should be high and it should be able to withstand creep. Now what is meant by creep? Can somebody help me? Does anybody have any definition for creep? Have you heard about creep in metals? See, changing the length of the specimen upon the relative length is the strain. Yes, exactly. It is the failure of a material due to prolonged exposure to loading. So, in an LTA system you deploy it for weeks or months. So, it might be possible that there is a fabric which can take a lot of load but only for a small amount of time. When the same material is exposed to one month of loading maybe it starts deforming faster. So, this is creep and definitely we want a material to have very low creep propagation or very high creep resistance. Obviously, high strength to weight ratio and low weight are related to each other in some ways but low weight is a direct parameter. So, obviously, a fabric of low weight is of no use if it does not meet the requirements if it does not contain the gas if it cannot take the load. But given a condition low weight is another requirement. High tier strength is also important because this system can be subjected to some amount of local loading because of which it might tear. And when it tears, the speed at which the tear propagates is going to be the time available between an incident and a disaster. So, many of times like in parachutes for example, we use nylon fabric for all these properties and we have what is called as the ripstop nylon. So, there are woven structures, you can say square fabrics which are enclosed. So, the tear will start at some place and it will end at the nearest rip cord and it will not easily propagate further. So similarly, it is important that the fabric that we use should not have very easy propensity to tear after the load is applied. So, for that special testing is used in LTA fabrics to determine the tear strength. Another property is good adhesiveness. In modern fabrics, the method of joining the envelope material happens to be adhesives. The Japanese have made tremendous progress in this area and they have come up with special silicon adhesives which are extremely good, extremely long lasting and they give very good strength. But certain materials may not be easy to join by adhesives. So, if we are going to use adhesives and which is going to be the case in most of the applications in the future at least, it is important that the nature of the fabric should be such that it allows it to be stuck to other fabrics. When you expose an LTA system for a long time in the atmosphere, there will be ultraviolet radiation of the ambient from the sun and the fabric will break down over a period of time. So therefore, either we have to provide coating on top of the envelope to have very good ultraviolet resistivity or the fabric itself should consist of materials which have inherently high resistance to ultraviolet degradation. So, environmental degradation could also come because of water, it can come because of snow. So, the fabric should be such. So, many materials are available which meet other requirements but they fail at this requirement. Similarly, there are many materials which are extremely good in other things but they fail in adhesiveness. It should have a good flexural and abrasion resistance. This system might rub against some obstacles. For example, if you deploy an aerostat, you might have a situation where it might start rubbing against some trees or some other manmade or natural objects. When you bring the aerostat down, there might be some kind of a rubbing between the envelope and some components of the winching and the mooring system. So, if it does not have good wear resistance, it will tear or it will create damage at that point. So, it is important that the surface of the fabric should be able to take little bit of beating. Then you will be surprised to know that even in ambient air, sometimes we have lot of particles which are suspended and these particles can start rubbing against the envelope and cause abrasion. So, it should have good abrasion resistance. Flexural resistance is required because we may have to bring it down, deflate, fold, transport, again inflate. So, if the fabric cannot take many folding and unfolding cycles, then after using for 2-3 times, it might start to rub and cracks. So, it is important to have flexural and abrasion resistance. So, these are just to show you the full list for those who came in late. This is the list of desirable properties of envelope material and we are still working for a fabric which meets all these requirements perfectly. So, the quest for a good LTA envelope is not over. Nobody can say that yes, we have achieved all these qualities. Large number of recess projects are going on all over the world. Many companies are developing new fabrics to meet some requirement better than the ones available previously. We also have some good, very good papers written by experts in this area which also I will load. Please understand, this is the postgraduate elective course. So, not everything will be covered in the class. Not everything can be covered in the class. Lot of self-reading is expected. So, do not think that the questions or the expectations are only to understand what you heard and memorize what is there in the notes. You have to go beyond that. So, a large amount of reading is expected to be done by you. I will help you by uploading on model the required literature or pointing out where the material is available. But you need to do some self-reading also.


My name is Neil Stewart. I'm from LSE in London. I'm here to talk to you about a project we undertook, which is called Charles Booth's London. I'm just waiting to make sure that the Wi-Fi is working. I've given it the snazzy subtitle Imagining the Victorian Metropolis. I hope I can demonstrate how we did try to imagine the Victorian Metropolis. I'm going to include a live demo later, assuming I can get the Wi-Fi to work. If that doesn't happen, then we all get to leave early, so that's good. If you'd like to have a look at the site while I speak, I'd encourage you to do so. You can search for Charles Booth's London. It should be the top hit on Google. Other search engines are available. Or you can go to booth.lse.ac.uk and have a look at the site while I talk. I should also say I'm going to try and keep the time because I am conscious it's the final slot in the graveyard shift.  Looks like we now have Wi-Fi, so on with the show. Who here has some knowledge of Charles Booth and Booth's projects in his poverty maps? That's good. I'm seeing maybe half of the people in the audience have got some knowledge of him. For those of you who don't, Charles Booth was a Victorian businessman, philanthropist and social reformer. I didn't write down when he was alive, but it was between 1840 and 1916, I want to say. Roughly around that. He was quintessential Victorian and latterly Edwardian. Booth's project was to try to understand the extent of poverty in Victorian London. Booth went into his project disbelieving that poverty was as prevalent as many of the thinkers of the day proposed, particularly the Fabian early socialists. His research showed that it was much higher. Some 30% of people in a city of 6 million lived below the poverty line. The poverty line was actually a phrase that Booth himself coined to express the points at which someone can be considered to be living in poverty. That's nearly 2 million people. It was what we would now consider to be a mammoth research project involving a very large team of people. The project lasted 15 years. One of those people was Beatrice Webb, Beatrice Potter, Ney Beatrice Potter, who went on, amongst other things, to form the LSE. It's another reason why it's an important project for us at LSE. Booth's findings were handed down to us by way of what we would now consider to be excellent Victorian research data management as a number of things. I'll just run through what those things were. There was the publication Life and Labour of the People in London, which ran to four editions between 1889 and 1903. The final edition in 1903 was 17 volumes and over 4,000 pages of findings. There were the poverty maps themselves. You can see an example of one here. I'll show you more of that a bit later on. There were 12 individual maps, each one representing a particular area of London. There were the notebooks, including the famous police notebooks, which were the writings of his research team as they went around London, literally walked the streets of London and recorded their findings. There are around 450 of those, so quite a few. That full archive is held at LSE Library. As you can probably guess, it's considered to be something of a jewel in the crown, not just LSE Library, but LSE more generally. What did we have? First of all, we had one, as well as the hard copy archive, we had one very old website, which is called Charles Booth's online archive. You can see here, we were very pleased and honoured to win the Multimedia and Web category Silip Emerald Public Relations and Publicity Awards 2002. This website was from 2000-2001, which in terms of the web is positively archaic. That website did a pretty good job of displaying the archival materials. The maps didn't really do them justice at all. To use a bit of a euphemism, it had become challenging to manage. Another way of putting that is that we couldn't really do anything with it at all, because the institutional memory about how to update this particular site had been lost, so it was in some senses a dead website. Although it's worth mentioning that it did continue to get a lot of traffic, so three or four hundred user sessions per day, so there was obviously demand for information about Booth and the Booth maps and so on. We also had an old-ish website, which was called Phone Booth, a colleague Peter Spring. I always mention Peter because he had the genius idea of naming it Phone Booth and you look at it on your phone. We got hits to the site from people looking for information about the history of London Phone Booth, so who knew that people were interested in that, but there we go. This had modern mapping application functionality, so it had kind of slippy maps. We geo-located the notebooks against areas of the map, but the site was experimental and prototypical. It was essentially in a sort of permanent public beta form, so we knew we needed to do more with that site as well, so we had these two different websites. What we knew we needed to do was to bring together the functionality of the old websites, but also we had an opportunity in that in 2016 it was the 100th anniversary of Booth's death, which is slightly morbid, but it seemed like a good hook to hang our hat on, so to speak. To commemorate that 100th anniversary, there was an exhibition in the library which was curated by my colleague Indi, who's in the audience over there. There was a research festival around the contemporary resonance of Booth's work, so all sorts of aspects to that, so information visualisation, the way in which we think about poverty in the city, social history, et cetera, et cetera. There's also a Booth family memorial event, so the many, many ancestors, what's the opposite of that? Many members of Booth's family came to LSE to commemorate his life, which was great, so there were about 50 of them, it was amazing. We actually, one very memorable moment was revealing the new version of the website, which I'll show you in a minute, and they actually gasped and clapped, so that was quite something. To do this work, we had a cross-library team, we had a project manager, which was me, we had a UX specialist, a web editor, a metadata specialist, and anarchist, Indi, who I've already mentioned who's in the audience. We divided our work between outsourced web design, and that was our web development partners, Mickey and Mallory, who are based just across the river in Manchester proper. But we did the conceptualisation, the technical development, copywriting, project management and so on in-house, so that's something that we took on ourselves to do. We did user experience and audience analysis, followed by the web and technical development, so we tried to work out, we tried to understand who our audiences actually were, and there's obviously a site like this has got obvious academic interests, so those people are interested in social history, the history of London, but we also found out by doing this research that there was considerable interest for people who were interested in family history and genealogy, so perhaps your great-great-grandfather or grandmother lived in Victorian London, you could actually have a look at the archives and the maps to perhaps get an understanding of what their life might have been like. So the project was started in May 2016, and we actually completed it at the end of November 2016, so almost exactly a year ago. The screenshots here give an idea of what we tried to do with an iterative design process, so there's probably not super clear, but that plus that sort of equals that, and we turned that final design, Frankenstein's Booth website, because we got the kind of paper and scissors and glue out and clutched things together and get a design that we liked. Here is the site. We've obviously made an effort to use modern web design pre-sets. We've got colour scheme both based on the maps but also some of the LSE branding, so we've tried to make it look like an LSE website. We've got this primary architecture at the top here, so we can see maps, notebooks, highlights, learn more and about, and I'll take you through some of that as well. So have a look at the maps. We have a single stitch, so the 12 maps are stitched together into one single map, and we've georectified that map, which means that we've aligned it with a map, properly aligned it with a map of modern-day London. So if we zoom in a bit, I'll use where LSE is as our point of reference to begin with, which is just here. We've got a legend, which is the legend that Booth himself used, and I'm not sure how visible that is, but you can see the famous categorisation of poverty, and streets marked as black. Streets marked as black, such as this one here. Booth classified as lowest-class vicious semi-criminal, which is a very Victorian way of thinking about poverty, although it's worth noting there that Booth, the Victorian sense of vicious, was vice-prone as opposed to liable to lash out. We also overlaid the notebooks against the map. For example, if we click here, you can show notebooks, and we get these green dots, which is a bit tricky to decide what colour to use for those dots, because you don't want anything too garish, but you also don't want anything that gets lost in the colours of the maps. I'm not sure how well we did that, but there we go. If you click on one of those dots, you get to view the notebook entries themselves, and we can go through to that. This uses the triple IF viewer, which has been mentioned a few times already today, which is a standard method of displaying images on the web, archival material on the web. It allows you to do all this great full screen, and we can zoom here as well, I think, just by clicking. You can see, you might be able to read that. At the top there, we've got Walk with Police Constable E-Tate round the district bounded to the north by New Oxford Street and High Hobe and on the east by the city boundary, which runs through Staples Inn and continues. George Duckworth, who's the researcher in question, has even drawn a little map to orientate himself. For those of you who know London, Lincolnton Fields is here, so the modern day LSE is sort of here. It gives you a real sense of the Victorian city, hopefully. It's also possible to access, if we go into the notebooks area proper, it's also possible to access the map via notebooks. If we run a quick search and look down a bit. Here's an example of something that's come up with High Hobe. This is actually a really nice page. Again, it's George Duckworth, and he's saying he's at the special licensing session of the Hobe and something. Justice is of the Peace at the Hobe Inn Hall. Once again, he's drawn a little diagram of the layout of this session of the Justice of the Peace. Again, hopefully very evocative of late 19th century London. If I go out of there. You can see where this is geolocated. Apparently this meeting happened just south of Oxford Street. We did think quite a lot about those interactions. Get my notes together. Some of that was quite tricky, just like me looking through my notes, which I shouldn't have allowed to get out of order, sorry. That interaction design, you might have noticed just when I was demoing this, we had some examples of non-digitised notebooks that were being geolocated against the map because we hadn't yet digitised the full archive. So we needed a way of telling people that, sorry, you can't see this. We did think about flashy pop-ups and all that sort of thing. In the end, we've just linked through to something saying, I'm sorry, we haven't digitised all of the notebooks, but hopefully we'll get round to that soon. Another challenge for us was thinking about the way in which we deal with discrepancies between modern-day and Victorian London. So to give you an example of that, it might be a bit tricky to see, but just here, there's a street called Veer Street. So you'd think in theory you'd be able to search for Veer Street and you'd think to yourself, oh great, there's Veer Street, I'll go to that and find it on the map. It's actually taking you elsewhere though, so it's taking you to Veer Street just off Oxford Street. Now I forgot to mention the opacity slider, so we're now transforming the map into modern-day London. The reason that we were able to locate Victorian Veer Street is because there's a modern-day version of Veer Street which continues to exist and the search is done on modern-day, the modern-day map of London as opposed to the Victorian, the poverty map. So we're giving, you know, we could be giving false positives there. And as part of the research we did into this problem, so that Veer Street, and you can see, if I zoom in a little bit, the Veer Street which is here is, it's no longer with us so it's gone and you can see there, it's been overlained by Kingsway and the Aldwych. That was actually a slum clearance which happened at the beginning of the 20th century. So the analysis that we did showed that some 50% of the streets of London had changed since Booth's time as a result of redevelopment. There's the Blitz, of course, which we've heard about a little bit in a previous session, I think. So how do we deal with this? I'll talk a little bit about how we might deal with that at the end of the presentation. So to go back into PowerPoints. So hopefully that gives you a sense of the site itself and some of the challenges we were thinking about. And just some brief notes on technology there. So we used OpenStreetMap and the OS names API to allow that searching that I showed you to take place. AAAF and Universal Viewer I've already talked about. We used Elasticsearch to index the metadata of the notebooks. If you're interested in this technical stuff, there's a full write-up by our developer Tom Carter which you can see at that URL. I'll tweet that out after the session because it's a horrible URL. So what does the future holds? So I've mentioned this issue with mapping and the fact that you can very easily, obviously, search the modern-day map of London but it can be difficult, it can be challenging to search the Victorian map. So we're thinking about how we address that. One way of doing that would be to create a gazeteer of Victorian London which would be to record every street in the Victorian city on the Victorian poverty maps and then give those vector coordinates to say where they are. The problem with doing that is that if one of us is a group of us in LSE library or if we outsource that or whatever, we estimate that it would take over a thousand hours to do. So a great deal of very painstaking and quite frankly quite tedious work for a single person to do. There would be other benefits to that though. We could release that information as an open data set so if other people wanted to recreate a map of Victorian London, they would be free to do so using that information. You could do nifty things presumably if we also got classifications of the level of poverty for each of those streets so you could have functionality on the website so you could select only streets that are deemed to be vicious and have those highlighted on the map. So there's a great deal of potential for this. We thought about options with crowd sourcing perhaps. Crowd sourcing would probably take a day or two to glean this information from citizen scientists. One avenue of possibility we're exploring is with the Institute of Historical Research's Layers of London projects. Layers of London, I'd encourage you to have a look at that if you're not familiar with it because they're doing some things that are quite similar to what we've done with Charles B's London except they're using multiple different maps, multiple different historical maps of London and then overlaying those on modern-day maps of the capital. I put there digitisation of the rest of the archives so we've actually done that. So we've now got digitised versions of all of the notebooks, give or take a few, which were very challenging to digitise. So at some point we'll need to add those to the site so we've got essentially the full-booth archive available via Charles Booth's London. One thing I didn't mention in my demo was highlights articles and I'm not going to do that now but highlights articles are a way, we've tried to give a way into the archive by providing narratives about particular thematic interests of the archives. So we had one on drink and drugs, one on migration and immigration and one on prostitution, that was the third one, wasn't it? So slightly salacious but we thought they'd be a way of giving people an in to the maps we thought sort of speak for themselves but the archive can be an intimidating thing to try and dive into so we wanted to give people a way in, an easy way in. We'd like to do more of that because we think they've been successful so we'd like to look at that again. Very briefly about user experience testing we did try and do UX work when we were doing in the fairly limited time we had with the project, we're yet to take it out to our public and see what they think and then act upon what they think about the site. So things, there's obviously things that we could be doing better but we need help in doing that and we need to talk to our users to understand that better. Thank you very much, there's that URL again. There's actually an LSE, there's a blog that LSE runs called the impact of social science so myself and my colleague Andy have written a post for that which will be coming out later in the week I couldn't persuade them to make it live for this talk unfortunately but there we go. So if you want to know more or want to read about this that's a good place to go as well as Tom Carter's technical writer. I think that's everything I had to say. Thank you.


Welcome back everybody. Happy Monday. And hopefully everybody's all back and ready to go. Hopefully we saw the Super Bowl yesterday. We're pretty fun. It was pretty boring actually, but it was really fun going into the end. I'm so upset that I almost got my box. It was pretty, pretty hectic. But you know what, you know, you know it was even better than what happened on the Super Bowl? BMR this morning. My God, look at this stock. We start, I mean, this was a perfect set. You don't really see this early in the morning on a Monday. But look what happened. We had this big pop around seven o'clock this morning. I'm gonna just back up here and show you what we got going on here. Big pop here this morning. And sure enough, it was hovering, hovering, hovering. And right when program trading kicks in right around 8 a.m. and at 8.30, right there at that 8.30. Look at this. If you came late at this time and saw this thing, it really didn't go anywhere from, you know, up until like seven o'clock. 3.80 to almost 5.80? I don't know about you, $2, I'm a thousand shares, a $2,000 profit. It's a half a million dollar salary right there. Like why would no one would even consider it? I know some of you guys traded it. A lot of you guys did pretty well this morning. I know we got some new trial members in there. We also got a bunch of people watching on social media too that I hear also. And this is what you guys missed. This is what we do here at Cybertree University. I mean, we'll look at some iceberg orders on it. Stock had some great ones on it. Starting to get a pretty volatile light right now. We'll come back and we'll check back at it. But let's go over some of the things that we traded last week because there were some really, really nice stocks that did unbelievable for some of you who are not here. I want to start off with this really big stock, H-O-L-O. This was the biggest winner of last week, okay? Here's a stock, if you look at it, started right around, what is that, $3? Went to $18. And then the very next day, the stock went all the way up to $41. This is probably, I would say, I would guess, I mean, Josh would probably agree with me. This is probably the biggest mover we have for 2024 so far. Percentage-wise, as dollar amount. So this stock did really, really well for some of you that are just logging in. If you don't believe us that we're in it, like I said, you could subscribe to our channel. You could be in our YouTube channel. You could look at our X channel. You could look at our TikTok channel. I sent out emails. I got some really good feedback from some of you. And then there's some of you that say, you know, Faust, I can't believe I missed it. That's okay. Don't worry about it. This stock is a super extreme, big, big runner up, but they're every day. So let's talk about some other ones that also did pretty well too. L-U-N-R, and I'm gonna throw this back on the watch list, L-A, this one right here. L-U-N-R, and we're gonna come back and we're gonna check level four and we'll see what with iceberg waters on it. But she's up again, about 21%. She was up pretty nicely from on Friday. She started around $3.80, went to a price around four, and then she just pushed really nicely over the course of the day. You could see on a long-term chart, $3 stock up to about $8. That one did pretty well. I-N-B-S was absolutely gorgeous just on Friday too. This stock took its time and it went from that $3.50 all the way to $6, all the way to $11. I mean, that was a unbelievable run-up also. That was probably the best run-up for Friday, the I-N-B-S. Now, yeah, it's down right now, it's done. But remember, I'm gonna show you this, cyber clock everybody, best times and worst times to trade. This is why it's important everybody needs one of those, all right? Anyway, that's why we do a lot of our commentary first hour and the last hour, and then obviously in the middle of the day, but good, good mover. Couple of the ones I do wanna cover too that did pretty well too, CLSK, another nice little push, a 12 to 14. PLTR was a really nice stock the last couple of days. She started going back down again on Friday, but even if you look here on the long-term chart, over last week, she had this nice gap up on earnings, went from 20, 08 to 25, great, great, great stock. Couple of the ones, some of the more expensive ones. This stock, I don't know what's going on, but I wanna sell it, and I haven't sold it yet, I still have it. I mean, almost 19,000 on that stock on 100 shares. I wanna sell it, I'm like, please give me a reason to get out of it and it just won't go down every day. And I thought after seeing it even on Friday, it was hovering there and I'm like, you know what, I have a good position on it. I know a lot of you guys here also were in it. I talked about this before. We were watching the stock when they came out with that announcement when it was at 333 and they said they were gonna beat earnings and that thing went to 428. I sold it, bought it back. I sold it, but I just, I don't know what the hell's going on with this SMCI. And I guess it's following pretty closely with NVIDIA because NVIDIA has not stopped. So as much as some of us miss NVIDIA, you could have jumped on that SMCI. Another big runner that's been doing phenomenal as Eli Lilly and I'm just waiting for the make announcement that gonna probably do a stock split because Nuvo also did the stock split. That was another swing trade that we've been doing also and they've been great, great options placed too.  I don't know, they're too cheap. It's not my style. Okay, listen, we do trade some of the ones and here they are and they've done pretty well. So you know what, we just broke 5,000 on ESMP, which is, you know, it was like a big celebration that was going on for the first time. The Dow's been doing great on certain ones. But listen, don't worry about it. The stock market is not going out of business. I always give everybody a guarantee.  You will always pay taxes and the stock market's not going out of business. Those are my three things I always tell my guarantees to everybody. So anyway, let's go back and listen, let's see what else was moving this morning because obviously we had a couple of really good moves. So let me just move this and bring this to my level three. We're gonna go to my book viewer default so we can watch some of the stocks here and see what's going on. Now I know some of you have been asking me for my template. I did send some emails today if you did not get my template or if you're on social media, if you guys want to get a where to find it, let's put that email out there for you for everyone to see. And then also, like I said, if you watch it on social media, make sure you subscribe to the channel, give us a thumbs up and make sure you ring that bell to get those alerts, okay, whenever we going online. Very, very important to all of you. Now regarding about what's moving this morning, we have the BMR stock was moving gorgeous. It's backing off a little bit. There was a little bit of an iceberg order around $6. You can see it right here. You got 38,000, 38 orders out there makes 6,000. It's not a lot. Stock is now starting to get out of the untradable. Now listen, market's not open. This thing could, could this be like another halo? You know that it could, it could. Listen, market's not over, but you know, we're definitely putting this on our watch list, BMR, you know, and once again, some people don't have access to pre-market. They don't know what direct access is. That's why you got to subscribe to the channel. Or if you're on, if you're watching on social media right now, just take your phone, scan that QR code on a top left hand corner and we'll let you in. All right, join us for a whole week. BMR on the watch list. Next one that's on the watch list. I saw this one right here, this stock right here and it's got two big iceberg orders. It's kind of flat. It's holding here at $2, big buyer out there, M-G-I-H. You could see it right there at two bucks.  I could see it's on, on another ECN for a little bit more than that. But we'll put, you know, listen, we have stocks like this and they call flat and then out of nowhere, they go from the B list to the A list. All right, DHAI. Now this stock is from, is an IPO from what it looks like. So I want, I'm not interested in this one right here. Wish on the other hand is looking pretty good. Okay, Wish is in a really, really nice little stock. It's got a little bit of, it's, let me bring it up over here. Wish, moving really nice in the morning. Stock start around $5.50 or a random seven that's in an hour. You could see right here, we got a couple of nice iceberg orders around our $8. We got this other one here at seven for about 19 orders. So I see there's a pretty big buy rate at 750. So right here at 10,000, you see it right there? So those are your iceberg orders on Wish. Remember, gotta have a game plan where those orders are. Next on that list, we see anything else, 24%, stocks aren't really going anywhere.  Vime's a little light right now. I got a big iceberg order, I need DGX for 10,000. GNSS, yeah, not really that much on NASDAQ. Looks a little bit more than that. I don't like the chart really quick and long-term chart on the bottom right hand side, looks like we're getting close to that big resistance at two bucks. So maybe that one, put this on the B list. I'm not really super sold on it. Shockingly, there's a lot of stocks for a Monday that are already above 20%, a lot of them. CAUD, stock took a really big hit from the beginning of the year.  Buying about a half a million already, I like that. CAUD, yeah, we got a 10,000 share buyer at a buck right there, no really big sellers out there. I'll put this on the B list. CAUD, call it Claudio. LUNR, stocks on a downtrend, two million shares. This one, 400,000, decent spread, starting to make a little bit move. BTAI, this one took a little bit of a hit, came back down, not really sold on that one. This stock is getting crushed right here. So this stock, ANTX, getting hammered. But, do we get a dead cat bounce on it?  We all know about pharmaceutical stocks, right? And I'm not gonna say it. You know the answer to that one. H-kit's starting to come back down. We know why it's on the losers list. New York Stock has changed. Any big gainers out there? Nope, not really. Big locks taking a big hit right here. And now we'll get a couple of, and what happened? And that pretty much does it. Anything over here that I see? Tesla, I saw a lot of news on that this morning. Talking about this, NVIDIA, Intel, look at all the fabulous sevens. Yeah, pretty much Mara, take a little bit of a hit today. After going up, making a huge rally. So those two stocks, listen, we got a pretty decent list. I don't like to get too cocky and have too much on my list on a Friday. We got one, two, three, four, five stocks. Not bad. We'll go out there. Draft King is tanking. DKNG, why do you think it would be tanking? Okay. Has anything to do with the Super Bowl yesterday? DKNG, DKNG, why can't I not type?  So listen, football's over. You're not gonna get really any more betting going on in Draft King's. Probably a good opportunity to look short, right? Way to go, Johnny, that one too. All right, anyone on social media, anyone out there looking at some stocks that you wanna bring up, anything I missed? I'll definitely put Draft King on that list. DKNG. All right, let's get ready for the market open up. We got about 15 minutes. Once again, if you're watching on social media, if you wanna come and join our trading room, or if you're watching a recording, take your phone, scan that QR code, or you got the little chat on the right-hand side. We're live every morning at 9 a.m. and at 2.30, but we'll be here all day from 7.30 up until 4 o'clock, 4.30 going into close.  I know we have a lot of new trial members starting here. Listen, for all you new trial members, I know you're first thing in the think, this is moving pretty fast. There are fast stocks and there are slow stocks. Just sit back and watch and watch how the traders think for themselves and watch how we give them the ideas when it comes to trading, all right? So just, and make sure you talk to education advisor. Good luck, everybody. Let's have a fun week. Super Bowl's over. Now it's this prime season, all right? Good luck, everyone. Happy trading.