Stand by for crime. Hi Chuck Morgan speaking. You know, being a newscaster on a radio station the size of KLP puts me in line to meet a lot of interesting people. Like Joe Stanley for instance. Joe was a scientist. He'd been employed by the government to work on some strictly hush-hush project, the hydrogen bomb I think. He came out here to the coast once or twice a year to huddle with airplane factory executives etc. And usually on such occasions he bunked with me. Last week Joe was here for a couple of days. Thursday morning Carol Curtis my secretary and I drove him out to the airport to catch an early plane back to Washington. We said our goodbyes. Watch the plane taxi down the runway for its takeoff. Well Glamopus, let's get started back. No wait Chuck, I want to see the plane take off. Why?  I don't care, I want to see it just the same. And besides Joe wouldn't like it if we left now. Listen if I know Joey's sound asleep by this time. Flight 183 for Kansas City, Chicago and New York. You know Chuck, there's something sad about saying goodbye. You like it though. Yes it's a, what do you mean I like it? Any time a female can find something sad enough to weep about she's in her element. I'm not weeping. No, but you will before we get away from there. Oh is that so? Yes that's so. Hey, here comes Joe's plane now. Look Chuck, he's waving. Goodbye Joe. Wave to him Chuck. Nonsense, you didn't see Joe. I did too. He was sitting way up front in that little egg-shaped room.  It was not. I guess I can tell a pilot when I see one. Okay Glamopus, you win. Now come on, let's get going. Chuck, wait. What's the matter now? Joe's plane, it's coming back. Oh no, he's just circling around. He's trying to, hey. What are the motives to stop him? I see it. Something's wrong. What are you talking about Billy Grash? This was the biggest news story of the year. The fourth disaster of its type within six weeks. Sixty-eight people died as a result of that last crash. Fifty of them were aboard the plane. Eighteen of them occupied an apartment house into which the plane had plunged. The co-pilot, a man named Jenkins, lived long enough to be rushed to a hospital. Just before he died he spoke two words. The light. Well, it wasn't much to go on. But my friend Joe Stanley had died in that crash and I was beginning to get ideas. That's why I took my problem to Pappy Mansfield, owner of Station KOP. Now, let me get this straight, Chuck. You're basing this cockeyed theory of yours on the fact that the co-pilot said something about a light before he died. Is that right? Plus the fact that this has been the fourth plane crash of its kind within two months under exactly the same circumstances. Ah, coincidence. And the fact that Joe's plane, on Joe's plane, get this, Pappy, two motors conked out. Can you call that coincidence? Those motors were checked and tested before the plane left the field. I don't know, Chuck. Look, Pappy, for once in your life, why not get with me? I've never let you down. But this theory of yours, that someone is trying to... Now, take a look at this map of the city. All right, here's the airport. Yeah. Over here is the apartment house the plane crashed into. So? Now, over here is a hill. Now, there's nothing on that hill but an abandoned oil well. Practically every outgoing plane passes over that area. And you're not going to tell me that someone is up there with a Buck Rogers rager. Stop, Pappy. Now, look. The derrick in that old well has been patched up and the shack at the bottom has been lived in. Oh, dozens of abandoned well shacks are occupied by hobos. And you think that one of these hobos fixed up that tumbled down derrick just for the exercise? Well... Well... All right, Pappy. There's something wrong about the whole thing. Now, look. It'd be a terrific scoop for KOP if we smelled out the rat. Well, what do you want me to do? There's an engineer out of the KOP transmitter named Bill Adams. Bill knows more about electronics than Einstein. Let me have him for a few days. And close down the station? We couldn't operate without Bill. You won't be operating anyhow if someone scoops me on this story. Well, OK, boy. We both knew when we began this conversation that you'd get what you wanted. Only get this. Unless you return Bill Adams to the transmitter in good health, well, I'll renovate. That was Pappy. Always pulling the hard to get along with the act and then giving in. I picked up Carol and we drove out to where KOP's transmitter is located and had a talk with Bill Adams. Bill wanted to be helpful, but it was obvious he had his doubts about my sanity. Anyway, I gave him my ideas and asked him to check into them. But we came away from there with the feeling that we were wasting the time of Pappy Mansfield's highest-paid senior engineer. You know something, Chuckie Boy? I think Bill Adams thought you were nuts. Yeah, maybe I am, but they thought the Wright brothers were too. But they're older than you, though. Right remark. I think so. Well, where do we go from here? You are going to the city hall and find out who owns that oil well. And where are you going? I'm going out to that demolished apartment house and have a look around. Then that's where I'm going. Oh, no, you're not. Oh, yes, I am. Oh, no, you're not. For the first time, I can remember, I won an argument with Glamour Puss. This was accomplished by driving to city hall and practically pushing her out of the car. It was late in the afternoon when I reached the apartment house. The workman was just quitting for the day. I parked at Jalopy and walked around back. A man in Levi's, wearing a hearing aid, was putting some carpenters tools back into a box. Hello there. You wanted the workman? Yes. Just quitting for the day. The place was pretty badly damaged, wasn't it? About $50,000, I say. That's quite a hunk of money. Now there was a friend of mine on that plane. Oh, a passenger? Yeah. I don't suppose any of you workmen picked up any of the personal effects of the passengers. Personal effects? No, not that I know of. The workman, I hadn't expected the question. As a matter of fact, I hadn't intended to ask it. To just something to say. His eyes darted to the toolbox. I took a couple steps forward. There was a briefcase lying on the ground behind it. This yours? Yes, give it to me. Well, hit a minute now. There's some initials here. J.S. What's your name, friend? Him? Yeah. It's John Sims. That's quick thinking. Suppose you open up the case and show me what's inside, huh? Why should I do that?  Telling or asking? Telling. Well, I'm telling you to mind your own business. Take it easy, friend. Let go of my arm. Sure.  Come on, open the briefcase. I haven't got the key. Where is it? It's home. I forget it. What's in the briefcase? Fluke, friends. I'm a draftsman. Ask the foreman. Where's he? He left ten minutes ago. Let go of my arm. Okay. Sure. There you are. So far, Mr. Simpson. Everything you've told me is very convenient. He left the key home. The foreman's gone for the day. And somehow it doesn't figure. That briefcase looks exactly like the one my friend Joe Stanley was carrying when I put him aboard the plane. All briefcases look alike. Who are you, anyway? The name's Morgan. Chuck Morgan. I'm a newscaster in station KOP. I never heard of you. Fair enough. You know something, Simpson?  Why, you... Don't try that again. Let's turn on my freak arm. Then give me my briefcase. Nah. I'm sticking my chin out on this when I'm taking the briefcase with me. And I am swearing out a warrant for robbery. That's your privilege. Here's my card. The address is right there. If you're on the level, you can have me arrested. If you're not, I'll have you arrested. I took the briefcase and drove to KOP. Kara was there, and she had my script ready for the 7 o'clock broadcast. Easy script. What in the world is that? It's a briefcase. I just bought it from a second-hand dealer. He assures me that it contains a small fortune and $100 banknotes. But Chuck, it looks like... Never mind what it looks like. Stash it away someplace until I can get hold of a locksmith. What did you find out about the oil well? The well and the hill are owned by Delfast Oil Corporation. They quit it eight years ago. Right now, all of their operations are in Texas. Good. Get hold of Burt Mayfair, police headquarters, and tell him I want him on hand when the locksmith opens that briefcase. Okay. But Chuck, where did you really get it? From an ugly man in blue overalls who's now swearing out a warrant for my arrest. Well, I did my 7 o'clock newscast. And I told the listening public that at the 11 o'clock program, I hoped to have some information that would break the airplane crash story wide open. But I wasn't anywhere near as confident as I sounded. I have expected to see the man in the Levi's and a police officer waiting for me in the corridor outside the studio. But the corridor was empty. So was my office. Not even Kara was around to needle me about the bragging I'd done over the air. So I drove out to my apartment on Wilshire. It was dark by now. I unlocked the door. Went in. Before I could snap on the wall, switched somebody beat me to it. I spun around and found the ugly man in the blue overalls standing across the room.  All right, Mr. Morgan. I'll take the briefcase. Now, the conclusion of stand by for crime. Well, the guy wasn't pretending this time. The gun was all he needed to give his face that ratty expression that it came by so naturally. So it's you again, rat face. What's the matter? Are you afraid the cops would put your name on that warrant instead of mine? My time is short, Mr. Morgan. Hand over the briefcase. There's a smart remark. How am I going to hand over something I haven't got? Then you will tell me what you did with it. Will I? Or I will take measures to force you to tell. Such a shooting me, I suppose.  Whatever your name is. Shooting me would mean you'd never find a briefcase. You're quite right.  In exactly one minute, your telephone will ring. The man at the other end will have some interesting information for you about Miss Carol Gertis. About who? That one won't work either, Buster. I left Carol at the studio 15 minutes ago. Did you? Think, Mr. Morgan. Was it before or after your broadcast that you last saw Miss Gertis? I was... Simpson, if you touch that girl, I'll break her... You'll do nothing, Mr. Morgan. Nothing at all. Leave the phone alone. This time, I'm giving the orders. Hello? Three, four, eight, six. Right. Put on the line, please. Very well, Mr. Morgan. Hello, hello. Chuck, Chuck, is that you? Carol, where are you? I can't tell you, Chuck.  Why, those dirty... It's no use, Chuck. You can never find me. Please give them the briefcase. Please, Chuck. Yeah, yeah, sure. I'll give it to them. But what about you? As soon as they have the briefcase, they'll let me go. They promised. They promised, huh? Listen, Chuck, it's important that I get away from here so that I can give you that information you asked me to get for you at City Hall this afternoon. You want to know about that, don't you? I stood there holding the phone, trying to get the numbness out of my brain. And gradually it came to me. If Carol was so afraid of being killed, why didn't she tell her captress where the briefcase was that was she who had stashed it away? And why did she keep reminding me about the information she got in at City Hall? She'd already told me about that. And suddenly I had it. The oil well. That's where she was being held prisoner. She was trying to tell me by referring to the information. Ah, smart girl. That blond secretary of mine. Eh, so what? I could still feel Ratface's gun pressed into my back. And I thought of something. The phone I was holding had an extension cord on it. I'd had it installed when I moved into the place because sometimes I like to walk around or do my telephoning. I hung up slowly. My fingers curled around the heavy base of the phone. Well, Mr. Morgan? Right, Mr. Simpson. Well, Buster, that takes care of you. Buster seemed to be sleeping peacefully and deeply. I got a couple of belts buckled them around his arms and legs and found him away in my bedroom closet for future reference. Then I got into the car and headed for the oil well. It was about 8.15 when I turned it to the side road that skirted the base of the hill. I'd parked the jalopy and started up toward the summit when the thought occurred to me that maybe I should have had the police in on this. It looked like it was going to be big stuff. But Carol was up there and in trouble and I hadn't had time to do much thinking about anything else. As I got up toward the top of the hill, I realized how deserted this spot was. It was a strange feeling. Below, the lights of the great, sprawling city spread out endlessly. Ahead, the skeleton-like framework of the well, Derek, was etched against the sky in ghostly silhouette. Then a figure stepped on my path and I caught a glint of steel. I lunged forward, wrapped my arms around his legs. He fell over my shoulder and I had him in a fireman's grip. I spun around and let go. He landed about 10 feet down the slope and cracked his head against a rock. Well, that was number two. The next one might not be so easy to handle. The well shack was just ahead. Lights streamed from beneath its door. I stopped and considered the situation. I'd be crazy to go barging in. But would I? Wasn't it the last thing anyone would expect? Then the problem was solved for me. The door opened and Carol Curtis stood framed against a light. Carol! Hello, Chuck. Is that you? We thought we heard someone. Carol was looking at me steadily. A look that told me to watch myself. Come on in. I want you to meet someone. You all right, Clamapers? Oh, yes. I'm fine. Chuck, I want you to meet Dr. Robert Burton. He's an inventor. How do you do, Mr. Morgan? How do you do? Ms. Curtis has been telling me about you. What an interesting life you have. I've heard your broadcast many, many times. Yes, I have. Thanks. Look, Clamapers. Dr. Burton was kind enough to entire me after that other man left. But, of course, I had to promise not to run away. Yeah, sure. But what other man are you talking about? Well, his name, I think, is Snide or something like that. A dreadful person. Really dreadful. Not at all like Ivan. Who's Ivan? Ivan? Ivan Stuka. He's a gentleman who pays me to stay here and work on my invention. He pays me well, too.  Yes, yes, indeed. That's exactly who he is. It was Ivan who repaired the derrick. Oh, you know him, man. Yeah, a telephone acquaintance. Dr. Burton has been telling me about his invention. How about explaining it to Chuck, Dr. Burton? Well, I don't know. Ivan might object, and after all, it is his money. But if Ivan doesn't know, it won't make any difference. And Chuck would never tell anyone, would you, Chuck? Cross my heart and hope to die. What kind of an invention is it, Doctor? Well, it's an electric current interceptor. Oh, what? Here, let me show you. Now, this is a small model. It looks like a pistol, doesn't it? Well, you see, I pointed at that electric bulb over there, and puff, the bulb is out. Well, I'll be... Quite a gadget, isn't it, Chuck? Yeah, quite. How do you do it, Doc, with mirrors or something? Oh, no, no, no, no, not at all. It took me years to perfect this instrument. As a matter of fact, if it hadn't been for Ivan, I might never have succeeded. How's that? Well, you see, during the last war, I got the idea, but I had to have financing. Naturally, I went to the government. I thought they might be interested in an invention that could put an airplane out of commission, merely by projecting a ray toward one of its motors. Yeah, I should think they might. What happened? Mr. Morgan, believe it or not, no one would listen to me. Oh, I went back time and time again.  Oh, I see. And when you were released, you met Ivan? Yeah, oh, a fine man, Ivan. He felt that if I came up here to live away from everybody, I could work on my invention undisturbed. Ivan arranged for the turning on of the power and the telephone and just everything. I've been quite comfortable. When did you get this invention of yours working? Well, about six weeks ago. Oh, I tell you, it was exciting. Ivan was most pleased. Oh, bad. How did you test it out? Well, I on a plane coming out of the airport, of course. That's why Ivan wanted me to come up here in the first place. He said we'd have plenty of subjects to work on. Oh, and he was right too. Oh, I tell you, it was a thrilling moment when I put that first plane out of commission. Oh, it made a tremendous crash. Yeah, yeah, I read about it. Weren't you worried about the passengers? Worryed? The passengers? Well, that's funny. I never thought of that. I'll bet Ivan did, particularly the planes of which important government officials were writing. By the way, doctor, I suppose you have the plans of your invention down on paper. That's a funny thing. Ivan keeps asking me about that. Why should I put them down on paper all right here in my head? No reason to talk, except if you ever wanted to sell the idea. No, no, no, but I don't. No, sir. I've had my experience of that sort of thing, and no one would listen to me. Just as long as Ivan will pay me, I'm going to stay right here. And continue to blast planes out of the sky. Does that seem quite right, Dr. Burton, with all those passengers aboard? Yes, those passengers. It's funny. I never thought about them before. I must do something about them. Oh, I really must. In the meantime, Dr. Burton, suppose you tell me just... All right, Morgan, get your hands up. It's night. Close the door. Well, well, if it isn't rat-faced and the gentleman who rode down the hill. A more permanent fate is in store for you, my friend. Doctor, what have you told these people? No, no, no, Ivan, you mustn't be displeased. I merely told them about my invention. You fool! Now it will become necessary for me to dispose of both of them. I bet that would break your heart.  After all, only sixty-eight died because of that last crash. So two more won't make any difference, really, Mr. Morgan. Except that you still don't know where the briefcase is. The secret of the ray gun is, I think, far more important than the plants contained in the briefcase. You see what kind of a rat you friend is, Doctor? He's going to murder Miss Curtis and me and then continue to induce you to blast planes out of the sky, killing innocent people. There's nothing about those passengers. I simply must... No, Ivan, you suppose that we could arrange... No! You will continue to experiment with the plays I suggest. Or there will no longer be funds to permit you to continue working on your inventions. No, no, no, I... He's making a murderer out of you, Doctor, without your realizing it. This man is an agent...  Snipe. Take care of the girl. All right, Morgan. This is it. Stop it! A change had come over Dr. Brayton. His voice held a commanding quality of vibrance that made us all turn and stare at him.  Snipe had taken two steps toward Carol and stopped. Drop that gun, Stucka! From now on, I'm giving the orders. Ivan didn't answer. None of us did. We all saw what was happening. Dr. Burden had his Ray gun pointed at the electric hearing aid on Ivan's head. I could see it the indecision on Ivan's face. He was wondering whether he could swing his gun away from me at the doctor in time to save himself. I could almost hear the thoughts racing through his mind. He knew that Dr. Burden had suddenly had a change of heart. If he, Ivan, didn't succeed in shooting the gun out of the inveterate's hand, it would mean the ruination of all his beautiful plans. It would mean the gas chamber for himself at Snide. There was only one course open for him. Drop that gun, I said. I'll drop it.  When I got back to the studio in time for the 11 o'clock broadcast, it made a good story. Of course, everyone wanted to know about the Ray gun, but Ivan's bullet had entered the inveter's heart. At the precise instant, the Ray gun had sent Ivan to his ancestors via the hearing aid. So the secret died with Dr. Burden. And all I know is what the doctor had told me and what I saw. Yeah, sure. There were plenty of skeptics. Even in this age of atomic weapons and jet planes and radar projected electric impulses, a lot of people weren't ready to accept Ray guns. However, if no more motors conk out after planes leave the airport, it'll be pretty conclusive proof that Dr. Burden did invent some sort of electric current interceptor. Well, anyway, time will tell that story. There was one question that Carol wanted cleared up, so she caught me about it at lunch the next day. Hmm, this chicken salad is delicious. I personally go for hamburgers. You can eat chicken salad for once and like it. I need it, but I won't like it. Say, Chuck, there must have been some reason why you convinced that Ivan was a phony. Well, as a matter of fact, it was. However, I'd rather not mention it. Rather not mention it, but why? Chuck Morgan, you tell me. Oh, now, Glamour, first you might think me a modest. Oh, fiddly-dee. Come on, make with the words. Well, if you insist. I do. All right. You remember when I first met Ivan at the apartment house? Yes. Well, I explained to him that I was Chuck Morgan, newscaster at KLP. Well? He said he'd never heard of me.


