The weird circle. In this cave, by the restless sea, we are met to call from out the past stories, strange, and weird. Bellkeeper, hold the bell, so all may know we are gathered again in the weird circle. She is? And we are glass. The world's on about. We'll drop live and take them on. Ah, I see. Turn back! Take out what ship she's from. They're too far, Captain. She's American now. Eh? They'll soon be on them. Mate, if the captain's with them, send him up to my cabin. Aye, aye, sir. Take him away, sir! I've been at sea in the longboat for two days when you sighted us. Just about done in. My friend here, Mr. Allen, was the only passenger to survive.  Aye. What cargo were you carrying? Cotton, a little hemp, and some timber. I see. And that was all? Aye. Did you happen to pass some drift, Captain? We did, but nothing you just spoke of. Would you care for a little more, Grog, gentlemen? Thank you. And you, sir? Yes. Yes, please. No, we passed nothing adrift that you mentioned, but we did hoist aboard something rather strange, you might say. It may not have come from your ship, though. It could only make out the port of embarkation and the date. Charleston, South Carolina, August the 2nd, 1881. That was our port. That was our date of sailing, Captain. What was it you took aboard? Two bodies. Passengers, I suppose. A man and a woman. Rather unusual though. The woman was in a coffin. A long, long box. You seem startled, Mr. Allen. Aye, I am. And the man? It's the strange part. He was lashed with a coffin by an inch-thick rope. From your reaction, Mr. Allen, I presume you know something about the box. Yes, I'm afraid so. Then, Mr. Allen, I suppose you relate the entire story. Very well. Truth, Captain, I had intended telling no one. You see, as Captain Hardy told you, the dead man had been a friend of mine. I'd hoped the sea would keep its dead. The man whose body you found tied to that oblong box was an artist from New York. His name was Cornelius Wyatt. As I remember, Wyatt had been married only a few months when I met him quite by accident. It was at our port of sailing Charleston. I had been on board only a few minutes when I heard his voice calling me by my first name. I was quite surprised to see my old friend. Edgar! Edgar, Allen, hello there! Wyatt! Wyatt, Heaven's man! How are you? Oh, it's good to see you. How long has it been? Oh, good year since I saw you last. At least. Let's see. Yes, since 1877. All the places to meet you. Tell me, Wyatt, is your wife aboard? My wife? Oh, yes. Good. The more people have raved about her astounding beauty to me than I could possibly count. I've swarmed to see you with my own eyes. Where is she? I'm sorry, Edgar. I'm afraid that would be impossible.   Well, then later I'm sure... No, no, no. Really, I think she'll remain in bed for the rest of the trip. Her health wouldn't permit it. Oh, come, Wyatt. You wouldn't cheat me of this chance to meet your beautiful wife. The C.L. do her good. Or is it because you're jealous of such beauty? Please keep that to relax for yourself. My wife's appearance should be of no concern to you. Oh, but, Wyatt, I was only joking. I meant no harm. Your humor has not appreciated, Mr. Allen. Well, forgive me. I'll show you I meant no harm.  Yes? Uh, that there boxy yours. You're having it shipped in the hold. Con? Found it, man. How many times was I giving these instructions?  It must be put in my cabin. Must I tell the captain himself? Sorry, sir, but there's hardly any room for such a large box in here. I don't care how little room there is. That box will go into my cabin if I have to move it there myself. All right, sir. Sorry, sir. Founded fools. Must I beg them to carry out my instructions? Is... Is that the box? Uh, excuse me, Mr. Allen. The clumsy fools may drop it. I'd better watch them. I'll see you later. Though at the time I was surprised by my friend's sudden outburst, I passed it off to temperament. After all, he was an artist. At the moment, I was more concerned over the... the oblong box than over my friend. It bothered me quite a bit. I couldn't find a reason for his being so overwrought over the placement of a cumbersome large wooden box. And furthermore, I couldn't find a reason for his use of one that shape. It was about six feet long and two-and-a-half feet wide. To me, its contents were a mystery. At first, I excused it as containing a number of its precious paintings. About three days out of Charleston, I met Wyatt again. He was walking about the deck. As I approached him, he cordially offered me his hand. Hello there. Hello, Wyatt. Uh, Edgar, I... I believe I owe you an apology. Apology? Yes, you must forgive the way I acted the day before we sailed.  Oh, think nothing of it. Here, let's sit here. That's it. I... I'm under a severe strain, Edgar. Perhaps I should tell you. You are my friend. I... I should tell someone. Of course. What others have told you about my wife is true. She is beautiful. Very beautiful. I'm afraid too beautiful. Yes. I was one of many, many suitors. I was the fortunate one. Why, I don't know. She doesn't love me, Edgar. Are you sure she doesn't love you? Yes, I'm sure. Very sure. Since I've been married, she's done her utmost to make me jealous. She knows how I worship her beauty. She knows her power. Men have always loved her for what they still do. I know, Edgar. I'm suffering because of it. There are men today who... who would give anything for my wife's hand. Anything. She knows that she taunts me with it continuously. The way she looks at me, laughs at me. You're in love with her? Desperately. You would never give her up? Never. And she knows this? Of course. That's why she taunts me. Well, perhaps if I could see her. No, no, no. She's, she's still ill. Ill. I'm sorry. This trip. You know why I'm going to Canada? Do you know why? Paintings? I'm taking her away. Away from all those men. She'll learn to love me. I'll make her. I'll keep her beauty for myself. Perhaps. Perhaps this is an extreme. Extreme? No. No, it's the only thing to do. You don't know the torture I've suffered. Well, let's talk no more about it. I, I feel better. As you wish. You will keep my confidence. Oh, without question. Now, how's your painting coming, Wyatt? I haven't touched a brush in months. But the canvases you brought aboard, weren't they yours? Canvases. I suppose they were in the large box you have in your cabin. Why do you suppose that? Well, because of its unusual size. That box doesn't concern you. It's none of your business. I didn't say that I... Don't ever mention that box again. I forbid you. You hear? Don't ever mention that box again. Perhaps I've been too hasty, Captain. Perhaps the man just doesn't well physically. Well, the box, it could contain something unimportant. I think I was overly curious. That's all. I've known him for a long while. You know, he's always appeared perfectly normal before. And everything's been all right lately? For the past few days, yes. He's been perfectly cordial. I think perhaps it's best we pass over the entire matter. There's probably some logical... some simple story behind what's happened. Yeah. More port? No. No, no thanks. I think it's best I be getting back to my cabin. Looks as though there's an unhealthy storm blowing along the coast. I'd best get back. Oh, I noticed it getting a little rough. Will it hit us? I can't tell yet. Well, good night, Mr. Ellen. Perhaps you'll join me at dinner tomorrow night, huh? Thank you, Captain. I'd be... Listen. What? Shh. I thought I heard... Listen. Again? Nothing, I... I hear nothing. The wind, that's all. The events have made you a little nervous, I suppose. No, wait. I'm sure I heard something strange groaning or something from out there. Open the door. It's probably the ship's captain. Here, quickly! The passageway's black. The steward probably took the lantern to... Listen. Again? Hear it? Oh, yes. Yes, I do. It came from the darkness down there to the end of the passageway. Somebody's in trouble. Who hears the safe room at the end of the passageway? I think, quiet. The first two are empty. Well, come along. Pull your cabin door closed. I'll get a lamp. The darkness... No, no, I know my way. We may need the darkness. Very well. Okay, close. The first two, you say, are empty? Yes.  It should be. I'll stand here a moment. I'll listen again. A knocking. Tapping. I'll try this clutch. I'll open it as quietly as possible. There's no light under the door. Stand back. Easy now. What? Blast it. It's locked from the inside. Well, someone is definitely in there. I am going to knock. Now, listen closely. Someone is in there. You heard it? Hello in there. Is that you, Wyatt? This is Alan. Anything wrong? Hello there. No answer. I don't like this. Open the door, Wyatt. It's the ship's captain. I'll be forced to break in. Here, help me. Help me as I count three. Go on. One. Two. Ready now? Three. Wait. There's a lantern by the port. I'll strike a light. Stand here and... Empty. The room is empty. For a moment, both of us stood there in the gloom of Wyatt's cabin. We were sure somebody had been there, but a moment before, we'd heard them. And now the cabin was apparently empty. The door had been locked from the inside. Nobody could have left the room without us seeing them. Then suddenly Captain Hardy pointed to the right wall of the cabin. There in the dimness of the gloomy shadows. Alan. This cabin and the one beside it are rejoined. Now, let me get the light and see if the adjoining door has been opened. Whoever left left in a hurry. Here. Here, Alan. Give me a handle. I can't reach the lantern. Blast it, Hardy! All right. All right. Just doubled over this blasted box. My hand. The oblong box. Excuse me, gentlemen. I didn't mean to intrude. Wyatt. May I come in? There's another lamp at the table. Allow me, Captain Hardy, but... Where did you come from? How did you get into the passageway? There. That's better. Mr. Alan, I have been walking my wife on deck. May I introduce you? Oh, you may come in, Marjorie. Marjorie, this is Mr. Alan. I'm the one who desired to meet you so much. And the captain of this vessel, Captain Hardy. How do you do? Do you do. And now, gentlemen, may I ask the reason for your, uh, breaking in? I, uh, we heard a noise. To cry. We thought it was from your cabin. That would have been impossible. There was nobody there. Are you sure? We heard... Of course I'm sure. There was nobody here, I tell you. Gentlemen, if you don't mind... Now, why it? Before we go... Yes, Mr. Alan? Ask your wife to... To remove her veil. Marjorie, would you please oblige the gentleman? My wife, Mr. Alan? You're... Your wife? But she is beautiful, isn't she? I... Yes. Yes, she is. You, too, seem stunned. Quite. Um, Captain Hardy, come. Thank you, Wyatt. One moment, uh, Captain Hardy. Yes. Would it be too much to ask for a new cabin door? This one seems to have suffered slightly. I'll, uh, I'll see to it. Good night, gentlemen. His wife. Did you see his wife? Yes. She was hideous. His rave about her beauty. Well, he's mad, Captain. Hopelessly mad. She was horribly ugly. Yet... Yet she was familiar. I've seen her before. I... I know it. Where? Did you notice the door leading to the adjoining cabin? No. It was open slightly. Someone could have left Wyatt's cabin and reached the passageway through the empty one next to it. Hardy? Yes.  Covered with blood. Well, you must have cut it yourself when you... When you fell. Yeah, let me wash it off. No. No, it isn't cut. It's put that blood. It isn't mine. Well, then where did you... The oblong box, Mr. Allen. The oblong box. It was behind this terrible mystery, neither of us knew. We would inform the police as soon as we put a port. From then on, I saw nothing of Wyatt. Two days passed since the incident in his cabin. Now on the second day, Captain Hardy warned all the passengers of what was in store for us. We were forbidden on deck, confined to our cabins. We were being blown out to sea by a furious hurricane wind. On the fateful night, I was lying fully clothed down my bed. The sea was sickening. The ship was yawing terribly with each plunge. I was expecting the worst at any moment. Then suddenly, above the roar of the terrible gale, I heard a strange sound coming from the passageway before my cabin. I was a little bewildered at first. For a few moments, I sat there on my bed wondering. And then... Edgar! Edgar! Mrs. Wyatt, do you hear me? What is it? I need your help, Edgar. I need your help!  You're here? Get out of the passageway. It's dangerous. The ship leaves. Please open the door. You must. You must help me. You're my friend, Edgar. Please. Very well. Good heavens. My box. I've got to get it on deck. I've got to. The ship may break into it any moment. Please. Please help me. I can't manage it alone. Please. You must be completely insane. The storm is too high.  You'll be blown overboard. Just the door. You don't have to go on deck. I have some room. I'll lie myself to the stairs. I'll be safe. Please. Yes, but your wife. You can't leave your wife alone now. Go back to her. Snap out of it. Stop the stairs. Please, Edgar. You're my friend. Please, Edgar, please. Very well. To the top of the stairs. The other end. Take the other end. That's it. Hurry. It's heavy. All right. Here. This way. Up these stairs. Here. Don't drop it, Edgar. Don't drop it. All right. Just a little further, Edgar. Just a little further. This is as far as I go. Oh, thank you, Edgar. Thank you. You don't know what this means. Now, go back to your cabin. I can't. I must get my box on deck. Then I leave. No, no, please. One other favor. Hold this hatch while I push the box out. I beg you. Why, it tears your head. The water will swamp us. Listen to it. Please, Edgar, please. Well, then, stand back. I'll open the hatch.  It will be swamped. I haven't seen Wyatt. You'll never make it. Wyatt, watch out.  Come back. Here, help me. Help me. Close it quickly. What in thunder are you doing? Wyatt. Wyatt is out there. He took the box. Oh, heaven, she's done for. It's too late to help him now. Great. We're going to have to abandon ship. She's great. A starved life boy, they were. Make for it. Yes, but Mrs. Wyatt, she's below. She'll be killed. I'll get her first. The starved boat, Edgar. The starved boat. Mrs. Wyatt, to the boats. Mrs. Wyatt, we're sinking. Hurry this way. Run. No, wait. In the name of heaven woman, come on. Quick. No time. Mrs. Wyatt. Mrs. Wyatt. Only she disappeared before me. Water gushed down the passageway. She was swallowed by it. I struggled forward and made my way to the starved boat. I jumped for the swinging davit and lowered myself as speedily as possible into the longboat. Captain Hardy joined me with three others of his crew. And then, just as we pushed out from the trembling mass of wreckage, I saw it. Hardy did too. Standing to aft, I saw Wyatt. He was binding himself tightly to the... to the oblong box. I stood there for a moment. I thought, laughing, that in one brief instant he was gone with a ship into the sea. And that's all? Yes. I see. Would you gentlemen be so kind as to follow me? This should prove rather interesting. This way, gentlemen. Captain, when did you find this box? Yesterday afternoon. In here, please. Mr. Allen, hand me that lantern and watch the stairs, please. They're rather sharp here. Me done. Now, ordinarily, we would not have bothered with a floating body. It's generally some poor wretch from a wrecked vessel. However, due to the box and the peculiar circumstances, I thought it best to hoist it on board. Yes, but the decomposition... Oh, the saltwater held preserve them for a while. I thought we could reach New London safely with them. However, since we were blown off our course by that wind, it'll be a good day and a half before we reach land. I'm afraid I shall have to commit them both back to the sea. Mr. Allen, swing that door open, please, will you? Over there. In that corner. Yes. Yes, that's the box. Captain Hoddie, would you kindly hold the lantern while I lift this blanket? Certainly. Is this the man you call Wyatt? Poor devil. Hardly recognizable. Yes, that's Wyatt. And now, Mr. Allen, if you would give me a hand with the top of this box, it had been firmly nailed. However, we tried it loose when we took it aboard. Just pull that in carefully. Good heavens. Even after two days at sea, death did not destroy that wax and beauty. It's almost impossible. Still so beautiful. You notice the wound over the heart. Yes. Mr. Allen, that was the beauty Mr. Wyatt talked of. Well, of course, this must have been his wife. But wait, the other Mrs. Wyatt. Yes, of course. I knew I'd seen her somewhere before. The maid. Their personal maid. Yes, now I remember. She tried to tell me something before she drowned. Wyatt murdered his real wife. If only we had done something sooner. Murdered his wife? How could he? Why? Insanely jealous. Terribly jealous. To die with her would be better than to live with her and her beauty. He planned to murder her on that trip when I saw them stowing that box. Remember the groans? She was murdered that night. The blood. It was fresh. Remember the tapping we heard as he nailed her in this coffin? I... Hardly, I think we'd better leave. Yes. Yes, Wyatt. Your wife is very, very beautiful. We have brought you the story. The Arblon Bus. Bell Keepers.


