Good morning, it's eight o'clock and welcome to another one-hour breakfast webinar. My name is Moby and if I just quickly click through the slides, my bio is there, but first I'll do the disclaimer for this webinar. All bookmap limited materials, information and presentations are for educational purposes only and should not be considered specific investment advice nor recommendations. Trading futures, equities and digital currencies involves substantial risk of loss and is not suitable for all investors. Past performance is not necessarily indicative of future results. The only real thing to note in my bio is that I have done this for quite a while and I do both discretionary and algorithmic trading. Let us get rid of that and turn on the capture. First thing today is to have a look at what is on our agenda. We are going to look through today's economic calendar. We are going to do a very quick recap of what happened in ETH. Then we are going to talk about PREP, that is preparation of what we can use or if anything from RTH to our ETH. That is whether we are trading in Asia or London. Then we are going to delve into the first of many delves into the Wycoff concept of springs, doubles, testing, an area which could be considered as a double bottom or a double top. Today is calendar. There is not as much on the calendar as it has been lately. We have at 8.15 the ADP employment change which has marked as a red, i.e. of significant importance. At 10.30 we have the crude inventories which is very red if you trade crude and can add some volatility to the equities. If the actual release is somewhat different from forecast. Going back to our little agenda, the first thing we want to do was an initial recap of ETH. If I dim these pictures and we go along and look at the screens. I think if we start off in the trading view screens because I have zoomed out as far back as is really visible. If I zoom back any more than this you cannot see anything at all. You cannot see the individual bars but I think you get the message. The close was around about here in NQ and around about there in ES. And then we broke down on the Asian Open and if there is a reason it could be the earnings released by Uber. It could be anything but that could be one of the factors which caused it to break down. The red line here in both ES and NQ is the previous days low. You can see that NQ broke down under yesterday's low, tagged it and went down further before reversing back. It is still below yesterday's low which means it is outside yesterday's range. For ES, ES broke down. First thing it did was tag or just have a small spring and we will get into that a little bit later. A small spring of yesterday's low recovered and then tagged it again or close as and broke through or distributed around here and broke down properly before rebounding and it is almost back at yesterday's low. I just want to recap again why I have got these two charts which I do use. Obviously not as zoomed out as this normally but I normally have it zoomed out something like that. In fact that is more like it about there. The reason why we have these two charts together so that we can see the high correlated action between ES and NQ and to go into a little bit more detail into provide a little bit more clarity why that can be or may be important is that if one of them tags or breaks through a significant zone or price level that may be enough for them both to reverse or to continue at that point. If we are going to have a continuation and if we are going to distribute here around the low and then continue one can drive the other so it can be NQ or ES but the fact that one has done it means that the other is likely to follow suit regardless of whether or not it's hit a similar zone i.e. for example the same yesterday low for ES as for NQ. It doesn't matter that ES on this occasion hadn't hit yesterday's low. The fact that one of those two symbols had done it is often good enough for the ARCOS to get the price action behaviour that we then saw. But again I don't use these charts in isolation and a big big disclaimer that you know the VWAP bands that I've got here are for informational purposes only and not for the basis of taking any trades. They're just an approximation of where value is. But we never have a trade with just a bear chart. The idea of this presentation as with my colleagues presentation is that we use this to then look at the liquidity over here to see what we get from liquidity presence to increase the probability of setups or trades that we are willing to take. I've only got the ES action from today so that's basically 1800 that's 6pm New York time or the Asian open which is just about there. I have to reboot to make sure that this presentation runs smoothly so I don't tend to keep my book map running for day upon day. But that is something that is worth mentioning because when we get into talking about the preparation of how we can use the RTH session in book map as well as the charts to look at zones that could have some significance or interest in the ETH session. The previous days RTH is important and so although I can't drag it down I can elucidate by looking at the type of action from the previous day that would cause us to market. So I mean if this was the previous days RTH and there was a significant level and by that I mean when we look at the previous days action and I'm sorry I am delving straight into the preparation and using profiles here so I will slow down. So you're in the room slow down so hello. Yeah I was already getting on to that topic but anyway let me just say out of courtesy if anybody's got any questions feel free to pop them into the Discord or the YouTube. I know that we don't at the early stages of this webinar we aren't going to have many live subscribers and yeah that's perfect expected and accepted. But anyway if anybody does have any questions yeah I'm happy to make this an interactive session so feel free to pop those into YouTube or Discord and I will as soon as I see them read them and comment or answer them. Okay so yeah so even though this is not the right session in terms of the ES book map for the RTH the previous day but I'm going to go into one of the first things that we look at okay and I'm going to have to sorry I've got the NQ one let me go back to ES okay and I'm trying to get into the afternoon session here sometimes it can be a bit of a pain looking at a trading view chart on such a small screen. Right okay there we go okay what I'm actually looking for is a midday New York time so again these are not exact times or reference what I'm actually looking at is the afternoon action in ES. So you can see here there's something akin to a double top almost a triple top since it comes back to the same zone before it breaks down. If this was not an earnings release week and again I'll stress how different this week can be from typical weeks you know this would be the very first thing that I would look at everybody's different but the very first thing I would look at is the afternoon action. So I'd look at this period midday through to 4, 5, 6 o'clock whatever the trading view action is and I'd look at the highs and lows. So here you'd have a triple top or a head and shoulder whatever you want to call it zone in ES from around about 06, 0625 down to about 03-ish. Okay so then I would go into the book map chart for the afternoon and I would do it before I rebooted obviously because once you reboot in book map you will lose certain information when you then reload the same data even if it is in the cache or the cache that you can load in book map and if you don't know what I mean by that one let me just scroll back and explain. If you scroll back when you restart book map you will always get or you should always get a little left chevron arrow which you can click if you've got cached data on your drive and your local drive and then you can add data so what I did because I think I rebooted around about 7.20 p.m. New York time so around about there is I added an hour's locals or two hours locals so I got the rest of the Asian session but one of the things that you do lose when you restart book map is the SI information so you can see here that all the stop release information starts around here which is 1939 I think that's sort of indicative of when I must have restarted book maps I must have done it around about half past seven in the evening so one of the things that you really want to look at or you might want to look at for those highs that we pointed out in ES for the previous afternoon was what stop information was up there what was the delta positioning if you grouped that information on the same chart in other words you zoomed and drag it into when I say that I mean you drag in a bit and you get a certain bit of information so you can see the particular delta the accumulation of buyers and sellers at that zone and you can also get the stops and icebergs information may be relevant because it may show you what's already been flushed out if there has been a big flush there is a possibility and again all of this is just possibilities and probabilities no certainties that they may not need to or may not want to have another test up and flush it to have a reverse spring or up thrust but the other thing to and I'm going to get into the profile now as well is that in addition to looking at that information in book map to see what was there and sorry there was one other bit of information that I'd be looking at in book map as well I'd be looking at the large trades so the large buy or sell trades just the large individual trades or clustered trades or however you have it on your book map to see what might be retested so there are a couple of possibilities or was always infinite possibilities but two of the possibilities are a flush of the activity at that double triple top and also a retest of the largest trade there because I tend to zoom in a lot and I tend to use book map more for the microaction one of the things that I will do is I have a chart in Sierra maybe I'll show it sometime showing me the large individual trades so I can go back 24, 36 hours very quickly and see was there a trade of 500 here or 1000 here just quickly so I can reference it and you'll often see if I'm streaming during the session that I'll have marked that in this column which is the cloud notes column that there might have been a 500 trade here for example that's just hypothetical because there's nothing marked here so what we're looking at in book map is what large trades occurred in that triple top area are there lots and lots of buyers and sellers that could be potentially flushed if price is taking out a little bit higher and if it is flushed there was a potential for a big reversal up because we are in a trend up that has not broken the more severe daily uptrend line which I mentioned the other day so we're still in a very very strong uptrend despite any downward action we may have had in this ETH session so we're looking at big trades presence or what presence do you have the buyers and sellers in those zones and what stop iceberg information mainly stop information we have in relation to what happened on those three touches of that zone okay right so I mentioned that we were also going to look at profile let me just stop and see if there's any questions no questions okay alright okay so someone asked in the last webinar if I could have a quick overview of how the profiles interact between RTH and ETH in the sense of how I use the profiles I would refer you to my colleague Tom if you want and in depth discussion of volume profile on a day by day by day basis but this is just a very quick overview of what I'm looking at so I'm looking at two things the two of the most basic things when I look at a profile chart and to explain what this is I think I have done before the grey edge is the volume profile the shaded area is a time profile or a market profile the pink lines are the point of control where the most volume is interacted in that particular session the vertical grey shaded zones are evening or ETH sessions and white ones are RTH sessions so if I turn on all the evening sessions and zoom out vertically we can start talking about how the ETH session has interacted with the preceding RTH session and how it may provide some information and I state some information that could be useful in the following RTH session okay so one of the things that I'm looking at I mean sometimes you get picture perfect information this does not happen very often it's like an indicator that has magical properties but this is one I mean one of the beauties about having a look at volume profile on Sierra and I must get back to book map after I do this and I'm going to do this as quickly as I can is that you can join value so you can basically merge all the value together so you can see where value begins and where value ends let me just reset that chart to get rid of all of that so we can see individual sessions so again the white sessions are the RTH sessions and the grey sessions are the ETH sessions so one of the things, again I say it's picture perfect but one of the things that may happen occasionally is that you have clear value that has developed over a period of time and one RTH session can be considered a decent period of time so here you have a clear value in their session which was whatever date that was, Monday and that value is delineated let me get a crayon up here let me change colour to pink okay, that value was delineated about there and there so you're looking in ETH for a potential flush beyond there and beyond there, so above and below and that's why I say this session here just happens to be a picture perfect session so you're looking at value and you're looking at the opposite of value so if I get rid of all of that go back to here, let me just get rid of that go back to the cursor the opposite of value is trend or exploration as they call it in the auction thing where price is exploring until it reaches value so in this RTH session if we turn it into a price chart and you can see over time what happens it had value, broke down from value and eventually found some new value there so you're looking at two things in the profile do you have value or do you not have value do you have value or do you have trend so if you have value is there a potential and this is when we look at book map and we go back and we see what action was there in RTH is there a good probability that there's a reason why they may take this high just to flush them and if we actually go and see what happened on that day so what they did was they flushed the top of the RTH value first and they flushed the bottom and then it formed another value area during the next RTH session let me just stop and see if there's any questions sorry, I will pause at this point Torchbearer, I do not do predictions that is one thing that you cannot use in trading nobody can predict the future you can't even predict the weather so I don't predict that I simply with a one minute chart it's just to help me see a zoomed out picture of what is happening in book map and to show me the direct correlation between ES and NQ again you've used the word predict in your second question again I can't answer that one because we cannot predict we can only find possibilities or probabilities we cannot do any prediction so that is just one example so to speak very very roughly we are looking at anything from the RTH session I want to get it back to book map as soon as I can here to see where the value was on the profile and where there was no value and where there was value so where there's no value we're talking about low volume nodes where it's clear and then again you go back to book map and you see what the price action was in book map around there so it's basically a map and I'm going to now get rid of it and we can always revisit this in a future webinar to assist how you might then look at the next session okay alright let's just zoom out again and just have a quick look I think I actually missed the news so let's have a look at what has happened at 8.15 I'm sorry I was too busy talking to even notice that the ADP employment change had been released at 8.15 so the actual number was 324,000 new jobs the expected number was 190,000 and the previous was 497,000 so it was a beat that was at 8.15 so if we zoom out for a while 8.15, yep 8.15 so positive news and the market did not react favorably instead it has continued to break down a little bit okay if we just get these back to how we like them and drag them there so yeah this is how I effectively use these one minute charts although I think this is on a three minute at the moment it doesn't matter if you're that interested in one minute charts and three minute charts there are some great practitioners around that I do recommend you read their stuff one is Lance Beggs I look at Lance Beggs and I look at Adam Grimes they both looked at this kind of stuff and they provide some very very good information I think Lance Beggs is also very very famous for his attention to process, process, process, process focusing everybody on sticking to a plan and sticking to process in fact I think he got so frustrated that he's recently stopped tweeting and his website's going to disappear as well but yeah he is one of the best instructors in terms of looking at these individual candle type charts okay I do not tend to take trades based on candle type charts there are certain things where I've got some statistics on levels such as yesterday's low or yesterday's high and again if I take a trade on that basis it's not actually on the basis of the individual candles it's on the basis of the type of stop that it is possible for them to flush through so again it's not on the basis of any price action it's not on the basis of any moving average and the VWAP is just an approximation of value okay right okay yeah so let's look at book map for a little bit and let's have a look at what's in the charts as we come up to half past 8 an hour before the open okay give me a second while I just observe so as you know from my last few webinars what I tend to do on the vertical scale is zoom out as much as possible on ES and then on NQ or vice versa just to see any resting liquidity that's been around a long long time and I discount any resting liquidity or I reduce in my own mind its significance if it happens to be on a particular set of round numbers being the 50s and the tons hey Mothers I doubt whether I have pronounced your name correctly but hello yeah okay so if I look at the ES liquidity map or the heat map here we see some liquidity again at the round number it stayed there it's not huge now if we zoom in and we double check what it is that is at 4550 just so we know it's it's not, I mean it's a nice double band but neither of the numbers 163 or 159 are significant and the fact they're at a round number means I'm not going to pay much attention to them there was a nice big fat 300 liquidity but that has been taken away that's one thing you've always got to bear in mind that you can get great resting liquidity it can provide meaningful information and then it can disappear again you cannot foretell the future just because something is there does not mean that it will stay there there is a probability that it will be hit if it stays there there's a probability it won't be hit and there's a probability that it will be yanked before price gets anywhere near it we're in a probability game, we're not in a certainty game so that is the ES1 zoomed out let's have a look at NQ just to see if there's anything that's been sitting around for a long time and clues for later on in the day this is something that I am doing so many times a day it's not funny that's if I am actually considering a trade in the next little while whether that's 5 minutes an hour, 2 hours, whatever I want to know what the liquidity map the picture is from a high level perspective as well as a micro level so again on NQ I can't see any resting liquidity that's close by that's not at a big round number here we have 15, 800 and we'll have a look to see what amount that is that's a decent number, 86 but the fact that it's at a round number means that I am tending to discount that and not pay much attention to it so if we look a little bit closer to them there is nothing there that stirs my attention much if at all so there is nothing to make me excited saying oh that's resting liquidity is playing a role in the picture and if I am just I am just looking to see where the big trades in NQ were there was a big trade up at 720, 715 but that's already been tested so that's one thing that I look in both Bookmap and Sierra if I am looking on a slightly longer basis I've got it to hand in Sierra so I will have a very quick look and if I want to see a bit more detail I'll get into Bookmap and zoom right into the trade to see exactly what happened so there is nothing on the liquidity map that gets me excited so we can go back to talking about about doubles and springs and everything like that and we have let's have a look I think the action in ES may actually I am just trying to see if there is any nice plain doubles or springs there is a reverse spring ok, so there is something for us to look at here ok, let me get the pen out again so what we are looking at here is we've got a swing high that's a terrible line, sorry and then we have a reverse spring so there is a breakout failure it goes up and this is just after 130 just about the pre-open for the DAX the German market and takes it out tags VWAP and reverses down so if we get rid of that we should go into Bookmap and have a look at what happened so we want to know what information was there at that 132am price action to provide us with a trade ok, so let me get back on the cursor get on the right bookmap chart which is ES and we are looking at around about 130 so we are looking at this area and the first tag was at 11pm so I thought we could zoom out and see if we've got it yep, we have got it there ok, now that's quite interesting because we have the stop icebergs information right in front of us so at 11pm there was a small, I don't know let's just have a look let's zoom right into this iceberg so there's a cell iceberg it's first a bi iceberg which looks quite small and then a cell iceberg which rests for a while ok, this is one of the things that I will say I do look at both in ETH and RTH if there is a resting iceberg and it has had a significant amount of volume the sellers have participated to a reasonable extent and it stays in position and it's not an exact round number I am interested to see if there is any action and here it's a cell iceberg so if there is any long type action i.e. if there are any potential longs to trade towards it to finish the business that the Algos or the large player may have had in that zone so here we've actually got a spring so this is quite fortunate so we can actually discuss this this is something that I would love to have traded but I was not around I was rather busy at that time today ok, so step one we have a breakdown sorry, so step one or the precursor to this is we've had the Uber earnings release or just negative market sentiment in Asia and we're breaking down and this is Asian time so this is, as I said this is before the Tokyo lunch hour so we've got an intraday trending type action going down let me just check there's no more questions ok we have a seller iceberg in play and there are two ways of looking at this one, if you're looking for a trade to go back up so along so you can try and target the same zone and again we are looking at high probability, high R-based trades we're talking about ES we're talking about a small stop but we're talking about equal dollar sized bets so even though if you've gotten around here and your stop may have been two points two points is only one part of the game here it's how many contracts times those two points give you that dollar value risk that you're going to repeat time and time and time again the point at which you decide for yourself that you don't want to do that well that's fine my thoughts on this are that equal dollar sized transactions or bets are the most sensible way to trade these markets simply because you cannot predict the future so ok we've got a target or target zone it doesn't have to be this exact tag you'll often find with these especially these ETH icebergs they may not come back to exactly tag what you're looking is to see whether they get the volume they get more fuel up around here to go down lower here so if you set your target at exactly that it might be that you never ever get filled so one thing we mentioned last time was scaling so you have your two point stock you get in you're not going to get in there that's imaginary maybe you got in there so what is that<PHONE_NUMBER>25 and you got a two point stop so that's for you know you are the other side of that liquidity so that would be a reasonable stop what is your actual target here your target is I don't know it's just over one to one to half hour it's not a huge trade but you know it's worth looking at yourself as to the probability of that trade working out because it is something that does interest me where you have a sell iceberg of a decent volume that rests in the market for a considerable amount of time it's just because they know or they have flagged that they are willing to do business up at that zone here they may well have flushed your stop and you're also trading against the market direction so you know you could say that's a full hardy adventure if you had a trend line or even a volatility based moving average or volume based moving average whatever you want concoct and believe me I have concocted just about every indicator there might be sorry I'm just stopping to read a question by MDHC clothing with that target zone be V epoch on a market profile I will have a look so the target there was 4583 or close to it at the time that that happened where we got in the right chart yes we are let me just get rid of the other let me get rid of the other days and then we break this one down yeah that V epoch is still up there it is up at about 4580 and the flush was on 36 so it was a flush away from the V epoch to answer your question so the target wasn't there but all this action around here was at the V epoch this is where they formed the value you can probably see it in these columns that you know they plenty of buying and selling in those columns but the big flush and we can just zoom back down we have yeah I said that one of two things you could do you could play longs towards it and I'm saying it's quite likely that if your first entry you'd have been stopped out and maybe you'd have got a better entry yeah maybe you'd have taken you'd have taken one of these two buy icebergs you know with again with a two point stop maybe two and a half point stop and a slightly bigger target you know if you got in with this iceberg here and you've managed to get in you're in at about seventy eight seventy five seventy eight fifty and again you've got that four eight three four five eight three so you've got a four and a half point target and again so you're over two are this time round and you've got action and if we actually see if our friend the market pulse would have helped us on this one so if we zoom out a little bit remember this this is just a help to know when instantaneous price action is stretched so we're looking here if we're going to go long where does it get into this red zone where it's at the minus seventy percentile and yeah it does there but it does there as well so yeah I mean there are a few different points one two if you count from there onwards one two three four the red zone and provided you know provided you had say you're in there seventy nine fifty seventy seven fifty yeah no provided you had a two and a half point stop even a two quarter point stop maybe two point stop you were fine so yeah so what are the triggers to get into that trade okay let's have look let's zoom out again okay there are a few reasons why you might consider that trade one the resting iceberg to the the buy icebergs three the market pulse for the the stop runs the mbo stops you've got forty five fifty five forty again there's more but we're talking about the Asian session so you're not going to get huge ones or unlikely to when you get something as big as that that's wow and that is a significant a significant indication and also the market pulse and this at that time play and of liquidity first touch of a thickish band of liquidity you often get a push away so you have all those factors saying long but as I said there were two different ways of looking at this this beast the other one was that we were breaking down and if we look at the on the on the on the the three-minute chart we were underneath the previous days low we were underneath the web and yeah we could have said we are not taking long so we could have taken it from the opposite perspective entirely so we could have just said well we'll wait we'll wait and we'll wait until we have a decent flush upwards and when you're going to do that you're looking if you're going to use the double top spring testing of significant zones whatever you want to call this and I will get the old Wycoff picture back up just temporarily let me just get that up okay yeah there's a whole area there a distribution zone which this actually was that you could equate this to I may come back to that and have a specific Wycoff session or just Wycoff and book map how we actually translate this map into book map and go through individual sessions minute by minute and how each of these terms I might even do my own one some of these terms I don't tend to use failed rally I use failed breakout so I call that an up thrust so that's not the terminology that I use and again I didn't draw this one this is just a generic one that I pulled off stock charts or wherever I pulled it off it's not the one that I learned with Wycoff but this is the type of action you have a top or you can count either of these at the top it fails to go beyond it it's called up thrust reverse bring and then it goes down okay where are we just check on the time 842 so we've got about 18 minutes left okay and let me get rid of that picture and go back to book map come on picture disappear good okay the right chart again yep okay here we are again sorry it was zoomed out so you're waiting in that zone there the 83 zone where that failed iceberg was where that previous reasonable swing high so you're not looking at every single micro swing high there I mean you could play that game but that is a different type of training that is scalping or micro scalping we can talk about that sometime as well there are practitioners that are very very good at that and if you are into micro scalping book map is definitely a platform that you should be looking at anyway on this occasion we were looking at a significant swing high which was in this region and it was that one that got flushed out on this 313 mbo stop and that would have been a trigger so you might have said oh this is a stop and just taken that one but that was not quite in the right price zone so the actual failed spring or failed reverse spring was up here at this price zone but that is a trigger that's your market pulse but more importantly it's your mbo stops and then when we look on the columns over here do we have an unfinished auction and yes no there are only buyers at that price there was 63 which is a significant number but if you look at the actual volume of the buyers it's relatively tapered or you look at the delta profile it's relatively tapered that is a good trigger in a market that is going down and breaking down exploring how far it can go the other factor in its favor is that you have this lovely liquidity below so there is a belief or some level of probability that they are going to go down and transact down here and again these are not at round numbers so we've got 4575 we've got this band here from 62 to 73 we've got this band at 68 so then if we watch what happened after the trigger and the idea here is scaling so if you've got your two and a half point stop I would not personally go more than two and a half point stop in ES at that time of the day if you're having a very volatile London session yes you may well need a wider stop but this was before the London session this was actually before the German pre-open which is around about 150 ish which is around about there so I would not have had a reason myself to take a wider stop you've got a liquidity based wall potentially but it's not very strong so maybe you have a reason for having a stop up there but again it's not the number of points it's the number of points times the contracts so in my personal view and again each to their own methodology a process to get in the number of contracts times the stop that you take that gives you the equal value risk on each and every trade okay so maybe you've got your two and a half points stop and you got in around about here on a market entry I have a feeling that that would have been the most likely way to get in a limit may not have been lucky enough to get in on this way in around about here which is the 82, 82, 82, 25, 52, 50 and you've got a stop of two and a half points then you know you've got your 1R, your 2R and you've got this lovely liquidity down here and the bottom half of this liquidity band stays nice and of interest and you're expecting the first bounce sorry the first touch to bounce so it bounces a little bit there and the liquidity band touches it bounces it bounces here you've got a triple bottom there is a price action rational probability possibility whatever you want to call these things that the more touches you have of a wall the more likely it is to eventually break and the beauty that you have in book map there is that you can look at the actual transactions occurring at that wall which is by iceberg which is absorbing sellers so you can see that they were at this stage let me make sure that I have got every level ok yep so you've got a delta of 585 and that's 585 sellers so the micro scalpers would see the by iceberg and they'd be scalping long on the basis of it or they might be and the people wanting to trend would be looking for a way to get back in one to have that as a target you know initially to have the resting by iceberg as a target and then to have that resting liquidity which was down there or down actually down here 4568 as their main target and the fact that you've got 585 contracted and transacted is a strength is a factor that strengthens the probability that we'll go down because this particular auction isn't finished so if we had a look on the profile at that time it would look a little bit fat you know if we stretch out this one yeah you can see it looks quite fat in in profile theory again this is just theory there is no predictions and no certainties it will often be a good initial long setup but that is kind of an unfinished or poor low so that at some stage it may move away quite away first at some stage it is likely that will come and finish it and go through it and not end in such a fat or poor low so we see what happened eventually hits the wall hits the wall hits the wall and goes straight down and takes out the resting liquidity below so there was some very very good action in ES which is unusual in today's session but we're in earnings week so anything can happen and earnings because a lot of them do take place after the RTH market close you often get extended rallies or falls or declines whatever you want to call them so in other words you get more volatility in the ETH session one of the other things that I look at and I've mentioned this one for as well is that I look at the relative volume this was a calculation that was invented one of the people invented it I think was Peter Davis at Jigsaw so it's his sheep accumulation index so it's looking at relative volume minute by minute during the day right about now which is 8.49am that is 202% that's 202% for this time of the day which takes into account all volume since the Asian Open Up Tool now vis-a-vis the last 10 business trading days so in other words it's very high where you have high relative volume in ETH that is another factor that you're going to get volatility i.e. there is a chance that the market will run and run okay let me stop and look through the comments or questions that we have again which are in the YouTube thing MDHC okay I mean Wycoff there are a lot of sources on Wycoff I'm happy to spend sessions on talking through how bookmap comes into play bookmap is like an x-ray that's the nickname of the product when it was first released it was an x-ray into the market so it's an x-ray into how those Wycoff type price structures occur how they actually develop and build so you know bookmap lets you see them so that when you then go back and zoom in you can take them apart and see what information there was that could have helped you get in or not one thing again I should stress you don't have to take a trade you don't have to take a single trade it is entirely up to you there will be sessions there will be sub-sessions there will be whole sessions where the price action or the activity whether it's the level of volatility or the action that you see whether it's on a heatmap or anything else that you use means that you do not have enough conviction to take a trade and that is absolutely fine you can waste your capital very very quickly if you take meaningless trades that are not in accordance with setups that you set out in your trading plan each and every instance of any setup again I will stress this I mentioned this the other day is 50-50 and each and every instance of the same setup is not going to be the same you know I think maybe in some future webinar we can go through um process preparation but one of the things that I would stress is that any process preparation all the mental prep and reading through your trading plans all of that stuff that you do before a session you don't want to get your mind so regimented that you do not have the flexibility to see the multiple different variations of the same setup that is in your trading plan because they will not appear in exactly the same way every single time or they will appear in a way that you do not recognize them in real time so having that mental flexibility to open up your mind to just to be present with the price action to be in the here and now so you can see them actually develop gives you a much greater chance of actually grabbing onto them so that you can get a decent number of hours from that trade 2052 let me just see we are on doubles and springs here let's have a look at the actual live action here so we have a small sell iceberg not a lot transacted up there unless I'm not seeing it properly let me zoom up and then they moved at price down and they went through it again I think that's another good illustration these icebergs are an interesting bit of information, a tidbit one factor, just one of the factors that you are going to use in your trading analysis they can be wrong this one you may have formed the view that oh it's going to go up there and then it's going to go back down anything can happen this one they only traded a little bit and then they moved down and they went through it doesn't mean the price won't go down doesn't mean the price won't go up it's just one piece of information you look at all the factors together one of the things that they do teach you certainly in Wyckoff methodology is confluence so I think that's one of the things that we've looked at in the last hour we've looked at confluence i.e. how many factors and how many good or significant factors play a role in validating your belief that it may result in one of the winners as opposed to the many losers that you might have during a session okay alright let us have a look at an NQ as well just to see what's happening there so we just click the chart just to remind us where we are here so we're still under, we're still outside yesterday's range yesterday's settlement is in pink up there so we're still, we're getting very close in AS to getting back into range how many touches we had, we had distribution zone, retest breakdown first test back up to the range and now we are getting a little bit closer so it will be interesting to see whether they can get it back into range during the RTH session or whether we continue to move down but so far in this ETH session we've had good range and one thing that tends to happen and again the word tends is important it's not predictive, nothing is predictive one thing that can happen or tends to happen is that when you have good range in ETH you often have a good range or large range in RTH so if you are somebody that is looking for decent sized wings that may be good news to you ok, I said we look at NQ as well ok, let's have a look see if there is any more resting liquidity of any information nope there is a level here at 20 that they are holding so we zoom in and we drag up and we just see if there is anything there, 23 I should mention the kinds of resting liquidity of volume of orders that would grab my attention 20, no 23, no anything above 30 during ETH in NQ you can show some interest or excitement in but 23, no and nothing else that is even forming as resting that is staying on board that could grab one's attention at this stage, again does not mean nothing will develop in the next hour lots and lots of things could then develop but we have got a quiet economic calendar so it gives them a chance to explore the ETH range during the RTH session ok, you ask where is yes days high and low you can see that if I click into this and just reset this chart you want to see yes days high and low you have got yes days high up there and yes days low there and we are almost more with we are almost back to the most traded area overnight but we have got a little way to get into yes days range and a long way from where settlement was and where the most value traded or the most volume traded was so in other words we are below and still not still not showing us strong action suggesting that we are going to go and get into it immediately again we are going to zoom out and have a look at the resting liquidity in ES just seeing if the picture has changed so they have added they have added 100 there and this is one of the reasons why this liquidity marker is so useful you can see what it is that they added and when so just after 845 they added 100 but it is at a round number so I kind of discount that but it is just interesting that they did that and on this iceberg here one thing that is worth pointing out is that I have got these numbers really really quite small you can choose the font size for your stops and icebergs indicated I zoom in and out all the time that is the primary reason why all my numbers are so small and I do apologize for that if there are any real difficulties reading it but it is just because I want to be able to see the whole picture sometimes especially on thinner instruments such as NQ the manipulation or the pressure by pressure I mean pushing with large orders takes place a long way away from current price action so again one of the benefits of using bookmap is being able to zoom out vertically so you can see if there is any new pressure that is being applied from far out and there is something missing on my chart so I better put it back in we seem to have to do this every time okay and the other thing I look at here is is there a big disparity between the total of orders over the 30 price levels below versus the 30 price levels above here we have got slightly more buy orders than sell orders within that 30 price level area 30 price levels is just something I've chosen you have to do your own research to find a number that you find that might be of interest to you right okay yeah with that I think we are coming to the end of the hour I think we right on the end so thank you very very much for listening that was


