All right, thank you everybody for coming, showing up today. Very happy that you made it this afternoon. This talk is a new way to roll. We're talking about supply chain choreography for enterprise Kubernetes. My name is Steve Watkins. This is my colleague, Kirti Apte. We're both solution architects with VMware with the Tanzu business unit. So that means we work with all things, modern apps and Kubernetes and things like that. So very happy to be here. Let's kick it off. So first thing, why in the world where we even talk about supply chains? So our most important thing is dealing with our developers. Developers cost a lot of money, right? We want them to write code. What do developers want to do? They want to write code. How do they want it deployed? They don't care while we're at KubeCon. So we want it deployed in Kubernetes, kind of obviously. But for those of you that have a little gray in your beard like me, if you remember back, all the way back about 15 years ago, the book Continuous Delivery, Jess Humble and David Farley nailed what is the preeminent challenge for us. If somebody thinks there's a good idea, how do we quickly get that in front of our users? How can we make that happen? And that is still the challenge. That is the challenge that we're all moving towards.  So that was 15 years ago. Even up to today, we're still running into this issue. 15 years later, we've built a bigger cloud native infrastructure. We're doing a lot more cool things. But Joe Beta, if you know Joe, one of the co-founders of Kubernetes, called out specifically, our job is to manage complexity and unlock velocity for all the good features that we get out of Kubernetes and cloud native operations. We're still can create some drags. So we're still struggling with velocity, getting things out. Okay, so the traditional way of approaching it or the way we have been approaching it is using a CI CD challenge or CI CD. Pretty straightforward, right? I identify some tasks that I need to do. There's code, build image, run some tests, build a release, get it in deployed and operate and monitor. And this has been around for a while. It depends on an external orchestrator. So an external orchestrator will start and stop each one of these tasks and it'll control them. And there are some advantages for sure. It's very mature. It's been around for a long time. There's a lot of great products out there. You've probably saw a lot of them on the Expo floor. It's also pretty easy to monitor. If you want to monitor uptime and delivery and really drive metrics and improvements, it's pretty good. And then for basic tests or straightforward tests, it's actually really fast and really quick to set up. But it's not perfect. There's a couple of things that could be improved. For one thing, it's very tightly coupled. So what does that mean? That means that because I have an external orchestrator controlling each one of those tasks, if I want to change one of those tasks or if I want to add a new one of those tasks, it impacts my orchestrator and it impacts my upstream and downstream tasks.  The second thing is that even though it's easier to monitor, it also creates a single point of failure. So this can take down production and slow down getting code in front of users. And finally, it's a little bit rigid. It can be rigid. So what does that mean? Well, let's say, for example, we discovered there's a CVE in our container image or in our libraries or something. We want to fix that CVE, so we've got the patch.  So it's a bit rigid that way, not so flexible. Okay. That's all well and good. A lot of people can live with that, but where things really get challenging is when we start to look at orchestration at scale. So here's what happens a lot of the time. We'll start out, we'll have one team, maybe they're developing and go or something like that. And we'll build a pipeline and that pipeline will go through A, B, C, D and E. Okay, so far so good. But then it turns out we have another team and this team, they're whatever, they're doing data and they're doing it in Python. And this team, they don't use A. They just use B, C, D and E. Okay, well, we're gonna build another pipeline for them.  All right, so this is just an example. So what happens? We end up having a library of pipelines to try to contain an orchestrate from one. And secondly, what happens is a lot of this work on customizing the pipeline gets pushed down to the individual development team. So now I've got developers working on pipeline and DevOps stop instead of writing code. And the point is to get code out as fast as possible. Okay, so how can we solve this? Well, as with so many things in agile and in DevOps, we can look to the practices that came out of lean manufacturing. And if you look at lean manufacturing, when they look at this problem, it is a supply chain problem. And here's the thing about manufacturing. Here we are in Detroit, by the way. And back in the 70s and 80s, it was the Toyota quality system that taught Chevy and Ford how to build a car to be perfectly fine. And we're doing it still today. So let's say we look at each one of these tasks instead of as a task that needs to be controlled, think of it as a downstream part of my supply chain. And the thing about in manufacturing and input for one becomes an output. So let's say I have raw rubber, I use rubber and I create a tire. And then the next step is we'll take that tire and we'll mount it on a rim and, or pardon me, yeah, a tire and mount it on a rim and now I have a wheel. Now that wheel goes down to the next step and it gets screwed onto a car. Hopefully quite securely with luck. So the point here is that the inputs, or pardon me, the outputs of each step in that supply chain, one output is the input for the other. And one output that becomes the trigger for the next steps. We start to establish pull, which is again one of the lean principles. So if we look at lean manufacturing, this gives us a way to approach the problem. Okay, here's the other thing that's really important and that was a critical part of the Toyota quality system for sure. And that is establishing provenance, trust, and transparency. So provenance, where did it come from? Who touched it? Which parts were added on? I need to have a complete trust and an agreement with my suppliers and the seams down the side and I should be able to pull up and view what happened each and every time. All right, so let's take that model and let's apply that to deploying some applications. So I'm gonna start out here and this is a typical collection of folks you might have, SREs and SecOps, Devs and Ops. All right, so let's start with our tradition. So we have our, we're gonna watch the repo, gonna build an image, I'm gonna do a test, configuration and deploy it. Those are my steps. All right, let's start by making each one of those steps instead of externally controlled. Let's make those independent steps. Let's encapsulate them and say you are self-sufficient now, okay? And then what we'll do is we're gonna wrap this in a template, okay? Now, by the way, we're gonna go into this in a lot more detail a little bit later on. I just wanna give you the high level version first. So we'll wrap this up in a template so it no longer becomes a very specific application, it no longer becomes flux or Argo, it becomes pull my repository, okay? Good, so then I'll say, all right, I know that you are now a template and you are independent, so your input, your raw material will come from the previous step. So test, look to the build image process to feed you what you need to do to run a test, okay? So far so good. So we'll put all of those together. They're all independent, they all fire independently, they all know to look for each other and we're gonna put that in a single definition and we're gonna call that a supply chain, okay? So into a single blueprint. All right, good, so far so good. So now somewhere, I have to be able to find a definition for what this supply chain is and be able to call it and kick it off. All right, so let's bring it back to our people. So first of all, our SREs and our SecOps are the ones that are going to help define and maintain this supply chain. And by the way, this is all Kubernetes native stuff. So it's not an external app that sits out there, it lives right inside of your Kubernetes cluster, right? And then my developers going to say, yes, I've finished my code and here's the workload gamel. Now we're gonna get into this a little bit more as well, but here's what's in a workload gamel. The GitHub repo for my code, or Git repo, pardon me, and the type of app or the name of the supply chain. And the name of the supply chain could be something like it's a web app, it's a data app, something like that, very straightforward. So the cartographer controller will say, yes, I can map that particular definition to a supply chain, the supply chain executes, runs itself and the delivery team is able to also maintain and match that supply chain definition in their output. So we're all able to kind of organize and manage this all at once, okay? So we've gone from having an external controller that's rigid and requires an external management into something that's a little bit more organic and it has more of a pull feel and it leans very heavily from not only manufacturing, but for those of you who are writing code and are familiar with an event-driven architecture, that's a better way to think about this. So I have publishers and subscribers, okay? All right, so now this is the high level view, we're gonna go in, we're gonna double click and go a little bit more detail on each of these components. All right, so the first thing we wanna do is we wanna introduce you to cartographer. Here. Okay, so hello everyone and first of all, thanks everyone for showing up for the session. So now we are going to go deep into cartographer and try to understand what cartographer is. So let's take a step back and let's look at, this is somewhat a messier slide. So what I'm showing here is the CNCF landscape. There are lots of projects and technologies are getting added into CNCF landscape. But if you zoom into a specific area, a very important area, CI CD, there are abundant amount of tools which are available in the CI CD space, such as Tecton, Argo CD, then lots of built tools, K-Pack and others. And how many of you use this CI CD tool from the CNCF landscape? Are there any? Yeah, lots of them. So basically community has provided these tools to integrate the CI CD. But when you're trying to make CI CD work, how does these tools come together? And that's where the motivation for cartographer is. So cartographer is an open source project. It is initiated by VMware and it joined the CNCF landscape as well as of October 2021. So fairly active community in that space as well. So now let's look at cartographer-based CI CD, how you can implement cartographer-based CI CD into your organization. So cartographer offers two levels of abstractions. First is supply chain, cluster supply chain and cluster delivery. So you can implement your CI or continuous integration with cluster supply chain. So what do these abstractions do? They help you define standardized way to implement your workflow. CI workflow as well as CD workflow in a Kubernetes native and in a declarative format. So that's the advantage of cartographer. So what operators will do, they will define this CI workflow supply chain. Typically developers will commit the code. It will go through the CI pipeline. This is continuous integration, which we will do it through supply chain that will be running on the shared Kubernetes cluster. So you can view that as a build cluster or a run cluster or where my supply chain is installed and entire workflow is getting executed. And typical outputs of the supply chains are images as well as application configuration. Now images, you can push it into the image registry. Application configuration, you can push it into the GitHub repository. Again, reusable asset. You are pushing it to the GitHub repository. When you move to higher level of environments, such as staging, production, you need to worry about deployment configurations, such as what are NFRs for your application, right? So basically, how are you going to scale your application? How are you going to, how many replicas do I need for my service? So all these decisions are baked into that deployment configuration. And environmental configuration, such as how my service is going to connect to other external systems, such as database. So production database, external URL will be different from the development database, external URL or endpoint. So delivery, if you look at it, CD actually will be again in a supply chain, similar to supply chain, it will be a resource which will define the workflow to deliver your product to the multiple workload cluster. So it will take inputs from, such as configurations, different configurations, image registry, and it will define a workflow, cartographer will implement that workflow, and then it will help define that workflow and install Kubernetes resources onto multiple cluster, multicluster environment as well. And the final product is the running app. So this is the entire CI CD flow, which you can implement with the cartographer. And what you're getting with this, you are getting reusability. You are getting full end to an automation. Many of the processes are manual, but here you are getting full end to an automation and also reproducibility. So you can reproduce errors or anything, anytime. So these are the advantages of this CI CD process. Now let's take a simple workflow, where I'm pulling a source code, I'm building an image, and I'm deploying it to the Kubernetes cluster. Now this is not a real world scenario, real world, it's going to be complex, but let's try to build a concept. What we are saying here is we are pulling a source code, I'm using community provided tools, such as flux CD, to build an image, I'm using K-Pack and deploying it to the Kubernetes cluster. Now what I'm saying here is the flux CD definition that I have given here is the normal Kubernetes construct, which is a GitHub repository. Now in the supply chain world basically, what operator has defined, operator defines this workflow, defines the steps inside that workflow, each step is autonomous in nature, has inputs and outputs, and also each step is implemented using the tool of your choice. And then each step later on can be templatized, and that's where Cartographer provides you this abstraction in the form of templates as well. So there are a couple of templates, there are four types of templates, there is cluster source template, cluster image template, cluster template, cluster config template, also runnable interface available there. So let's take an example of one template, each one has different inputs and outputs, and based on your task or the step requirement, you can choose which type of template to use. So for example here, to pull the source code using flux CD, I'm using cluster source template, and very simple, right? So flux CD definition, I have wrapped it under template section, and the output of that is the URL path. Now URL path is the flux CD, basically pulls the source code and generates the source code URL, and that will be stored in the URL path. Similarly cluster image template will have a different output which will store, which will provide you image path as the output. So generated images will be stored in the image path in the GitHub repository, and cluster image template will have image, as image path as the output, cluster config template will have a config path as the output. And yeah, sure. Okay, quick point, one of the questions we get from folks is they say, well, we just implemented Argo, can't we just do this with Argo? And what Kirti was showing is we happen to be using flux, if you're using Argo, you insert Argo in there. The goal of making the template around is that you can swap your tools out. Remember when I talked about different teams want different tools and different steps? The idea behind the templates is to make that very, very simple. I can use the same supply chain with different tools, the only thing that changes. And it also allows you to have a little bit of extra diversity. So if I wanna make a change and we wanna try something out, we can work it. Yeah, so basically templatizing one advantage is instead of flux CD, I can use Argo CD template and just get it working as well. So how do you stitch all this together? The cluster supply chain defines that workflow, such as CI workflow or the CD workflow, and then you stitch together with cluster supply chain. It is nothing but combinations of different templates and then wiring of inputs and outputs. So for example here, flux CD generates the source URL output which will be input to the image builder. Then image builder generates images that will be input to the next step which is deploying those images. Also another one is developer basically typically submits or create the workload resource that is also extracted out. It is nothing but the application configuration. Developer knows really well the application parameters and the configuration and things like that. So those are stored in the workload and supply chain selector will be matched. Cartographer will match that supply chain selector with the workload label. So that way that supply chain will be executed. So for example, you have multiple supply chains for different purpose in your organization. Then you can use that selector matching algorithm which is provided by cartographer. Security you cannot ignore. Security compliance need to be embedded into your supply chains and into your organization. Now there are lots of vectors where your application and the systems will be compromised. For example here, CI CD can be compromised, build, there are vulnerabilities. There are scanning and other tools are necessary. So what we, these are the best practices that we recommend where signing the images is really important. Guard rails are put together security guard rails in terms of signing the images, scanning the images for vulnerabilities, your images as well as source code needs to be scanned. And the best practice is to store in a centralized, all these results of scanning and vulnerabilities into centralized data store. So for example here, VMware Tanzu application platform which is based on open source cartographer, we provide out of the box supply chain which is called test scan and store which provides you this ability which is enterprise grade supply chain that we provide with the scanning ability with the gripe scanner and others and which stores the metadata results into the metadata store which is the centralized store where the results of, where you can query that as metadata store and then generate SBOM which is really, really important from the auditing perspective for your security. So here just the output of the SBOM is shown where you are seeing the packages inside image and then CVEs are detected with that. So you can query that any time, give it to developers, submit to auditors, there are multiple advantages of that. So with that, Steve, you can talk to me. Okay, so one more thing on that. One of the advantages of this model of having inputs and outputs is you can capture those outputs and use that for your security purposes. So it's very cool this way. What we're gonna do for you is we're gonna take you through a live demo. It's gonna be great but it's gonna be a lot of yaml so I'm gonna give you a quick flyover. So this is how things actually work in real life.  As part of that, as we saw, he'll do the workload. Call the workload out. The workload will kick off the supply chain. The supply chain will execute as it executes. Some of the outputs will be an OCI compliant image that'll get pushed out to some kind of a container repo and then a configuration will be put into some kind of a get repo as well. So that'll be out and then once we have things out, remember we do push and we do pull just like in manufacturing, there's a pull you establish pull. So we'll pull that into a test scenario and the idea here is that my developer can have real-time access to it and be able to pull in and run his tests. The goal here is to iterate as fast as possible because remember, we wanna get good ideas out to end users as fast as possible. So once we're happy with the code, we do the publish and then when the same thing runs through only this time we'll pull it out and we'll pull and deploy into production and we end up with happy users, okay? So high level, that's what's gonna fly. You'll notice that we're using all open source tools in this. If you recognize some of the icons, we're using Plex, we're using Tecton, we're using GRIP, we're using K-Pax and CloudBuild, we're using Cosign for our sign, we're using Knative to do scale to zeros and we're using Carvel to do some of the extra templating. Okay. All right, who wants to see a demo? Yeah? All right, good stuff. Hey, so it's going to be a live demo, so bear with me and I hope demo guards are with us. Yeah, switch it to mirror, you can see it now, okay? Okay, so I have, it's going to be a live demo. I like a scripting demo actually, so I have created a script for the demo. So what that means is the commands.  So they're all scripted, but it's actually running live and you'll see it running live, okay? We're not trying to pull a fast one on you. Okay, yeah, that's a great explanation. Okay, so let's consider a basic GitHub's workflow here. So pulling the source code from Flux CD, building an image with K-Pax, then I'm going to generate a config map and then pushing it to the GitHub repository using Tecton. So that's a very basic workflow. Now what is installed on the cluster? Let's see that real quick. And I'm using Tanzu, which is provided by Tanzu CLI, which is provided by VMware Tanzu application platform. So here, actually I have, let's say, the cartographer running and then I have also installed the community plugin, such as Flux CD, I have installed GRIP and also the Tecton pipelines. Now cartographer will choreograph the passing results from one resource to another using the graph which is described in the cluster supply chain object. Now let's look at the developer perspective. So my developer basically is in charge of creating a workload. So how does that workload looks like? So basically what I have done here is I'm using a Golang project and this is a GitHub URL and I'm using the main branch and the labels. Basically this is many supply chains are running on this cluster. So I'm teaching cartographer to use supply chain web demo for this GitHub's flow. And there are specific build related parameters that my application architect has defined that I have included in that as well. So let's try to deploy this workload. Very simple to deploy that with Cook CTL apply. I'm going to deploy it. Okay, so the workload is created and let's see the status of the workload. Okay, so this one, these are the resources created after deploying that workload supply chain. Supply chain demo is used there and then the source provider, these are the other resources which are created. It's waiting for status dot artifact URL. So basically flux CD is trying to pull the GitHub repository and then trying to generate the URL. So let's see that one more time. Okay, so now I think flux CD has generated the URL here and others are basically in progress still. So it will take some time. So in the next window, actually I'm just going to watch it a little bit more. Okay, looks like it is ready. So what it is done is basically generated the flux CD URL. This is the flux CD URL, which is generated. Then this is my, basically I'm pushing my image, image and digest is created. I'm pushing that image to the harbor registry, but it can be any image registry of your choice. Harbor is by the way, open source product from VMware as well. Open source product and it is used heavily in the VMware. So let's switch back to this window now and let's see now how from the operator perspective, how did I put together the supply chain or which supply chain or did I use? So in this cluster, basically all the supply chains are running and I use for this GitOps flow, I use supply chain demo. So let's look under the hood of this supply chain and what's is there. So these are the resources. So these are multiple templates, which I have used and I have defined the order, execution order of the template in such a way that, you know, source provider, source provider output is input for image builder, config provider with the config cluster config template and image builder output is input for that step. So this is just a wiring that I have done. And if everything went good, actually I should have, you know, config uploaded into my GitHub repository. Let's see that live. Okay, so this manifest.yaml created two minutes ago and this config is uploaded. So this supply chain basically got executed, this config, what we were expecting results, basically upload the config to my GitHub repository, that's done. Now these are the templates basically in the supply chain. So this is, like I said, there are templates available and these are the API resources. Basically cartographer uses these templates and just to show you cluster image template, basically output of the cluster image template is image path. I'm teaching a cartographer to use image path and use value status dot latest image. K-Pack actually builds the image and puts it into status dot latest image. I'm teaching cartographer use that image path and pass it there, set the input and pass it to the other step. Now let's look at the enterprise grade GitOps workflow. We just saw basically basic workflow. Here I'm adding testing. So basically source tester, Tecton pipeline or Tecton, basically Tecton job. And then source scan is gripe, image build with K-Pack, image scan with gripe. So I'm going to scan the image and push the results of the scanning into metadata store. Config provider, you generate the config map and then configure writer with Tecton pipeline run and deploy as K-NATO service deployment and HTTP proxy. So these are the Kubernetes resources which are created. To save some time, I have already deployed this basically. So what you see here, the supply chain is source test scan to URL. That's the supply chain I use for this. And these are the resources created by that supply chain. It already deployed it. Another thing to point out, delivery. So basically what I'm doing, taking those configurations and deploying it into Kubernetes cluster. So there is a source provider. Flux CD will pull that source config map and then deploy it with the deployer, which is cluster deployer in this case. And K-NATO service is also created. And as you can see, there is external endpoint created as well for the application where end users can access that. And just to show you a little bit more, if we have time, Tanzu application platform, which is based on open source cartographer, gives you visualization of that supply chain as well. So what you're seeing here is the UI based on backstage. And it gives you basically the supply chain visualization and you can see the health of each component inside or workflow basically inside that UI. So here is the test. Basically, if I click on that, my developers have written test, unit test. Test is run and the test is successful. Then just to show you image scanner, basically all these are all the CVs detected with my gripe scanner. And basically there is I found one CV critical. I can define a policy on the cluster where I can say don't promote the code if critical CVs are found to other environments or the higher environments. You can define those policies as well. And so this is about it. This is the choreography. I know I rushed through the demo, but it was a live demo. And I hope you have gotten something out of it. We hope we got some extra bonuses for doing live demo. All right, so I know we were at time, but a couple of quick things. First of all, as you walked around on the floor, you've seen a lot of supply chain coming up. It's really starting to pick up, especially in the last six months. And some places like Google is way ahead of the curve. We think that supply chains need to have security built in. So we're actually working towards the Google standard, the Salsa standard. I know in our team, we're working towards level three and we expect to be there very soon. We're already at level two. So I just wanted to bring that out that this is, even though we did diverge and we talked a little bit about our particular product, our particular product is built on all of these open source tools and we're embracing those open standards. You have the next slide, please. And then finally, a couple of things I want to leave you with, please, please, please go check out Cartographer and it's cartographer.sh. If you go to IO, it'll take you to the completely the wrong place. Don't make that mistake. But go to cartographer.sh. You can download this. One of the really cool things they did is they packaged in a sub folder called hack. There's the ability to run and test this in a kind cluster right on your laptop. So you don't even have to deploy it on a Kubernetes cluster. Makes things a little bit easier. Of course, there's always the GitHub. Please check us out on our Tanzu cartographer repo. Pull some things down as well as this Slack channel and of course, Twitter. That's what we have for right now. I know we're right at time. I don't know if we have any questions or actually, Kirti and I will hang around at the end and we'll be happy to take questions as well. Yeah. Thank you.


