This 2016 Toyota Tundra Double Cab is stock number 12029Z-A. We're here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used light-duty truck headquarters. This 2016 Toyota Tundra has the 5.7-liter V8 engine, pumps out 381 horsepower. This truck has been fully-safetyed and inspected by our service shop. It has a fresh oil and filter change. All the fluids have been checked and topped off for the state of Wisconsin inspection process. And this truck is 100% ready to go. Super white is the color. We shoot all of our videos in 1080p, 60 frames per second. So if you have HD capabilities on your computer, tablet, smartphone, or television, I highly recommend turning them on right now because it is your best way to check out the quality, condition, and options of the truck before seeing it in person. If you like the video and like how we do things here at Summit Auto, in the upper right-hand part of the screen is a link to subscribe to our YouTube channel where we do videos of our new and used inventory each and every day. Click that and then click the bell notifications. You'll get updates on the videos we do. And you can watch all those and see our inventory as it turns over day by day. It comes with the painted and polished aluminum rims. They're in pretty nice shape. And it has a nice set of Yoko Hama Geolander AT tires. These are 275, 65, R18s. And they look very new. I'd say at least 90% of the tread left on them. You can see on the very outside, you still have the little wear knobs. So I'd say at least 80 to 90% of the tread. Front fenders in nice shape. I didn't see any dents or dings in there. Headlight lenses are nice and clear. It does come with the factory fog lights. And that front bumper is in excellent condition as well. You do get the chrome trimmed grille. And the hood is in very nice shape too. Passengers side front fender looks really good. And the passengers side rim. No major scuffs or scrapes on there. As you go down this side of the truck, take note of how clean the body is, how reflective and mirror-like that paint is. We take these HD videos so if you are far away or even if you're close by, just cannot make the trip down but you're still interested in purchasing the vehicle. You can see the truck, hear the truck, and have confidence in the vehicle that you're looking at before you even get here. So when you do get here, there's absolutely no surprises. And you can make a smart and informed buying decision from wherever you're at. And if this video helps you make that buying decision, let your salesmen know that you saw the video and that Brett sent you. His back rim is in excellent shape as well. The back tires have just about as much tread as the front tires. It does come with the Bilstein shocks and they are part of that TRD off-road package. Frame and underbody looks really good for a truck with 100,000 miles on it. Cab corners, lower rockers all look really good. And the passenger side doors, I didn't see any dents or dings on them. Coming around to the back, the rear bumper is in pretty good condition. It does have full towing package which includes a receiver hitch four pin and seven pin wiring. The tailgate is in very nice condition as well. It has a shock down assist tailgate so it's never going to slam on you. Spray and bed liner, that's in nice shape as well. Looks really good. And that tailgate shuts nice and solidly. Going down the driver's side just as clean as that passenger's side. No dents or dings on the box. And the back rim is in pretty nice condition as well. Driver's side doors look really good and it does come with heated power mirrors. Inside the SR5 package gives you the black and gray cloth interior and there are no rips, there are no tears on the seats. They are in really nice shape. Power driver's seat with lumbar weather tech floor mats throughout. Power windows, power locks, power mirrors inside the doors look really good. We'll hop inside, turn the radio on, check out the miles and everything that the interior has to offer. So you can see that this one has 100,089 miles. You do get an outside temperature display. Digital instrument cluster there as well. And let's see if we can get that. You get your miles to empty and the outside temp instrument cluster is very nice and clean. Steering wheel is in excellent shape. You do get Bluetooth and information center controls on the left, radio controls and audio controls. I'm sorry that was on the right, but this is on the left, the Bluetooth and display are on the right. Cruise controls down here as well. This one does have the AM FM radio. You also get serious XM radio capabilities and this is where your backup camera shows up. It also has a CD player. Turned-out four-wheel drive over here is your factory brake control, your stability control and tow-haul mode. Down there you get an Augs and a USB jack and a 12-volt power point. Cup holders galore in here. Automatic transmission, that's a six-speed automatic. Passenger side format and seat are in excellent condition. No rips or tears. The headliner is in excellent shape as well. You do get map lights up there. Compass display in the rear view mirror as well as home link buttons for your garage door security systems and lighting systems. We'll take a quick look at the back seats and then we'll start it up and check out under the hood. Back seats are just as clean as the front seats. No rips or tears back here. It does have the latch-child safety system, the manual sliding rear window. Once again, that headliner is in really nice shape. These seats do fold up for extra storage. There is a close-able storage bin back here or a covered storage bin, you can say. And you also get the WeatherTech floor mat back here. Child safety locks on the back doors. The bottoms of the doors all look really good. I didn't see any corrosion on them. And we'll start it up and take a look under the hood. It starts right up. No check engine lights or anything like that. You get the tundra animation on there. And everything looks good. I would personally like to thank you for checking out the video today and hopefully from this HD video you'll have been able to verify the quality and condition of this truck inside and out all the way around under the hood. We have the 5.7 liter V8 engine. Engine bay is very clean. Runs very smooth. Once again, this truck has been fully-safetyed and inspected by our service shop. It has a fresh oil and filter change. All the fluids have been checked and topped off. You can see the shocks are doing a nice job holding that hood up. It's got newer tires. There's your emission sticker. Feel free to pause that. And this truck is 100% ready to go. For the age of miles I would highly recommend this truck from a quality and condition standpoint. And to see more pictures of this truck or one of our other 450 new and used cars, trucks, SCVs, minivans, wranglers, halftones, three-quarter-tons, one-tons, you name it, we got to go to that website right there, www.summitauto.com. Full pictures and descriptions of every single vehicle from two locations all at summitauto.com. And if you'd like to check out more HD videos you can go to youtube.com slash summitauto.com. Remember to like, subscribe, and share on this video and all the videos that you see there. Click the bell notifications. You'll get updates on the videos we do each and every day here at Summit Auto. In fact, in a second you will see a link to subscribe to our YouTube channel in the upper left. A link to more Tundra videos like this one in the upper right. A link to this vehicle on our website in the lower left. And a link to one of our latest YouTube videos in the lower right. Click those, check us out. And we're super excited to help you with this Ultra Clean 2016 Toyota Tundra SR5 Double Cab TRD Off-Road in Super White. Thanks again for checking out the video. Remember to like, subscribe, and share.


Hello everyone! Welcome to the session of Expansion of Function by Taylor series part 1st. This is Swati Nikam, Assistant Professor, Department of Humanities and Sciences, Valchan Institute of Technology, Sulapur. At the end of this session, students can create the Expansion of Function about any point with the help of Taylor series. Now, let us see what are these different Taylor series. Assuming that f of x plus h can be expanded in ascending powers of h, it is expressed as f of x plus h is equal to f of x plus h times f dash of x plus h square by 2 factorial f double dash of x plus h cube by 3 factorial f triple dash of x plus dash dash dash plus and so on. In general, the nth term can be written as h raised to n upon n factorial into nth derivative of f at x plus and so on. Let us call this as representation number 1. This is known as Taylor series. Now, interchanging x and h, we can express f of x plus h in ascending powers of x as f of x plus h is equal to f of h plus x times f dash of h plus x square by 2 factorial f double dash of h plus x cube by 3 factorial f triple dash of h plus and so on. Plus, the nth term is x raised to n upon n factorial nth derivative of f at h plus and so on. This is representation number 2. This is also known as Taylor series. Taylor series number 1 is the expression in ascending powers of h that is constant term while representation number 2 is the expression in ascending powers of x which is variable. Now, replacing x by a and h by x minus a so that a plus h is equal to a plus x minus a is equal to x. In equation number 1, we get f of x as a power series of x minus a as f of x is equal to f of a plus x minus a into f dash of a plus x minus a whole square upon 2 factorial f double dash of a plus x minus a whole cube upon 3 factorial f triple dash of a plus and so on. The nth term is x minus a whole raised to n upon n factorial f nth derivative at a plus and so on. Let us call this as representation number 3. Representation number 1, 2 and 3. All these 3 represents Taylor series. The first one represents Taylor series in ascending powers of h, second in ascending powers of x and third is in ascending powers of x minus a. We are going to use one of the three series according to the expectation of our example. So, let us see an example so that we will be clear about use of any one of the series. Before that, friends please pause your video for minute and write first two derivatives of function f of x is equal to tan inverse x. I hope you have written your answer. So, the first two derivatives of function f of x is equal to tan inverse x is, we know that tan inverse of x is a standard function and its derivative f dash of x is 1 upon 1 plus x square. Now, second order derivative f double dash of x is applying u by v rule. It is minus 2x upon 1 plus x square whole square. Let us see an example. Example number 1, expand tan inverse of x in powers of x minus 1 up to second power of x minus 1. Now friends see here how to choose the correct expansion of Taylor series for this example. Now here for tan inverse of x we need to expression in terms of x minus a. So, among the three forms we have to use form number 3. That is why in answer let us consider function f of x is equal to tan inverse x and comparing with x minus a form value of a is 1. Let us put this value of a in representation number 3. So, this is representation number 3 of Taylor series.  Let us call this as representation number 1. Now, f of x is equal to tan inverse of x. So, it is first order derivative. You have calculated already in previous slide f dash of x is equal to 1 upon 1 plus x square and second order derivative is minus 2x upon 1 plus x square whole square. Now, according to the need in this representation number 1 we want to calculate the value f at 1 f dash at 1 f double dash at 1 and f triple dash at 1. So, here let us replace each x by 1 and hence we get f of 1 is equal to tan inverse of 1 which is pi by 4. Now, from f dash of x f dash of 1 is 1 upon 1 plus 1 square that is 1 by 2. From f double dash of 1 is minus 2 into 1 that is minus 2 upon 1 plus 1 square is 2 square that is minus half. So, now putting all these values in equation number 1 we have f of x is equal to tan inverse of x is equal to pi by 4 plus x minus 1 into half plus x minus 1 square upon 2 factorial into minus 1 by 2 plus and so on. Therefore, tan inverse of x is equal to pi by 4 plus x minus 1 into 1 by 2 minus x minus 1 whole square divided by 4 plus and so on. So, this is the required expression of tan inverse of x in ascending powers of x minus 1. In example, it is as that we have to do the expansion up to power 2. Now, friends let us solve one more example for the practice of Taylor series example number 2. Expand 3x cube minus 2x square plus x minus 4 in powers of x plus 2. Now, again we have to choose the correct form of Taylor series among the three. So, in this example also we need expression in terms of x plus 2 that is x minus a form. We know that here Taylor series a is given by f of x is equal to f of a plus x minus a into f dash of a plus x minus a whole square upon 2 factorial into f double dash of a plus x minus a whole cube upon 3 factorial f triple dash of a. Now, friends see here the given polynomial is a cubic polynomial. We know that the cubic polynomial has three non-zero derivatives all higher order derivative becomes 0. So, we will stop our expansion up to f triple dash of a only. Now, let us calculate all these required first, second and third order derivative from the given function f of x. So, f dash of x is 9x square minus 4x plus 1. Now, according to the requirement of our expression we need to find out f of minus 2 which is minus 38 f dash of minus 2 is 45. Second order derivative at x is equal to 18x minus 4 and third order derivative at x is equal to 18. This implies that f double dash at minus 2 is equal to minus 40 and f triple dash at x is constant 18. So, f triple dash at minus 2 is without any change 18.  Therefore, f of x is equal to minus 38. Value of f of minus 2 is minus 38. We have calculated here. Then x plus 2 into value of f dash of minus 2 which is 45. So, substituting 45 here plus x plus 2 whole square upon 2 factorial is 2 into f double dash of minus 2 which is minus 40. Substitute here plus x plus 2 whole cube upon 3 factorial is 6 into f triple dash at minus 2 is 18. Do the simple calculations so that f of x turns to be minus 38 plus x plus 2 into 45 plus x plus 2 whole square minus 40 upon 2 is minus 20 plus x plus 2 whole cube upon 6 and it is multiplied by 18 is 18 divided by 6 which is 3 simply. So, this is the representation of given cubic polynomial f of x in ascending powers of x plus 2 with the help of Taylor series. For creation of this video, I have applied a text of applied mathematics by NP Bali. Thank you so much for watching this video and have a happy learning.


