Oh, there's this massive ship. It's massive. It's one of these super container ships that has run aground in the Suez Canal. And is, I just remember an Israeli military intelligence war story I could tell you. Do you want to hear an Israeli military military, I wonder if I'd re-violating any secrecy laws in Israel if I told you the story about running aground. That could be interesting.  I'm trying to think of all the details of the story, but yeah, running aground, I just, the Suez Canal running aground right now just, it just flashed in front of me. This experience I had in the Israeli army. Okay, I'll tell you that story after I tell you about, particularly if somebody puts in a good amount on the super chat, I definitely will tell you. But let me see if I, there you go, Ryan's put in 20 American dollars in for that. So I'll tell you, but let me start with the Suez Canal. Massive ship, running aground the Suez Canal.  I mean, it is the major link between Asia, China, India, Singapore, Taiwan, South Korea, all the industrial nations of Asia and Europe, basically all the imports from China and from all those other Asian countries coming to Europe go through the Suez Canal. It's so much cheaper than going around the Horn of Africa. And this is why it was built because it's a massive shortcut to allow trade between Europe and Asia, which is a massive benefit to Europe and Asia.  I don't know how much trade goes through the Suez Canal that comes to the United States because I think most of it goes through the Pacific to either San Francisco or Los Angeles or through the Panama Canal to the East Coast. I don't know what the numbers are, but I assume some of the trade goes through the Suez Canal to the United States. This is a massive disruption. But think about it. Who is responsible for the Suez Canal? Who maintains it? Who maintains its depth, its widths? Who maintains the pilot boats? These massive ships through the canal. Who maintains the functioning of one of the most, maybe the most important, narrow shipping lane in the world, in the entire world? Now you say Egyptians, but who do these Egyptians actually work for? Well, the Egyptian government does. Scott says the UK, Audrey says the Andrew says the UK and neither of those are true. It's the Egyptian government. Now I don't know how many of you know the story of the Suez Canal, but the Suez Canal was dug by the British and the French. It was dug by private corporations. I think, I don't have the whole history in front of me, but late 19th century, early 20th century, when Egypt was under basically British control, call it. And it was a joint French-British project, basically because it was massive, massive, really important for the British and the French to increase trade between Europe and Asia. So this is an 18th century project built privately by French and British businesses. And indeed, those French and British businesses ran the Suez Canal. They owned the Suez Canal. They took revenue out of the Suez Canal, maintained the waterway, made sure it was deep enough, made sure it was wide enough through 1956. And then in 1956, a military dictator of Egypt, Nasser, Nasser, N-A-S-A-A-R, something like that, right? Nasser nationalized the Suez Canal. He just stole it from British and French, legit corporations, businesses. The Suez Canal was private. Now, it wasn't Anthony Eden who screwed it up because Anthony Eden, together with, I don't know who was president of France at the time, maybe it was Charles de Gaulle, actually sent troops. They parachuted troops onto the Suez Canal. They occupied both sides of the Suez Canal, drove back the Egyptian military, and basically declared that they were gonna defend the private property of French and British corporations to this vital, vital national interests of both France and England. Israel at the same time, in coordination with the French and the British, invaded the Sinai, which had been a hornet's nest of terrorism supported and supplied by the Egyptians that were crossing over the border in the negative in the south of Israel and killing Americans. And Israel took the Sinai theirs at 1956. The Egyptians, sorry, the French and the British held the Suez Canal. And I can't remember how long they stayed there, but not very long. Why? Why did they leave? Who forced them to leave? Suddenly not the Egyptian military, which both Israel had whipped and the British and French had whipped. Who, I ask you on the super chat, who forced them to leave the Suez Canal, to hand it over to the Egyptian authorities, Israel to evacuate the Sinai desert, Jimbo, Nikolas, you are right. It was the United States of America, the Eisenhower administration. President Eisenhower. Oh my God, a Republican. How can this be true? I thought Republicans were pure good. Eisenhower forced them to retreat. By the way, this was a signal to Saudi Arabia and to Iran that they could go ahead and continue to nationalize American oil in those places and America would do nothing about it. So Eisenhower forced everybody to back away. Israel backed out of the Suez Canal, backed away from the Sinai desert with the agreement that the United Nations would occupy the Sinai desert and that the Egyptians were banned, outlawed, from bringing troops into the Sinai desert that could threaten Israel. That all changed, if you just a little bit of more of history, in 1967, in the spring of 1967, where Nasser, the same Nasser, ordered massive numbers of troops into the Sinai desert and massed them on the Israeli border. In spite of the barring by the Americans and by the United Nations, he told the UN to go take a hike. And that's what led to the 1967 war, which is known as the Six-Day War. Yeah, yeah, Eisenhower was the establishment. Who wasn't exactly the establishment? All right, all right.  So that was, okay, so my take on the Swiss Canal is it should be French and British. It should be in private hands. They should be a profit motive to keeping it running well. What was Eisenhower's rationale? Good question, Richard. Richard usually doesn't ask me good questions, but this is a good question. Yeah, I'm sorry if I'm insulting you, Richard, but sometimes you were pest on the chat. Why did Eisenhower support the withdrawal, or not support, basically encourage, twist the arm off the French and the British to retreat? I wonder if anybody knows. The official reason was, and I think this was the real reason, but this is what's called real politic. The reason was that Nasser was quoting the Soviet Union. And the United States was afraid that Egypt would become, come under the sway, under the influence of the Soviet Union. Nasser was considering building a mass of dam, the Anwar Dam, and was considering different companies, including American and Soviet companies, to build that dam. And Eisenhower figured that if he'd go in with Nasser on this one, Nasser would then not go in with the Soviets and become a friend of the United States. Guess what happened?   And Nasser became basically a satellite of the Soviet Union. It became a huge friend of the Soviet Union, the Soviets build the dam. They provided the Egyptians with massive quantities of weapons. Indeed, Egypt and the Soviet Union were buddy, buddy, right up to the early 1970s up until the Yom Kippur War in 1973, after which Egypt slowly started moving away and started moving towards the United States. And the United States started giving, and then after the peace agreement between Egypt and Israel, the United States started giving Egypt as many billions dollars a year as they do to Israel. And I find it interesting that people always complain about all the money Israel gets from the United States as far in aid. What about all the money Egypt gets, right? So, oh, I forgot about my army story. Anyway, that's why they did it. They did it as part of the Cold War, but it failed as most of the stuff they did during the Cold War is mostly their attempts to manipulate were all wrong and distorted. What we need today, what I call the new intellectual would be any man or woman who is willing to think. Meaning any man or woman who knows that man's life must be guided by reason, by the intellect, not by feelings, wishes, whims or mystic revelations. Any man or woman who values his life and who does not want to give in to today's cult of despair, cynicism and impotence and does not intend to give up the world to the dark ages and to the role of the collectivist growth. All right, before we go on, reminder, please like the show. We've got 163 live listeners right now, 30 likes. That should be at least 100. I figure at least 100 of you actually like the show. Maybe they're like 60 of the Matthews out there who hate it, but at least the people who are liking it, I wanna see a thumbs up, there you go. Start liking it, I wanna see that go to 100. All it takes is a click of a thing, whether you're looking at this. And you know the likes matter. It's not an issue of my ego. It's an issue of the algorithm. The more you like something, the more the algorithm likes it. So you know, and if you don't like the show, give it a thumbs down. Let's see your actual views being reflected in the likes. But if you like it, don't just sit there, help get the show promoted. Of course, you should also share. And you can support the show at yourunbrookshow.com slash support on Patreon or Subscribestar or locals and show your support for the work, for the value, hopefully you're receiving from this.  You'll know what shows are on, when they're on. You'll get notified, right? So yes, like, share, subscribe, support. Like, share, subscribe, support. There you go. Easy. Do one or all of those, please.