Greetings and welcome to the Introduction to Astronomy. In this week's Astronomy of Other Cultures, we are going to look at Maya Astronomy and specifically look at the region of Chitsune Itza, and we'll see what we can understand and what we can learn about Maya astronomy from this region. Now this is actually contains a number of different things, and in fact the region contains that one of the Maya pyramids known as El Castillo kind of centered in the image here, and we also can see the observatory El Caracol, which is down a little bit further down here, and of course you can see that there's a number of other buildings here as well that are also other temples and other things related to the different observations that could have gone on here. So first of all let's look at El Castillo, which is one of the primary pyramids of Maya civilization, and could have some relationships to various observations. In fact if you count the steps and counting the very top step, there are a total of 365 steps. Now that's not on each, we see one section here, but there are similar steps on every side, and if you count up those total number of steps, it ends up being 365. Is that related to the number of days of the year? It lines up, but is that the reasoning? Of course we don't know. There are possible alignments with things like the Sun, the Moon, and the planet Venus, so are those related as well? Could those be a part of how this temple and this pyramid was constructed? And one of the more interesting things that come up in one of the prominent things that people go to see is the serpent that appears. Now here we see an image of that, and you can see a serpent head down at the bottom, but at the right time on the equinox you actually get this wavy shadow like the body of the serpent, and as the Sun moves that will seem to move and progress down the pyramid. So the question is again with all of these, are these designed this way? So were these designed to be, or are they just coincidences? And of course we don't have records of the construction as to what each of these things was supposed to mean. So it's certainly very interesting that we have these alignments such as we do with Stonehenge. We also have the number of steps matching 365. Is that just a coincidence? And the patterns that appear just on the equinox, is that, was that planned? And we don't know whether it was planned or it just happened to come out that way because of the alignments of the pyramids. So it's a very good question as to whether or not these are what was intended by the Maya who built this area. Now we can also look at the observatory and the observatory here is El Caracol and that it was built almost over a thousand years ago now. And we can find there are sight lines for positions of the equinoxes and solstices. Now these are very prominent times and we see them across various civilizations that have line things that line up with these. The equinoxes when the day and night length are equal in the solstices. Summer solstice when the sun reaches its highest point in the sky and the winter solstice when the sun would reach its lowest point in the sky. So those are both very prominent. One of the more interesting things with the Maya civilization is that they knew the cycle of Venus very precisely. It's a 225 day cycle which means that five Venusian cycles make eight Earth years. So the extremes of Venus in its position in the sky will reoccur in eight-year intervals and this is something that ties into a lot of the Maya observations. Now we see the pyramid and the observatory after they have not been reconstructed but kind of reclaimed from the vegetation that had overgrown them over time. So they had been lost essentially for a while and then now reclaimed as a major tourist and research area to research to better understand the astronomy of the Maya. Let's go ahead and finish up with our summary. We're looking at the Chitsune-Itsa region which contains a couple of different structures related to Maya astronomy. We looked a little bit at El Castillo, one of the Great Maya Pyramids, and El Caracol, one of the early Maya observatories and we did see how many things there were based on cycles of Venus which is of course the most the brightest star-like object in the night sky. So that concludes this lecture on Chitsune-Itsa. We'll be back again next time for another astronomy of other cultures. So until then, have a great day everyone and I will see you in class.