I mean, good evening, good afternoon, whatever it is, wherever you are on tap for today. We have our usual reminders about the upcoming act fest in June in Amsterdam and the internship progress project program. Sorry, it's early, which the deadline for students to apply is a second tomorrow. So, if you're interested in that, please, or you know, somebody who is please make sure they get that in there. Today, we're going to have an update from Explorer and and then from a working group perspective, we have requirements this week, correct? Yes. And we have somebody on for is Clive or Oleg on for requirements. Clive is on. Okay. Awesome. Awesome. And then I have updated the the lifecycle document to add, you know, this sort of first major release stage requiring a TSC review and approval. And so you can go over that. And then we have a proposal for a template to standardize. I'm launching working groups. And you have a thread on that. So, and then finally, I think Dave is going to reveal us with a proposal to open up the bug bounty for hyperlinked to the public. Any other agenda items for today? We're going to pre visit. Okay, then I think we'll turn it over to who's giving the update on Explorer. That would be me, Vinita, I'm representing part of the part of is unfortunately occupied in another meeting. Okay, great. Okay, so I joined the Hyperledger Explorer project last month. So there's quite a few new members that have joined in the last quarter. We have Ashish Kumar Jitendra Dikit from American Express India. Nick Franza, Mikiya Edwards and myself. We are from DTCC and we have recently added Kamak of Inspire Technologies from California. We are making good progress at this time. The project status is green. There are two major changes we have made in this quarter in the past six weeks or so is the front end was switched to React.js. So we have a new UI design. American Express folks are helping us with the UI design work. And besides that, we have also switched out our database from MySQL to Postgres. There are changes going on on that and also with a DB redesign for future development in mind. So our current plans are to finish up whatever we have started. So we have quite a few things on the front end going on. We want to complete the hookup of the front end with the back end data and finish that in the upcoming quarter. We also want to add some admin functionality. So we're helping us with that is Kam with starting with adding a channel that's the first admin functionality we will be adding to explore. So that is the update and I did post the update to the wiki. So it should be up there. If anybody is interested in looking at what it what the Hyperledger Explorer looks like right now I can share my screen. If that is okay. And Sure. Okay. Okay. Here we go. Share screen. Okay, so I have it running locally right now. On my machine. So can you guys see my screen. Yes, I can. Yeah. Okay. Perfect. So this is the new look and feel we were talking about. So we we do need to add a logo up top here, which is something we will be doing over the next couple of days. We do have a logo in place right now, but we just hadn't had a chance to put it in. I have the file that was created for us this morning. So we will be adding that soon. So right now it has five major navigation. Possibilities up top. So when you first log in dashboard is where you would be presented to this is where we want to show some analytics about how many blocks coming per hour per minute or transactions per hour. So this is something we're working on right now. So we know what we want to put here. You only see what the one transaction that got pushed last night that when I was working with this the block with the one block right now and The activity chart right now down here that would be showing blocks as they come in. This is right now static data, but we are working on Making a dynamic. So you will see it as it comes in. Peer graphs. So right now the Network we have up and running has four peers. So this is just showing that Then we have the network tab, which is going to list all the peers in the network currently The blocks will list all the blocks that we have right now. So this is the data that is coming from our Postgres database right now. And this is transactions page right now is static, but we are working on making a dynamic. So it pulls the data from the database and puts it out. And also the smart contracts is to be done. It is in the works. So this is all going to be driven off of what channel you're looking at. We are building functionality to be able to change the channel. So right now there's this is the only channel. We have the my channel. And this is where we are at with this and that is my update. Any questions. Thanks, Anita. Any questions. How does it interact with identity. How does it interact with identity. Right. Able to see You know, is there any restriction on Who can see what We haven't gotten that far yet. We have to build that into it. So this is this is the very first basic Being able to take a peek into the ledger and see what's on there. But yes, that will be coming up in future sprints for us. So, will it support the fabric while and why my version together. This is working with the fabric one dot oh right now. I see one dot one is released, but we haven't upgraded to that yet. So that is also going to be happening sometimes soon. Okay. And second question is about the docker image. Do you have any plans that make some doctor image. Yes. So absolutely. Absolutely. So that that is that is what we want to do. We were discussing yesterday. So make it easier to provide a docker image for people to get up and running quick. That is also slated for for the second quarter. Okay, cool. Thanks. And can you speak about your plans for supporting the other hyper ledger infrastructure projects. I am afraid I don't have an insight into that maybe Part of them might be able to give a better update on that. I can get back to you on that. Great. I know when I was in China, one chain who was working on the Explorer project talked about sporting sawtooth as one of the next things that they wanted to do. I don't know what the status of that is, but I know that they they had it in their plans. Oh, they did. Okay. Yep. Okay, so unfortunately they're not on the project anymore. I'm not sure what happened, but they're not at this point. On the on the contributors list. I might I myself joined last month. So I'm not sure what the status is there. Okay. Okay, I don't know if you know how already has a Explorer capability. I know that they had started off with a lot of Handset capabilities with their platform that you might be able to find existing code within their project that would help you Oh, awesome. Similar capabilities there. Yeah. And then on the sawtooth project. We had a contribution a few months back adding in an Explorer that was geared towards sawtooth. And you'd be more than welcome to just grab that code as a starting point. So you'll see that in sawtooth Explorer. I think what the repo is called or any type of ledger. And then I think Nate is on from the indie project. If there's some similar Explorer capabilities there. On the indie side, we haven't added an Explorer capability yet. We do have some APIs to get the right transaction sets and the right information out of the system. So, you know, if there is a common code base for kind of the UI side, I think that there's some interest in integrating those APIs into whatever others are using Right, that would that would make sense. Yeah, I would guess across all of the projects. And I think this is an assumption that led to the creation of your project assumption that for most of these blockchains, there's just going to be a couple simple restful get queries that would get most of the information from these chains. So it shouldn't be a wide set of differing APIs that you'd have to address. Well, actually, there probably is. Right. Right now we have the. Yeah. So right now we have the Node SDK we are using for for fabric. So, right, I mean, I think that this is, you know, this is an opportunity to, you know, be collaborating across all the projects to get alignment on what that might be. If we want that to be indeed, you know, sort of cross platform, there are going to be some distinctions, right, you know, we was talking about, you know, sort of per channel visibility. Obviously, I'm unaware of any other platform projects that we have that has the concept of channels. But, you know, so there are going to be some impedance mismatches that we have to sort of work through but I think, you know, maybe this is an opportunity, maybe in the context of the architecture working group and then in conjunction with all the projects that are interested in getting integration with the Explorer function so that we have a common Explorer across all these really involved in what it really means is that it's a it's a collaborative effort. Right. So, you know, I heard asked for, you know, when is blockchain is for going to do the saw tooth integration. I heard similarly, you know, the discussion about composer and really what it boils down to is it boils down to everybody. You know, what what what is the interest, you know, open source is developed by people scratching an itch if you have an interest in doing something you get down and do it. So, I think, you know, what we need to do is we need to be thinking about how are we going to affect a little bit more collaboration to actually get these things done if that's what we want to do. Yeah, and I guess I was trying to point out that there's probably not 30 different API calls at each project. It's probably a small handful. So it's a tractable problem. And I think that was that was part of the impetus for this this project. And then when project sponsors come forward to create a project that has the aspiration of being across the hyper ledger technologies. That's that's certainly a statement that that they're looking to go do that that work as far as it being a kind of a doocracy. So there's going to there will have to be a balance between if if a cross project effort is started. How much does that imply a resource demand on the existing projects and how much is that a statement by those people starting the new project that they're the ones that are taking up the the the onus to go across those projects. And I think one of the things that you know the fact that there are explorers that there is an explorer for sawtooth is an indication of a desire for that for that capability so in that you know in the doocracy view of things. And the other observation is that the longer we go down the path with an assumption of a single back end, the more bound we are and the harder it is to add additional features so you know that again as as Dan says if there's some intention for something being kind of cross hyper ledger capabilities then there has to be some pressure put on on ensuring that that happens. Well but again make I'm not sure that pressure is the right. Adjective here I mean yeah you're it's not a function of if I agree but you understand what I'm saying though that there has to be some I do motivation to do it. But again, I think that you know it was also a function and if I recall correctly the way that it was presented was, you know, other back ends could be supported. It wasn't we intend to do all you know support for all the back end and actually I think there was just two at the time, right.  And we did discuss some collaboration between the two products but I don't recall any of that ever happening so. You know, again, I think, as I was trying to say before, I think it's on us collectively to find ways that we can do this collaboration so that we can end up with not multiples. But you know we can have a common project that is in fact across, you know, and satisfies those requirements but it means that there's a certain alignment of apis or certain degree of alignment of the apis to get access to the information we're looking for, and then agreement that you know we'll share some resource and doing that work. You know, necessary to do the integration with the various back ends. And, you know, I think, as I said, you know the architecture work group is an opportunity, you know, we could leverage that potentially to try and figure out what, you know, what it would be and then share that amongst the various projects, so that we can actually start working towards that objective. And, you know, if there's a sawtooth explorer, then I think collaborative working to figure out understand that code base and figure out how it does integrate, you know, maybe what we need is to have a pluggable set of widgets gadgets whatever you want to call them. That are, you know, reflective of an underlying platform, but that are particular to a platform, because maybe there are some distinctions like channels and so forth that you need to be able to height, you know, to elevate to the level of an explorer. All I'm really saying is that I think that level of collaboration is needed in order to pull this off. The other. Well, I do think that if a project has taken on a charter, though they are taking on the responsibility for fulfilling that charter. And in the case of Explorer, my recollection is that the charter for that was to be a cross platform explorer. Otherwise, it wouldn't have been, you know, interesting outside the realm of of say fabric specifically in this case. But likewise, you know, it would be weird to take an Iroha explorer and put that out as a hyper ledger explorer with a stated goal being cross project. I think Dan's pointing out the other end of the spectrum Chris, which is just an acknowledgement that this is really a fabric project, change the charter to reflect that and make it essentially managed as a sub project under fabric. I think that at the very least we should have integration milestones, you know, we should set the few. I don't know if it's quarterly or every even two months, we try to put some API that people can plug into and get some feedback across the project. If you thought as people want to chime in, I don't know, just to make it easy for other people to understand like how much they need to do in order to work together. At the moment, we just update each other about what we have done. We should tell about kind of what we are doing so that it's easy to kind of, let's say if now it's March, maybe okay, mid May, we'll have something to look up to. And then if a sub project or another project needs to change some stuff to work together like the pluggable things that Chris mentioned, it's going to be easy at the moment. I think that the projects don't talk to each other at all, right, at least in the context of Explorer. So so this has something you rise the plan. You know, it doesn't look like we even have the milestones on any roadmap. Right. And that's, that's really my point. I think, you know, again, if, you know, if we want to do this and I think we should, and I think many of us do want to get to this level of collaboration we have to stop acting as if we're all independent competing projects, and start working collaboratively across the various projects now it's starting to happen. But again, I think that it does require sort of investment and interest and execution by all of us collectively. That's all I'm saying. Well, if there's not a team can publish some API that you can plug plug stuff into is going to be easier so that we don't have to dive in too much into it. I think it's the other way around though, right. Did the other projects would say what they expect that yes, something that's an Explorer that's reading information so that's calling the API is that are produced by the by the other projects. So. Right. To that point, the roadmap that was presented to us. We, this is not even though we started with the fabric. This is not just for fabric. There is on our roadmap items to make it compatible with Ethereum sawtooth and other platforms too. So this this is just the starting point we started with fabric. Well, the theorem is a different beast if you have a different API right like completely different. Yeah. Well, they all do that. Yeah. They are different. So you're going to have to have an API that's pretty open, flexible to accommodate, you know, significant variations. And I think that I think it would be an interesting challenge to actually do that and you know, you have to kind of, I mean, there are two possibilities, right. It's always like this. Either you take the common denominator and it's not going to be very useful, or you have to make it, you know, capable of handling as much as you can and, you know, have some part be not appearing or be disabled if it's not provided by the underlying framework. I do think, you know, it's still, it should still be a goal, but I agree, you know, we cannot force people to work on things if they don't want to. This is open source, right? No, but then the challenge should change, right? That's what Danny's saying. If people don't, yeah. I think that's the only that's the only point that I was having as well is that look, let the charter reflect the reality of the project. Well, I'm just saying that it's a sad reality. Yeah, I don't know, it's true. It's very true. It's a sad reality that's not going to change until we view hyper ledger more than we view our individual interests. That's exactly right. Right. And, and we're not there yet. Yeah, I don't even know if I, if I'd go quite in that direction with it. For me, it's quite simply the, the charter that a project aspires to, if they're marching down a path that's making progress towards that charter, that's great. And so if, if the charter is wide, then that's, that's what they've signed up for. So. Yeah, but so let's give her, let's give them a chance. We heard from Vinita that they still have this, this plan, right? So I think we can, at this point, it's fair for the TSE to express the, you know, to basically give a reminder that the goal of the project and the charter is to support more than one framework. And completely agree, not suggesting any, any remediations right now, just that recognition. Okay. Well, actually, but I am, I'm suggesting if that's really interesting to the sawtooth community, for instance, then some of the sawtooth engineers are going to have to, or people that are interested in sawtooth are going to have to step up to help accelerate that if that's indeed what is needed everybody is driven by whatever their priorities are. Right. And, you know, I think, well, at this point, we can't just expect that people are going to do things because. No, I totally disagree, Chris. I'm saying that the charter that they signed up for was to go cross project. If that's what you said you want to do, that's what you're going to do. I'm not saying that I don't think that we can reverse the tables and say that a project can come out and claim that they will be a cross project effort and then require resources from all the other programs. Yeah, so to, I mean, to reinforce that point, sawtooth has an explorer that's clearly a priority for the community for the subject community, but it's easier for sawtooth to build their own explorer than it is to go off and try to modify and work with something that's principally focused on fabric. You're getting in and again that ease is sort of avoiding the collaboration and that's my. I don't think it's avoiding collaboration at all. I mean, we've put out the API's the code is out there. Somebody has signed up to say, alright, there's an interesting problem here which is how can you come up with an interface that goes across multiple API's. That's work that the explorer project signed up for. Dan, I understand, but I don't recall any effort whatsoever to reach out and engage the explorer team before that work was done. That's all that's my in the very early stages one of the first hackfest we had we worked on what was a common API. I had no idea what happened with the artifacts of that, but there was some initial effort at that. And certainly all of our API documentation is, I mean, it's pretty straightforward. I just put the links in there. It's not like there's a lack of collaboration in the sense that there's withholding of information or anything. I didn't say any information was being withheld again. Open source is a doocracy. It means if you're interested in doing something if you have an it you scratch it.  That's my only point. And so, again, if the interest is in the collaboration, engage and remain engaged and remain and continue to press that. But if we're not interested in doing that, then maybe you're right. Maybe we should just acknowledge that these are all independent projects. But I think we do. I think that we should be, you know, aligning a little bit more towards the ideal that, you know, that Brian and others are affecting with this organization and that is to have it be an umbrella. There that that fosters the kind of collaboration innovation cross project to the point where we do have pluggable components that interoperate with one another. That's that's where we're I think I think that's where we're trying to get maybe we should stop fooling ourselves. But I personally think that that's where we should be heading. Hey, guys, this is Brian. I've been trying to talk for about 15 minutes, but fighting the new teacher. I, you know, there are certainly some mandates that I think the TFP can play some projects and that, you know, overall we can expect projects to do, even if they didn't want to. One of those is, you know, a release process. What do you get to call a one dot oh, right. So one of those might be, you know, paying attention and joining other working groups around architecture. I mean, the things that it have to do with the quality of the release and that have to do with following kind of a standardized development process. One of the things I don't think we really can mandate of a project is to do work that none of the individual developers to add specific features to add specific functions that the developers on that project simply aren't otherwise motivated to because the response to that won't be, you know, we get those features built despite developers not wanting to work on it the response will be they leave the project. The only way to really affect this is to for somewhere a developer to show up with patches, just as if they showed up on sauce use and said here patches to implement support for poet on chips other than Intel. Right. There's no expectation on Intel to support other non Intel chips with with poet extensions right. Likewise, we need we need those developers to show up and the only way that we as as the project has to do that to pay for work like that we've done is the internships. We can talk about whether we want to pay for other types of development that don't spontaneously appear of their own accord I think that the very, very dangerous path but one that be on the table, but other than those, you know, paying for that kind of work. I don't really think we can cause that reports materialize short of one of the now many companies using and depending upon thought to to be interested in doing that work. As long as the project as long as explore as long as those developers are not actively refusing to support that kind of thing. I think we should change the charter. I think the only reason you would change the charter of Explorer is if you wanted to prevent somebody from adding support for sawtooth to it, or prevent somebody from adding a real hard to work otherwise leave that prospect that possibility. What differentiates a sub project then from a cross project right because, you know, if, if we were to create something that was, you know, let's say propose a hyper ledger wallet, and it and we're only staffed and resource to do that for ero ha. Why should that not just be a ero ha wallet instead of a hyper ledger wallet. Because by definition, if you showed up to an ero ha wallet and said, hey, I've got support for sawtooth for this and they, and they felt charge the order would allow them to say no to that. Right. If instead it's the, you know, this is a hyper ledger wallet that somebody shows up with patches to support ero ha or patches for both either fabric. The developer should at least meet them halfway by saying, here's where you can go or here's the API to follow or, hey, that's, that's great, but it needs to support this feature, you know, like internally you can have that occasion that that here's, here's the standard to me, but unless the charter were to say this is the ero ha wallet, there's no reason the developers should say that's not, that's not the thing we will support. No matter how good the quality of the passage. Well, I think everybody's set a piece here and maybe we can chew on that over the intervening week and head on to the next subject. I agree. Okay, so Clive, thank you, Vanita. Next up is the requirements working group updates of Clive. Hi everybody is Clive Bolton here. I've been heading the requirements working group up now for the year or more. And so I've got some mixed reports. The report actually spans more than the past quarter. It's more, I'd say the past year. Folks when they come along to the requirements working group, we don't have a regular cadre of attendees, the folks who come along to the requirements working group. We have a couple but generally the folks come to the attendee requirements working group are on new solution architects who join consultancies show up a couple of times. Sometimes folks from the consultancies intend to author requirements, but very rarely do they actually get to author requirements. After talking with some of them quite often the reason for that is that once they and actually this has happened a couple of times once they start sharing authoring requirements. It leads them into the business ideas, and that gets cut off pretty quickly. In fact, very broadly. It stops because I think they're sharing some IP in ideas and we've already covered many of the use cases which span generic functionality. This actually happened last week. The product traceability group came along from, I think, North America and projects traceability group came along. They've got a marvelously rich website, but don't really have any starting place to go to implement Hyperledger. I'll come to that in a little bit because most of the folks that I'm talking to are not really developers, they're solution architects or even business architects. What is happening though, increasingly, and I've actually visited some of these folks personally actually even flown to a couple of and actually gone out of country to visit somebody in Canada, is we have folks coming to Hyperledger who really want to develop new SaaS and solutions, but they have a different starting point than a technical starting point. They start the requirements, but they need that next step to get going and they find that many of them I find are now looking for a mobile client, a mobile application that interacts with the Hyperledger projects and are almost looking for a copy and paste mobile app. So I'm going to talk a little bit about that. I'm going to skip over our accomplishments over the past quarter because these have been a reflection of what I've just updated, just gave. And also they are, they're actually, I would say, more of a contributions over the past year, over the past four quarters. And they span everything from input from a research group on after the fact mandate changes that got stopped pretty abruptly to supply chain counter anti counterfeiting. And we recently had a an academic project submitted contributed by Tatic consultancy on actually a full full belt braces permission blockchain on fabric. So, and there's links to that on the on the on the update. So the way in terms of like our participant diversity, we have, we have folks coming from all over the US and also Canada and internationally. And again, I think the, certainly the folks coming from India are much more interested in a, and a mobile client help in foster a mobile requirements for a mobile client. And also in Canada as well with the Canadian government legalizing the small growers of that of cannabis. So there's a need for a mobile client to, and actually this interfaces with the product traceability.org to, to, to provide a very simple in app, which interfaces with a larger SAS hyper ledger database. And so I think that the overall requirements with group our, our, our folks are participants, folks showing up have changed from sort of folks who come along to because they recently joined the hyper ledger blockchain ecosystem, just navigating and trying to understand how do they plug in probably into these other projects that we've just spoken about like, such as Explorer. But they're, and they're also particularly interested when they make any contributions to the requirements working group that they rarely do. How do we interface with the other groups such as the architecture working group. And I don't think we have done a great job of that so far. And I think the opportunity is to personally, I am a developer, or program manager developer. And I have actually been giving some actually reprising Mark Miller's work on on security, particularly capabilities in JavaScript and also mobile applications. And I think this is probably a message in a bottle that that we could be working to with some of the business people to on the requirements of a mobile app and then turn that into some UI screens just getting some and trying to do the simplest things possible to make a easy to get going mobile app that works with some of the more popular hyper ledger projects, whatever the easiest way to do that is, whether it's the restful API that was commented on earlier. So that's, that's pretty much my update, I would actually like to add, additionally, I think it's really important and somebody put this in the chat that the The one, the, the sample sample code that we come up with should really should be in light of meltdown a spectra and Cambridge analytic or and all that stuff, and the ability of new standards which have dropped in Atmoscript 2015 ES six and so forth. We should be Coming up with the best security templates or just That we can in in sample code. And I think there's a number of ways to go about doing that. So that's, that's pretty much my Update and I'd love to hear any feedback. Thanks for the the thorough description there. I'd taken a look at some of the meeting minutes and been listening to your feedback on on what sounds like the principal challenges that the If I can overstate things slightly that the requirements work group has difficulty producing requirements. And I wonder if we're at a stage now after this working group has been active for so long that we can thank the working group participants for their time and maybe transition That community into a discussion forum so they can keep Ford momentum with the sorts of mobile app discussions that you were talking about there, but we can archive The products such as they are so far from this working group And then there won't be any confusion by Any of the the general public that comes to the hyper ledger working group Comes at the hyper ledger requirements site and gets maybe some confusion based on the current state of artifacts there I think I would I would support that and support that for two two really important factor of reasons. One is that we do occasionally get folks who come along And add a document title to the hyper ledger requirements That we're working on but that's all they do they don't actually add actually add a document And they I think they add it because they would like to get to those requirements or they'd like to have somebody else create the requirements but it never actually happens unless one of us who's I would say is a more regular participant and there's not too many Dig in and actually user expertise to all of those requirements So that has happened but it's it's attenuated to to to pretty much zero So I but on the other hand is this this discussion in this need to get going with hyper ledger projects from an app developer point of view as I'm not sure about is surge the right ways but it it's it's active and it's it's it's tangible I get And the other thing that happens is I get you know private advice please you know can we talk about this privately because they've got some sort of a business idea and they don't want to quite share that but they need this application piece and I would like to Help surface that and turn that into into code into some working especially app code Great right so and and you know this has been saying this for the longest time and every time you know people ask me how come there aren't more you know use cases and requirements. And you know the fundamentally inclined you just you just mentioned this people aren't willing to share for various you know oh my God we're going to disrupt the world. You know sort of business thoughts and so they're somewhat unwilling to share what their use cases are because they don't want to give away their bright ideas to somebody else but You know I You know I know you know I know that you know the the the folk that are working on you know the various platforms, various tools are being driven by some set of requirements. Some of those are getting shared you know within the context of the projects. You know as you know jeers or you know whatever have issues or what have you You know that are motivating development of some new feature or of some Capability And And we're we're you know maybe the approach that we've been thinking about is somewhat You know turned on its head that instead of that that we actually work to see how are the requirements that are driving the development of sawtooth and fabric and borough and indeed Anaroha Aligned or not as the case may be and surfacing where they're common and surfacing where they're different and then trying to understand Both aspects of that. Why are these the same and why are these different is their different use cases is you know what's motivating that that set of things. And You know I think initially you know we had the idea of starting with a set of use cases and then distilling from use cases a set of requirements and then mapping those requirements to some development. But the development in the individual projects has been you know sort of Parochial and And I think that again this this this highlights the fact that you know I mean we could continue down that path and maybe that's the right path. I don't know But I do think that there's opportunity here for us to be You know larger than the sum of its you know a certain amount of time. Something that's larger than the sum of its parts and yet right now you know I think if we continue down the path then we're just the sum of our parts. I can I also belong to the Google Developer groups have been a belong to that organization for five plus years and I noticed that They have an active Code labs in that help foster a community of app developers and it's almost I could see some sort of opportunity to Stand things on their head and figure out what are the What do the API's look like across some popular projects and Or maybe even there's some quite I couldn't I don't quite know what hyperledger explorer does apart from the great demo we saw earlier But if there's some sort of a A restful API which is has commonality somehow Understanding what that API looks like and the Capabilities that it provides and then and then Discussing and building the mobile app that but mobile app client that would work with that and trying and trying to use standards to do that whether that's mobile web standards or Or a client that will work on both iOS and Android So, you know, so Dan made a proposal Do do do we feel like that's fully fleshed that People are ready to think about Making a decision on that proposal or is there a desire to Maybe Have a little bit more discussion I'm fine with this especially since Clive seems to agree to Agree with it, too I do think that this This Dan mentioned another part of that which is this discussion that is kind of quite important for people that are new You know professionals arriving and they're They want to jump right into the to hyperledger unit By weekly provides that point, but it doesn't actually add too much other than just me giving some navigation updates I would like to much more Turn that into into some into some helps in that into some some app So that smaller projects that don't come Don't come from folks don't come from large consultancies could get going with hyperledger Maybe think about coming back with a proposal that creates a discussion forum that might meet on the phone or video chat or something on some periodic basis Okay, okay And On the other side to that Coming up with a Mobile app is that also of interest I know that there are some efforts to do mobile apps for the indeed ledger simply because it's the identity edge agents mandated But I don't know if there's a jet if there's general developer support for that A broad hyperledger level or not It's been my experience with distributed apps that each Each distributed app is you know an app unto itself And so you would want a mobile component of of an app But I don't know if there's a good way to have a general purpose Mobile client But yeah, I think we're always open to new projects and that's that's something that maybe you could Think on and if there's a way to make that general purpose You could propose that as a project or maybe if if you're able to have What heart was referring to here as an onboarding form an onboarding call that that might produce some Some other Engineers that have a similar interest or or designers for that matter that have similar interest and you might be able to collaborate on something Yeah Okay, I see the there's a template Which is going to be for standardizing and launching working groups that is coming up Maybe some of this work on the edge stuff is You know could be Generalized into a template I mean generalized into a working group that can then work at least explore some of these things without Being bound to a specific projects because that seems to be the biggest Point that we are discussing today because What seems to happen is there is a Fragmentation or balconization And only the working groups are the only glue sort of trying to hold things together rather than You know the projects are naturally as they mature They are diverging from each other and as they mature they have these two needs one is you know Some kind of a wallet app the other working group that probably should be there is some kind of a Deployment focused working group that has Is you know Puts together Some of the common themes around deployment So the product work product of a working group should not be seen in the same light as The work product of a Project because most of the you know it's it's Lightly bound together and it's cross project most of the time And it's very difficult to elicit Support from people because they're not you know in most of these cases people are either employed by Technical companies or work full-time on these projects like fabric or Souto's or Indy Of course there is a character of people who come along to help you know with the coding but even they are you know either somehow able to Devote a hundred percent or you know eighty percent of their time to this to producing Artifacts like code but for the working groups. It's a different story. You know that's that's been our experience So so we have to rethink our approach to working group and what the artifacts they produce should be and I am proposing that Clive is wanting to produce some to actually create some mobile app You know maybe it can be the launching pad for you know a particular mobile apps targeted to a particular DLT but at the same time be thinking about how that could you know those kind of things could be generalized into something bigger than Just one DLT and Sorry to cut you up. We're kind of digressing away from the the working group Agenda item Yeah, we are Well, okay, we haven't we haven't closed on it and we only have a couple minutes left So I I think you know given that I didn't hear any pushback on You know sort of calling the vote. I think so the proposal as I understood it is basically to deprecate the requirements working group and I'm not sure how we archive if you will The the the products of the working group and then maybe Let me just speak up in favor of keeping the working through different sections I think that you know the proposal is basically to To deprecate the the requirements working group and thank Clive and and the others for their all their efforts So Todd you want to run our role? Yeah, I think Brian are you trying to yeah I didn't hear just one one last it's kind of the thing to for folks to think about as a reason for The requirements working group to stay which is all the time people ask us, you know how What are what are some use cases? What are some ways in which I would use? These underlying tools to meet, you know specific challenges in my industry and It's been very useful to say we have a set of use cases on the wiki that are abstractly defined that are You know You know about explorations from a Place where you can detach it from specific vendors to say here's how you would use Hyperledger technologies to address You know supply chain issues health care issues those sorts of things and so you know it may be that that we need to Reboot the requirements working group to do that But it's been useful to have somebody that's have a working group I feel like separate from from the individual projects as at least a place to direct that interest And maybe it just needs a reboot. I don't know but it feels like if we lost that working group We might lose that cross-project view of you know What are the kinds of ways you might use these technologies to solve those problems? I think Brian just to picking up on that I think maybe it might be good to take a couple of weeks and just look at that and just in Actually, Jeremy had done some work very early on When there was only a maybe fabric In terms of doing that almost like reverse engineering one of the capabilities of the interfaces of a Other project and surface those so that they can So that people coming with requirements can understand what those are I Think the TSC is ready in a rare moment of decisiveness and alacrity to act And I'd ask that we just continue on that stream So I remove that we take a vote to close the working group All right, so voting for for Closing a work group and archiving correct. Yes. All right all in favor. Please say hi Hi Any abstaining any opposed all right that passes unanimously. All right Thanks everyone. We're at end of game and I did send out the proposal for The new milestone and please weigh in also on The working group template discussion and we'll pick those up next week. So thanks everyone and Have a nice day