Dear students, in this module we shall discuss the resting membrane potential. Dear students, every non-excited or resting cell has a potential difference across its membrane. That is known as the resting membrane potential. The values of resting membrane potential vary in different types of cells. For example, the neurons which are not conducting any impulse have a typical minus 70 millivolt resting membrane potential. Now we shall have a view of the ions which are responsible to cause resting membrane potential. You know that plasma membrane is permeable to many species of ions. All these diffusible ions affect membrane potential across the membrane in proportion to their permeability. However, non-diffusible ions have no effect on resting membrane potential. The major ions which are involved in producing the resting membrane potential are the sodium, potassium and chloride ions. Now we shall discuss the equations which help to calculate the effect of a single ion or multiple ions. To calculate the effect of single ion on generating resting membrane potential, we use an equation that is called Nernst equation. While to calculate the effect of multiple ions on membrane potential, we use Gold's-Mann's equation. Both these equations apply equally to all excitable cells that is neurons and muscle cells. First we shall discuss the Nernst equation which is used to calculate the effect of single ion on the equilibrium potential of the membrane. According to Nernst equation, the equilibrium potential of a diffusible ion x depends on the nature log of the ratio of concentration of ion x on two sides of the membrane that is inside and outside the membrane. Apart from this, membrane potential gas constant R, absolute temperature i.e. T, valence of the ion z or fredic constant per B depends on it. So that we can read the Nernst equation as Ex i.e. equilibrium potential of diffusible ion x is equal to RT over Zf into log of concentration x inside the membrane over concentration of x outside the membrane. Now the Gold's-Mann equation is used to determine the effect of multiple ions on membrane potential. This equation is very similar to the Nernst equation. In this equation, we add the inside and outside concentrations of multiple ions and we get the equilibrium potential of multiple ions on the membrane. Dear students, now we shall discuss the role of ion channels in maintaining the resting membrane potential. Two types of ion channels i.e. the resting potassium selective channels and the voltage-gated sodium channels play major role in producing and maintaining the resting membrane potential. First we shall discuss the role of potassium selective channels. The potassium selective channels remain open in the resting membrane. They do not close. So the membrane is highly permeable to potassium ions. If the concentration of potassium ions changes on the outside of the cell, the cell membrane and its potential are highly sensitive. While the role of sodium channel is in this fact that they remain closed in the resting membrane. Due to this, the resting membrane remains relatively non-diffusable to sodium ions. If the concentration of sodium ions changes on the outside of the cell, then there is no effect on the membrane potential. Dear students, in addition to the effect of ions and ion channels, there is one other factor that has a major role in establishment of resting membrane potential and that phenomena is the active transport. Active transport moves ions against their concentration gradient. So it results in asymmetrical distribution of ions. The asymmetrical distribution of ions is the basis of resting membrane potential.