Countdown for Blastoff. X minus five. Four. Three. Two. X minus one. Fire. From the far horizons of the unknown come transcribed tales of new dimensions in time and space. These are stories of the future. Adventures in which you'll live in a million could be years on a thousand maybe worlds. The National Broadcasting Company in cooperation with Street and Smith publishers of astounding science fiction presents X. One. One. One. The Martian Death March. I've always been interested in lost causes. The revolt of the Scottish Jacobites against England. The last stand of the Cherokee and Sue Indians. And the Death March of the Martian Highlanders in 1997. There's been a lot written about that march. The UN Commission report covers four volumes but the whole story isn't down on paper yet. I know it because I was on that march from the beginning to the end. There's one part of the story that no one ever mentions. The Martian Death March of 97 was led by an Earth man. Maybe you've been over the root of the march. There wasn't any highway there 30 years ago in 97. There was desert. Hot burning desert. I lived at the edge of the Kalmack Canal then with my father. He was a prospector searching the surrounding desert with sonar probe and Geiger counter. Scratching just enough ore from under the Martian sands to pay for our grub steak the next year. I remember he was in the Adams and Digger in the North Quadrant when I came running out that day. There's somebody coming dad across the desert. You sure? I saw them. There are a couple of miles out. Well how many cars? They're on foot. On foot across the desert? Honest dad. I saw them.  No. It was dark against the sand. I don't like that. You run back and get the rifles out. I've got to pull the Digger into the shed. Is there going to be fighting dad? I don't know. I got a whole year's ore piled out back in the bins and I ain't going to lose it with no claim jumpers. You go back to the shack and break out those rifles and see they're loaded. You hear and jump. Dad had three surplus army rifles and a couple of homemade grenades made out of ore cans stuffed with Adams and A explosives. We crouched inside the shack waiting. The shadow of the water tower in the doorway grew longer as the quick Martian dusk settled down over the desert. And there they come Al. There's two of them. What's that on the first ones back? Why, I haven't seen one of those in 20 years. What is it? A one man desert tank. They used to carry water that way before Adamson put out the air still units. There's something funny about that second one. Look, he's all spindly and his head's funny. He's funny all right. Al, that's a Martian. I never saw one off the reservation before. There hasn't been one out in 10 years. I don't like this. Here they come into the door yard. I don't know what I told you. Line up the sights and just squeeze the trigger. Hello, hello there. Now dad? Hello. Wait a minute. What do you want? Water. I need water. Who are you? My name is John. John, huh? What are you doing with that spider? His name is Cantalcar. I don't care what his name is. What's a human doing with a Martian? I'm in the dry bed of Kalmack Canal. Nearly dead of thirst. He probably ran off on the reservation. When our brothers are caged, they seek freedom. Brothers? Those spiders? All living creatures are our brothers. On Mars, as on Earth. Hey, wait a minute. Bert Ostrom at Forst Wells told me there was a screwball hedge preacher over there hollering about letting the spiders loose off the reservations. Let no man call his own. No man, no tribe, no nation. Well, I guess that's you all right.  I don't suppose any harm in you. Fill your tank up at the air still. And you can even have supper with us. We would be happy to. We? What do you mean we? Cantalcar and myself. That spider? Oh, no. I ain't having a Martian sitting down here with me. You come on, though. Thank you, sir. No. Where my brother is not welcome, I cannot go. Look at yourself. I'll get the key to the water tower. Come out here. All right, Dad. And put away the guns. We won't have any trouble from these two. The old man filled his tank at the air still tower. And the Martian went through the ash pile for half-burned fuel brick. When he went to the house for supper, I could see them silhouetted against the fire. The old man with his wild hair and beard and the thin spidery arms and legs of the Martian. Dad. What? Are all the Martians on the reservation? Yeah. Oh, but a couple of wild ones in the mountains up north. The patrol catches a couple every year. Why? Well, they murder people. No, I mean, why are they on the reservation? Because it's the safest place to keep them. They've passed us off. How many are there? Oh, I don't know. A few thousand. They keep dying off. Why? Well, they catch earth diseases. Chickenpox almost wiped out the whole gang of them two years ago. Chickenpox? I had that. It didn't wipe me out.  I was born on Mars.   It'll get cold. Okay. Dad. Oh, what now? Were the Martians always on the reservation? Well, since the Outpost 3 massacre they had been. What was that? Oh, back before you were born, they lived wild in the mountains up north. Were they fierce? Fierce enough. Only place for them spiders behind wire. Yeah, it sure is. Out in the door yard, the campfire flickered at the base of the water tower. The first of the Martian moons had set. The other wouldn't rise for several hours. I could hear the sand peepers out in the desert as I stood there. The old man and the Martian were sitting on the ground huddled close to the fire. It gets cold fast on the desert when the sun goes down. Is that you, boy? You can come up to the fire if you like. My dad wouldn't like it. All right. But I'm not afraid of no spider. No. There is nothing to be afraid of. How come his arms are all skinny? Ask him. Does he talk? Yes. His name is Cantalca. It is, huh? Hello. Hello, boy. He talks funny. It is not my language. Why isn't he on the reservation? You can get in trouble helping spiders to escape. No man has the right to imprison the innocent. They that are enslaved will be freed. They that are in sickness and misery will be comforted. They that are exiled in a strange place will be restored. My dad says the spiders are treacherous, cowardly, murdering savages. That's what he says. Boy, there was a time on this world when there were no earthmen, when the ships and the machinery of earth were unknown. Then the people of the highlands lived in peace. But today they are a handful starving, dying behind the wire. But the reservation isn't so bad. Our home is in the mountains of the north, not the desert. I heard a voice which cried out to me in the desert. Who to your brothers? Did they really call you crazy, John? I have been called many things. You really think we ought to let those old spiders off the reservation? Boy, we die here in the desert. We die in the sun and of the sicknesses you have brought from earth. That's cause Martians are just weak. I'll bet I could knock you down myself. You could. We are a different people. We are not the strength of muscle of earthmen.  You won't get off the reservation. The patrol takes care of all that. They won't let any stinking old spiders out. Ah, even in the minds of children is splanted the poison of evil. How long? That night through the window I could see the flicker of the old man's campfire. He was walking up and down now, shouting, singing hymns verse after verse. His white beard catching the light as he passed behind the fire. The Martians sat slumped over. His thin spindly arms folded across the huge barrel chest that had developed over the centuries as the air of Mars thinned and escaped into space. In the morning I looked out and they were gone. Looking back now we wonder how they did it. The high voltage wire around the reservation carried a fatal charge. The patrolmen in the tower had 50 caliber machine guns. The desert around the camp was mined heavily. Yet at dawn, August 7th, 1997, they broke out. I was down at the dried up canal bed hunting sand peepers when my father came running after me. Al! Al! Here I am. Come on, back to the house. What's the matter, Dad?  What is it? The spiders busted loose. Bird holes from radioed in. They come in here? They're headed this way, the murdering devils.  Six patrolmen when they busted through the wire. What are you going to do, Dad? Wire a keg of Adamson A across the gate. You get in there and get the guns out. I got the rifles and shoved a full clip in each one. Then I slipped a primer fuse on the homemade grenades and lugged them out to the porch. Dad was running lead wires back to a detonator from a half keg of Adamson A he'd set across the gate. There. And that's it. Now give me one of those rifles. Will they be here soon? You can see the dust over the rise. Murdering spiders. What will they do? I don't know. Now make sure you get a good sight, Al. Don't waste any bullets. There they are, Dad. There they come. Wait a minute. Hold up now. I want to get a good shot. Let them get closer. Dad, that's crazy John up in front. There. He's taller than the spiders. You can see his beard. You're right. Oh, that renegade rat. He probably helped them break out of the reservation. Listen, Al. If anything happens to me, you hide out back to the shed. You can hide out in the empty ore bins till they go away. Now you got that? All right, Dad. The spider's shouting something, Dad. Probably a trick. Get down a little, Al. You're in the way. I got them clear now. Right in the head. Up a little now. Got him. Got him, Al. Dad, look out. They've got guns. Get down. Get down. Get out, Al. Get out to the shed. Dad, you're here. Go on. Those spiders are going to rush. Now get going. No, no. I can't let you.  You're here. Get out. I ran back through the house to the shed. Behind me I could hear the Martians sweeping up to the door yard. And suddenly the ground shook. And I could feel the dull concussion waves hit my ears as the atoms in A exploded. I could hear the high, whispered screams of the Martians and the rattle of fragments on the metal roof of the shed. I dived into the empty ore bin and slammed the hatch almost shut. I sat there waiting. Then suddenly a shadow fell across the edge of light. And the hatch slid open on top of me. Boy, I've been looking for you. Where's my dad? What did you do to my dad? He's dead. You killed him. You and those spiders.   They are our brothers, boy. Your father shot without warning. And the fire was returned against my orders. You mean you weren't going to attack us? Our brothers came in peace. They are going home to their mountains. We came to get water for the journey. You mean you just wanted water? John, the Earth Patrol will be following us soon. We must go. And the boy? We'll have to leave him here with water and supplies. No, the Earth Patrol would question him. We need the time. He goes with us. They tore the Adamson air still from the tower and mounted it on poles. They piled our supplies in the yard and loaded them on their backs. And then they started. I marched with the old man up ahead and the column stretched out behind us on the desert. I turned to look back at our house. But the sun was behind it, blinding red. The old man pulled me around as he marched, his eyes fixed on the horizon, where far to the north rose the cool mountains that were the ancient home of the Highlanders. Fourteen of the Martians died the first day. They dropped to the side of the column when they could go no farther and died. But the march went on. On the fifth day we swung wide to avoid a mining settlement, but not wide enough. The miners were in ambush behind a pile of rocks. They shall lead them home, home to the promised rest, home to the mountains. March forward! And the march went on. We wound across the desert in wild zigzags, following the paths the old man had traveled through the years. Only once a patrol plane hovered on the horizon and then shot away. The days went on, the weeks, and the Martians died. They died of exhaustion, they died of the diseases we had given, and they died of thirst. The Adamsons still could produce 27 units of water an hour, no more. And on that, they died of thirst. Here, boy, here's your water. But that's more than the others, God. Take it. It's yours. You're giving me your water. It will be provided to me. He that brings justice to his brothers will drink deep of the water of righteousness. He that drink... drink your water, boy! Across the desert from the Kalmak Canal to Fever Dip, past the towering maces of the Higgins Badlands, across the dry sea bottoms they marched. On the 54th day of the march, we halted at evening. The air was thinner, colder now. The rations had long since been exhausted. I laid out a sleep wrapped in the old man's coat. Early in the morning before sunrise, I woke suddenly. The ground mist that had covered the desert the night before was lifting slowly. I saw the old man standing by the burned-out fire. The vapor swirling around his legs in the cold light of the false dawn, edging his wild beard.  I can't. The end is near. I have led them through the wilderness, dry shard across the seas, and before us lie the mountains. You mean we're almost there? When the mist is taken from the eyes of man, the place of refuge can be seen. You mean the mountains? It's over. We're there. I have led them to their home, and I must go back to the desert. You mean alone? Now. Now even now I hear a voice in the wind. Carry the message to the men of earth. Bring to this new world the message of the old. All beings created in the universe are my brothers. And he that harms my brother, harms me. Boy, you'll be safe. Bye, John. Goodbye. The Martians found him 500 yards from the camp, dead. Now the mist rose, and before us towered the highlands, the tall green mountains in the cool sky. The march was over. Of the 7,000 Martians who started it, 900 were alive. They gathered now on the rise of ground and faced the hills. Their thin bodies wavered as they stood, and some dropped to the ground as they stood there. But there was a light of hope in their large, staring eyes. Most of them had died, but they had died on the way home, and now the march was over. Then the patrol planes were spotted on the horizon, and within 10 minutes they had landed. The Martians stood silently as the squads piled out and set up the 50 caliber machine guns and the petroleum gel flamethrower. All right, you spiders. Hands up and stay together.  Sergeant? Yes, sir? Shoot the first spider that moves and shoot to kill. All right, where's that boy? There was a boy reported. Here I am. Oh. Are you all right, kid? They hurt you? No, I'm all right. John gave me his water ration. Oh, the leader, huh? Well, I've got a warrant for him. Where is he? There. He's dead. Well, just as well.  What are you going to do to them? The spiders? See those transport planes coming in? We're going to ship them all back to the reservation where they belong. You can't. You can't do that. What are you talking about, kid? You can't take them back. They're home. John said they were home. You can't take them back. It isn't fair. I won't let you. I won't let you. I won't let you. Hey, let go of me. Let go. Sergeant. Yes?  All right, now kid, take it easy. I must be shocked. Can't believe he's safe now. Yeah, I guess that's it. All right, you splatters. Step it up. Move along to those transport planes. It's over now. You're headed right back to the reservation. They separated them in groups of 50 and loaded them on the planes. 900 out of 7,000. Insume the first big-bellied ships waddle out on the hard sands and lifted slowly into the air, headed back to the south, flying over the trail of dead and dying who started on the march to the highlands. The march to home. Don't worry about them, spiders kid. We'll take care of them. Come on now, kid. You'll feel better as soon as you get back to civilization. I looked once more at the green mountains towering through the mist. And then just before the motor raced, I saw John. Crazy John cropped up against a dog nut bush in the mountains it placed him. The wind from the south gave the wild hair and beard a rippling life. He faced the hills, the home and rest he had promised his brothers as he led them through the wilderness of Mars. You have just heard X-1, presented by the National Broadcasting Company in cooperation with Street and Smith, publishers of astounding science fiction. X-1 was an NBC radio network production.