Here's just a little bit about us. I'm a senior engineer at Microsoft working on service mesh things, but I like to do anything to distribute it systems or Kubernetes, which is how I got involved here. I'm an MLOps engineer at Meringue Code. I'm the co-founder, so we do a lot of machine learning deployments on cloud native, with cloud native platforms, so we do a lot of work on Kubernetes. So we're going to run through these four pretty quick points today as it is a lightning talk, and hopefully by the end of it you'll want to come and help us make Kubeflow Metal better. So going to start by answering the elephant in the room, what is Kubeflow Metal? So Kubeflow Metal is a new way, I guess new, of deploying Kubeflow onto a Kubernetes cluster on bare metal servers. So what it is, it's a Terraform module that is composed with a couple other Terraform modules that will spin up a Kubernetes cluster on Equinex Metal, and it will deploy Kubeflow on it based on the manifest. This creation, like I said, is on bare metal clusters, so it doesn't have the bells and whistles of a cloud provider, so you've got a little bit more control. We use KubeVIP as the bare metal load balancer for your cluster, so when you create your Istio and Gress Gateway, it's going to be powered by a KubeVIP in the background, and we actually, in the future, hope to have ways to bring your own cluster, where we just assume that you have load balancing provision there, and we're also looking into independent versioning of those components. Yes, so on the high level, this is all the architecture looks. What we've done is basically replaced the underlying managed infrastructure that you normally get from AWS, Azure, or Google. So with that, we can just provision with the head of Terraform, we can provision the underlying infrastructure, and you have your Kubernetes environment, similar to what you have in the cloud environment. So everything is managed by Terraform, so if you can write Terraform scripts, you can easily create a provider to target whatever bare metal box you want to access. We have load balancers implemented for you with KubeVIP, it's easy to configure and provision, and the cool thing about this is it's a cheaper alternative to cloud infrastructure where you can basically have a fixed cost rather than something that just runs as people use the underlying infrastructure. So this is a kind of a high level view of the components of KubeVIP, what you get when you run a Terraform apply. Like we've mentioned, the underlying infrastructure here is going to be equinex metal servers at this time. We're looking into maybe adding different kinds of providers, like line out or digital ocean into the future, and then of course we use Terraform to manage those boxes. KubeADM is the process for actually installing Kubernetes on top of that cluster, and the good folks at equinex have already put a Terraform module together to do a lot of that stuff, so shout out to them for helping us do this. For PVCs that you often use for Kubeflow, what we've done is we used something called the local path PVC provisioner, and what that will do is instead of having to set up a secondary like storage component of your equinex cloud installation, we'll just use the nodes of the Kubernetes cluster in order to provide you PVC storage. There's a plugin out there that does that, and we use that for just a really simple experience, especially if it's just CI CD or just testing. It's really quick and less hassle to have to deal with. Now, of course, on top of that, you've got Kubeflow. These are the different pieces of Kubeflow that we install by default, but we hope to add more plugs for folks to modify and add other things. So this is the installation step. It's pretty easy. So we have a demo repo in the main repository, Kubeflow on-prem. So you can go in, get cloned to repo, configure all the environment variables. You can run the cubes, the Terraform apply. It runs all the scripts, and you're validated that all your packages are installed. We've got a video here because I was nowhere near brave enough to try to demo this live, and we've also sped it up a bit. So this is what the process looks like. If you're familiar with Terraform, this looks familiar. From the beginning, like a complete install, it's going to be 602 different Terraform resources, including your cluster, including all the different Kubernetes manifests that you're applying to your cluster. We've sped this up because the process here running on my box takes about 18 minutes or so, so you throw more compute behind that. You're going to see that time increase, and it also takes around the same time, a little bit faster. I say maybe about half the time, actually, to tear it down. So in your head, start imagining some of the CI-CD use cases, the elasticity of being able to tear a cluster up with Kubeflow and tear it back down to validate some experiment or to validate a version of Kubeflow even. There are lots of applications for this. This finished about 52 seconds real time. It's about 18 minutes. This is what it looks like. This is the familiar Kubeflow dashboard where you can click through. You're going to have a, like I said, a Kubernetes Ingress Gateway or Istio Ingress Gateway with an IP address.  You can put that behind a DNS A record or whatever else and be able to access the dashboard that we all know and love. Why should you consider Kubeflow Metal? Yeah, so the number one benefit is a fixed cost. If you're still experimenting with AI and ML and you're not fully, you don't want to spend a lot of money in the cloud. You can just gang up some bugs, sabers in your office and just try to install Kubeflow Metal on it. The other advantage that we see a lot from running this is like you can quickly bootstrap an ML environmental infrastructure for your team. So if you're still doing stuff and you're new to this, you can quickly bring up the environment and use it. The other cool thing is the deployment is very elastic. So you can easily add 10 nodes, scale it down, destroy it, and make it 20 nodes and things like that while you're testing. The other part of it that is going to be really interesting is like plugging it into your CI-CD process. So you can have a CI-CD process that basically brings up all the clusters you need. You can provision from a GUI where you can specify the size of parameters and all the things you need to provision to tell from infrastructure. So that's something we're really working on right now. And there's some special use cases where you don't want your data to touch the cloud. Things like financial data, insurance data that you don't want to move to the cloud. You can easily run it on Kubeflow Metal in-house. And IoT devices, if you're doing federated learning, you have a lot of IoT devices in the field and you don't want to quickly build models to do inference and things like that. You might want to consider Kubeflow Metal. Yeah. So we are looking for more people to make this better. I think the current version on GitHub is 010 Release Candidate 2. So we're very early, but the cool thing about open source is you can just share it with people and just talk about something cool that you've done. So on our roadmap, we want to expose more knobs in the configuration, change the password, all these things take it to the next level and make it a lot more feasible for folks to put into production. Yeah. And currently, right now, we've demonstrated this proof of value with Equinix. So we're going to extend it beyond just that. And now, we have all the providers for bare metal boxes. So things like Clanode, Digital Ocean, and if you have any infrastructure on-prem, we might be able to build a provider for that as well. So we're basically looking for people to help us with these efforts. So if you're working on Digital Ocean and you want to walk on the tariff from providers for that, we can use them to help in that place. Yeah. And wrapping up here, we want to go ahead and contribute some of the change. You have to change some of the manifest for Kubeflow to make them technically more correct for Kubernetes and allow for, for example, changing the load balancer service. And so we want to upstream some of those changes to the Kubeflow manifest working group slash SIG so that it's democratized and available for everybody. And then other things like wiki updates and stuff like that. Yeah. And basically integrating with CI CD. We're working on that right now so that we can do GitOps provisioning and stuff like that. Thank you for coming. Thank you all.