The phone is still attached What you're about to experience I do not condone I don't endorse but I just couldn't help myself So don't try this at home. Hey, so what you're saying is I shouldn't attach my phone to the drone and fly it, right? Like I wait yes, I of course I should no you should not But I feel like it would be just I'm interested in seeing what that would look like on a phone Your positive I shouldn't do it, okay, so what I'm hearing you say for the last time Do not attach my phone to the drone By I will I'm thinking about doing it, okay? All right, sounds good Do you do you want some sweet tea? Yeah, okay? I'll bring it to you in a second. I love you. All right. Bye Yeah, we're gonna do it anyway Okay, I Tape my phone to my drone. It's 4k at 24 drowners at 4k 24, and I'm gonna fly it Here we go. What am I doing right now? Duck taping the way and I think I'm gonna try to adjust it so I have to land it again. Here's take two Really hard to control because again, I think it's the weight that's messing with this and I'm just all over the place as you can tell so it's not a good idea This is not a good idea. Okay. Here's the thing Drones coming back.   Oh, no, okay, please be there The phone is still attached I mean the spot's just beautiful, isn't it? Okay, so Johnny Q Why in the world would you ever attach your iPhone 10 to a drone? It's a good question guys That is a very good question one that I cannot answer. I can only say squirrel I can only say it was out of pure curiosity. I just wanted to see what it would look like in 4k up above from my phone. Look, I don't know why I do things I just thought it was gonna be a good thing to do. I love crazy ideas I mean, what else is there to do like there's no questions. Just do it just go out and do it Alright, if you guys enjoyed this video, please give it a like please subscribe to the channel and I'll catch you next time on the Johnny Q channel. Peace. I wonder if I should attach anything else on a drone. Hmm