Hello, my name is Maria and I'm the Developer Advocate at BotCube and today we'll be talking about how BotCube can empower your developer productivity with their new ArgoCity integration. Just a little bit about me, I'm a Developer Advocate at Cubeshop and I work on the BotCube project and BotCube is a collaborative Kubernetes troubleshooting tool. I have a background in Industrial Systems Engineering which will come into play a little bit in this talk. I also have a background in Software Engineering and Developer Relations. So I just want to make sure everybody's on the same page about what GitOps is, maybe clicked on this by accident, you have no idea what GitOps is, but just a quick refresher. GitOps is an operational framework that came from DevOps and it's based on four main principles that it's declarative, that it's versioned and immutable, it's continuously reconciled and the apps are pulled automatically. So that's all you need to know for this talk. So here are some organizational challenges of working with GitOps. Like anything in the cloud native landscape, it's going to be very complex and because of that complexity it's very difficult to audit and get to the source of a lot of these issues because if you have multiple layers of complexity and people having access to different things, it can be very challenging to find the root cause of a lot of your issues. So it can be very difficult to troubleshoot quickly and get back up and running. Additionally, it can be very challenging to scale, so Argo and GitOps and all these tools require a lot of technical expertise, so it can be very difficult to scale and it requires a lot of technical requirements for every workflow that you build, so it can be very challenging to scale for the average engineering team. And alerting and monitoring can be challenging as well, so if you don't have a good setup, it can be very challenging to filter those alerts, so not everybody needs the same types of alerts. It can be very challenging to get the right amount of information at the right time. And this goes along with the last challenge about context switching, so a lot of times people are using these GitOps tools in tandem with a tool like GitHub or GitLab and most of the time communication is not solely in GitHub, so it's required to go back and forth to get any proper alerting or when you're managing issues, you have to go back and forth between GitHub, your communication platform tool to check on your team and whatever workflow you have, whether you're on-prem or working with one of the cloud providers. So here are some of the challenges. In the core of our presentation, developer productivity, and at its core it just means that its developer productivity just means efficiency and effectiveness where software developers accomplish their tasks and contribute to the development process, so just measuring the output of developers in short. So how do we measure it? There's lots of different ways you can measure it, but for the sake of this talk, we're going to be measuring it based on three different criteria. Number one is deployment frequency, which just means how often is code deployed to production. And this can be representative of the health of the engineering team, so if you're able to have faster releases, it typically means that you have a good CICD pipeline and CICD process. Additionally, your mean time to recover. So it's the average time it takes to recover from a failure or an outage. And if you have a shorter mean time to recovery, it usually means that your team is more resilient, more reliable, and more dynamic. And then lastly, your lead-slash cycle time. So how much time it takes to go from the beginning of a task to the completion. So in our team, it's like measuring sprint cycles. So how long does it take? How many mandates does it take to get a new feature out to fix bugs and all that sort of thing? Here's the current state of things. After working in this space for the past two years and talking to a lot of developers, I mean, everybody knows that Kubernetes is very complex, but then when you add an additional layer of GitOps frameworks and having to follow and use different tools, it can be very challenging for the average app developer who just wants to make sure their apps are healthy. So when you add all this extra load, and frequently, most of these companies don't just use Kubernetes bare metal or Argo bare metal. It's usually in tandem with multiple different tools. Maybe you're using Argo and Helm. Maybe you're using Prometheus, Helm and Argo. Or maybe you're using AKS and EC2 all in one place. So it could be very challenging. I feel like this tech stack just gets longer and longer. So there needs to be a solution for developers who are just really just trying to keep their apps up and running. And then also for the platform engineering side of what happens when your team is not as available, do your developers understand what the work that you're doing. So what does that communication look like? So when you add complexity, it's very communication-tensive breakdown. So this is where Argo CD comes in. So in short, Argo CD is a declarative GitOps continuous delivery tool. It allows DevOps professionals to simplify and automate their deployment processes. It's really great because you have this nice UI that you can visualize the help of your apps. And it really helps reduce errors by being able to visualize what's going on in your infrastructure. And it helps simplify different deployments. So that's just Argo CD at its core. And what is Bokube and how does it help teams improve developer productivity? So Bokube is a Kubernetes troubleshooting and monitoring tool that allows developer teams to work more efficiently. And how it does that is by allowing you to act, to receive and act on your events in the same communication platform. So you're able to use Bokube in tools like Slack, Microsoft Teams, Discord, and Mattermost. And you're able to have an insight to that process without having to, your troubleshooting process without having to context switch. So you're able to collaborate with your team and give everybody the same amount of context that needs it. So you're able to filter your alerts, you're able to run automations and have an insight to what's going on in your cluster without having to be a Kubernetes expert, without everybody having to have the same open access to the cluster. You can have it in a gated environment where people can just watch notifications. And it's really great for reducing manual processes because when I'll talk about it a little bit more later, it allows you to audit. So you're able to continuously improve on different steps that you do over and over again when you run into the same amount of problems. So just more on overview. So I talked about how you can receive and act. So Baku is split via source and executor plugins. So what this means is these source plugins. So a source plugin can be like Kubernetes events, Prometheus, and it watches all these alerts and hooks it right into your communication platform tool. And then the executor side allows you to act on those alerts that you got. So one great example of working in tandem. Let's say you're using the Argo CD source plugin and you see an issue. You're able to act on that alert by easily running a kubectl command all within your same Slack platform without ever having to change context and switch screens. And through the audit log that I mentioned briefly, you're able to see all that information in one place and get an insight on the performance of your team and who's doing what and having access to your cluster at all times. So how they work together. So without Baku, Argo's notification setup can be a little clunky and a little hard to get set up if you're not super familiar with the Argo ecosystem. So what Baku does is help simplify that process. It helps simplify the configuration. So making configuration changes. You're able to access the Argo CD UI right from your communication platform tool. You can filter your notifications much more easily. So you can divide by channel. So for example, your front end channel does not need to see the same level of Argo CD alerts as your back end channel. And it allows developers who may not be as Kubernetes native or Argo CD native to still get the information that they need to keep their apps healthy. So here is an example of what the plug-in looks like in Slack. So it'll show you that an app has been created. It'll show you like the sync status and it'll keep you updated on the health of your app without you having to touch anything. So then you can either open the repository or view the UI or run commands directly against that app. So this really streamlines a lot of the manual steps that go on in building Argo CD pipelines. And it gives everybody in your engineering team, regardless of their Kubernetes expertise, access to the information that they need to solve problems quickly. And I think visibility is super important. And that's what mainly improves developer productivity. What you see, you can act on. So a lot of times developers get bogged down by things that they don't understand. So they get lost in the weeds. And BotCube kind of helps shine a shining light onto that deployment process so they can just focus on getting their apps deployed and building interesting code. So in conclusion, BotCube's Argo CD plug-in can help revolutionize your organizational efficiency. So it can really streamline your deployment process by helping developers stay on track and stay up to date on all of their Kubernetes notifications without being overwhelmed. And it kind of follows a belief that software tools should enhance, not hinder productivity. So when you have this ever-growing tech stack, it can be more of a hindrance than a help. So with tools like BotCube can help simplify it and help you work with those tools in tandem. And then finally, by adding automation, you're able to focus on innovation and not just your deployment complexities. So I'm going to get started with the demo. So here we are at our Argo CD demo. We have a application guestbook that we created for this demo. You're able to run a kube control get and a kube control describe. So you're able to see the health status of your application. And then if you want to see more information, you can have the describe log right in your Slack channel. If we want, we can open the repository just to see all of the different template apps. So that's really great for easily navigating different steps of your troubleshooting process. Next, if you'd like, you can view it directly in the Argo CD UI. And there you can get that visualization that I talked about earlier in the presentation. You can sync up your apps and just start getting playing around in the Argo CD UI. And here we're going to play around with what those different changes can look like in Slack. OK, so you see that we have a guest, our guestbook app has been successfully synced. So let's also see what happens when we do some sort of error. What we're going to do is we're going to see, OK, that we have a pod error. And then we're going to delete it. We're going to delete our pod and see what happens in our Slack channel. So let's let that sync. All right, so we have a new version of our app up and running. And that works instantaneously. So this is great for when you have issues and you can see that you're both working on your cube control and your Argo CD all at the same time. And that's part of that interoperability. And it gives you insight on all the errors that occur. So that is the gist of the Argo CD app. And then you can easily delete your app guestbook, which I'll do right now. And then go back to Slack and it says it's been deleted. All right, perfect. Get started with the demo. OK, thank you so much for watching my talk and listening to my talk. You can scan this QR code to get started with Bokube today. It's free. You can get started. And we work with Slack, Microsoft Teams, Discord and MatterMos. You can use it on-prem or with any of the cloud providers. And if you have any questions, you can reach out to me in the Bokube Slack or on Twitter. And yeah, thank you so much for your time and I hope you guys stay productive.