Hi, I'm Claudio Zondonella, from the University of Padua that will present the PRDA R-Package. While conducting a power analysis, there is often a narrow focus on the statistical significance overlooking other important aspects as estimates accuracy. To overcome these issues, Gellman and Carlin in 2014 proposed a design analysis to evaluate together with power other inferential risks as the type M error, that is the factor by which the magnitude on an effect might be overestimated, and type S error that is the probability of an estimate being in the wrong direction. We created the PRDA package to allow researchers to conduct a design analysis. The package can be downloaded from the github repository mas pastore slash prda, and allows researchers to conduct design analysis considering correlation or mean differences between two variables. In the package, there are two main functions, retrospective, that allows to conduct a retrospective design analysis where, given a plausible value of effect size and the study sample size, you can define the inferential risks. In the output, we've got a summary about the hypothesized effect, about the study characteristics, in particular with the test method, the study sample size, the alternative hypothesis, and the significant level. And then we've got the inferential risk. In this case, we can see we're not doing really well. We've got a really low level of power, and the type M error is really high. And we also have around 1% probability to get results in the opposite direction. The second function is perspective that allows us to conduct a prospective design analysis for a plausible value of effect size and a required level of power, we can compute the study sample size we need. In this case, for a correlation of point three, we need 84 participants to obtain a power of 80% that is associated with a really low type M error and approximately zero type S error. To know more about the package, you can see the supplemental material in the presentation folder. This is the github page for the menu. Thank you.