Hi everyone, Joe for jaskiescasebrakes.com. Happy Saturday, coming at you with 2019-2020 Panini Chronicles basketball fat pack break number 780. At the end of this, we're going to give away four spots in that flawless collegiate basketball break, which I think is pretty underrated, folks. It's $400 a spot, so get in on that. We still need to do a couple more of these packs and then sell a handful of spots straight up, but then we can be in breaksville pretty quickly. You're guaranteed a hit as well. It's a random hit break. All right, so let's do the break itself first. As always, so thanks everyone for getting in. All 30 teams are in. Let's roll it, let's randomize it. 12 times, full 12, six and a six. One, two, 11, and 12th and final time. Brian Frank down to Brian Frank. Obviously a different dice roll, separate dice roll for the giveaway. All right, 12 times for these guys here. One, two, three, four, 11, and 12th and final time. After, oh, that still says 11 right there. Did I not click? Again, there we go. There's 12 times, although this part really doesn't matter as much. The part that matters really is who's gonna win those big spots? It's $400 spots, 390 to be exact. All right, here's the first half right here. All right, so this is 1920, so could there be some surprises with the Palakins and the Grizzlies? Maybe, maybe. No trades in these little mini breaks, these little filler breaks. Let's box these up, center these up, print these out. Rex is saying there's two left in one of those in the Jeter Mixer filler. Wanna get that one. That's actually a pretty good filler break too, the optic choice. All right, we're gonna lead off with Anthony Davis up on top. Here's the final printout, hot off the presses real quick. Here's a second year Luka Donchitz, a Hachimura, there's a Zion, there's an RJ Barrett, there's a Kobe White, another Kobe White, Kevin Porter Jr., and a Gogo Goga Batadze. All right, so there's the second year Luka Donchitz for Dallas, that'll be for Kelly. The two Kobe Whites are pretty nice too, Robert and the Bulls, and looks like this is a luminance bronze parallel of Kobe White, also pretty cool. We got Playbook Zion, that is for Roy. He's been playing some excellent basketball lately. RJ Barrett also taking a nice next step, forward step in his career as well. Ryan Frank, I think Barrett might still be a good by low candidate if you're looking for stuff like that. All right, let's flip back to this list right here. Let's grab everyone's names from Daniel down to Eric. Let's get you into a blank list. Let's roll it, let's randomize it. Two and a one, three times. So it's gonna be top four after three, good luck. One, two, and three. So after three times, once again top four after three. So sad times for five on down. We'll get them next time. Congrats to the top four. Daniel, Brian, Brian, and Robert. There you have it.  We should be able to do that later tonight. JaspeysCaseRakes.com.