So, I'm going to talk about sustainability in a slightly different way now. I'm going to talk about the energy and resource consumption related to software and how to recognize energy-efficient software with Blower Angle ECO certification. I'd also like to announce that we now have a website that launched today, eco.kde.org. You're welcome to check it out. An overview of what I'm going to talk about. I'm going to first present the KDE ECO projects as well as the Blower Angle ECO label. And then I'm going to go through three steps to obtaining ECO certification for software and then wrap it up with looking to the future. If you'd like the slides, I have a lot of links that are in here. If you'd like them, you're welcome to download them from GitLab at invent.kde.org slash Joseph slash BE for FOSS. I will have that link again at the end of the slides. So to frame the conversation, I'm going to first present a discussion of software bloat from the Blower Angle award criteria which were released last year in January 2020. They write, the availability of more and more powerful hardware has resulted in software becoming more and more bloated from version to version so that more resources are required for only minimal or even no enhancement of the functionality. To illustrate that, here's a bar plot. The access is various software. I'm going to focus on the far left, two plots here, on the y-axis you're looking at the watt hours. And this is comparing in the green word processor one versus the blue word processor two. These are word processors running on the same hardware doing the exact same task. And the word processor one has about four times the energy consumption of word processor two. In some sense, you can talk about sustainability here as being the relative sustainability between the two word processors. Word processor one requires less resources and is therefore more sustainable. To compare this to other things like light bulbs that you might know, running a 50-watt light bulb for half an hour would be the equivalent to running word processor one for only seven hours in comparison to word processor two, which you get 27 hours of use time out of that for the exact same tasks. So this is to illustrate that there's an interdependency between software engineering and environmental issues here, resource consumption. It's not just the energy consumption, it's also software bloat can result in hardware becoming obsolescent, meaning that the perfectly functioning hardware, as Eric talked about earlier, can then become unusable because the demands get higher and higher with new versions of software. So KDE ECO is a new project. We're looking to explore the energy efficient software world in various ways. One is to push a conversation on the environmental impact of software. We want to be pioneers in developing energy efficient software. We want to promote tools for measuring energy efficiency, which I'm going to talk about today in terms of energy consumption labs. And we want to certify free and open source software with Blower Angle ECO certification. So in general, our goal is to put free software at the forefront of energy efficient software. And we have many channels to get involved. We're going to have two sprints coming up in the next few months, one in December to set up our community lab and one in January, February 2022 to start measuring free software. We have a mailing list and a matrix room to have conversations about the topic of energy efficient software, a forum channel, et cetera. And I will present a list of various ways to contact us at the end. So KDE ECO is made up of two projects. The first one is a community-driven project that's the FEAP project, the free and open source energy efficiency project. And the goal here is to collect energy consumption measurements and integrate these measurement tools into the development process. The Blower Angle for FOSS project, the project that I'm working for, is supporting FEAP by collecting summarizing and spreading information about ECO certification with Blower Angle and energy consumption measurements. And one of the main takeaway messages I want to have today in the talk is that free and open source software is particularly well positioned for obtaining a Blower Angle ECO label, as we'll see in the three steps to getting ECO certification. So what is Blower Angle? I imagine some of you might know it here. It's a German ECO label for environmentally friendly products. It's the oldest in the world since 1978. It's recognized by 92% of Germans and highly regarded internationally. And it's awarded to a variety of products. So most Germans, when you talk about Blower Angle, they immediately think of paper. That's probably the most common association. They award it to various products, including laundry detergents, cleaning services, as well as construction products, et cetera. And since last year, also for software. International perspectives on the Blower Angle. So 15% of the recipients are outside of Germany. So it's a German-based and German government backed ECO label. But the recipients are international. One of the nice things about this ECO label compared to other ECO labels is there are no requirements on where a product that receives the label can be marketed. Worldwide it's seen as a mark of quality or quality insurance. For example, if a company is building a building in another country, they might choose Blower Angle products because they will be more assured that it's environmentally friendly and of a higher quality. For companies, the award criteria of the Blower Angle are seen as indicators of the direction of the European Union market, as well as a potential guideline for optimizing their own products, whether or not they apply for the Blower Angle certification. And the Blower Angle is a member of the global ECO labeling network, which is an international cooperation to define common core criteria for ECO labels across borders. KDE is very interested in Blower Angle. We already have the KML email client and ocular PDF reader measured, and the application is ready to submit. The digital painting program Krita has been measured, and we need to prepare the application. In early 2022, we're going to have a measure-a-thon. You all are welcome to join. We're going to measure the text editor more, Kate, as well as the educational software G-Compre, and we're open to other projects, free and open source projects, if you're interested. Why are we interested in Blower Angle? Well, there are many benefits to it. One is it recognizes, when you receive the ECO label, it recognizes that you have high standards in environmentally friendly software design. It differentiates KDE and free software from the alternatives. It increases the appeal of adoption for users and institutions. For example, the green public procurement, and it shows transparency in the ecological footprint of the software. What is green public procurement? It's the process whereby public authorities seek to procure goods, services, and works with a reduced environmental impact throughout their life cycle, meaning that this might increase the adoption in institutions of software in official capacities. Now, let's get to what I'm calling the ABCs of the Blower Angle ECO label. There are three main categories in the award criteria. The award criteria now are only for local software. In future revisions, they want to include client-server software, as well as mobile phones, but at the moment it's only local software. The three main categories include resource and energy efficiency, similar to what we saw at the very beginning with the bar plots. How much does the software consume? The potential hardware operating life that's related to things like upcycling and other ways that software can influence the hardware life cycle, as well as user autonomy. So in a bit more detail, today we're going to focus mostly on the hardware performance and energy consumption part, but the other requirements include things, in particular under user autonomy, things like does it support, does the software support open standards, can you completely uninstall the software without leaving a trace other than the user generated data, is that documented somewhere, is the software open source, is there a continuity of support, can the user decide to install only the essential functions without all of the other functions that they may not need or want, and can the software run offline and can the user choose not to have advertising, which is also a drain on resources. So we're going to focus on this for right now. So three steps, measure, analyze, certify, measure energy consumption at, for example, a community lab. We're going to set one up in December in KDAB Berlin. Once you have the results and the data, you can use a tool like Oscar, the open source software consumption analysis in R to analyze the data and get a report, which can then be used for your application for a Blaua Engel, and then you can certify it by submitting a full report with the ABCs of the Blaua Engel criteria. What do you need for a lab? You need at least two computers and one power meter. The primary computer is the system under test. This is the computer that's going to be running the operating system that you choose with the application installed. And then it's going to be connected to a power meter as well as a data aggregator. Power meters, high powered power meters are expensive, and a KDE community manor, Kakaoza, has hacked a cheap power meter, cost about 10 euros compared to perhaps 300 plus for a more powerful power meter. The data, the sampling rate is lower. You get about five samples per second compared to a more high powered power meter where you get up to 1,000. But for 10 euros, you can do quite a bit with that already to get a sense of how much energy your software is consuming. You get a visualization of the lab setup. You have the system under test connected to a power meter, and the power meter and the system under test are both connected to the data aggregator. The system under test will also be collecting data, which then will then be used to analyze, which includes the performance data, the hardware performance. That includes things like the CPU, the memory, the disk, and network data. There's a free and open source tool that can do this, collect all, and the power meter is collecting then the energy consumption. One of the recommended power meters is the Gouda Expert Power Control Meter. This is recommended by the Blaue Engel. There are others that you can use. Janitza is another one. Then what do you measure? So there are three different scenarios to measure. One is the baseline measurement. This is just the operating system running without anything happening. It gives you the underlying power consumption of that OS. You have the idle mode, which is the operating plus the application running, but nothing happening. This gives you, when you subtract out the baseline, you get then the energy consumption of just that piece of software when it's not doing anything. And the standard usage scenario, which is the application being used, and it should represent typical and frequent functions of that software. This is a step that needs to be defined before you measure, obviously. And there are many ways to emulate this. Right now there's a lot of discussion in our matrix room about, so, okay. So there are many emulation tools, one that's been used by some researchers in this area as axionauts are quite easy to use, but pixel-based tool. Pixel-based means if you change monitor sizes, you might have problems reproducing the tasks because the pixels have changed relative to the monitor. But there are various other tools, and right now we're in discussion about which of those tools we want to use in the sprint in early 2022. If you want a summary of the various tools that can do this emulation of the standard usage scenario, there's a list here at the GitLab repository from one of KDE's members, David Hurko. At the moment, these standard usage scenarios are freely selected for blower angle certification. In the future, they may become standardized. And one thing to note is that for blower angle certification, you will need a log file of what actions were taken. So the kinds of things that you might expect, for example, when measuring something like an email client is opening an email, sending an email, adding an attachment, reading through the email. These are all standard usage scenario tasks that then go into the standard usage scenario that goes into the energy measurement. So that's the measurement part. Step one, step two is analyze. The Umbet Campus Birkenfeld has developed an online tool to produce reports automatically. You need a log file of the actions taken for both the idle mode and standard usage scenario, as well as the energy consumption and hardware performance results. You feed that into OSCAR, the open source software consumption analysis in our tool. And what you get back is a full report with the energy measurements, the hardware performance, et cetera. Here is just an example of the K-mail report. This is a standard usage scenario. And the gray lines here represent 31 repetitions of the measurements, and the importance of doing that is so you have a statistical valid data set that you can then use for analysis. Each of those gray lines represents, at each second, an average over 1,000 measurements with the Yanica power meter. And if you look here, what you see here is the power consumption over time. And this is, for example, at the point when sending an email and you see that the power consumption goes up. With this report, you are now done with the first part of the resource and energy efficiency component of the award criteria. What's really nice for us as free software enthusiasts, developers, et cetera, is that everything else here, free and open source software, already does in most cases. All that's missing, if it's missing, is documentation. So we're in a really great position here to get recognition of environmentally friendly software design once we have the energy consumption measurements. Looking to the future, we have the idea of doing a KDAB community lab. This is already in progress. We have a planned sprint in December. And again, you're all welcome to join if you would like. Long-term vision is to have a software upload portal where steps one and two are done automatically.  The short-term goal for now is just to get a lab set up. We're going to document the entire process. If you would want to set up your own lab, you can either look at our documentation or get in touch with us. We'd be happy to help get more labs set up to measure the energy consumption of free and open source software. There are many other ways to help. Started labeling in KDE, bugzilla, efficiency bugs. Those are bugs related to CPU spikes, delays, hangs, et cetera. You can provide support for statistical analysis tools, submit Blower angle applications, help with promotion and outreach. Give us feedback for revised criteria and help develop automation tools. Okay, okay, I'm actually almost done anyway. So for the last point, the development of automation tools, there's another project also funded by the Bundesamt, which might be of interest, is the Software Project. This is a project between the Sustainable Digital Infrastructure Alliance and the Öko Institute. And they're specifically focused on developing CI tools to bring energy efficiency measurements into the CI pipeline. And they're very interested in getting community support, and they have various hackathons and workshops planned for the next two years. And just to point out that if you want to learn more about this project, there's a conference presentation coming up in February. If you'd like to get involved, we'd love to have as many of you join us as possible. You can contact me at josephatkde.org. It just started a Master Don account for the project. We have two sprints, as I've mentioned several times now, one in December, one in early 2022. We also have a regular monthly big blue button meetup on the second Wednesday at 7 o'clock CET. Contact me if you'd like to join us. We just had our meeting two days ago, and it's been lively discussions about things, for example, which tools do we want to use to emulate the standard usage scenarios? We also have an energy efficiency mailing list in a matrix room. And there, again, you're welcome to join and then join the conversation. And then if you want some community support in general, we have a forum page. Here's just some more links, the GitLab repository for Feep and for Blower Angular Foss, as well as our promo. And the Blower Angular applications that we have completed, you're welcome to take as a template for your own software, and hopefully we can get as much free software certified as possible. So that is it. I just want to note that this was funded by the BMU, which is the Federal Ministry for the Environment and Natural Conservation and Nuclear Safety, as well as the UNVEB Bundesamt. And we are responsible for all the content. So thank you. So thanks for this presentation. I was wondering, does it really make sense to have pure CLI tools also to be satisfied? Or is it rather focused on desktop software or user facing software? Like what's the threshold where it really makes sense to make a software having Blower Angular? So at the moment, measurement labs are the way to get the reports for the Blower Angular. And the CLI tools is more of a long term to bring energy efficiency into the development pipeline so that we can get a sense, as we're making commits, if we're changing the energy consumption. I think I was perhaps actually like CLI tools, like pure console tools, like which you have in the terminal. So does it make sense to have it certified? So as far as I understand, that's not part of the award criteria for Blower Angular, that they would require external measurements. And I think part of that is because there are things that don't get picked up by the CLI tools is one of the issues. Another one is that itself is going to be creating some energy consumption. But I think the main one is that having this external, you have an objective measurement of the energy consumption. Naturally, that's going to be when you don't have a battery that could also then create issues. So laptops might cause problems because there's other kinds of energy management that's happening. But you want to have this sort of objective measurement that's external to the computer itself. But for the Blower Angular, as far as I understand, they need this kind of report at this point. So having the command line tools may not be enough. OK. Thank you. You're welcome. Thanks for the question. Thank you. Are there any other questions in the audience? Eric, please. Could you come? Thanks a lot. Is there already software that has the blue angel, or when do we expect the first to have it? That's a good question. No, not yet. And this is something that we're excited about because fingers crossed if we get these applications in in the next few weeks, that maybe KDE can be the first, which has a certain symbolic value. When do you think that could be? So we plan to submit by the end of this month, early next month, there are just a couple of things we still need to work out in the reports to make sure we understand what's happening and what the values are that we're reporting. Yeah. And on that note, whenever the Blower Angle awards a product for the first time, they have a big event with various politicians and whatnot. And it also would be nice publicity for free software.