The National Construction Code, or NCC, is a performance-based code. It requires minimum levels of fire safety for all buildings. One way to verify that the relevant fire safety performance requirements in NCC Volume 1 are met is to use the Fire Safety Verification Method, or FSVM. The verification method can be used for all building classifications covered by NCC Volume 1. The verification method is outlined in Schedule 7 of the NCC. The verification method provides a robust framework and quantifiable benchmark. The verification method can be used to demonstrate compliance of a performance solution for multiple fire safety performance requirements in NCC Volume 1. The relevant fire safety performance requirements are found in Section C, Fire Resistance, Section D, Access and egress, and Section E, Services and Equipment. Using the verification method, a DTS or another performance solution is the decision of the building design team. Remember, the verification method is just one way of developing fire safety solutions. The level of fire safety achieved using this verification method must be at least equivalent to the relevant NCC Volume 1 fire safety DTS provisions. The verification method sets out a process to develop a performance solution for fire safety. The process includes 12 design scenarios. They are used to determine if a building meets the relevant fire safety performance requirements. Each design scenario must consider one or more locations in the building to capture the range of reasonable possibilities in relation to the threat to safety. The 12 different design scenarios and their associated references are BE Fire Blocks Evacuation Route UT Fire in a normally unoccupied room threatens occupants of other rooms. CS Fire Starts in Concealed Space SF Smoldering Fire HS Horizontal Fire Spread VS Vertical Fire Spread Involving Cladding or Arrangement of Openings in Walls IS Fire Spread Involving Internal Finishes FI Fire Brigade Intervention UF Unexpected Catastrophic Failure SCF Challenging Fire RC Robustness Check SS Structural Stability and Other Properties All scenarios need to be compared to a reference building that complies fully with the DTS provisions to verify that the proposed performance solution complies with the relevant performance requirements through equivalence with the DTS provisions. The design of the reference building should be as close as possible to that of the actual proposed building that the verification method is being applied to and in full compliance with the DTS provisions. The performance solution for the proposed building needs to be equal to or better than the DTS compliant reference building. This provides a benchmark for comparing the performance solutions being verified through using the verification method. The ABCB Handbook about the Fire Safety Verification Method sets out how to define a reference building based on a DTS solution to provide a benchmark for comparison. It also sets out key principles to assist with selecting an appropriate reference building. The process for applying the verification method can be broken down into three key stages. The first stage is developing the Performance-Based Design Brief, or PBDB, as outlined in part A2.24 of the governing requirements. The second stage is developing the Performance-Based Design Risk Assessment. These two stages are then combined to form the Performance-Based Design Report, the third stage. The purpose of the report is to document how the proposed performance solution complies with the relevant Fire Safety Performance Requirements. Note that the verification method must only be used by suitably qualified and experienced practitioners. They must have demonstrated their competency in fire safety engineering, be proficient in the use of fire engineering modelling methods, and be familiar with fire testing and validation of computational data. It is the role of the appropriate authority, most commonly the building surveyor, to make the judgement of whether the relevant performance requirements are met. The fire services will be a participant in the verification method process, regardless of which state or territory the relevant building is located. The verification method handbook is not intended to be a comprehensive guide to fire safety. The International Fire Engineering Guidelines, or IFEG, provides more comprehensive guidelines on fire safety engineering. The verification method can be used in part on a project. When using the verification method in part, every scenario relevant to the performance requirements being addressed by the performance solution must be assessed. Supporting materials to assist practitioners using the verification method have been developed by the ABCB. These include a handbook, supporting data sheets, FAQs and videos. Learn more about the verification method at abcb.gov.au