Let's go back to 1998, the ALDS post-season dot good and on the bump for the then Indians. This one's brought to you by SeatGeek and he doesn't like that he didn't get that call, use code johnboy20-dollars-off-your-first-purchase at SeatGeek, stares in a little bit. It's 2-0, umpire, his name is Joe. Kind of looks back, says let's get on with it. Come on, keep playing. They put down the sign, another fastball. That one is where? Dot good and doesn't like that now. Kind of looks in, he's like, god damn. Where is it? Turns around, puts on a little show, three pitches. All right, my bad, sorry. I'll stop. Manager walks out to the mound, Doc's talking.  Okay, okay.  They look at each other some more. Manager Michael Hargrove comes out. He says they're right down the middle of the zone. Are they? Let's take a look. It's, I mean, he catches it just barely below the knees, which means it probably crossed in the zone. Who knows? It's very borderline. Manager says like, where did you have it? It was down. He says no one's calling that effing ball up. He says, I'm telling you it's not down. Yes it is. No, it's not. And then he must say it again, like it's not down. Or he says something, he gets run. Three pitches into a playoff game. Don't tell me what the F is low. Oh, I'll tell you what the F is low. You don't get to tell me nothing. Oh, did I hurt your feelings there, Joe?   I don't tell you what to do. And you don't have to tell me. Don't you eff and touch me. Don't you eff and touch me.  Just looks at them. But for you to miss both calls, that's why I'm saying, I didn't argue with you. I just told you that.  And then they talk a little bit more.  Oh no wait, he goes back for more and it seems like it's a bit calm. And it is, Amp says, Michael, Michael, Michael, listen to me. Right now, really? Yeah, right now. And then the broadcast had mentioned that he was upset about a call in game one of this series, but it was a blowout so he couldn't argue.  And Amp's like, really? Right now? Finally then he leaves. Amp straps on his gear. He heads to the clubhouse. Can't watch the rest of the game. Did get to see those three pitches though and they were exhilarating. Here they are again. That one's low, we all agree. This one, this one, I don't know, borderline maybe. The next pitch is a ball high. How about that? So he walks the batter and then the umpire stares at him. He's like, come on, get mad at me again. I'm itching. Get mad at me again. Come on, let's do it. A one, two pitch to the next batter, a steal second overthrow goes to third. Gooding's not having a great time on the mound. And then once this check swing on Nomar, Amp says, no he did not. And he did. So that's also a call that's just not going Doc's way. And Nomar puts one off the wall about a foot away from a home run in the first inning. It scores one. The second runner is rounding third. He's heading home. Doc Gooden's right behind him. He's got a great view of the tag. Gets him the sleeve moves. He hasn't touched home. And the great news is home plate umpire had a great view. He was in perfect position. He saw the whole thing. He says safe, says safe. And that's just a couple of batters later from the hall ordeal earlier. So Doc Gooden's like screw this, man. I'm out. What's wrong with you? What do you got against me? Newman's holding him back. And then this super old guy who maybe isn't even that old. Maybe this in 1998 age, he's 60, but he looks old. He's, oh, I'm itching. And Doc is pissed. Pissed. He's gonna leave, he's gonna throw stuff at the ump and say that's for you.   Throw out the ump, says that sign from the fans sitting in the seats. If you wanna be a fan sitting in the seats, you can use code JOMBOY, get $20 off at SeatGeek because they are sponsoring this breakdown. Thank you to JOMBOY. Oh, no, I meant thank you to SeatGeek, but thank you to myself too, it was fun.