If students want an overview of the book in one course, they still would very much enjoy principles of economics, right? Principles of economics is the single course that we have available as an independent study course where you covered sort of the most important ideas in the book in one course. Other students who maybe they're homeschoolers or maybe they really want to spend a lot of time to just dig through the, thoroughly go through the whole textbook, then this series of courses would be for them, right? Right, yeah. So that previous course was titled Principles of Economics. Don't get me wrong. I think that was a great course. I mean, the professor was phenomenal in my opinion. So yeah, by all means, if people want to go look at that because they just, they don't have the time to spend three courses, that's still there. And I think that's great for what we did. But the point is, as you say, if you really want to go through and basically it was there were a lot of material in the textbook, let me put it to you this way. When I was writing the textbook, I had this thought in my mind saying, what if this is the one book somebody reads on free market economics and his or her life, what needs to be in this book? And that was the criterion that I used as to what material to put in and what to exclude. And so given that it was almost causing me physical pain in the Principles of Economics Mises course where I just realized, I just can't cover this. And I was hoping they would go on their own and do the reading. And so that's now the point of doing this three-part series is that to say, instead of hoping, why don't we go through and carefully do it? Because there's so much in here that people need to know if they are being introduced to economics in particular. And I want to just make sure they catch all those important points of all those stuff that's in that textbook. Now, in this textbook, you cover Austrian economics principles, but these are also principles that they would find in other economics courses, wouldn't they? Right. So it's a good issue you're bringing up. We didn't want lessons for the young economists to be an explicitly Austrian book because then I was afraid just general homeschoolers who tend to be sort of right-wing or conservative and that's the way they might think of themselves. And they might not, it might sound like it was some obscure thing if they saw a textbook that was explicitly billed as this is Austrian economics. They might say, well, I don't even know what that means. And so that's why the lessons for the young economists per se is just trying to be a general free market or introduction free market economics. But of course, I think any Austrian reader would like everything that's in the book, it's not that there's anything non-Austrian in there. And that's partly too, it's Milton Friedman's famous thing about, oh, there's not Austrian or this or that, it's just good economics and bad economics. And I agree. And I think Austrian economics is good economics. And that's why I'm an Austrian. I don't go out of my way to do something I think is wrong. So everything in there is Austrian, but we didn't try to make it that explicit. We just, I was billing it as this is free market economic analysis. So the difference, though, in terms of what we're going to be able to do now with these Mises Academy courses is I can, if there's a particular point in the textbook that we cover, I can now have the freedom since we're teaching it through the Mises Academy. And I know the people who are signing up are going to be coming from that background and have that level of interest. I can fill in the details and talk about, you know, this is what Murray Rothbard had to say on this issue and so forth. The things that were just a little bit too much inside baseball to get into the textbook, I can sort of give that flavor and explain this particularly Austrian contribution on some particular issue. So this won't be just a tutorial through the textbook. There'll be a lot of extra value that students will get from the lectures because they'll be getting a lot of distinctly Austrian information and theory through the lectures, right? Right. And I mean, that's, at least to me, that's kind of what the point of a lecture is that ideally, you know, this is how I conducted my classes at Hillsdale College, where I taught for three years, and then what I do with the online courses here is, yeah, the lecture has to be standalone in the sense that I know some people are, especially if they're adults who are working, they just don't have time to do the reading and they just want to tune in and that's what they can afford to carve out of their schedule. And so the lecture does have to be able to stand alone. But the most value someone's going to get is if they do the reading first and then tune into the lecture. And so because of that, you know, I make the two dovetail each other that I'm not merely just basically reading from the textbook or giving a book report on lessons for the economist. What I'm doing is giving an independent lecture that is based on the same type of material. So, so, yeah, to answer your question, someone who just read the textbook, they're going to get a lot more from these Mises Academy classes based on it. And in particular, they're going to get a lot of anecdotes and other sorts of things that Austrians have said on these topics to sort of give them a broader range of education on what the Austrian take is on these issues. And but there will be a lot of sort of tutorial aspects to the course. One of the most challenging things about working through a textbook is to really get the message out of graphs and charts. And one of the things that I've really enjoyed in watching your previous Mises Academy courses, especially when you're covering this book and when you're covering man economy and state, is that you walk the student through interpreting tables and charts. And so you have a cursor floating on the screen that all the students can see while they're watching the live broadcast or watching the video later and you're circling different parts of the table and and guiding the student's eye from one part to another and just holding their hand through it so they can really understand it. Is that something that you enjoy about online teaching? Yeah, yeah, definitely. And that's, and that just come from my experience teaching in the actual physical classroom that I realized you can give students reading to do and they can be tables and things in there and they can even have read it and you just realize talking to them or like you give a quiz the next day with some of the cells in the table not filled in and they don't know how to put them in and you realize oh man these these they just don't get the table saying and it's it's partly because you just as the professor you assume well they've been reading about this their whole lives they know exactly what the context is here and then you got to say well no this is the first time you've seen this thing you don't know really what's going on. So yes, that is I think one of the the things that that's one of the functions of giving a lecture based on something that the student ideally has read before is that if there's something like that you can walk through and really make sure they understand you know how is this table working and so that's why if it's the things that are in this book since I wrote it I put in there because I thought they were important so there are a few places where just to give a specific illustrator things like comparative advantage and when does it make sense for somebody who is really good at two tasks to hire somebody who is inferior in the absolute sense but yet it's still as efficient you know to hire somebody so the classic example of the you know the lawyer hiring the secretary to do some of his correspondence even though he's a faster typist that that can make sense or the doctor hiring nurses to take the patient's blood pressure before he meets with them even though he's better at taking blood pressure than the nurses are you know things like that where it helps to illustrate that concept with a specific numerical example so yes we hit that part in the book and the lecture all walks through that to make sure the students really get where those numbers coming from how do you read this table so even Superman and Jimmy Olson that they they have incentive to divide their labor in exchange right right