in the age of NSA spying and warrantless surveillance and these private companies selling your private information to third parties in order to better advertise to you. I think it's time that folks really come out and take a stand unequivocally against the next step that will absolutely erode the privacies that we have left. And that means we have to ban facial recognition software. We have to do it before it catches on anymore. And Jake Johnson in common dreams wrote a phenomenal article explaining how there are more and more organizations calling for an outright ban on facial recognition software because this isn't just a threat to our data and information but now private companies such as Amazon and Apple could use it to crack down on their employees and potentially use it to crack down on union bust. Because we already know that companies like Amazon they will monitor every little minute detail about their employees.  And this isn't me saying this. This is what they said in their union busting video where they influenced their employees to look for things like this, look for signs that the coworkers that you work with are possibly trying to form a union. So this is all laid out in this article that I wanna share because I think it's really brilliant and I want more and more people to actually pay attention to this. Fight for the Future, the company who fought to save net neutrality in 2017. They've really led the charge on banning facial recognition software and I really think that this issue needs to be more important to leftists because if we don't stop this now then once the floodgates open and this is implemented everywhere then we lose that much more privacy. So as Jake Johnson of Common Dreams reports a coalition of more than 20 human rights organizations released an open letter Wednesday morning calling for a total ban on private and corporate use of facial recognition and invasive technology that the groups characterized as discriminatory and too dangerous to exist. While campaigners have typically focused on the civil liberties threats posed by government and law enforcement use of facial recognition the rights groups has lettered the man's that businesses be barred from using the technology as well warning that proliferation of face surveillance in the private sector would have serious privacy consequences for workers and consumers. In a world where private companies are already collecting our data, analyzing it and using it to manipulate us to make a profit we can't afford to naively believe that private entities can be trusted with our biometric information the letter reads. We call on all local, state and federal elected officials as well as corporate leaders to ban the use of facial recognition surveillance by private entities. The group cite several examples of corporations using facial recognition in ways that threaten workers rights including Amazon's requirement that delivery drivers consent to allowing the company's artificial intelligence equipped cameras to collect their biometric data and surveil their activity on the job. The coalition also points to Apple's facial recognition scans of its factory employees. These cases clearly show how private use of facial recognition by corporations, institutions and even individuals possess just as much of a threat to marginalized communities as government use, the letter reads. Corporations are already using facial recognition on workers in hiring to replace traditional time cards and to monitor workers' movements and productivity all of which particularly harm frontline workers and make them susceptible to harassment, exploitation and put their personal information at risk. Several cities across the United States have banned government use of facial recognition but just one, Portland, Oregon, has banned both public agencies and private corporations from wielding the technology to surveil workers and customers. The coalition held the Portland ban as a template for other lawmakers to address the concerns with private and corporate use of the technology. Facial recognition technology poses serious threats to personal freedom. Letting this tool of authoritarian control spread throughout the private sector has serious implications for worker organizing rights and heightens the risk of catastrophic biometric data breaches, Tracey Rosenberg, Advocacy Director at Oakland Privacy said in a statement Wednesday. And I think that the article speaks for itself. You know, as technology advances, we have to make sure that technology is used to the benefit of humanity, not to actually further suppress the rights and freedom of humanity. And it's already the case that other types of new technologies that are emerging is not helping humanity. I mean, drones are a huge example of that. I'm not talking about the ones that you can buy and fly personally. I'm talking about unmanned drones used in Pakistan, Yemen and Somalia. And at first you'd think, well, wow, if we can just conduct this robotic warfare where there's no human casualties, then, you know, that could be great. Maybe technology can revolutionize war so that way it's not bloody. But that's not what happened. We're just using those unmanned drones to terrorize countries and murder innocent civilians in these countries that we are illegally patrolling. It's against international law. And it's happening here at home with other types of new technology. I mean, if you've seen those really cool videos of the robot dogs from Boston Dynamics and the dancing robots and how they can do all these cool things, those aren't going to be used to the betterment of humanity. It's not going to be like, you know, the Jetsons where we have these robot servants who bring us coffees and wash our cars. It's going to be used to terrorize communities. Boston Dynamics already has one of their RoboDogs patrolling communities of color. I mean, this is what we're investing our money in as a country, making sure we further crack down on the civil rights and civil liberties of American citizens. So, I mean, technological advances, they're inevitable, right? As we learn more, we become more intelligent. We utilize different technology and information differently. There's going to be changes and we have to be capable of adapting. The traditional means of authoritarian control, you know, we can't just think about it in that antiquated way. We have to consider the new ways that governments will crack down on civil rights and civil liberties using technology, right? We have to adapt with the times because authoritarianism is adapting with the times and that means that the minute any new technology pops up and it's already being used against us, then we have to take action. We have to speak out before it's too late because again, once facial recognition software becomes widely implemented, you know, by the US government, by state and local governments, by private corporations, it'll be too late if it's widespread. So this is a phenomenal article by Jake Johnson. I would really encourage people to look into this because I didn't necessarily realize how dire the threat was posed by facial recognition software until I was able to grasp some of these concrete examples and it's just, it's unacceptable. We can't stand for it. We've got to ban facial recognition software. I'm 100% on board with this movement.