The National Christian Women Coalition, NCWC, have declared support for the presidential candidate of the PDP with the theme, the mother's voice. The National President of the Northern Christian Women Coalition under the leadership of Princess Leah Solomon made this declaration while speaking to some journalists in Abuja. Speaking, Leah explained that a PDP presidential candidate is working in favor of the women and youths to bring to reality their five-point agenda. The entire women that attended this program, 414, from the state level, the local government level, the world and the unit, I want to congratulate all of us because we have one voice that we stood in partnership in support of His Excellency. Abu Bakar Artigu was sitting at the moment with Dr. Okowa. They have shown what it means and neither in action. So with this we follow as mothers in the Northern Christian Women Coalition. We have to prove this by saying the experience is the best teacher, a unifier, a man that understands the five agenda we have which we feel as mothers in the Northern Nigeria Coalition. We have to speak on behalf of our children youths. We have to speak on behalf of our own humble selves. We have to stand and say. Also speaking, Mrs. Zayna Boni, Matron Northen Christian Women Coalition, SCWC called on the Northen Christian Women to participate in politics by coming out to support the presidential candidate of the PDP. And so we saw a lot of our Christian brothers and sisters in reacting to the empty ticket. We also wanted their own, but we needed to guide them which side is safe. And as far as we are concerned, we have come to agree that pitching our camp with Aladdin Artigu, Abu Bakar is safer for all of us and they are even for the church. The first point of all is for Northern Christian Women to rise up and participate in politics. Remember that power is one negotiation. So we need to also make ourselves, you know, we also need to show that we can do it. It is not that they just carry power and give it to us. No. Every one of us, what we are seeing is that with the proper giving of people chance, women also have the grace to what they need to do.


Shout out to InnerScope man, you heard it here first man, I should be finalizing my deal with InnerScope this year. C'mon man, congrats. That's hard man. Hey, congratulations man. Yeah, we on boss talk one on one, one on one, yeah we gon' talk. Shout out to InnerScope man, you heard it here first man, I should be finalizing my deal with InnerScope this year. C'mon man, congrats. That's hard man. Hey, congratulations man, peace and blessings man, that's hard man. I had everybody reach out to me, Warner Brothers, Columbia, Capitol Records. That guy Wharton, what's his name? Wharton from? Which one?  Hey, what's his name? Orlando Whartonberg? Yeah. Where's he from? Oh, Capitol. Yeah. I didn't even know who he was, I'm sitting right next to him, he's sitting right next to me.    And yeah, we met with him, Johnny Scheif's, or Jeb Vaughn from Columbia, Johnny Scheif's woman was Sony, Warner Brothers. How did you make your decision? Honestly, my decision was, it's sad to say, but whoever puts the more money up, that's the truth. That's the right decision. Whoever puts more money up, whoever's putting the most money up believes in me. He's working to make that money back. So even if I wanted to go with Jeb Vaughn or Johnny Scheif's or whatever, it was between Columbia, this one and also Akon's brother. So he was, he was, he was doing two shout outs to him and I really, at the beginning I wanted to go with Akon's brother because I felt like they'll just be more invested in me. But Jeb Vaughn was like, I've really vibed with him and I really do believe he believed what I said. Johnny Scheif's, I met him in Interscope. He signed Nip and it's just like, he was cool, man, but like he's in New York. So I was like, I was thinking about all that stuff, but Johnny Scheif's is the one that just kept coming back. I want him here. Boom. I want to counteract. Boom. I want him counteract. Boom. Boom. Boom. He just kept coming with the most dose. So obviously he believes in me the most and I'm going to give him all I got and yeah, Interscope Records left the gunplay. It's going down. Come on, man. Going down. Going down first. Yeah. Yeah. That's all. Being independent. Being independent versus going on this label now. What do you think is going to be the biggest changes? The money. The money. The money. So you always come back to the money. Yeah, because next year I'm going to make another million. That's all. And next year I'm going to make another million. And next year I'm going to make another million. So I'm not worried about this 2 million million. I'm going to make another million next year. I'm going to make another million next year. And that's my mentality. This is just getting started 2024. I'm killing it. Killing it. Yeah. And I'm going to keep doing that. I moved out the hood. I'm in LA now. I'm staying low-key. Come on, man. Congrats. You got to. I know there's a bigger picture. There's a bigger bag to it. I know my responsibilities. I'm starting to understand it now. I'm starting to learn. You know? You can't be so accessible to every single female. That's right. You can't be a... You just got to just stay focused and just do you, man. And that's what I just do. I keep doing me. Keep putting out more content, more videos. And every song I'm getting better. Every song. It says it. Yeah, I keep getting better, better, better. Every song I'm bettering. I'm getting more views. I'm getting bettering with my music. So I was just like... Now it's like...  And we're barely in January. Wow.