Today we are going to discuss the topic monotonic and non-monotonic reasoning in AI. At the end of this session, students will be able to demonstrate the difference between monotonic and non-monotonic reasoning. Monotonic reasoning involves techniques for reasoning with a complete, consistent and unchanging model of the world. It is used in conventional reasoning systems. AI reasons to finally deduct certain things which are required in the form of inferences. Information is complete with respect to the domain of interest here. All facts that are necessary to solve a problem are present or can be derived from those that are. The only way to change is to add new facts. For new consistent facts, nothing will ever be retracted. Therefore, this system is consistent. The methods we adopt for monotonic reasoning are represent all your facts in a predicate logic, put them into a particular form which is maybe a clause form and then solve the particular problem with the help of resolution to get inferences. A natural deduction is another form in which we deduce or find out a derived representation to represent our goals of reasoning. Logic programming is another form. Here we may use predicate or propositional logic once again and adopt particular systems so that an adaption is seen in this orientation to provide our goals. We may go for forward and backward reasoning environments wherein we change forward till we find a particular error and then we may backtrack or go backward till we achieve a particular path which is reasonably good. The last form is matching of the particular aspects. It may be matching of predicates, it may be matching of normal forms which we are using in symbolic representations. What do we now expect under non-monotonic reasoning? Non-monotonic reasoning deals with problems with incomplete and uncertain models. They are used to reasonably establish complete, consistent and constant models of the world which is not available. We resolve inconsistencies and this is done by rejection of facts. It is required to observe how revision progresses downwards into a particular environment till reasoning is established. Inconsistent beliefs are singled out and separated. It illustrates problems posed by uncertain, fuzzy and constantly changing knowledge. At a given moment, a statement is believed to be true, false or not believed at all. The key issues for non-monotonic reasoning arise and they are 1. How can knowledge base be extended to allow inferences to be made on the basis of lack of knowledge? Here we need to make a clear distinction between the existing facts which are supplied to us. Any information that depends on the lack of some piece of knowledge is non-monotonic inference. Non-monotonic inferences may be defeated by the addition of new information that violates originally taken assumptions. Therefore, we may have to redo our assumptions if we want to continue these particular aspects. The second assumption is how can knowledge base be updated properly when a new fact is added to the system or when an old fact is removed? Keep track of the proofs or justifications that we have encountered up till our present state. Find all justifications that depend on the absence of a new fact and those proofs that can be marked as invalid. Non-monotonic inferences may be defeated by the addition of new information that violates originally taken assumptions. Now our assumptions have to be modified and we go ahead to reason our particular environment. The third aspect is how can knowledge be used to resolve conflicts when there are several inconsistent non-monotonic inferences that can be drawn? Here we see that normally contradictions are more likely to occur than conventional logic system. This addition adds to more computational power to be used and portions of knowledge base are locally consistent but they seem to be globally inconsistent in many purposes. The methods for non-monotonic reason can be actually felt when we look at the need why we require this to happen and under what conditions this has to happen. We use non-monotonic reasoning to perform default reasoning. We also go to draw conclusions based on what is most likely to be true avoiding the facts that will never be true. The approaches we use are non-monotonic logic. These are systems that provide default reasoning in which the language of the first order logic is augmented with a model operator which is read as inconsistent. When we consider default logic these are new classes of inference rules to be introduced to extend plausible extensions to the knowledge. Non-monotonic reasoning may be of the type abduction that is arriving at a conclusion not licensed by rules of standard logic. This may be wrong but a true guess method may lead us to a near miss to our particular final reasoning result. Inheritance is using values from a prototype to the individual entries that belong to a class. Therefore using inconsistent knowledge or incomplete knowledge accepts these two formulations. A monotonic which will give you a more conventional method of reasoning and a non-monotonic reasoning which will require efforts to develop our particular reasoning. As an example of non-monotonic reasoning let us suppose to take an example that a purchasing agent is investigating purchasing holidays. A resort may be adjacent to the beach or may be away from the beach. This is not symmetric because if the resort was adjacent to the beach the knowledge provider would provide specificness about this particular location. Thus it is reasonable to have a clause if not on the beach implies away from the beach. This clause enables an agent to take an inference that the resort is away from the beach if the agent is not told it is adjacent to a beach. Thus the facts play an important role to show that this combination becomes close to the miss but is not the exact what is required. This is non-monotonic reasoning aspect. For our references we have used the following texts. Thank you.