Inner Sanctum Mysteries. Good evening friends of the creaking door. This is your host to welcome you again into the Inner Sanctum. Come here. Huh? Kind of dead, did you say? Well, yes, but we have our grisly little amusements. For example, our museum has the only authentic copy of the Morning Leisure. In music, we're very fond of Mendelground's overture to a Midsummer Night's Scream. As for the movies, what really rattled our bones was The Razor's Edge. As the dentist said when the drill hit bottom and the patient screamed, you've got a nerve. It begins at night outside a railroad station. It's raining. And Anne Winslow has just missed the last train that would take her to the house she lives in a couple of miles outside the city. Taxi! Taxi! Trying to hide getting a taxi in the rain, Miss. I know, but I've got to get one. I missed my train. Taxi! All taken. Want me to check your bag? No, Porter. I've got to get home. Hey, there's one with his flag up. Stop with the light. If you run, ladies. Oh, yes, thank you. Like trees don't change. Don't change. Hey, lady. Made it. I guess you didn't see me waving till you've been beside Walter. I ain't taking passes. Well, you've got to. The lights changed. Yes, but listen. Uh-huh. You see, I missed my train, and I live some way out. Not really very far, though, on the reservoir road. The reservoir road? I know it's outside the city, but I'm willing to pay a little extra, and the flag on your meter was upside down. Okay, okay. Oh, thank you very much. Well, I guess I can relax now. What's the matter? There's someone else in the cab. He's a friend of mine.  If you already had a passenger, why didn't you turn your meter down? Because he ain't paying for the ride. I was frightened. The man on the back seat of the cab with me didn't say anything or do anything, but I was frightened.  And I was frightened. Driver? Yeah? I think you passed the reservoir road. I did. It was the road that turned off to the right just a little way back. I didn't notice it until after you passed it over. Okay, sit tight. What's eating you back there? I have to turn around, don't I? The man, when you stopped short, he slid over. He's leaning on me now. So what? He won't bite you. He's just tired. But I don't know it. Believe me, lady, if you're dead, you wouldn't be any happier. He leaned against my shoulder without speaking, without moving. His hat was still over his eyes, and the upturn collar of his coat still around his neck. My shoulder began to hurt, and the weight grew heavier. And somehow from the silent body beside me there came a feeling of cold. A deadly paralyzing cold. I straightened up and pushed him away.  And the collar of his coat parted, and I saw that his throat had been cut. Yes? What are you yelling about now? Nothing. I fell asleep and had a nightmare. Well, stay awake. I don't like that kind of music. All right, I'll stay awake. This it? Yes, this is where I live. Kind of isolated, ain't it? How much is it? A couple of bucks. Here. Thanks. Good night. The key. He didn't know. The door. I forgot to lock it. The little pal here. He wants to sit down. Yeah, this ought to be nice and comfortable for him. You can't. I did. You see, later he got kind of fun to you on the long ride together. He don't want to go back to the city with me. He wants to stay here with you. No. Yeah. He's a very headstrong fella. I wouldn't care to argue with him. You can't leave him here. Hey, I better hurry. Looks like the rain's coming back.  He don't want to go. Besides, you wouldn't send him into the storm, would you? In his condition. Tonight, my... No, no, come back! Come back! No one except the... No, the phone. The phone. Of course. I'll phone the police and they'll take him away. There's a room I'm coming to. There's a man whose throat has been cut. And he and I are alone in this house. I won't look at it. If I turn my head, I can see it. He's moving out of the chair. I'm good. Yes, I would have come earlier, but... Morning, men. I must have been unconscious all night. I beg your pardon? Who are you? Manson, Detective Second Grade County Police. From the police? Yes. Oh, but I couldn't reach you. Last night, the phone was dead. I tried... The lines were out all through this area. That's why Mrs. Blaine didn't get through to us till this morning. Mrs. Blaine. The old power life woman down the road. Yeah, that's right. As soon as the telephone lines were working again, she phoned us. She was worried about what she'd heard during the night. She... ...read something during the night? A woman screaming this... ...from this house. That was me. Why did you seem to be all right? Why did you scream? The dead man in the living room... ...moved. The dead man in the living room? I see. Uh, suppose we go take a look at him, huh? Don't believe me, do you? Well, it's not an easy story to believe, is it? But we don't have to argue about it. All we have to do is go into the living room. All right, come in. I feel sort of shaky. You see, I fainted when... ...when he moved, and I've been on the floor all night. This is the living room? Yes. I think I'll stay out here if you don't mind. I'd rather not look at him again. There's nothing to be afraid of now. My policeman's here. And it's daylight, and they'll take him away with it. Well, Miss... You saw him? I guess you must have been dreaming. Dreaming? Mm-hmm. Because you see, there is no dead man in the living room. There's nobody there at all. Try looking under the sofa next. Why? Oh, you weren't looking around for the corpse. You were just hunting for that collar button you lost last spring. All right. Have it your own way. But if you're happy to reach in under a hunk of furniture... ...and your hand touches something cold and wet... ...that won't be a collar button for him. Well, let's get back to Ann Winslow, who was a nice girl... ...but who had corpses walk out on her. No dead man in the living room. But he must be there. I don't believe him. Now, look here, Miss. He was in that chair in that... Now, Miss, it was just a dream. Or maybe a shock you had of some kind. Don't call me Miss. My name is Ann Winslow. That's a pretty name for a pretty girl. He was there. I took a taxi in the city last night. When I missed my train and he was on the back seat... ...and when I pushed him, he fell over. And I thought that his throat had been cut. And when we got here, the taxi driver brought him into the living room... ...and went away and left him here with me. Well, sometimes it's hard to tell the difference... ...between what you dream and what really happens. Stop trying to be kind to me. He was here. If he was, he'd still be here. Corpses had a habit of staying with her. Wait. There was blood on him. There'll be some on the chair. On the back, maybe. Or the seat cushion. Well? Nothing. How'd you happen to miss the train last night? I was at a party. Did you get the taxi's license number? No. The driver's name, remember? No. I was too frightened to think I'd... Would you recognize the driver if you saw him again? I'm not sure. It was dark and I... I might, but I... You're not giving me anything at all. Thousands of cabs, thousands of drivers... ...and I've got nothing to go on. I'm sorry, Mr. Manson. Well, forget it. The drive out here wasn't bad... ...and I met someone nice. Thank you. I just wish I could be of more help. Well, if anything comes up... ...don't be shy about yelling for me. It's my job. You... You don't think I'm crazy? Of course not. This whole business... Well, it was just one of those things, huh? Well, I'd better get back to headquarters. Yes. You've been very patient. That's all right. So long. Goodbye. Just one of those things. One of what things? He... he was in that chair. No, it's all right now. There's nothing. Nobody in it. But I can't sit in it. Seat cushion's getting shabby. Maybe if I turn it over... On the other side... ...someone already had turned it over because... ...it wasn't a dream. It wasn't a dream because it was blinded. I hope you'll miss.  Oh, no, thanks, Porter. There's nothing you can do. Well, you're the young lady on Mr. Train last night, aren't you? Yes, I am. Of course. You're the porter who helped me. Plenty of taxis around now. I know, but I'm trying to find the one I had last night. You are? Yes, you see, I left something in the cab. I thought if I could find the taxi again... The cab's not easy. Well, uh... ...but taxis usually work in the same neighborhood all the time, don't they? I mean, they had their special stand... Well, that's true, Miss, but you didn't get your cab last night at a stand. It was cruising. Oh. You didn't happen to notice the license number, did you? No, Miss, I didn't. Or recognize the driver? I didn't even see him. I'm beginning to wonder if I saw him. I beg your pardon? Nothing. I guess I'd better go. I don't want to miss my train again tonight. Goodbye. And tonight, I locked the door. That's the lights on. The cab driver, what are you doing?  And a friend of mine. Hey, I noticed he ain't around. No. Where is he? I don't know. I was awful fond of him. I wouldn't like to think of him wandering around cold, maybe, and, uh... Why were you looking for me? The police didn't believe a... Policeman, huh? Didn't believe what? That... There had ever been a cross. It's too bad.  Maybe he'll change his mind. Maybe one of these days you'll spot me and call a cop. Maybe the cop will start asking questions, and I ain't good at answering questions. They... won't. Once you put the finger on me, they will. I won't do that. I'll forget the whole thing, honestly, I will. Maybe. But will the cop you called? He thinks I'm crazy.  Which means the cop's gonna be back, and if he comes back, he's gonna find out you're not crazy. Because you're not crazy. Stay away from me. There was a corpse, and he had his throat cut, and he was in this room, and you saw him, and if the cop starts believing you, you'll look for that corpse, and he'll find it sooner or later, and then he'll ask me questions. So it'd be a lot better if you went away. I'll go. I'll do anything you say. Don't touch me. You'll go. But further than you think... Your hand! Seconds, you won't have to. Okay, okay! For a minute, I thought maybe it was a cop. Hey, what's the matter? I don't like the way you're looking at me. Listen, listen. Maybe things were lost up a little bit last night, but I'm cleaning it up. Hey, put that in your hand. Now get away from me! The driver, he came back for me. Get away. Miss Winslow, what's the matter? Let me help you up. You better get back to your house. No. I have no coat. Come on. He's there. He? The driver. I see. How's he care of him? He doesn't... doesn't need care. He's dead. Did you? Somebody... He's thrown it. Got it. Don't talk anymore. He started to strangle it. Here's the house. How did you get here? My car, south in the road. I meant in time to be... I was worried about you. I want your steps. I can't go through that door. I'm trying to cross it. You've been very brave. Just step past him.  You're not? Sit down. The chair. Not the chair. It's the one. All right. The couch. Now to get the body away from your door. Notify headquarters. Yes, of course. Where's your phone? In the hallway. Right outside the living room door. Good. Phone's dead. The lines? They're all right. But the wire on this phone must have been cut. Never, maybe. I've got to get word to town, though. Yes. Can you drive? No. That's too bad. Otherwise, you could hop into my car. Look, I'll be gone only a little while. No, don't. A man was murdered. And his murderer must be found. We can't waste time. You're right, but... I leave. You lock the door of this room behind me, see? Nobody can get those windows. So with the door locked, you'll be perfectly safe. All right? All right. I'll lock it. And don't open it for anyone but me. Yes. Then I'll be seeing it. And don't open it for anyone but Mr. Manson. And I'll be perfectly safe. The door for... The phone. Wait, he told me not to open it for anyone but himself. Still, this isn't anyone. This is the phone. No, I'll let it ring. I won't leave this room. Let it ring. Let it... He said the phone was dead. Not the line, but only my phone. Mr. Manson said the wire had been cut, but... If it really had been cut, it... It couldn't ring. And it is ringing. It's ringing. That means he... He was lying. And if he was lying, he wanted me locked in this room, so I wouldn't tell anyone... Stopped. Stopped, but I... I can call the police. I'll call... Calling somebody. Put the receiver back. I said put it back. But... That's gone. That's better. Living room, please. How come you tried the phone? It rang. Too bad I didn't rip the wire out as I should have. Careless of me, but too bad for you. What do you mean? I have much choice, am I? The driver's buried alongside of the corpse you met last night. Back in the woods. That's where I went. No, not a police. I'm a murderer. The corpse you saw last night was an old friend of mine who had ideas about sharing my profits in a little rocket I run. I cut his throat and fixed things with that cab driver to take the body out into the country and bury him. You hopped his cab and the girl didn't have brains to get rid of you before you spotted the corpse. You got panicky and left it with you and told me about it. I rushed out here to sell you a bill of goods. You bought all right. Except the cab driver got scared when he spotted you watching for him at the railroad terminal.  I trailed him and realized how easily he lost his head. I took care of him. And? And now I'll have to take care of you.  I've done all right so far. What's that? The door. You did call somebody before I got back. No. The door. I forgot to lock the door. I've got to get out. Let's just stay pooper. You won't get... Anybody else? Hey you. He's dead. It's a doornail. He was a murderer. He was. That's why he started shooting without waiting to find out. All I wanted was to tell him to move that car of his. It was blocking the road. Glad to cut up, Mr. Manson, wasn't he? An ambitious still wanted to leave his mark on his clothes. He probably believed wholeheartedly in that proverb. You know the one. All work and no slay makes Jack a dull boy. Oh, that reminds me. I'd better hurry out and turn the motor up on that taxi. Oh yes, it'll be still going. You can rely on that because nothing's sure but death and taxis. Inner sanctum has come to you through the worldwide facilities of the United States Armed Forces Radio and Television Service.