Hello, everyone. My name is Ken. I work at Astra. Astra is a launch services provider. And today I'm going to talk about one of our use cases for Argo and how we use it to orchestrate some of our launch tests and simulation of the structure. Quick show of hands for folks that are using Argo today. OK, so that's pretty much everybody, almost everybody. Folks that are using Hera today, nobody? OK, wow, cool. OK, so before kind of talk about Argo, first we need to talk about how do you even test rocket software, which is something that I've been learning over the past year. So in order to test software that runs on a rocket, there's quite a few challenges. You've got multiple embedded systems. We're not using Raspberry Pi's or like off-the-shelf reference boards, typically custom hardware. We've got a lot of IO interfaces and control loops that are actually talking to or meant to talk to physical things and then receive data from physical things like sensors and real-time systems. And it's a high burden to actually operate the real thing. You want to be able to ensure that your software is functioning correctly before you actually plug it into the physical thing because you could break the physical thing if it's not. And so that kind of leads us into hardware in a loop, commonly referred to as Hill. And so this is a test methodology for embedded control systems where basically you take the control system that's under test and then you, instead of hooking it up to the real physical things that it's going to control, you actually hook it up to simulated models. So then it's able to send control signals, get feedback from the models. And as far as it knows, it's talking to the real thing, but actually it's not. So what does that look like? At a high level, if you look at the picture here, you can see we've got up in the green box, we kind of call the device under test or the control system that we're testing. And then typically the inputs and outputs are physical wires going into simulator or simulators. And then what that simulator often looks like in a nutshell is that you have some kind of specific hardware platform sometimes referred to as a DAC or data acquisition hardware that basically takes all of the wires coming out of the device under test and all the electrical signals and then converts that through some software into data that the models can consume. And then the models basically kind of do a similar thing on the way out where they basically talk to the data acquisition hardware and then that gets turned into electrical signals which then go back into the device under test inputs. And so that's basically how you do it in a nutshell, but it does get a little bit more complicated in our case because we have some other things that we need to control and orchestrate. So we have our ground system software and computers that we use before the rocket takes off. We have our cloud data pipeline where we basically take all the telemetry data and ingest it for analysis. And then in addition to just the DAC hardware then we also have a GPS simulator that needs to be orchestrated as well. And the GPS simulator is hooked up to the models and that basically sends spoof GPS signals to the vehicle to tell it to basically convince it that it's fine. And so all of this stuff needs to have basically be orchestrated so that we can automate deployments to this. So some of the challenges with that got multiple hardware platforms with varying levels of APIs. Some of it's hardware we build, some of it's hardware we buy from other people. Hardware state needs to be queried, verified, reset through those APIs or even sometimes like CLI tools. We've got lots of software to deploy not only into the test system but then also onto the launch system and vehicle itself. And then we've got a lot of log and data sources that we need to be able to look at when we're trying to monitor the system, debug it. And it's time-intensive. Time, it's an expensive system to build. And so if it's not functioning properly or if we have an issue running tests, then that costs this time and money. So those are some of the challenges with operating this. I think the big one is it applies to Argo and how we use Argo is one the manual process that we use before Argo, which was typically a human going through a well-documented process, which takes a long time, is also error-prone and you don't have the ability to run it unattended. And then also just being able to gather all of the, when you have a human running manual steps to do things, you don't automatically get logging sent to centralized systems, that person would have to cut and paste logs out of that or use some tool that would do that for them. So having computers do this gives us lots of benefits. And so we decided to basically orchestrate the system using Argo workflows in particular. And so why did we choose Argo workflows? Well, basically our entire tool chain and build system was already containerized. So all of the software that we build in-house and deploy into the launch system, all of the CLI tools, all of the API clients, like everything is basically already built and shipped in containers. When we need to get from where one of the rocket, the rocket doesn't run Docker or doesn't run Kubernetes, but the image lives in a Docker image which then goes into some system, which is then capable of updating that. And that was all done through Docker. So it wasn't really a big leap for us to go to basically having people running tools that are containerized to then mapping it to a workflow system like Argo where every step is effectively, is just a container. We use K8s quite a bit across the company already. So again, not a big jump for us. And we already had some experience with Argo. And overall, just when looking at different options, we had a person before us talking about like Argo workflows versus Airflow. There's tons of options out there for building workflows, for automating things, for task management and scheduling. This was by far out of all the options I looked at, the least amount of code to actually build the system partially because of the things, maybe mostly because of the things that I already mentioned around our kind of adoption of Docker or container images and Kubernetes. And I think one other aspect of that, which I don't have up here, which kind of relates to our, I'll get into later our decision to use Hera, is that for non-embedded stuff, we do use Python quite a bit. And so when we decided to leverage Hera, having a Python tool that allowed us to basically kind of codify and create those workflows was very beneficial as well. So a couple of key considerations that we were thinking about before we started building this, the version of the Argo workflow or at least capturing the state of an Argo workflow at a point in time is important to us because the environment evolves over time and so its configuration will change over time. And sometimes we may need to go back in time to basically run the same test or simulation in the exact same environment that we ran it before because we need to go back to an older piece of hardware, an older piece of software. So unlike writing a web app or something, it's not always just living off of main or trunk the whole time and kind of moving forward. Sometimes you have to move back and you want to know what workflow you ran with a particular test or simulation so that you can run it again later. Or later down the road you may discover that there was a bug in there and you want to know basically which tests or simulations were impacted by that bug and the bug could actually be in the workflow that could potentially have an impact on the outcome so you need to have all that metadata. Workflows, so basically we wanted to be able to trigger the hardware and the loop simulations through pipelines, through GitLab or GitHub type pipelines, where basically like if somebody's working on a particular piece of code and they make a change, they want to be able to ship that change in addition to their unit tests and local integration tests, they want to be able to kind of run it on this platform which in the manual world that was hard because then now they've got to coordinate getting time to access the system, they've got to figure out how to use it and how to get their code deployed on and how to run it. And so we really wanted it to be as simple as possible from an automation perspective. It also though needs to be triggerable via humans. So we don't, not all of our use cases are just pipelines or automated processes kicking off jobs. We have humans that want to run basically one off tests or series of tests and maybe potentially test out certain software configurations or certain hardware changes and then go run that test through something like a GUI. And we also, because this is an expensive resource, we can't just go to Amazon and say, give me like a thousand simulation environments and if we could it would probably be prohibitively expensive. But so we have few of these resources and we generally have more demand for them than we have supply. So we need to be able to queue all of the requests coming into the system which Argo doesn't natively do for us and we also need to be able to lock those resources to ensure that we don't have multiple people or multiple systems running workflows on a simulation environment at the same time. So at a high level architecture overview or really technology choices, no surprise there. We're at ArgoCon, I'm talking about Argo. We chose Argo workflows. I already kind of talked about why that was a fairly easy choice for us. For actually kind of authoring and codifying the workflows, we chose Hera, which is a Python SDK that basically allows you to, it has basically full APIs into all of the Argo workflow primitives, the stuff that you would see in the CRDs or in the YAML when you're building a workflow and allows you to basically author that in Python. And so you can codify your entire workflow in Python and then use Hera to produce basically a YAML that you would then submit to your Argo workflows. You could actually just use it to create the YAML file and you could keep track of that yourself. If you want, in our case, we specifically, from Hera, we just run the Python code to generate the YAML and then submit it every time we run a job. I'll get into that a little bit more. I don't honestly know, in terms of the Argo community, I don't know much about complexity of workflows and what other people are doing. We have around 2.5,000 lines of Hera code, which is, I don't know if that's a lot or a little, but we do have a lot of helper classes and stuff to make it easy to write new workflows and to add functionality to workflows. And then to basically, so as I mentioned earlier, we need to be able to queue these jobs coming into Argo. And so we built basically a purpose specific queue for this around FastAPI, which is just a Python web framework and Postgres, and then also using some of our existing internal web platform and Angular UI in front of it, which I'll kind of show you some screenshots of in a little bit. So next, I guess we'll kind of just look at a high level kind of overview of the architecture here. So on the top left, I kind of try to demonstrate here that we have, we have multiple inputs coming in to the system. We have pipelines and we have end users talking or requesting simulations through either UI or API. Those get queued up into a system that we have coined as hill queue, kind of short and gets the point across. And so that basically stacks up requests for Argo jobs. So basically what happens is like a user comes to the system and there's two main inputs. There is, or actually three main inputs. There is what is the software version of the launch system that I want to test?  So you can kind of think of it as a deployment manifest. Then there is what is the version of the Argo workflow that I want to run, which is basically the Git ref for our Heracode base. And then what is the target environment? And so you provide those three inputs and then it gets stacked up into this task queue. And when your target environment is available, then the next step is that it'll actually take, we package our Heracode in container images. So like every time you want to update the workflow or create a new version of it and you go and make an update to your, to our Heracode base, that produces a net new container image and that's tagged along and that lines up with you can correlate that to the Git ref. And so basically when you tell the system, hey, go run this workflow for me on Argo, it knows that it has to go get a particular version of our Hera Docker image. And then it actually runs that in a Kubernetes job, which then runs the Hera and then submits the ML to Argo and then kicks off the workflow. And then basically the Hilki system will just effectively babysit the workflows. So it knows at all times, which workflows are running on which systems. And it also, you know, it basically has a, we do that through like the, through the Argo API, the web API, not the Argo, not like the CR, not the Kubernetes API and the CRDs for the actual Argo workflows, but the thing that you talk to when you're in the Argo UI, there's a rest API behind that. And so we actually just query that directly to get workflow status. And so whenever we put something into Argo, we have a bunch of metadata in there. So we know how to track it. And that's in our, you know, in our Q database and we can come back and check up on it later. And yeah, and so then basically Argo goes ahead and orchestrates that job against our simulation platform. So let's see here, we've got about nine minutes left. I'll kind of go through a couple of things here around, you know, just user experience and what it looks like. So as I'd mentioned, you know, so we have the queue that basically kind of stacks all the jobs before they go into Argo. And then we have an API and UI in front of that. And so this is actually what the end user would see. So if I had a, if I had like, you know, a pipeline that's kicked off a simulation job and I wanna come and check on the status of that, I can go to this UI and I can basically see, you know, okay, this is the job that's running and it's actually got a link to the Argo UI in there. So I can go see the status of that workflow. I can see, you know, basically which jobs are stacked up, waiting to go on to, waiting for Argo to execute on our simulation platforms. I can see which job is coming up next. And then also got a little bit of visibility there of the environments that are available. What does the workflow look like? Well, so at a high level, it kind of looks like this. Or actually you've got another version of it here too. Again, I don't really know like for Argo, I don't know like how complicated these workflows are in terms of like logic and nodes and everything like that. I think for at least my experience, you know, doing this with something other than Hera would have been really tough. It was actually fairly easy to do in Hera and to kind of keep it all in my head and know what's going on whereas kind of just, you know, trying to like build our own tool to manually construct the YAML or something else would have been, I think, a little bit more challenging. One other screenshot here that I've got is just kind of a little kind of, when we're actually running at the Argo workflow as it goes through, you know, kind of each step of the simulation process of configuring the hardware, deploying the software. We actually also have it shoot, the workflow itself shoots messages back to basically a chat channel that we have that provides people that have jobs running with the links so that they can go drill down into the workflow if a step fails or something like that or if they just want to go see what the status is. So in terms of experiences with Argo, as I mentioned earlier, I feel like we were able to build this out much faster because we were using Argo and because we were already kind of had everything containerized and we're very Kubernetes centric. The other things that Argo got us out of the box that were super helpful were basically having a system that automatically integrates with our SSO, automatically having a log archiving system built into it. One of the things that we struggled with before, as I mentioned, is that when people are running this and they're running these steps by hand or running the simulations by hand, it's up to a human being to basically capture all of the output and get it into some system where we can see it later. Argo gives us all that out of the box because in our workflow we can just basically say every step, for every step should be archived and then it automatically captures all the log output, keeps it in object store and then if I want to go look at a job that ran two months ago, I can go look at that job and then see all of the logs for every step in that job. And I'd say I guess the only other thing was that I know that I don't know what the current status is but I've heard people talking about having a basically like a more kind of like Argo or K8's native queue, I think that would, that would definitely be a welcome addition. I feel like what we built kind of going back here to the system for kind of queuing up Argo jobs, I imagine that that is not an uncommon use case. And so I was kind of surprised that there hasn't really been any traction around that lately but maybe if folks know of something they want to tell me about it I can do that in the Q&A. Let's see here. What else do we, oh, Hera, yeah, yeah. So I guess considering how few people raise their hands around Hera at the beginning of the talk, I would say if there's one thing you walk away from this with, if you're using Argo, I would definitely check out Hera. I felt like it made implementing this project way easier, you know, I would actually, I feel like I actually kind of learned the Argo workflows API through the Hera code base because I was just trying to figure out how to do stuff. I would just go read through, you know, Hera basically maps all of the, all of the Argo resources into Python code so I could just kind of go jump into their code, look at it, see, you know, see how those things worked. I felt like it was actually better, better than reading documentation. I feel like it's a lot easier to just kind of reason about complex workflows in Python versus YAML and then we got a lot of benefit out of just creating reusable code. So like for our workflows, when we have, you know, we have like some baseline kind of classes and functions that set up boilerplate for common tasks, you know, for example, like CPU and memory resource limits, you know, you can kind of set all that stuff up in one place for tasks that share the same container image, you can set all that stuff up in one place for our, you know, Mattermost or kind of Slack type notifications, you know, we just had like a little helper class for that and then, you know, I can literally just write like, you know, take the entire Argo, you know, like an entire DAG and say, effectively, like for everything in this DAG, you know, send a Mattermost message if one of them fails, that type of stuff. So I found it to be super useful. I would definitely recommend checking it out if you hadn't and if you have not and also just developer response from the Hera developers was great as well. They might open a couple bugs with at least one bug and then a couple feature requests and always got like super prompt feedback and yeah, overall great experience. And then just as kind of a parting screenshot here, kind of talking about Hera, you know, this is basically kind of like how our workflow initialization kind of works at the end of our Hera code base where, you know, we basically got a couple of different DAGs and then we set them up and then we set some, you know, things to basically like, you know, if this DAG succeeds, run this thing, if this DAG fails, run that thing and then on exit run another DAG which is just basically a list of tasks that we run at the end of every workflow. And so obviously there's like a lot of code that goes behind this to set these things up but in terms of kind of being able to express what you're trying to do, I found it super useful. All right, we've got two minutes for questions. Anybody? Okay, thanks.