Missing Children Europe is a European federation that brings together 30 organisations from 24 European countries and in doing so we really try to help parents and children and law enforcement in building the bridges that are necessary to protect children from going missing. We are very happy that Interpol really puts the issue of missing children and child abductions on the table because we believe firmly that we need to work together and coordinate efforts to make sure that children don't go missing in the first place and that when they do they receive the best possible support. I guess some of the findings from this meeting today is that we have to make sure to use the tools that are available in the most effective ways. I'm thinking of yellow notices for Interpol, I'm thinking of the Schengen information system, hotlines for missing children, mediators, child alert systems and all of these tools have a very specific role to play. So ultimately it's really about having a good toolbox at national level that is connected across borders through Interpol, through the different European and international entities that exist and making sure that when children go missing we respond as quickly as possible using the best tool available for this specific situation. I think when a child goes missing it is often a child that slips through the nets of child protection and we need to make sure that we are there with parents, with families, with schools, all of those who are also represented to some extent here today and prevent this child from going missing and being harmed and to focus on the individual child and the needs of this individual child and respond to those effectively and that is I think a struggle that we all face and that we have to continue to prioritise in all our actions making sure that the child is at the centre of our concern.


Hi, I'm Jeremiah Robinson. This is rushing water fisheries. We got an NRC serigrant to build an aquaponics greenhouse here. This is gonna be not like any other aquaponics greenhouse that has been built before. Oh, I've been growing using aquaponics, which is a combination of hydroponics and aquaculture. So fish provide the waste that grows plants, plants clean the water for four years now. And I've been teaching people how to do it for two. And I've sort of built a reputation as the person who has worked with all the issues on growing in cold water. Typically groups around the country grow in warm water with warm water fish. I grow in cold water with cold water fish. And so my barber actually is a very chatty person. He took a business card. He knows Peter who runs this place, gave him my business card and said, he should call me, Peter called me and we hit it off. So we decided to go for something. So Peter who runs the fish farm and his investors were extremely skeptical that there was ever gonna be any money in this. And so without the grant, they would have remained just a skeptical. But as soon as I said, hey, if you're willing to spend 10, we can get you.  He said, all right, we'll do that. So this, no way this would have happened otherwise. This is a flow through trout aquaculture facility. So it's spring fed trout live in the ponds. The water runs through the ponds and then goes down into the creek, which ends up in various rivers and waterways and in the rock river watershed, I think is where it ends up. So the things that make this project unique and from a hydroponic greenhouse perspective, this is absolutely minuscule. This is tiny. So this is just an experiment. We're just checking to see if this will work. What we're hoping will happen is two things. One is we'll be able to grow vegetables using this water, which has been fertilized by the trout that we have here on site, which is an experiment. We don't really know if it'll work. It's been tested at a university level, you know, in controlled lab conditions, but on an actual farm, it has not been tested. We're gonna try it in a few different ways. We have a few grow beds that are built as three in parallel, so we'll be able to grow in three different ways. There's gonna be some more grow beds built also in three in parallel, so we can try a variety of different growing methods using three different sources of nutrients. We're gonna use the water from the fish ponds. We're gonna use digested pure fish manure. And then we're gonna grow using standard hydroponics as a control. So this will be just a double poly inflated greenhouse, 30 by 50. We might experiment with some unusual heating schemes using some of the water as a heat sink. Other than that, the main other thing that we're doing is we're hoping to test whether we can remove a significant amount of nutrients from the water. If we can remove a lot of nutrients for the water, that'll resolve tensions between farms like ours and the DNR because they can do something that's profitable while also removing their pollutants. So that's sort of a big deal if it works. We don't know if it'll work. That's why we're trying it. Phosphorus is the primary nutrient, both dissolved and suspended phosphorus. Yeah, so total and dissolved phosphorus.  We wanna remove both of those. We also wanna remove as many solids as we can because they're regulated on solids. There's talk about nitrogen regulations coming down the line at some point and so we're concerned about that. They have ammonia regulations, but they're not anywhere near their ammonia regulation levels. So, you know, I have friends in the wastewater world and they're basically all of the mind that there will eventually be a no added nutrients rule for everybody. So this is gonna be a place that we're gonna end up at some point. So that's what we're hoping we'll accomplish here. At least being able to verify whether one can do these things. If it also proves to be profitable, then we may end up scaling up to be not miniscule anymore and actual grow significant quantities of vegetables.


Hi, my name is Kim McMillan and I'm the editor of a new anthology on the history and legacy of the Black Arts Movement, featuring the writings of burial poets along with over 80 other contributors from across the country. This 500 page collection Black Fire this time, oh, I would upside down. This 500 page collection Black Fire this time provides a new generation with the important voices of the Black Arts Movement and beyond. On July 16, 2022, the San Francisco Public Library will have an online book event to showcase these wonderful writers. I hope to see you there. Thank you.