Wiki automation tool. The reason why we are developing this is that we run multiple wikis. They all have different user groups, they all use different data models behind them. They all require a lot of maintenance. For instance, if you want to change a form or you want to add a property, it trickles down into multiple pages and a lot of edits and then you end up with inconsistencies. So it's very tough to maintain. And while the data models get more complex over time, we run into bigger problems that are a threat to the events or the products that we support with these wikis. So we recognize that and wiki development is not a core task. We have to do other things on a daily basis like world peace and stuff like that. So this is a side track but we are not very effective in how we spend our time. We spend our time in doing mediocre maintenance on wiki markup instead of governing the overall picture and only spending our creativity on the things that cannot be automated because we feel that in the design of a wiki and I'm almost losing that screen as well. In the design of a wiki, when you have a clear vision or a clear description of your data model 90% of what you need is standard template forms, properties, category definitions and your creativity is in that 10% that makes it a special tailor made for your situation. So what we did is think about how can we automate that 90% and the start is that if you have a data model and you define the data model in a way that it can be consumed by a certain piece of software that can translate the data model into all those things that you otherwise need to add to that single white page that you end up with when you install media wiki on your system. The pack of flour that you have to speak with Greg, all the things that you need to add and the data model that we chose was and this is somewhat ambiguous use of words but we use, our data sets are called concepts and those concepts are grouped together in packages. So here in this picture you see okay this is the data model, it has packages that define a set of related concepts concepts might be related to another and that is the trick of the semantic relationship that we have of course and concepts are composed of properties etc. So if someone who wants to have a wiki is able to write this down in a format that we need and currently that is an XML file where we define everything then we can use a piece of software to translate that into a set of standardized templates, forms, properties, categories everything you need and then you just upload your data and you're good to go. So what we did is we divided the runtime of the wiki as the middle piece from the design time of the wiki in the design time you have the wiki model schema on top of that we put the wiki model that we exclusively designed for a certain wiki, we run it through a wiki automation tool and then out pop what my colleague called the application pages and those are the templates, forms, properties, categories in that process you can maintain a change log so you know what you have been changing from a previous version of the wiki and you can do it on a live wiki as well so the change log and you can produce some incoherent reports for things to go wrong but in that runtime if you don't have this you don't have the purple blocks on the schema because the only thing that you end up with is a wiki platform with a wiki instance so on top of that our software projects the application pages and some CSS files that we need for the particular wiki and then you're good to go that defines in itself the data model on the wiki and then we populate it with data and that constitutes the runtime version of our wiki it runs very quick unfortunately I don't have it on my laptop yet there were some bugs that we needed to cover first but we're hopeful that within two or three months we have it running because we have a big project coming up over the summer where we need to use this explicitly right now like I said we're about to go live with this tool so to give you an idea what it does let me see the wiki model like I said it's just an XML file here you see for instance the start of the definition of the data model with this package is called standards management and it has a concept named profile and profile has these properties and down in the XML these properties are defined in what data type they have etc etc and that's about the way that you define your data model you can even define how it's being displayed on the screen because we have some choices in there as well then forget about the changelog the application pages what you see is what we generate based upon the model are the files for the packages and the concepts and the related properties we keep an extensive library of files in the project namespace that give us a better insight of how the data model functions and what goes in where so we have over a few pages per data set so to speak that gives us a better insight in the underwater behavior of the data model and because in the project namespace it's way out of vision for the generic users now next to the model-based generated pages we also can add a common library of pages and think about those templates that you use in every wiki that you have because they are so nice to have or CSS files that you use in every wiki because it gives you that added functionality that you don't have in the default setting so those are easy to add as well so you can add a base functionality there that doesn't require any generation from the model but as you see on the page it will give you some pages in the project namespace that gives you an overview of what each part of the model is and then per package, concept, all the properties that we have and the common library with all the default templates that we move over so this is all very well documented the CSS files that we use they are all linked and displayed so you can see what goes in there even the color schemes that we use for different concepts and the result is functions that we use to hard code every time again in templates and sometimes you use templates in templates of templates to standardize, look and feel, functionality on your pages these are all now part of that wiki automation, we don't have to worry about that anymore and instead of nesting multiple templates over and over again because all the templates are generated automatically by a computer we don't have to worry about... the reason why you use a template for a piece of code is because you don't want to type it over and over again and you don't want to make mistakes or introduce inconsistency because you change the part of code in one page but not in the other but if all those pages are generated by a piece of software then by definition they all are consistent already so a lot of the things that normally you would have in multiple nestings of templates can now be directly configured into the page itself and that gives you some advantage in speed of processing and stuff like that so here this is just a very simple example of what we have in the wiki this is still in the project namespace but it shows you the packages we have installed at this moment and in each package what concepts there are so in what we call the C3 taxonomy we have servers and applications and you can see a listing, a tree format you can add new with the default form that we have etc etc so to give you an idea normally in our enterprise mapping wiki or EM wiki if you have an application like for instance an airspace control application you have a description, you have a navigator on the side you have a nice little graph that shows the place in a hierarchy of applications requirements definitions, you have the services that are required to run that application the capability standards, the information products that are being consumed or that are generated as output etc etc this is just one example of one wiki that we have this one is for our enterprise architecture and so this is how it looks right now and this is how it looks in the new setting it doesn't have all those semantic relationships yet because we haven't transposed all the data and all the functions in that new data model yet but you see that it's a very clean navigator with the simple links for the category, for a tree listing for a semantic search, for opening the form and a relation to other concepts and the point is this didn't take any editing I didn't touch the templates, I didn't touch the forms I just defined the data model, we run the code and what is it, 10 seconds, 15 seconds later you have a completely installed or a completely refreshed wiki with all the templates, forms, properties and categories and all the things that you define on top of that there may always be pages that or templates that are not part of that wiki automation for whatever stupid reason they are not deleted, they will still be there but the things that you have if you want to update them, if you want to add a property or you want to change or add a category, whatever you don't do it in the wiki anymore you do it in the XML file, you press run and it's in the wiki so it makes it very easy to design, maintain a wiki it makes it easy to replicate a wiki I had a short discussion with Cindy yesterday so what the good thing is, we discussed yesterday about how to make installation packages for wikis and there are multiple ways to do that but then you're with a blank bare bone wiki page then you have to start coding this helps us to do a lot of that 90% or maybe 95% of what we want to achieve now the next step is, and Cindy was absolutely right in that the next step is we now need to define our data model in XML and XML is even harder to combat than wiki markup so it takes a lot of effort to do it right you do it step by step and if you have a complex data model it takes quite a bit of time to do that it's hard labor what would be nice if eventually you would have a more graphical user interface so that you wouldn't ask your user group your audience, your customers to go hack XML to create a wiki just ask them to define it in a graphic interface and if that translated into the XML or into any other format that we can process in our automation tool then that will be great as well so I'll certainly will take it home and we'll discuss that the thing is it isn't operational yet it will be in the next couple of months now Jaron might remember I brought this up two years ago in the EMW con in New York and it's taken more time than we wanted but I'm pretty sure that by the next EMW con we're able to present this but if it runs well one of the options is also if we could make this available to a wider user community and that other people could have a go at this as well any questions? yes sir you do that in the XML file you run the wiki automation tool again and it replaces your old templates with the new ones yes on the wiki itself you can but those will be overwritten so the best way is to define it in the model if you have templates that you do not want to be generated then you choose a different name that's not part of what is being generated by the model and then it will remain I have a lively discussion with my colleague who is programming this stuff he is absolutely sure that any template can be generated in his tool so that is his useful enthusiasm that I appreciate very much but I don't think that is entirely true I think there will be reason enough for templates to exist outside of that 90% or maybe it's 95% that we generate automatically but even if a user wants to make a template for whatever stupid reason because he feels comfortable with how he or she uses the data on the wiki and wants to display it on some pages in their own user domain who am I to stop her? that should be possible so that is but in principle there is one thing that Cindy asked as well is everything that is being generated by the wiki automation tool is protected so only administrators have editing rights to change them so users cannot change the templates, forms, categories properties, anything the CSS files, anything that is being defined through that automation tool is all protected from editing users are supposed to focus on content content is the most important thing that we have on our wikis that's where they need to do their edits we don't want them to edit the templates good question quick question is the XML, are you designing that from scratch or using any standard for the XML I presume you are doing a schema to define what it is are you I was sort of thinking about XMI when you were talking about the potential to be able to translate from XMI into your XML I don't know, might be I don't know, I'm not too familiar with that that is part of the work that my colleague has done but he has I have stressed this from the beginning that he needed to document it very well so luckily for me and my colleagues who now have to run some wikis through this process he has documented in a manual very detailed what goes where and how we do that for instance, you know when you load it up with data it will be displayed in a certain way well, do you want to have it in bullet lists or in plain text or you want to have tables do you want to have it in a pie chart so there are so many ways to display things and there is a way to already define in the XML how data on certain pages are being expressed so he documents that so he said there you put a line between those tags and then you fill in either this one or that one or those values and then you will have the outcome if you don't like the outcome you change the XML you run the script again and you see the results are people interested to get a demonstration and see more of this when it finally works is that something that I could plan ahead for the next conference yeah, okay, good, good if there are no more questions then I can close shop here