This research explains how the introduction of silver into a porous SiO2 microsphere matrix can create a random metamaterial with precise control over electrical percolation, leading to the creation of both negative permittivity and negative permeability. Additionally, the researchers demonstrate how the frequency of epsilon near zero, Enz, can be adjusted according to the amount of silver present in the material. Furthermore, they show that the material exhibits a linear relationship between the frequency of Enz and the square root of the angular frequency, indicating that it behaves like a relaxation-type spectrum. Finally, the researchers explain how these materials can be used for electromagnetic attenuation and shielding. This article was authored by Paytalsia, Zidong Zhang, Zhongyang Wang, and others.


Simple example, first we will identify variables for a system and then we will try to draw a causal diagram for this one. Hypothesis of dynamics in urban region, the job availability attracts migrants to the city. New arrivals to city expand the labour population, population absorbs available jobs, decreasing job availability. The long run as labour also creates demand for additional services and facilities. The further increase the number of jobs in the city comes about, more jobs increases job availability. It is a pretty simple and kind of an example written in a more straight forward language. So using this we can identify one causal link per statement so that is what it is about. So we have job availability attracts migrants to the cities so job availability should influence migrants or migration into the city in migration and as migrations occur that expands the labour population within the city for second statement. So first statement the variables are job availability increases migrants, more jobs are job availability is there more migrants are in the city, as more migrants are as migration happens migrants are going to expand the labour population within the city. As population as the entire population this thing labour as this labour population absorbs the existing jobs decreases job availability. So the population is going to take up jobs and jobs will decrease the job availability. The long run labour also creates demand for additional services as more labour comes new shops open new services has to be offered so that will after long term increase the number of job availability within the city. So we will identify this let us take it CLD for example 1. So we can identify some variables or let us say job availability migration labour population jobs these are four variables we identified using this let us create our kind of first let us create the links I guess. So let us take the job availability we say effects are migration the first statement said job availability attracts migrants to the city so job availability is more migration is going to be more that is what we can intuitively expect the job availability affects migration. So these left side are the initial variables we identified and migration expands the labour population within the city so migration increases the labour population this labour population is more what you can expect the job availability has to come down because you are observing the new jobs decreases job availability let us suppose there is more jobs come there is more job availability there is one more statement there which had the same way we had two links other one was the labour population after some time increases jobs within the system. So to indicate the after some time part we can simply put a D on the link to indicate that there is some delay in the process after some time the labour population increases the jobs within the system. So these are initial set of causal links that we have created based on the description but this again is still very cumbersome to read you can just combine all of them we do not need to repeat all the variables so many times and create what we call as a nice causal map of it we are continuing the same example let us start with job availability can call it in migration also we are not talking about people leaving people coming in can make it more explicit then we have labour population then we have jobs these are the unique variables that we have job availability increases immigration increases immigration is more you can expect increase in labour population less labour population absorbs the jobs a decrease in general job availability has to happen which but after some time the labour population increases the number of jobs but after some time so there is a delay and as jobs increases of course job availability also tends to increase. So just to indicate it this D indicates delay this is a nice diagram we have this captures the same description that we had in English but it is much more easier to read and much more compact. So the idea is not to just make the diagram but also to have our discussions revolved around that suppose we say as job availability is more you expect the immigration to increase that in turn is going to increase our labour population that is going to absorb the jobs as labour population increases that is going to decrease the number of jobs available so as jobs decreases you can expect migration also to slow down the migration rate as migration rate slows down the labour population increase that also slows down and it going to come to some sort of a balance in the system. So this loop will again be a balancing loop this loop is again a balancing loop. So in this model as you can see there are two loops they start the job availability in migration labour population jobs and job availability there is an outer loop and there is an inner loop. So inner loop is negative feedback let us look at outer loop as job availability is more immigration increases as the increase labour population increases as labour population increases jobs increase that increases again job availability. So there is a positive feedback also that is happening in the same direction or strengthening the phenomenon. So this so we have one reinforcing loop or a positive feedback loop this is a balancing loop or a negative feedback loop. In the term positive negatives are all placeholders negative does not mean bad positive does not mean it is good this reinforcing or balancing or positive negative. Throughout the course you will find that it is very easy to explain the concepts in fact that is it that is the entire thing about causal loop diagram I have done. The difficulty comes in when you start practicing it and start trying to say for example read newspapers and try to come up with a causal map of what is actually happening to understand dynamics now that becomes challenging. There are some certain guidelines for this causal loop diagram which I will discuss let me move on to some of those guidelines for the causal loop diagram. So this about description itself is called as a reference mode. So many times we can use this causal loop diagram this kind of mapping to actually understand what the problem is many of us want to become analysts right. So this kind of system thinking tool will really help you make a good analyst or a systems analyst rather than focusing on the domain of the subject you can actually become system analyst but these kind of causal diagram can help understand and link the various variables and help understand the problems. This itself can help discover what the actual problem is that we are trying to solve. So we already seen this the loop polarity links we saw and loops also we saw balancing loop and reinforcing is going by reinforcing it when loop feedback loop response opposes the original perturbation the loop is negative or goal seeking when feedback loop response reinforces original perturbation the loop is positive or reinforcing. So negative loop or goal seeking loop or balancing loop is the same and reinforcing a positive feedback loop are the same ok. So one way to understand that is suppose we have links like this so for example X1 of XX2 of XX3 which again affects X1 right and if you want to do it the right way then what we need to do is split it let us call it X1 say dash let us see how X1 affects X2 and how X2 affects X3 and in turn how X3 affects X1. So in I think we kind of cut the cut one of the variables and say ok let us initially allow X1 to increase and as for X1 changes how does it affect X2 and X2 changes how does it affect X3 and again as X3 changes how do you affect X1 ensure that you again come back and see what is happening to the variable X1 which is which you perturbed initially. And if the original direction of X1 dash and X double dash is the same then we say that it is a reinforcing loop or a positive feedback loop if it is in the opposite direction as many we initially perturbed this by increasing it but then eventually X1 double dash seems to decrease here then it becomes a goal seeking loop or a negative feedback loop. We are not interested in the quantum of increase we are not interested in the quantum of increase we are only looking at the direction it may be that even the positive or negative the direction is very tiny but still we are only interested in that for now when we move into simulation put numbers then we will worry about actual how the system is behaving it will come to that but right now we can only worry about the direction of for example the job availability attracted huge number of migrants but maybe their job creation is very low the new jobs that they add to the system it can be there is because labour population it does not mean that similar number of jobs has to be created but the direction is the same the number of some additional jobs happen that is what you are trying to say. So, even in this so one has shortcut to figure out where is positive or negative feedback loop is simply count the number of positive or negative signs within a loop to the number of negative signs is odd then it is a positive feedback loop. So, here if you see plus plus and there is one minus sign there is odd number of minus signs so it must be a negative feedback loop even in this example I can do one more let us say x, y, z, w, x so here suppose I have minus plus minus plus as x increases so there are two negative feedbacks so x increases y decreases as y decreases z also decreases same direction as z decreases w increases as w increases x again increases. So, it is the same direction finally the variable x. So, short way is there is two negative feedbacks or a even number of negative feedbacks of a negative links then it is a positive feedback system. So, it is odd this x increases y decreases as y decreases z again increases as z increases again w decreases as w decreases x also decreases. So, eventually x went down when you originally started with x increase it. So, the shorter way is you can see there is odd number of negative links that means it must be a negative feedback loop. So, we have two loops here loop job availability in migration labour population job availability this is the loop. The second case job availability in migration labour population jobs job availability. So, that is the loop.  So, only problem comes in when there is one negative link then what happens then count the number of negative links if it is even then it must be a become a positive feedback. If it is odd number of negative links we have then must be a positive feedback. Can I say there are all these small tips that we can give, but then we will we will go through them and then we will do lot of examples. So, the number of negative links in a loop is even the loop is reinforcing number of negative links in loop is odd the loop is balancing.