Hi friends. Welcome back to my channel and welcome if you're new here. My name is Jen. I'm a certified weight loss and nutrition coach and I follow the WW or the Weight Watcher's Blue Plan. Today I'm here to talk to you about whether or not it's time for you to quit WW. As a nutrition coach and talking with my clients, I get this question a lot. Should I continue on WW or is it time for me to make the switch?  A little bit of food for thought when it comes to whether or not the WW program is the right program for you. So if you're excited for today's video, please give it a big huge thumbs up and don't forget if you're new or you're not yet subscribed. I'd love to have you hit the subscribe button and don't forget to click the bell next to it so you don't miss a single video. I do upload most days of the week so you definitely don't want to miss out. Check out the description box down below for nutrition coaching. I do have a meal planner that's available. We're running low on inventory so pick it up while it's still available and also personalized macro and calorie calculation, which is essential to lose weight, especially if you are considering giving up the WW program. Calories is program proof, easy to follow, never changes and may be a good alternative to the WW program for you. I can do your macros and calories personalized to you and then I offer one-on-one coaching sessions in both 30 and 60 minutes increments so that I can help you more one-on-one reach your goals. Links, discount codes to my favorite things and my Facebook group are also down in the description box. We'd love to have you join that community as well. So let's jump right in because we have an important topic to discuss today on whether or not it's time for you to quit WW. I want to give you a little bit of back history for those of you that are new to my channel or don't know my entire history. So over a year ago, following the WW program, I decided to switch to a cleaner approach, basically eating more whole real food versus a lot of the processed fat-free sugar-free foods. And this was just so that I felt better overall. And I also knew that eating all of those foods wasn't sustainable to me. That I might eat that free cheese to lose weight, but do I want to eat that free cheese after I've lost my weight? So I made that transition about a year ago over to the cleaner approach to the program. Since then and since receiving my nutrition and weight loss coach certification, I've also made some other changes and that is tracking calories. I do still follow the WW blue plan, but it is secondary to me reaching my calorie and protein goal every single day. That is my number one focus because I found myself under eating on WW and I didn't want to do any more damage to my metabolism than I already have being a chronic dieter. So I decided to put a heavy focus on calorie counting with a secondary focus on the WW blue plan. So that's a little back history on me and why this video was something that I felt that was needed to be made in addition to getting this question a lot in my coaching sessions. Before I jump in, I want to remind you that you have to do the program that works for you. A lot of people have long-term success on WW. They're able to keep their weight off long-term, maintain and never have to make a transition to another program. And if that's you, congratulations. You are a model for the WW program. But there are a lot of people who struggle to not only lose weight on the program, but when they get to maintenance, it is a huge struggle to keep the weight off. So if you're struggling or if this has crossed your mind on whether or not WW is right for you or maybe you love the program and you just want to hear what I have to say, then this is the perfect video for you. So one thing to think about on whether WW is right for you is do you want to attend the meetings or are you able to attend the meetings? Let's be honest, paying 45 or $55 a month to attend a weekly workshop is a large amount of money. And we really have to think if we're getting the benefit out of that weekly workshop. Now, don't get me wrong. I love all the friends that I've made. I love my leader, but it's just not beneficial for me to drive into the workshop, sit there for a half of an hour to 45 minutes, drive home when I could be using my time a little bit more productively. I've actually been working out on Friday mornings instead of going to the in-person WW workshop. Now, as we know, there's virtual meetings as well. That is about $20 a month. So this may be a more economical, affordable solution, but is it benefiting you? Are you getting anything out of those virtual meetings or would your time be better spent elsewhere?  So really think about whether or not you're utilizing your WW membership. Reason number two, maybe the point system just isn't really working for you anymore. And I want to start this portion of the video off with reminding you that the point system is basically putting you in a calorie deficit. A calorie makes up a portion of a point. So Weight Watchers is a calorie restricted program because the only way to lose weight is to be in a calorie deficit. And Weight Watchers just chooses to call this calorie deficit a point system. So what I want to really focus on when we're talking about whether the point system works for you or not is how these points are made up. Now, I understand WW's approach and leaning us towards choosing healthier options. By giving us zero point fruits, vegetables, lean meats, chances are that's what we're going to reach for when we're wanting to build a meal or a snack. But they do heavily penalize healthy things with high point content. Things like avocados, nut butters, and really real whole food. And we'll get into the real whole food in the next segment. Although I understand how the point system is made up, I struggle with making certain foods certain point values, which leads us to choosing those items. For example, fat free or sugar free items. I also find that the point system does not lend itself at all to intuitive eating. You're constantly thinking about food. There's days that you're starving. There's days that you're content. And it just really doesn't set you up to get to maintenance and be able to intuitively eat effectively because you're always thinking about the points in food. I also find that the point system makes me think about food all the time. And honestly, I would rather put my energy in my mind somewhere else a lot of the time. So if you're someone that struggles with the points values of healthy food, if you struggle to be satisfied and full, or if you just don't understand or think that the point system works for you, this may be another reason to not be a WW member. So the next topic is real whole food. I really want to talk about this because I think that this is one of the main reasons that I chose to move into calorie counting as my number one priority and WW as my second priority. Like I mentioned, I found myself eating a lot of fat free sugar free foods. I was getting stomach upset. I was not full or satisfied. And it really dawned on me one day that the food that I'm eating to lose weight should be the same food that I'm eating when I'm at maintenance.  I don't want to eat sugar free this and sugar free that I wanted to have a holistic whole food approach to the program. And I wanted to see if I could stay in my points by eating real whole food. And this leads me to one of my main issues with the WW program and something that you should think about if you also want to steer clear of that free sugar free and you really want to focus on whole foods. Unfortunately on WW we only receive a certain number of points every day. So we're automatically going to choose lower point foods so that we can have more volume of food throughout our day. It's human nature. Who doesn't want to eat as much as we can and still lose weight? The problem with that is we find ourselves choosing fat free cheese because it's zero points versus full fat cheese. That's two to three points. We're choosing sugar free syrup that's made up of chemicals versus pure maple syrup. That's a great natural sweetener. I didn't want to do this anymore. I didn't want to have to feel like I had to choose these unhealthy process options to stay within my points. Let's be honest. A bank of chips is less points than hummus. Now tell me how that makes any sense at all on whether or not you should be choosing a bag of chips over hummus. So if you're struggling to stay in your points eating real whole food maybe it's time to take a look at the program. Another reason you may want to consider dropping the WW program is if weight just isn't the most important thing to you anymore. If that number on the scale isn't the be all end all then maybe it's time to put your focus into something a little bit more beneficial to your body like strength training, eating healthy foods, non-scale victories, taking your measurements, seeing how your body changes as you lose fat and honestly the weight on the scale isn't a direct link to how healthy a person is. As you know bodybuilders due to their weight can be considered obese by the BMI chart and we all know that when you have less than 10% body fat you're not obese but the chart tells us that. So we can play a little bit of a mind game on us and it can become something that we obsess about. I know a lot of the clients that I coach say that they are obsessed with the scale it's time to put the scale away and not make the scale the be all end all. I recommend weighing yourself no more than once a week even longer if you can do it two weeks maybe once a month maybe even better for your mental health maybe you don't want to step on a scale in front of a coach at a WW workshop or maybe you don't want the whole world to know whether you were up or down at your workshop. Don't let the scale affect your mood don't let the scale allow you to throw in the towel and don't feel ashamed if your weight doesn't go down one week and I found myself when I was weighing in at this workshop to start feeling a little bit of embarrassment if I was stepping on the scale and it wasn't going in the right direction and we should never feel that way because a lot of times we can do everything right and our body just has a mind of its own. So maybe it's time to put the scale away and focus on some other pieces of your health journey.  I know it can be a scary word but healthy fats and fat in your diet in general is essential. You'll find yourself feeling a lot more hungry if you're not filling up on protein and fats and the WW program the point system actually penalizes us for fats. Prime example of that would be avocados. You can find yourself having low blood sugar levels because you're just not eating enough you find yourself extremely hungry between snacks and meals because if you're not choosing protein and healthy fats the food that you're eating isn't going to sustain you from meal to meal or snack to meal and let's be honest the low fat diet is kind of out.  Since I focus on calories I find myself eating a lot more full fat everything full fat dairy I'm putting oil on my vegetables instead of Pam spray I'm using real butter instead of fake butter I'm eating nut butter instead of PB2 it's very freeing and eye-opening and I definitely can tell you that I'm much more satisfied when I'm incorporating fats into my diet and unfortunately because that affects the points a lot of people on WW eliminate or restrict their fat so if this is you maybe it's time to make a change and the last thing to think about is WW a lifestyle I know they talk about it being a lifestyle not a diet but is it truly something that will transition over into a lifestyle do you want to count points for the rest of your life do you want to skip the cake at birthday parties or skip beers out with your friends because you don't have the points for it or are you somebody that just doesn't count your points on the weekends or vacations or maybe you throw in the towel for an entire week and just decide that counting points and tracking just isn't something that you want to do there are a couple pieces to this to think about number one is counting points every day realistic probably not we are busy people and there are days in our life where we're just not able or willing or wanting to track points so because it's not realistic isn't something that's considered a lifestyle change something that you can do for the long term and secondly when you don't count points you tend to feel guilty do you tend to feel that you screwed up whether or not you ate unhealthy during the day or not maybe you stayed within your calorie deficit maybe you made good food choices but because you didn't count points and track your points you feel like a failure and when we feel out of control or feel like a failure we tend to eat a bunch of crap food and now we're putting ourselves outside of our calorie deficit and we're making it so that we fall off the wagon so to speak and sometimes it's really hard for us to get back on i know for myself i'm an all or nothing person and when i was strictly counting points if i would go over my points say on saturday or sunday then i would just throw in the towel until my next way in the following friday and what i'm finding with other lifestyles especially calorie counting is you really can't screw it up if you have a high calorie meal or treat you just compensate for that the rest of the week now yes you can use your weeklies for those high calorie meals or treats but a lot of people are scared to use their weeklies which please use your weeklies if you're on ww or they go over their weeklies and that's when they throw in the towel so with ww you really need to think about is this something that is sustainable and is this truly a lifestyle for you are you going to count points for the rest of your life now like i said there are a lot of people who do ww forever and are very successful there are people who do ww to lose their weight and then transition into another way of maintaining their weight whether that be calorie counting or intuitive eating we are all different so we need to think about what works for us but i always say whatever you're doing to lose weight you should be able to do to maintain and sustain that same weight loss so maybe it's time to really dive deep and take a hard look into ourselves to see if the ww program is the right program for us and if it's not just be aware that there are a lot of other programs out there and if it is then continue doing what works for you i hope that this helped open your eyes a little bit gave you a little bit of food for thought things to think about when it comes to the ww program so if you enjoyed today's video don't forget to give it a big huge thumbs up and if you're new or you're not yet subscribed to my channel of course i'd love to have you hit the subscribe button and don't forget to ring the bell next to it if you'd like to talk about this a little bit further or maybe dive into what may or may not work for you when it comes to ww or switching programs you can take advantage of my one-on-one coaching sessions which are on my nutrition coaching website along with macro and calories now whether you're on ww or not it's very important to have your macros and calories done because you need to make sure that number one you're eating enough but number two you're also in a calorie deficit in order to lose weight links discount codes to all of my favorite things are also down in the description box in my facebook group head on over and join us we'd love to have you thank you for hanging out with me today i really hope this video helped you and if you have any other questions please leave those down in the comments i'm happy to help and i'll see you in my next video bye


We are part of a company level attack. Right now we are on Golf 29 conducting the platoon version. So my platoon is on Golf 29 while the other two platoons in my company are conducting a two platoon attack on Golf 36. So right now we are doing a platoon level with company level assets on Golf 36 as well. On Golf 29 we have 240s and we have Moz and squad level assets trying to close with and destroy an enemy that is located within Golf 29. Within my squad every rifleman has a M27 automatic rifle. Three members in my squad have M320 grenade launchers so these grenade launchers have the ability to employ HE on trenches and bunkers that can ultimately change the level of the fight and we can allow our squad to close on a trench. The purpose of this entire exercise is to certify our company in a live fire exercise which will ultimately perfect our movement and our communication which will get us ready for a deployment. There are always challenges that we face with every live fire attack, every range, every mission that we get handed. There's never a mission without friction. That's what I always like to say is if there's friction then that's a good thing. So if you're dealing with a mission and something comes up that wasn't in your plan then something's going right. And today we were executing our attack on Golf 29 and my squad was too close up to the Moz front blast which was not expected so we had to pull back about 50 to 100 meters and then we were able to get the Moz on a trench which allows us to close.