hundreds and hundreds of bodies lining the streets. Panic spread worldwide after a leaked report from the World Health Organization. The UK has a strategy so there was an existing strategy from 2007 that was then later updated in nine and ten after this wine flow outbreak. So there is a pandemic strategy that was written in 2011 and that you know it obviously reflects a lot of the kind civil acts so the responsibilities of primary care providers and the responsibilities of acute care providers and who has to support kind of business contingency plans and that kind of thing. There is some modelling done as well where they kind of predicted an influence outbreak might look at adding kind of say 25 percent more ill people and from that you might get maybe 5000 more people accessing primary care services so going to their GPs and then maybe from that you might get 150 people who would then go to hospital and a hundred of those people could potentially die. So you know if you're looking at this per hundred thousand and then looking at it per population you know the numbers can soon kind of mount up really. So there is some kind of you know general this is what we potentially expect in terms of strategy and this is what we plan to do on this respect but a lot of it is obviously guesswork because obviously it has to be a new you know just talking about influenza it would be something new that people might potentially not have any resistance to or we might not have any kind of vaccinations for it at present. So you have to kind of you're almost anticipating how severe the disease is going to be. Obviously in 2009 we were quite lucky because wine flu was a relatively mild flu virus so there's kinds of lots of elements to consider but there's certainly preparedness plans in place and obviously the European Centre for Disease Control and Prevention work with European countries to have preparedness plans in place. So to some degree the majority of countries will have some kind of plan or strategy in place and I guess it's just about kind of how easy it is to implement that and how severe the illness is and also again there's all the same things that we've discussed like incubation periods and surveillance and transmission and all of those things to consider because that will obviously affect like the kind of general strategic approach to addressing something like that. One thing that really struck me when I was researching this a year or two ago is that if you really do have the massive pandemic and then there's a question of how do we vaccinate everyone. It turns out that there's one of the bottlenecks is the actual global capacity to manufacture enough vaccines and I think that it seemed that part of the problem was that well it seems a bit of a waste of money to have all these you know vaccine factories you know doing nothing all the time and then to gear up and actually to make sometimes you might need two doses of vaccine to make enough vaccine to you know to vaccinate seven billion people and it's not something that the world can do at the drop of a hat it's how long would it take? It takes a lot of time and especially because it's several vaccines are made differently so you need different types of plans of conditions to prepare the vaccine to grow the vaccine it depends if it's an attenuated or a killed whole bug or whether it's a recombinant protein or this is a totally different plant and a different approach so normally I mean I'm a breaking vaccine developer I'm not working in private companies or pharma producing vaccine but as much as I know that the plant is actually designed for the vaccine when the vaccine is coming through the the pipeline so plants are designed for specific vaccines very often so let's say the new pandemic needs a type of vaccines where there's maybe two plants in the whole world because there's two pharma company producing it you entirely right there's there's no capacity at all to produce very quickly one vaccine for seven billion people this time it's going to be different I just know it what do you mean we're going to be there the fireflies I'm sure of it