Yeah, I thought it was a good good day of work You know against good football team. They had a really good year last year a lot of good players You know, it's a tough scheme to go against who's good work for our our rules both in the run game and past protection And it's a good change of pace during camp. You're going against somebody different It brings a little bit different energy level, but for the most part. I thought it was a really good day They did a pretty good job, I mean obviously I haven't watched the tape yet, but For the most part, you know, I thought they were solid in the run game I'm sure we'll have some things to clean up when we watch the film But you know overall, I thought the effort was really good Really, I mean, it's just this is practice, you know It's our chance to you know, see what our guys can do to test where we're at to go against a great player But for the most part, no, it was just you know, we have our reads and our progressions and in an environment like this You you try and you know test those rules and just see where you're at in terms of knowing what you need to do Yeah, I mean You know, I think I've been around long enough. I know that you just have to Can't look too far in advance, you know, you can't think that because you had a good practice one day We're gonna be you know, a really good offense. You got to stack them You got to you got to put in that work every day You've got to gradually get a little bit better and you know, I hope we took a step forward today It felt like that will obviously watch film and you know watch a practice tape and see where we're at But certainly felt like we took a step forward and we need to you know, continue that as we move through camp Feel great, you know, my body feels really good. I feel like I've got a good routine and plan to you know, keep my body healthy and You know, I feel really good You know, I thought I thought they showed us a few things I was texting with Brian Flores yesterday Brian and I were teammates at Boston College and so I was texting him just saying I was excited to come down. He's like, I know you've seen everything So I put in some new stuff for you I was like, all right, man, don't treat me like 2003 scout team at BC, you know, like but they had a few You know a few different things out there today They stress you defensively with with your rules, you know, and they do a really good job and they got us a few times and We certainly, you know, had a few on our end to that we did well But this is what this time of the year is all about, you know to see what we can do what we can't do and what we Need to clean up Listen Brian was Brian was kicking my ass when I was on scout team, so he was physical He was a good player back then but as soon as he went to New England as a scout, you know right after just how professional he always was and He was quiet hard worker Great teammate, you know was was good to me, you know as a freshman young kid coming in He was great to me and I'm happy for him.  Does that register at all like? I Don't know. It's it's cool. You know, it's cool.  I think these things are huge every practice You know that we have is an opportunity to get better particularly when you're going against a really good football team like we did today You know, that's a great opportunity to you know for me to get better And so, you know, I was I was excited about it I'm in the past again. I'm sorry. I got more questions. Sorry How was the time in the past again against the competition after being on there? It was pretty good, you know for the most part. I thought timing was pretty good There's definitely a handful of things we need to clean up, you know, and we've got to watch that But for the most part first time going against a different unit different scheme all that kind of stuff I thought it was pretty good You know every day Every day I watch our running backs and I watch how they Condition and run and their technique and those things and I watch Mike Davis and what he does and I try and do the opposite You know, I just go out there and I don't take anything from it and crime do the opposite of that and just do my own thing So thanks Mike I think there's been improvement I think we got a long way to go for sure But I think there's there's definitely been improvement. We need more of it. You know, there's no doubt about that But I certainly think that that we've gotten better, you know in the first couple of weeks here