What you're about to see are the events that led to one fatality on the Macklake fire on May 5th, 1980 The Macklake fire burned on the Mayo Ranger District of the Huron Manistee National Forest Located in the lower peninsula of Michigan The fire was an escaped prescribed burn that spread over 20,000 acres in six hours In addition to the firefighter fatality, 44 homes were destroyed Much of this area is dominated by jack pine Live fuel moisture in jack pine is a contributing factor to most of the large fires that have occurred in Michigan Live fuel moisture is dropping early May as the jackpines concentrate all available moisture into the new growth This new growth is covered with a waxy coating that is very flammable Live fuel moisture is on the day of the fire were estimated to be about 105 percent which is low enough to sustain a crown fire The topography in the area of the fire is comprised of gently rolling hills There is a significant intermix of developed subdivisions within the forest boundaries weather observations at 1045 hours on the morning of the fire were temperature 82 degrees relative humidity 34% Wind southwest at 8 to 12 miles per hour In the forest-wide morning fire weather forecast a cold front passage was predicted for that afternoon at about 1500 This incident began as the Crane Lake prescribed burn Which was intended to reduce logging slash and regenerate a new jack pine stand for wildlife habitat Prior to the ignition of the burn wind and relative humidity factors were outside of prescription Several of the resources identified in the burn plan were not on site and no spot weather forecast was requested However pressure to accomplish district reforestation targets swayed the decision to go ahead with the burn The plan was to start the burn at about 0900 and have the 70 acre unit completely burned by 1200 Then some of the personnel on the burn could be moved into standby status to cover the higher fire dangers That would accompany the cold front passage that afternoon The district had been stripped of any Contingency resources because a number of red-carded individuals were in a training session that day Although slash burning had been conducted in jack pine for many years on the forest Several of the individuals on this burn were new firefighters that had limited experience with jack pine fuels and the equipment they were operating at 1026 hours the Crane Lake prescribed burn was ignited at the south end of the unit by 1115 three spot fires had developed in grass fuels along the southeast side of the burn They were quickly suppressed by the myo district tractor plow and the district 1,000 gallon engine As ignition continued three more spot fires occurred in the grass fuels These were also suppressed by the tractor plow and engine At 1206 a seventh spot fire occurred in an area of mature timber Located between the burn unit and highway 33 This area was a green strip left for aesthetic purposes At this time ignition operations were shut down and the fire crews went into a suppression mode The tractor plow began to build line east followed by the engine trying to tie the escape back into highway 33 Here you can see where the actual plow line was put in The tractor plow operator was a second-year firefighter and in his first year as a tractor plow operator The engine was a new piece of equipment and the operators were new forest or trainees who were not experienced with using the equipment You're looking south down highway 33 the burn unit is on the right at 1215 the fire spotted across highway 33 The wind had shifted to west and increased to 20 miles per hour as the cold front approached the area Sooner than was expected a sharp drop in relative humidity accompanied the frontal wind shift This spot fire grew to three-quarters of an acre and was suppressed by the tractor plow and engine However, another spot fire started just to the north This spot began torching trees almost immediately The tractor began to plow the north flank of this next spot fire, but could not get a line around it Radio traffic during this time described the fire behavior as heavy rolling black smoke It's highly probable that the fire had developed into a full-crowned fire by this time moving east from highway 33 As the situation escalated the radio became flooded with traffic all fire and district radio traffic transmissions were on the same channel Additionally, no aerial detection plane was available this left the inexperienced tractor operator and engine crew isolated without effective communication all The actions of the tractor plow unit and engine crew from this point on were initiated without the benefit of instructions from an experienced supervisor This was also about the time that personnel on the fire realized they could no longer stop the forward spread of the fire They had lit and that it was headed for heavily developed areas around Mack Lake to the east The tractor plow and engine again re-engaged the fire at approximately 12 30 They attempted a direct flanking attack north of a power line right of way in a stand of young dense jackpine The engine was following the dozer spraying water in an attempt to keep fire out of the tree crowns The fire was intense enough that the tractor plow could not work directly on the fire edge So it was decided that the engine would work in front to cool the flames and allow the tractor to plow the line with less heat impact The engine moved ahead of the tractor crashing through the jackpine thicket. This is the plow line. They were working at that time Spot fires continued to develop behind the tractor plow and the operator began to concentrate on catching the spots behind him Within minutes the fire intensity forced the engine to abandon suppression efforts and they made a desperate run to the east and then north There was no communication between the tractor and the engine regarding this action The engine and crew escaped without harm It should be noted that there were no other suppression resources working the control lines behind the tractor and engine Rapid fire spread from unsecured control lines and the numerous spot fires began to threaten the location where the tractor plow was working At this point the tractor operator left the original line and moved 75 feet to the north and continued in a flanking attack He began to plow but must have finally realized his effort was ineffective and tried to escape moving away from the flank of the fire At approximately 1240 he abandoned the tractor and began to run as his position was overtaken by the fire His body was found within 100 feet of the tractor Less than 30 minutes after the burn had escaped a firefighter was dead Significant horizontal roll vortex activity and associated rapid rates of spread along the fire's flanks occurred on this fire as evidenced by the burn patterns At its peak between 1230 and 1500 this fire burned at an average rate of spread of two miles per hour Spotting was occurring up to one third of a mile ahead of the fire and a column of smoke of up to 15,000 feet was created The fire was finally controlled at 24,800 acres This infrared satellite image shows the final fire perimeter You have just seen the events that occurred on the Mack Lake fire The instructor will now facilitate a discussion about the use of fire safety guidelines by the involved personnel The strategic and tactical decisions that were made and the human factors that contributed to this burn over incident