Welcome everybody to the LFX mentorship showcase, this is segment three, and we have several mentees that are going to be sharing their experiences with you all. Let's talk a little bit about the beginner's problem. And we all struggle with where do we start whenever we embark on a new journey, something new feel that we want to learn new project and, and so on. So this is a not an unique problem. We all face this problem. The first thing really that gets us all is what, what do we want to do, what are we passionate about, what do we enjoy doing, and which open source project to pick from, as we have several in different areas. And once we figure that out, we do our research and we figure that out. The next problem we face is the how, how do we get started in a with our learning, and also how do we break into the community. And the code makes it looks complex always, and the community looks intimidating and daunting, and what's the best place to start learning. So these are all the questions we all face. And once we figure a little bit out of that, and where do we find resources to learn, because that's one of the obstacles. And then comes the question, who can we turn to for help, who can help us with our questions, who can we reach out to. So, we all face this what, how, where, and who questions, and we at the Linux Foundation, we do understand these are obstacles for new developers. We provide resources for you. The site you see here, plan your learning paths, you can do that at the training site. You can go look at the Explorer Pathways, and figure out what you want to, what kind of technology and fields you want to look at, and you can do all that planning and research as well. There are several free training classes that you can take to get a feel for what you would like to do. Once you've done that, and you kind of identified which area you want to be in, you can benefit from looking at the webinars and learning from our webinar series. We have several webinars already archived. You can go take a look at them. They cover a wide range of technologies, anywhere from debugging to open source methodologies and fuzzing, static analysis and so on. This is a wealth of knowledge here, and some of them are cardinal ones as well. Once you have done that, you can explore mentorships. And we offer several mentorships, part-time, full-time options, and paid and unpaid, and so on. And once you have done that, we also connect you with people looking for talent. That's the event we are in right now, mentorship showcase. And I'll leave you with this slide with lots of resources on where to find information. And keep in mind that we do at LF, we do recognize that access to resources is a barrier for people and equitable access. So we try to provide resources for everybody, and we welcome everybody, whether you are a student or you are a career change, you're looking to change careers and explore new career options. We provide all of that to you. And part-time mentorships, we have now straining resources, and we do all of that, keeping in mind that you are balancing, a lot of people are balancing work-life situations for learning and growth. And we just did a survey. We are continuing to look at what we can improve, what kind of resources we can provide, and fine-tuning our mentorship programs. So we have done a survey recently of all our graduates, and we have a report out. Check that out just out a couple of days ago. Okay, so with that, I'll hand this off to Takumi to share his experiences with the mentorship. Okay. Okay. Hello. Hello, everyone. My name is Takumi Hiraoka. Today, I'm going to talk about the experience of LFX risk-5 mentorship with the title Opening the Door to the Open Source Software through the Open Brass Project. I'm an undergraduate student at the University of Tokyo. My research topics are computer architecture and compilers. In my research, I spend a lot of time dealing with risk-5 and LLVM technologies. So I'm very interested in systems programming, including them. Therefore, I formed the Open Brass Project, so appearing and decided to join it. After being selected as a mentee, I'm working on improving Open Brass.  Open Brass is an optimized Brass library. Brass stands for basic linear algebra sub-programs. Brass has three levels of computations. Level 1 is about vector scalar, and level 2 is about matrix vector, and level 3 is about matrix matrix. Open Brass is optimized for each processor to achieve high performance in those computations. Level 3, Open Brass kernel didn't support risk-5 vector version 1.0, so I was trying to implement it. Then, I will now give a brief description of the project I worked on, Open Brass. Open Brass uses blocking and packing techniques to speed up processing by using registers and caches as efficiently as possible. You can see this in the figure. Blocking is done with register and cache size awareness in order to increase register and cache utilization and reduce access to main memory as much as possible. Packing techniques also arrange data in a contiguous manner in memory, which simplifies a memory access pattern and reduces cache miss-rate. These are the goals I like to achieve through this project. First, I want to contribute to Open Brass repository. I've never contributed to OSS before, but I've always wanted to do so. This is because it is very attractive to develop software used by many people and because I can deepen my knowledge of the area and improve my coding skills. Second, I want to deepen my understanding of risk-5 related technologies. Although I have had some exposure to risk-5 technology, I know that the scope of risk-5 technology is broad and there are still areas that I'm unavailable. Therefore, I'd like to further push my risk-5 technology through working on this project. Third, I want to get used to coding large-scale software. Large-scale software is often difficult to understand where to start, how classes rate to each other, and what kind of processing is performed. Therefore, through this project, I'd like to get used to working with large-scale software. From now, I'll talk about what I learned through this mentorship. First of all, it gave me a better understanding of risk-5 technology. First, my PC is equipped with a processor for x86, so I needed to prepare a compiler for risk-5 in order to cross-compile. The two most famous compilers are Krang and GCC, each of which has subtle differences and I used them for operating risk-5 assembly code. Throughout using post-compilers, I got to be able to understand the differences between them. Furthermore, I did not have an actual risk-5 machine and risk-5 PCs are rarely available on the market, so performance measurement had to be done by simulation. So I used simulator software, such as Spike and QM, and understood their usage. First of all, since I dealt with risk-5 vector extension this time, I gained a deeper understanding of the specification of it. I also learned the importance of breaking difficult tasks into smaller, simpler tasks. In the beginning, I was very nervous about the project to contribute to Open Brass, because I did not know how to accomplish it. However, my mentor assigned us detailed steps to accomplish our goals, and I was able to move forward without feeling too much difficulty. Specifically, I first followed the tutorial to run the elementary technologies of Open Brass by optimizing GMM for x86. Since I can visualize the results in graphs, it was easy to see the effect of optimization on performance. Next, I created an environment capable of executing risk-5 vector instructions. Specifically, I prepared a compiler, a simulator, and a Bronx kernel. Bronx kernel is a set of binaries necessary to run the simulator. It's easy to prepare a general instruction set such as RB64IM, but vector extensions are rather recent extension, and the tool chain around them is either newly developed or in the middle of development. So I couldn't find an article that successfully prepared an environment for vector extensions. So I had to check the documentation and issues to build, and I had a hard time using the correct version of vector extensions and the correct repository branch. So I decided to write and post a technical blog on how to build the environment. Third, I wrote a program using risk-5 vector instincts to compute GMM using 4x4 kernel. Here I was able to familiarize myself with the risk-5 vector instructions to some extent. Finally, I wrote a call to compute GMM using inline assembly of risk-5 vector instructions. At this point, the project is still in progress, and I think it will finally enter the stage of contributing to the Open Blast repository. What I have also run through this project is that it's not difficult to contribute to OSS. In fact, I have not yet contributed to Open Blast repository, but considering that I am at the stage where I can do so in a short time, if we take small steps like the one I set in a previous slide and build them up little by little, everyone can contribute to OSS. So if you are hesitant to contribute to OSS, I encourage you to take the branch. I also continue to contribute not only Open Blast, but also various OSS from now on. In this slide, I'd like to thank both of the persons for their support throughout this mentorship. First, I'd like to thank Mentor Cianni. He gave us appropriate assignments and guided us on our way to becoming contributors. He also followed up with us when we had technical difficulties. Also, thanks to Morazan. He is an assignmentee and worked with me on the project with issues. He gave me technical advice when I had programs and helped me when I could understand in the meeting because of awareness of my English skills. Finally, I'd like to talk about my future plans. First of all, I'll continue to study and develop Open Blast if after this mentorship is over. With the rise of machine running, material cooperation will become more important. And the performance of linear algebra libraries such as Open Blast will also become more important. Next, I will be more active in OSS activities. Through this project, I have deepened my understanding of risk 5 and I have always been interested in compiler technologies, especially LLVM. So I'd like to work on OSS related to those technologies. Also, I'm currently a senior in college and will be entering graduate school in the spring of this year. And I'm looking for an internship. I'd like to experience remote internship at and overseas companies to make some more stop this experience of working on a project with people from overseas. This is my email address and GitHub account. If you are interested in me, feel free to contact me. Thank you. Hello. I hope I'm audible. Anyone could just quickly confirm this thing. Okay, sure. So, hi everyone. Good morning, good evening, good afternoon, a good night depending on the place you're currently living. I am Anbub and I'm going to talk about my experience as Linux on which inventory for the spring of 2022. So a little bit of instruction of mine. Who am I? My name is Anubhav Chaudhary and I'm currently an intern at Veritas. I'm a CS undergraduate from Tripaliti, Bhuvaneshwar. I love piddling around with code and exploring stuff around. I've contributed to some open source projects before also like Calamaris, the system installer. And yeah, you can Google me by this name, DIPRO447. I'm quite famous. Not really. So, let's start. So I was interning under Linux Foundation for this, under this organization called CNCF. So what's CNCF? CNCF is a nonprofit organization founded by the Linux Foundation in year 2015. With the goal of promoting the adoption of cloud-native technologies and methodologies. And under CNCF also there are various projects, mostly there is Kubernetes, there is NV, there are Pixi. So I was contributing to this project called Pixi. What's Pixi? Pixi is an observationality tool for Kubernetes. And it works without having any changes to the main port base. So, let's see a bit more what Pixi. So what Pixi allows you to do is it lets you audit your Kubernetes environment. It makes you, it allows you to see different events. It allows you to monitor different stuff and it also allows you to log different stuff that's going around in a Kubernetes application. A little bit about my project. So, okay, so when we moved from this monolithic, monolithic kind of structure of our applications to more of microservices environment. The number of messages going around with these, between these services increased drastically, very exponentially. So naturally there should be some way to look around these messages that are going between different services. And of course, messages requires protocols, protocols basically rules. So there are different protocols available for different microservices to talk between them. There are HTTP protocols, there are GRPC protocols, etc. What my goal for this project was, it was to add support for automatic tracing and parsing of KMQP protocol. So Pixi already had support for various protocols like HTTP, it had for Redis, etc. And what was required at that time was to implement support for KMQP. KMQP is the full form of KMQP's advanced messaging protocol. It's an open standard application layer protocol for message oriented middlewares. It's very similar to something if you've heard MQTT. And what I had to do is implement different type of, implement parsing of different types of messages of KMQP version 0.9.1. There are different versions of MQP available, but I have to work on this. So proceeding further. Let's see how my three months went and there is a bit of story and excitement really around everything. So I'd be sharing that. So first of all, selection. My selection was, it was around the end of Feb. I was, at this time I was learning about networking in general, I was highly interested in networking. And I just came, came through this mentorship page on Linux Foundation mentorship website. Where Pixi was mentioning something to implement a protocol Mongo. I was somewhat familiar with MongoDB. So I tried creating a demo parser myself. Then we came to the Pixi Slack page and I told my mentor that I've done this and that. And he just loved the parser that I made. I was selected after a few days. Then one of the biggest step of these three months was setting up Dev environment. So Pixi works with Kubernetes applications and for an undergraduate like Kubernetes itself, I guess is somewhat tough. So I set up my Dev environment in, first of all, I tried to set up this environment on my local laptop, but it was very tough. Then there, there are Docker based Dev environment, which was, which I wasn't familiar with beforehand. So it was a great learning that, yeah, you can develop stuff around in Docker also. Anyway, then next was reading Redis protocol. Okay, so there, there might be much confusion around. Initially that was Mongo, now I'm reading Redis specs and finally I would implement AMQP protocol. So yeah, protocols are like, you should get a sense how protocols work and then you can implement various protocols all around. And that's I guess is universal for all computer science. You get sense around some things and then you proceed further with specifics. So yeah, Redis was easy to understand it has shorter specs. So I gave a read, I gave a reading to Redis protocol, first of all, then I read about AMQP protocol. And if you have observed like it's a lot of reading. So I guess for almost 45 days out of 90 days, I was reading stuff. I was just learning stuff. Then there was time for implementation. I started implementing various messages, various passing techniques in C++ in the, in the pixie environment. It was kind of, I guess stuff thing like C++. I was somewhat familiar with C++ but not with the development C++ but my mentors really helped me a lot. So really like to thank them. And finally, there was testing involved. So testing was also kind of different. I was get, I manually tested a lot of data. I was getting boundary strings and I was manually trying to parse them by myself and then seeing if my application, my parser was giving the same result or not. So what I learned, I learned a lot about AMQP. I learned a lot about Docker like really, really Docker was one of the great things that I learned C++. Yeah, of course C++. I was programming C++. So I learned a lot of programming techniques, build tools. I use Bazel for building. I learned a lot about build tools and Kubernetes in general. Yeah. So pixie is dependent on Kubernetes. So Kubernetes in general. But the main thing that I learned was computer science. Really this mentorship program helped me a lot understand the deep, deep things of computer science. So if anyone is thinking about joining this mentorship program applying for mentorship, I would say it's the, it's one of my best decisions of life. Then these two people are my mentors. Yaxiang and Omit. So I would personally like to thank them a lot. Like they are kind of very senior people. They are principal software engineers and the founding members of pixie. But they held me around in almost every corner of my project. So even very small things I was getting some issues and build and all they were manually helping me a lot, especially Zong. He was my, he was my main mentor. So he helped me a lot. And yeah, that's pretty much about it. You can, I go by this name again, DIPRA447. You can just Google me around on Twitter. You can follow me on at the rate 65 and you can message me here at DIPRA447 about my future aspirations. I would say, if you have an opportunity for me, let me know. I might be interested. And I would, I would always be contributing to open source. It's one of my main loves. Thanks a lot for hearing me. Hey, everyone, I am Sundipan Panda. And today I will be sharing with you my experience of working as a mentee to improve the supply chain security of CILIUM as part of the Linux Foundation mentorship program. So let's get started. A little bit about me. I am a senior undergraduate majoring in information technology at Maulana Abul Kalamajat University of Technology in India. I started my journey in open source as a mentee in the Kubernetes community where I am now a member. I am passionate about open source and cloud native technologies. Now let's get a quick overview of the project. CILIUM is a software defined networking and network security solution for cloud native applications. It provides visibility and security for applications running on Kubernetes using an open source high performance model that is simple to set up and configure. Now let me share with you my project goals. I improved the security posture of CILIUM family's open source projects as part of the Linux Foundation mentorship program. This includes implementing container image signing, generating software build-up materials and bringing the CILIUM monitor score of CILIUM to 100%. As you can see after the project completion, we are generating a software build-up materials and signing the container images and the HBOM images using cosine and we have achieved a CILIUM monitor score of 100%. Now let me share with you the key takeaways of my mentorship experience at CILIUM. While working on the project, I came to know about the importance of container security and signing container images and how it provides a means of verifying the integrity of the images which ensures that only trusted images are deployed in production. Signed images also help to protect against malicious actors who may try to modify or replace the images with malicious code. But why is keyless better than conventional signing? It is so because it eliminates the need for manual key management and reduces the risk of maliciously signed images being deployed into production. Keyless signing also simplifies the process of securely managing large numbers of container images as there is no need to maintain a key per image. And that's why we implemented keyless container image signing in CILIUM. I also came to know the importance of generating software build-up materials while working on the CILIUM project. It allows organizations to have visibility and control over components used in their applications. And this helps organizations ensure that they are using secure and reliable components as well as reducing the risk of security vulnerabilities or compliance issues. You might remember me mentioning that CILIUM attained the CILIUM monitor score of 100%. But what is CILIUM monitor? It is a tool that periodically checks open source projects repositories to verify they meet certain project health best practices. Now let me introduce you to my mentors and let me share with you how we worked together. My mentors Andrew Martins, Natalia Reka Ivanko and Zed Salazar played an pivotal role in my successful graduation from the Linux Foundation Mentorship Program. They played a pivotal role by providing me with valuable guidance and feedback throughout the entire project development process. This included helping me to define my ideas and develop an achievable plan for completing the project. They offered moral support and encouragement throughout the entire time I was working on the project. Their positive attitude kept me motivated even when things got tough or I felt overwhelmed by the task ahead of me. Finally, they provided technical advice, resources and connections that enabled me to complete the project successfully. Their constant support and dedication to helping me reach my goals made all the difference in my successful graduation from the Linux Foundation Mentorship Program. We worked together by scheduling weekly check-ins to review progress, blockers and upcoming tasks, communicating via Slack to discuss issues and get feedback, and coordinating with folks from the Kubernetes and 6-store community. I would like to extend my heartfelt gratitude to the awesome community of developers at Cillium, Kubernetes and 6-store for their valuable input and helping us implement the Kubernetes BOM tool used to generate software build-up materials and the 6-store's cosine tool used in assigning the container images. So, what's next? I plan to utilize my skills in coding and development to create open-source applications that serve a greater purpose, become a mentor for new students interested in open-source and helping them guide through the processes of getting started. Join or even start an organization or group of students devoted to furthering the advancement of open-source technology in both education and industry and attend conferences, workshops, hackathons and other events related to open-source software in order to stay informed on the latest developments and trends within the field. With that, I will wrap up the session. Thank you so much for joining. I would like to take a moment to thank my mentors who have helped me throughout my term. Your guidance and support has been invaluable and I am grateful for all the knowledge you have shared with me. Finally, I would like to thank the Linux Foundation for organizing and hosting this showcase and giving me the opportunity to build relationships with the open-source communities that will last far beyond this program. Thank you. Thank you. Thank you. Thank you so much. Thank you. Thank you. I have been like, worked and learned about K-1-O policy engine, how dynamic admission control works in the Kubernetes, how you can validate and validate the resources, deep understanding of various Kubernetes resources also. And I have also developed a deep understanding of YAML and Jamspath, which is a JSON query language used in K-1-O policy engine. Along with it, I also understand how you can handle and understand heavy code base, like K-1-O is an example of this. During this mentorship, I have also developed an understanding and a keen interest of learning Goal and also more about Git and GitHub. During this mentorship also, I have learned how I can write test cases for various scenarios. Along with this, I learned how I can meet deadlines and can handle multiple things at a time. It also helped me to be a better communicator. It helped me to come out of my comfort zone and ask questions to various people and clear my doubts. And it also helped me in growing as a professionally and personally also. And it helped me to make mistakes come while solving any issue or if I face any roadblocks while solving any particular issue. So, my mentorship has been an amazing experience and one of the reason for this was my mentors. My mentors Venkatesh Kuttarkar and Pratik Pandey both are senior software engineer at Nirmata. They both helped me really in understanding the K-1-O policies from dropping daily updates on Slack to weekly connecting meetings for progress and roadblocks discussion. They also shared me the right resources to learn about the various K-1-O policies. How can I understand about them? And they also helped me in how I can approach a particular policy and solve an issue related to it. Along with this while my exams came in between during the mentorship period. So, they were quite supportive and friendly regarding that also. And they also helped me providing career guidance. I would like to give a special gratitude to Chief Zola who is a technical product manager at Nirmata. Chief helped me in understanding the K-1-O policies very deeply. He helped me in solving each and every doubt and helped me in merging PRs in the K-1-O policies repository and helped me in proving the test cases. The surprises that I got from my mentorship is the K-1-O community support. All the community members were very helpful in making me understand the K-1-O policies. It also helped me in increasing my self-confidence. I also got some amazing people to whom I can add in my network. And the last one which I never expected but my mentorship experience blog got published on the Nirmata website itself. So, in future, like K-1-O introduced me to software supply chain security. So, I will be exploring that in that particular field. I will also in planning to increase my open source involvement in the cloud native world and looking for more opportunities to learn and improve my knowledge. So, you can connect with me on different social medias like on LinkedIn, Twitter and can drop me an email also. And you can check my work and read about my mentorship blog also. So, thank you so much for joining. Oh, my name is Juhi. Today I'm going to talk about my experience with Lin's Connor contributions, especially troubleshooting the Connor panic. Before we go any further, please allow me to introduce myself. My name is Juhi Kang and I'm currently working as an open source developer and have been contributing to the Lin's Connor networking subsystem for years. So, let's get started. When we develop with Lin's Connor, sometimes the Connor panic occurs. When I was a newbie for the Lin's Connor, serving the Connor panic was difficult. So, instead of debugging it, I choose just to reboot my computer. Actually, it wasn't a proper solution for this infinity loop. In order to get out the loop, I tried to find an effective way of troubleshooting the Connor panic. So, what I'm going to show you is about step through the Connor panic debugging with example. Before we dive in, I will show you how to raise Connor panic in this way. The command is pretty simple, just write character C to process R to trigger. This command raised the Connor panic like life size. But why does this command raise the Connor panic? Let's find that way. First, let's look at the Connor panic log. By skimming through the Connor panic log, we can see many details which are not familiar to us. Let me give you a brief description of how this log is constructed. At the top, the Connor panic log header is located. This provides the abstraction about the crash. Such as the cause of the panic or a poison of your Connor. Next is called trace. Coltrace provides the context information about the crash. As you can see on the left side, Coltrace shows the function symbol and the function offset of the execution flow. At the bottom, you can find the registered information. Register information provides the current executing dump of the CPU registers. RIP register holds the current executing instruction. And code includes the current executing code information. So now, before we start to analyze this Coltrace, we need to save this panic log. In here, I've saved this as error.log. In Connor, there is a script called decode stack trace. This script decodes the stack trace function symbol with the source code information. So we can easily troubleshoot the Connor panic as easily look up the Connor source code to figure out what caused the crash. Now, let's take a look deep dive into how Connor panic actually occurs. First, let's look what comments triggered the Connor panic. In here, the comments triggered Connor panic are pretty simple. As you can see, output redirection is used to the Connor panic, Connor profile. So what is this comment actually doing? Just write the character C to process our trigger to figure out why this comment raised the Connor panic. Let's analyze with the Coltrace. As you can see, at the right side, the Coltrace is reported from bottom to top. So entry score is called first, and panic is called last. Before we start, I will ignore the symbols that have a question mark. Before the symbols with question mark in Coltrace means that information about those tag entries probably not reliable. So as you can see it right here, I will visualize the Coltrace on the right side. Although I can explain everything because I don't have enough time, so writing a file in a loose environment involves several steps. The function on the right is color coded for each sub-systems. So let's begin with our panic troubleshooting with the Connor codes. Here, we will use the Connor code version 6.2.0 RC2. Initially, a system call interface and 3c score 64 after hardware frame is called. And as you can see the code on the left side, this function calls 2c score 64. Then from 2c score 64, the 2c score x64 is called. And this function calls the c score table by passing the register as an argument. Let's take a different look at the c score table. The c score table actually is an array that consists of c score handlers. At the second entry of this table, you can find the c score right handler. From this handler, the case is right function is called. Back to c score table, this will call c score right and eventually case is right will be called. After that, case is right will call and VFS right, which is the right function from the virtual file system layer. And you can see from the source code, VFS right is calling the right function. As we dig deeper, we can realize that this right function is actually met with the project right function. So this project right function is located at prog right system from the prox like the right function, the PDE right function will be called. And this will eventually call the prog right function. As we look deeper, we can find this prog right function is met with right c-circ trigger, which is located at c-circ device driver level. Moving on c-circ trigger will call the handler c-circ. And from handle c-circ, the c-circ get key operation function will check which c-circ command is issued. From this function, c-circ get key operation will check c-circ key table data structure. Then c-circ will finally realize that the character C is transferred to c-circ crash operation. Back to c-circ handle, this will eventually call c-circ crash operations handler function. At last, the c-circ handle crash function will call it. Finally, this will laser panic with panic function. So far, we've looked at how the tunnel panic is caused by deep dive from entry c-circ crash operation after hardware frame to panic. And for the last table analyzing the tunnel panic, you can find c-circ dashboard for additional resources. From c-circ, you can gather various resources related to your bug. With the tunnel panic analysis methods we have learned. So far, I was able to learn how to counter debugging in various way. So this opportunity also gave me a chance to boost my links counter contribution skills. So thanks for listening my session. If you have any questions, feel free to ask me via the email. Thank you. My title is LFX mentorship and me. So a bit about me. Hi, I'm Sitchul Maurya and I'm LFX mentee for Spring Term for 2022 for the Cubama project. And I'm a 2022 engineering graduate and currently I'm working as an associate product engineer and for cloud. So what is Cubama and why I selected to work on this project? So Cubama is a cloud native runtime enforcement system that restricts that restricts a behavior such as process, file and network operations.  Cubama has policies that we define on the Kubernetes clusters. And by using Cubama users get rich alert and elementary that they can use to identify malicious actors. The other question is why I selected to work on this project. So security has always been an interesting topic to me since my college days and I used to explore and drink or how Linux works and how things work around Linux. And I was to, I also learned about web security during my college days where I learned about what stopped and eventually when I got introduced to the Kubernetes I started exploring projects which are related to security. And that's how I ended up working with Cubama, which is also related to security. So now the problem. So as I already discussed, Cubama provides rich alert and telemetry. So this is the image that you see on the screen is one of the alerts that we get whenever there's a tag on the Kubernetes cluster. Having a, having a bit before you can see that it give us some basic details like timestamp, cluster name, host name, pod name and container ID of the cluster. So some of the important details which we can see in the alert is the policy name that we, that was defined by the user and the important field is operation field. So the operation field is the field where we can see it is a type process. So as I already discussed, Cubama provides three types of protection that is for process for files and for the network operations. So here the demo is for the, the telemetry that you see is for the process type. It is of type operations and another field is of type resource. So when we check, it is, it is pointing to the sleep binary. So the policy that was applied to the sleep, sleep, sleep binary and whenever the malicious attacker will try to run the sleep binary on the Kubernetes cluster. It will give the permission denied to the attacker and it will send this telemetry to the user that who has applied the policy to the cluster. So this is one of the alerts that we get on the Cubama cluster. But if we consider a scenario where we are running, we have applied many policies to the cluster and there is an attack done on the system. So at that time, there will be a lot of telemetry that will be reached to the user and it will get really difficult to see which one is the more attention than the other one which is not so severe. So that's the reason we have CLI on the Cubama which is called as K-Armor and that's a part that I worked on during my mentorship project. So we call it as K-Armor and my task there was to work on adding the flag option to the current CLI that we have and the flags that I added were this. So the first was the names first flag that I added on the Cubama. So names space, as we can see, we have a Kubernetes cluster and there are different names that we can have on the Kubernetes cluster. And based on the requirement, there are different policies that are applied to the cluster. So if the user want to see the alerts on the particular main space, they can use this flag that I applied. The other flag was the log flag. So log flag, we have a two type that is host log and container log. So Cubama can be applied on both the system, the Kubernetes cluster as well as on the normal host system like Ubuntu. So if the policies are applied on the host system like Ubuntu, so the user, if the attack is done on the host system, they can easily use the log filter and see the alerts that are given by Cubama. The other flag was the operation flag. So this is, we have three types of operations on the Cubama side that is process filing network. So there are many scenarios like if you consider a scenario where we have this SQL running on your system and so we have a password file which is already stored in your system. And we have, if you apply a Cubama policy so that you can keep a check on the, if there's no malicious hacker who is trying to access files or SQL password files. So we can create a policy for it. And if there is, if the attacker tried the accesses, access the files, we can get an alert quickly and we can also fill, we can use this operation flag and we can easily filter it out. So the other flag was a limit flag. So this flag was a bit tricky to apply and it took quite a while for me to understand like how things work with the limit flag and eventually after understanding the whole flow I was able to apply it. So the limit flag is a very basic flag which can be used if you want to limit the number of alerts that the user is getting. If there's an attack down on the system and there are multiple different types of attacks done so it gets really difficult to see the number of, like there will be a plethora of alerts coming on your system. So the user can use this limit flag and they can specify any number of flag alerts they want to see. For example, if they want to see 20 alerts they can specify the 20 number and they can easily get 20 flag and the CLI will stop. So basically the last flag that I walk was on the label flag that we have, that is very similar to the QPCK label flag, we can use it and by using this flag we can easily get the policies based on the labels that are applied to the pods. So these were all the flags that I walk during the project and yeah, so basically this was the solution that was given from my side. So before my learning, so there were many things that I learned through this mentorship project and some of the things that I didn't highlight to us, but Golang, so as a project is written in Golang. So Golang was something that I had some bit of experience with but while working on this mentorship project I was able to learn things and how Golang works and how about some of the packages like Cobra CLI that we that was used to build QBAP, KABMA CLI, I was to learn about it and another thing was the GRPC. So I was already familiar with REST protocols but GRPC was pretty new to me. It started exploring how it works and when I got to know about it then I was very much surprised and happy to see that how fast the GRPC is going to compare in terms of speed when we compare it with REST. The other thing was EBPF, the current bus world that we have in the network namespace, so like EBPF, like there's a quote that we say, if I if I did like to define what the EBPF is, EBPF, what JavaScript is to the web, EBPF is to the kernel. So it becomes really easy for you to program your kernel system by using EBPF code. So I got introduced to it and I started exploring more about EBPF and that's how I ended up on learning CLI and I'm still continuing to learn about QBAP and contribute to the CLI project. And other than this, I also learned many other soft skills like how to present yourself, how to communicate with people, how to do us in communication and many other stuff. Another thing is another pointers when applying. So there are many people who are looking to apply this for the LFX mentorship project. So a bit about myself, I was selected to this mentorship project in my third attempt so I already tried twice and I was not selected, but in my third attempt I was selected. So some of the pointers that I would like to give you whenever applying for this mentorship project is first is a community involvement. It is always good if you join the Slack channel of the project, introduce yourself and start taking good first issues from the report, try to install the project on a local development and see how things work with the project. Another thing is to contact mentors. So it is always good to be in the eyes of mentors and let them know that you want to work as LFX mentee for this fall and try attending community calls and show up to the meeting and ask open questions to the Slack channel. Third point is you don't doubt yourself. So there's an imposter system that everyone has. So I also have this. So if you many people think I don't know stuff, I will not be able to make it. But I will say just keep applying and you have nothing to lose at the end of the day. You still have PRs done and you can show it in your interviews and anywhere you want to use it. And the last point is to learn the tech stack. So it is always good. If you know this stuff because that's make me way forward than other people because mentors look for the people who already know the tech stack the project based on it is not a hard requirement but still if you know the start it really gets easy for like it help you to get selected for the project. So I did like to thank both of my mentors, Barun and Raul. They really helped me during my whole mentorship. So I still remember like I was trying to set up Cubama on my local system. And like Cubama is a bit heavy project to run on your local system. It requires quite a lot of RAM. So at that time I was using Windows and I was using virtual machine inside it. So it was really difficult to set it up and I asked a question to on the Slack channel and Raul was very important to ask me to join a call and he can really help me how I can set it up and how I can use dual boot and I can run that on a human to machine. So yeah, and Barun also helped me during my whole journey with all my small doubts and really was very helpful while working on this project. So I did like to thank my both of my mentors for their help. Finally, thank you. I did like to thank the whole Kubernetes community because that's where it all started. I still remember like I joined KCD Bangalore Meetup where I was able to meet a lot of Kubernetes people and they asked me to join Kubernetes in-depth channel where a lot of people hang out and talk about Kubernetes and this is a channel where I got introduced to many people and started exploring more about Kubernetes and that's how my journey started. So I did like to thank the whole Kubernetes community, Linux Foundation, CLCF and thank you and these are the handlers where you can contact me and reach out to me once again. Thank you. Thank you everybody. It's awesome presentations and thanks for sharing your experiences today with us and thank you all the mentors. Without them, we won't be able to offer the mentorship programs as we do. We won't be able to run them. Thank you very much everybody and good luck and that's the wrap. Thank you.


Hey guys, my name's Zach Fox and for today's MTV News intro, I hit the streets to ask you what you'd like to see. Let's hear the winning idea. An intro for what? I mean, did you ask more than one person? Lazy. Every January, the Hollywood Foreign Press Association hosts the Glittering Golden Globe Awards, a prestigious ceremony that attracts more stars than...I don't know, come back to me on that. So to celebrate, here's our top 5 favourite cringe moments from the event.  At least they weren't stood up in the middle of the room, though. 2. James Franco did not want Tommy Wiseau to talk on stage. Where was he during the filming of The Room? Am I right? I sure hope so. 3. Natalie Portman subtly threw shade at the awards for snubbing female directors by announcing the award with, and here are the all-male nominees. I thought you said subtly. 4. Halle Berry was spotted, that is not Halle Berry. And finally, 5.  Well, nearly every star. Whoopsie. Sorry, actress Blanca Blanco. You might want to get back on your email. You simply have to be in this day and age.  This is more awkward than any of those 5 things. Sophie Kasai looks great after dropping 4 whole dress sizes. Hoo wee! Trust me, fellas. That's a big achievement. It's like Leicester winning the Championship Ashes Cup international tournament. Sophie jumped straight on Instagram to present to us the results of her rigorous diet, dropping from a size 16 to a size 8. Wow. She's now got more confidence than vowels in her name. The caption reads, hashtag Sunday Selfie! I never ever thought I would have the confidence to pose for lingerie selfie. It's never too late to make a change. I did it, so can you. I've gone from a size 16 to a size 8 in the last 6 months. And in another selfie, Sophie says, I got myself in such a bad place where I thought there was no way out. But there always is. Healthy eating and changing my way of life has changed me not only physically, but mentally. Fantastic advice. Selena Gomez unfollows nearly 300 people on Instagram. Now, I know what you're thinking. Can you list some big juicy names she's both given the axe to and decided to spare from the culling? I don't care what you're actually thinking. Strap in, we're doing it. Taylor Swift. In. Justin Trantle. In. Demi Lovato. Out. Amy Schumer. In. Jiji Hadid. See ya. Her assistant Theresa Mingus. Goodbye. Louis Vuitton. In. Oh, thank goodness. She's also going to change her profile picture to a picture of her mum, Mandy Teefe. Now, I know what you're thinking. What's brought on this sudden change? Well, she recently took a trip to her childhood home in Texas. She's quoted as saying, I visit this place at every chance I get. In many ways, it very well could have been better than my life today. But I'm grateful for a voice that can enable change today. Even when I don't know how to do it well or actually want it. I love you, Grand Prairie. Thank you. Now, I know what you're thinking. This little strolled-down memory lane and subsequent mental and physical revisiting of our youth could have sparked a nostalgia-fuelled spiritual and virtual spring cleaning. All right? I don't know what you're thinking. Okay? You got me. I have no idea. Turns out, plants can hear themselves being eaten. Yes. Really. Sorry, vegans. The University of Missouri have discovered that plants can identify sounds nearby and can then react, like defending themselves when they hear a hungry insect or grinding on the dance floor when they hear a UK top 40. For an infinitely less funny and more true explanation, Heidi Appel says, We found that feeding vibrations signal changes in the plant's cells metabolism, creating more defensive chemicals that can repel attacks from caterpillars. That is genius. Maybe I should try defending myself with defensive chemicals. Yuck. She continues, This research also opens the window of plant behavior a little wider, showing that plants have many of the same responses to outside influences that animals do, even though the responses look different. That almost seems hard to believe, doesn't it? A plant scientist whose name is literally Apple. What world do we live in? That's all for this week. Jack will see you soon. Is anyone going to pull their weight? Run here.