What's going on guys got Kyle here with laden sports cards, and we are ripping this is one box for Garrett tee It is a 2022 2023 Bowman Chrome University, and this is for Garrett. Good luck, sir. Let's see that Wemby See some nice little numbers here. Maybe a red maybe a little super maybe a little super Good luck, sir And get orange Again guys, we are out of these for personal at the moment. I would keep an eye on the website though We're running a lot of breaks of these but we will probably have some more personals coming up There's a can Whitmore refractor nice one to start for Nova Jeremy Roach, there's a refractor of Kendrick Davis first out of Memphis Playing for Penny. There's a Invicta of Mari Bailey at a UCLA Canada boy Murray. That's right, man. That's right. There's a couple Canadians in the league right now, man Pretty solid. I think Shays Canadian too, right? Got the Mari Bailey throwback 2009 throwback No, Andrew Wiggins is Canadian. There's another Invicta this time. It's Caitlyn Clark. Nice one there Invicta base Nice Clark Kyle Filipowski, there's a MJ Rice on the throwback 2009 Consul Emanuel, there's Langford. There's a skyscraping arterial Morris Come on Garrett. Where's the redemption? Come on There's an auto gonna be a Roddy Gale, Jr. Out of the Ohio State University on the refractor auto it's a 499 Roddy Gale Come on redemption and our second auto is gonna be Jordan Walsh Jordan Walsh on the 2009 throwback auto there out of Arkansas Jordan Walsh Come on still get the redemption. I think you get two autos even with the redemption So we're still hunting here. We're still hunting race Thompson So Cooper, I just made some good stuff, man. I think it's something good stuff I'm not exactly sure what you missed, but it's definitely been some good stuff God judo mints on the purple shimmer not numbered. Yeah, we've had some love. We've had some good breaks today for sure Some nice personals There's a refractor Timmy Allen. No Malcolm Mitchell though. No Malcolm Mitchell. Yeah, Cooper There's refractor MJ Rice Jet Howard JJ Starling mom super where you at JJ Starling throwback Zach Edie Come on super There's skyscraping judo mints What's up Python? Typically, it's usually around two days 48 hours before breaks are ready We're a little bit behind right now. These Bowman breaks do take a while so Sometime mid-week probably Python. Maybe it's Wednesday on a You'll get an email as well. You're gonna email with your tracking when it is ready. There's an aqua skyscraping number two 150 For a Jordan Walsh there. You can email with tracking once they are shipped. I would guess Wednesday or Thursday though Python we are a little behind. I know you had to have breaks last night later last night Face pack purple to 399. That's Tyrese Proctor It's a 399 out of Duke. Yeah, no problem. No problem. Yeah, like I said, typically it's about 48 hours Or so always depends just what we've got what we got break in what well we can get sorted in time Seth Trimble. Oh, thank you Serena. There we go. There's a skyscraping Jordan Walsh Ryan Nemhardt that is our shipping manager there Python. So I definitely take her. I would take her advice there It's probably four to five days. So maybe later in the week get a shipping notification All righty guys that will do it there Garrett for your box of bowmen you thank you so much. We'll get that right out to you