Okay, so, hey guys, I'm Venkat, I run the data platform for Predix platform, so we're both coming from Sandramon, so yeah, we're sitting here to actually talk about, it's actually a change in the topic a little bit, so we talked, we want to, we'll touch up on real time events as well, but we will do handling stateful applications on our past journey more, so it's going to basically cover more ground from Predix perspective. Hi guys, this is Zubala Ji, I run Predix's application and container platform for Predix. Okay, so what are we going to do in this talk? So we're going to bring you guys up to speed quickly on what Predix IoT platform is and what we actually do. We will talk about our past journey, we started building a platform about two to one half years ago, so we'll actually talk about like how we originally initiated and then where we are and what our challenges and we are actually hitting. We'll also talk about stateless and stateful applications in general and what our needs from both of these services are. We'll talk about our challenges and we'll do a demo on Q&A. So the first slide we want to talk about is here, when people talk about IoT platform, everybody gravitates towards a consumer IoT product like Nest. The first differentiator that we are building in as part of GE Digital Charter here is we're building in whole class secure industrial IoT platform. The biggest difference when you throw in the word industrial is just one word but the scale of what we're talking about, it just grows out astronomically. We're talking here about mission critical applications, mission critical devices like jet engines, MRI machines and wind turbines which are pumping in data at a much higher rate than that's ever been seen on any IoT platform before and all of these devices come in with their own inherent challenges and intricacies especially around security, around compliance and all this stuff. So that has been our biggest differentiator when we talk about an IoT platform. So right when the word GE has been around for, this is actually coincidentally a 125th year of GE. GE is being a well-known name across all households and we have presence all over the world but GE has been tagged as being an industrial big company. So there's not even a single vertical that exists in the world where GE's presence has not been there but when you take such a big company and you pivot around GE to become a digital footprint, that journey is not easy for one and that journey has been something that we willfully taken head on and to quote our former CEO here, we are in the business of dealing with information, we are in the business of dealing with data whether we like it or not, whether we want it or not and given the fact that GE has such a huge footprint in many business verticals, we are the biggest domain expertise of if you've taken any business vertical here and it is such a natural organic growth for us to become the leader in building up this industry IoT platform especially because of that of our inherent domain expertise. Okay, just a quick survey. How many of you guys have known our use predicts? Okay that's awesome actually it's the right audience we wanted to talk about. So like Balaji talked about, so predicts is our IoT platform. GE's industrial customers are pretty much everywhere in the world. They are in almost all the geographies because we span across like various businesses right from aviation to transportation to healthcare, energy and so forth. So from a predicts perspective in order to build a platform that's going to sort of help all of these different customers we have to be there in multiple areas. So predicts is right now in like four regions. There's one in US, East, West, there's one in Europe and Japan and it's only expanding pretty much and majority of our food plants there are in AWS today while we are also expanding it in other clouds. So we have about multiples of 10,000s of machines. We have thousands of developers using the platform today. We have close to about 30,000 applications that are deployed in this platform across various businesses and whatnot. And we have a number of software stacks that are actually running in predicts. These stacks are included from stateless applications to stateless applications like relational databases to no SQL source and whatnot. So from a cloud perspective, you guys got a sort of view of scale from a cloud perspective but there is also humongous data that's coming to our cloud. So G has assets or machines that are deployed in so many different places that all of these are actually generating a lot of data. So for example, this is one of the jet engines. This basically says a particular jet engine generates about a terabyte of data every day. So the way we actually build cloud is to make sure that all of these data from these edges are able to be ingested into the cloud for doing your analytics and everything else. So when you talk about how predicts is built in, we are trying to become a cloud agnostic IoT platform. So we depend heavily on automation to bring up our predict infrastructure itself. We use Hashicarp's Terraform for bringing up a infrastructure in any footprint today. That's Amazon and Azure eventually into any other public cloud that's available. So we depend on Terraform to bring out our underlying cloud infrastructure. On top of that, we use CloudFoundry's Bosch to bring up CloudFoundry. From the time CloudFoundry is exposed out to our developers, CloudFoundry is the only contract that our developers exist within predicts. CloudFoundry provides a very unified way of accessing predicts itself for our developers and for end customers' developers who want to consume predicts. The advantage of what CloudFoundry provided us when we started this journey was CloudFoundry has this robust marketplace service where you can have asset building models, analytic building models, and then CloudFoundry also provides a very secure interface to predicts itself. What you see here is a typical use case of predicts where we have predict edge machines that are deployed out to our customer site, which acts as a local aggregation point of sensor data, does some computation on it, sends back the learnings and the data back to the cloud. We also have a enterprise data connect, which is used by G-current, for example, to pull in data from local light sensors to do analytic jobs on the predicts. On the other extreme, we have northbound applications that customers build on top of predicts to consume that data to do predictive analysis. Awesome. So extending to that, we use CloudFoundry as our base platform infrastructure that we just talked about. CloudFoundry, for one, abstracts the developer experience in a way that's actually sane for them. They don't have to manage individual machines and infrastructure and whatnot. It's actually great for state-less applications. It gives you a nice marketplace that you can interact with to sort of create your service instances that you need, bind it to your applications and so forth. There's also CLI and API access to it, and Balaji also touched upon how we deploy CloudFoundry. All of these are fun, but although the biggest sort of shortage or limitation with CloudFoundry today is the support for state-full applications. Currently, many of our state-full services are deployed through automations outside of CloudFoundry. So this is either using Bosch-type deployment or Sheffield Terraform-based infrastructure. So we deploy these outside of CloudFoundry in a separate sort of segregated set of instances, and then expose them to CloudFoundry via a service broker. So this essentially started about six to nine months ago. We started this journey of looking at the next-gen platform for providing a seamless integration for anybody who wants to run state-full work program predicts on a container platform. We naturally gravitated towards Mesos, which provides a very generic orchestration platform for running containers with a very good robust two-level scheduler, great adoption among the open-source community and enterprises, who has done all... We have similar customers who are going through this journey, who cry about each other's shoulders, who understand what the pain points are going from one pass and other passes, how we provide a unified experience to our end customers as well. The stuff that we like today about Mesos is the fact that you have a first-class citizenship for state-full workloads and for persistent volumes. Okay, so now we talk about how do we bridge both of these worlds. I mean, we talked about state-less applications and how our customers use CloudFoundry today. And the goodness of what Mesos actually brings into this platform of state-full centric applications. So our intention is to see how to bring both of these worlds together in a way that our customers still have the same experience from how they are using and the predicts platform, like how they actually go and look at a marketplace and how they actually use the service instances and everything. So what we are essentially looking upon is kind of actually building a unified marketplace across both of these past systems, where you can still expose all of your native constructs that are available for state-less applications in CF, but also bring up the services, the state-full services that are available in Mesos into CF. So we're going to talk a little bit more about how this integration actually works and what we are doing there. So what you see here is a sample of a marketplace that anybody who logs into predicts using the CLI look like. So here you see about five catalog services here. The good thing about what this particular representation view gives you is, for example, you have our RabbitMQ cluster and a Redis cluster. These are orchestrated using our on-demand Chef Broker, where anytime a user interacts with either one of those brokers, Chef is our backend infrastructure which kicks in, which goes there and creates a on-demand cluster for the user. The anomaly detection that you see here is actually a native app in Cloud Foundry itself, which is running as an app in Cloud Foundry, and people can interact with that natively within Cloud Foundry. The last two here are our first cut of our implementation on Mesos, where people use these two clusters to go spin up a Mesos cluster to consume Elastic and Cassander. Okay, so how this happens behind the scene? So is anyone here familiar about Open Service Broker? Okay, a few hands. Okay, that's good. So a Service Broker is an API that the CF community came up with a long time before. So it's effectively a way to sort of integrate your platform's marketplace and your sort of service provision which is your broker. So the broker spec is like five or six APIs. One API is to basically return your service offerings, like what is your service, what are the plans that your service is offering, and what are its configurations. There are a couple of APIs around instance creation and deletion and a couple around like how do you get the credentials from this service instance and attach it to a particular application. So I think the community saw the value in having a Service Broker API that's common across different platforms and sort of came together. So the Kubernetes and the Cloud Foundry community have both sort of adopted the Service Broker API and they essentially have extensions for both. But the missing piece was a Service Broker for Mesos. So we went ahead and did an implementation of a Service Broker for Mesos. So Mesos DCOS has this API called Cosmos which is a package manager API.  You can actually go and create an instance and whatnot. So we went ahead and created an implementation of Open Service Broker that actually talks to this Cosmos API to go and spin the instance, sort of make sure that the instance are completely up, sort of monitor each of those tasks and also bring back the credentials and everything the Service Broker normally does. So this actually sort of shows you about the different sort of service frameworks that we've got and how we've essentially integrated with different APIs on the Mesos side. On the other side, we essentially have the Provisioner or the Service Broker APIs on this side. So what you see here is a typical call flow of what happens when a user interacts with Cloud Controller API to instantiate a service. So the request is when a user goes logs into CLI, which is what we're going to be seeing the demo at the end of it under the deck is, a user logs into CLI and hits a command to go create instantiator service instance. That call goes to the Cloud Controller, which looks at which broker is registered for that instance. In this case, it would be a broker running in marathon itself. That call goes out of the broker turns around and then instantiates a cluster within marathon. The response back to the end user would be a environment variable, which gets embedded into their CF application itself. And at that point, the application then can consume the cluster that's in Mesos. What we're also attempting to do here is to create a seamless service mesh between Cloud Foundry and Mesos and also start down the journey of having a secure isolated single-tenant offering within Mesos itself. Cool. So before we go there, so we do plan to open source the implementation here. The implementation is about 100 to 150 lines of code pretty much. It's written in Scala. It does have a sort of open implementation that can actually talk to any package in Mesos, except for a couple of things, because there are going to be specific sort of nuances within each package on what configuration it exposes and what configuration that you have to send it to it. Those are easily extendable in the framework. The framework has written in such a way. So yeah, we'll probably write a blog or something at some point to sort of let you guys know. Okay, so the next important thing is persistent. We just wanted to do a double click on the persistent volume, because this is the whole missing piece in the Cloud Foundry infrastructure today. So two things that are super important for us is to have sort of a unified infrastructure where we can essentially do both persistent and non-persistent services. So for persistent services, of course, there's a couple of things that you need. You need to be able to sort of attach a persistent volume to a container. So the container actually moves from one place to another place. You want to be able to reattach your volume. The second thing is you won't also be able to do this dynamically. So you don't have to sort of pre-create this huge massive disk and attach it as a single volume to your container. So you want to be able to sort of shard and then partition these disks and then assign it to these containers. So when we started this journey, CSI was CSI as the container storage interface that was already talked about at that point. So we looked at it closely. There is still work that needs to be done across each of these platforms, including Mesos and Kubernetes and everything else. And there is also the sort of integration with the frameworks that's also missing. So we decided to sort of stick with the DVDI module and gravitated towards port to works as our solution for using persistent volume. So from an industrial perspective, so there are a few, I mean, like when Balaji talked about security and compliance, supporting encrypted volume, being able to take backups and snapshots are all very, very important characteristics for a data store that we essentially provide. So we were looking at a storage solution that actually has all of this and that's, that was one of our primary sort of requirement when we are actually looking at these things. Then the other thing is we also wanted a level of support from the community and with the frameworks that are available in the community because we didn't want to go back and reinvent every single thing across all of them. So DVDI came in very handy and the support on port works was also super useful for us. So when you talk about workloads that we want to run on the IoT platform, there are two prominent types of workload, high ops like Cassandra and Elastic, which is a bread and butter that as far as our platform is concerned, and a throughput intensive application, for example, Spark. The ability for a underlying persistent volume provided to quickly switch back and forth between either one of those and have a quality of service associated with each of those was very imperative for that. And that's where port works came in and helped us out. So the other thing is we also, when we started working at persistent volumes and the persistent data stores, we immediately started working with the Meso skies on the DCOS Commons SDK that they started building. So we work with them on a few frameworks including Cassandra and Elastic search and work with the port door skies and sort of switching them together to be able to use them. So we will talk about those learnings as well. So one particular use case that might be interesting for this conversation is sort of an additive manufacturing use case from aviation. So I mean jet engines, GEE has been one of the largest manufacturers of jet engines. They actually say for every few seconds, there is actually a flight that's taking off with the GEE engine. So one of the things, the first thing that the additive team started actually working on is sort of figuring out like what is the one that can actually make a lot of difference. And they picked up fuel nozzles as one of those initial sort of pieces that they wanted to reprint. So this, to give you guys a little bit more idea, these nozzles are like made up of 20 parts when they started. But when they were 3D printed, that's just one part. And it essentially provides you 5x durability and it's like 25% lighter weight. All of these are important attributes when it essentially comes to like building a jet engine, so to say. On the background from our perspective, from an outcome perspective, I think two things. One is the metal powder that are being utilized for manufacturing is like a highly expensive commodity. And these printing actually takes a long time. So some of these nozzles actually takes like hours and hours to essentially get this right. So what we wanted to do from a business perspective, what they're actually looking for from us is to essentially provide them an anomaly detection algorithm and a system behind that can essentially go and identify if there are any issues while it's actually printing. If there are, the need is to immediately stop it and sort of basically flag it to someone, say go and actually take a look at it. Because if you continue to print, I mean these metal powders are like super expensive and can be erased. So to help with such a use case, what we are looking at is a architecture that looks something like this where we are trying to push the computation of as much closer to the edge as possible with the chipsets that we have in business today. A lot of these edge devices are very powerful, but we still see the need of doing in near real time analysis on the cloud as well. Which is why we have a edge processing which pushes in data to our IoT event hub infrastructure. That's a running in Mesos as a framework, which then takes in two forks based on a record of time real time computation goes into work in progress with Apex and the Heron teams as a framework on Mesos, which then uses Cassandra for its tape or a micro batch processing that can be done on Spark, again using Cassandra in the back end of the finish line. Okay, it's back. This is our basic picture of how our real time architecture looks like today in progress. Okay, so we will sort of briefly talk about some of the challenges that we were essentially faced over the course. So cleanup of tasks wasn't automatically done when the service was done. So when we started using the new SDK for the persistent framework like Cassandra, I think one of the initial problems that we faced was everything was working for sort of creating a particular data store and then sort of managing it. But then the moment you actually issue a delet for whatever reason, all of these tasks are basically still running there like a ghost task, so to say. Which is an important problem for us is because when a customer actually chooses to delet his particular service instance, we want the entire thing to be cleaned without any traces. So that's one of the stuff. The good part is we worked with Mesos community and then that got actually fixed as a part of 1.10. Application metrics. So we sort of actually, we have our own monitoring system to essentially monitor our infrastructure. And PromiseDS is one of the prominent ones that we actually use. The application metrics API in Mesos is a completely custom API. So we've given the feedback and we're working with them to essentially see if we can get something as more standard API or maybe compatible with PromiseDS itself because it's a good show today. Few other things that are in Cosmos API is, so when you actually saw the create instance call that Balaji was essentially sort of helping us trace through, there is actually a call to Cosmos API that actually says here is all of the parameters go and essentially spin a cluster for me. But the sort of the pain point there is the JSON that we essentially send it to this API is not getting returned back to us. They're actually completely returned in a completely different format. So this is something that the community is aware, so that's getting fixed. We talked about a few other issues in the SDK frameworks along this. I'm going to skip that. Windows support.  I mean, GE has been running analytics for a long time now and some of these analytics are written in so many different languages across businesses. They go from Python to MATLAB to R to like very custom Windows-y analytics that are actually written. And some of these analytics are like so big and complex that it's actually not a trivial task to be able to rewrite the same thing in some of their language. It might essentially take time and it's going to be a gradual sort of migration. So for us, being able to support Windows and Mesa's DSCOs is pretty important because there is so much of analytics that are still in Windows ecosystem for us need to be able to run in this sort of unified infrastructure. So that's been something that we're working with them as well. Okay, let's switch back to a demo. So the first demo that we're going to essentially show you guys is sort of how do you essentially see the marketplace? How does this marketplace integration actually works? And how can you do a lifecycle of service? So I am logged into a CF environment, I hope. Okay, cool. So we're hoping it's all visible to you guys. Okay, so I am going to look at the marketplace. I'm actually using the CF-CLI, which is the CLI interface to interact with Cloud Foundry. So I'm doing a CF marketplace to actually get all of the services that are available in CF to use. I think it's the Wi-Fi network, which is okay. Okay, perfect. So there is a service that's actually available here, which is a Cassandra framework that we have essentially exposed it from Mesa's. So what I'm going to actually do is I'm going to essentially create an instance of this particular service.  So what this actually says is it says, when a customer actually logs in, he's going to basically run this command and say, okay, I need a Cassandra cluster, and I need three nodes in this Cassandra cluster, and this is my name of the cluster. So the moment you run this, this actually talks to our open service broker implementation between the scenes, and then that actually talks to the Cosmos API for Mesa's. So at this time, I have essentially initiated a request to create an instance. So I'm just going to do CF service to actually see where it is. So you see the create is in progress at this time, and then if I do a dash dash GUID, it actually gives me an instance ID here. So now if I switch back here and then go to my browser, the connectivity is still fine here. Okay, this is a test Mesa's cluster that we put together for this demo. So going into this particular one, if you click on the services, you can actually see this particular service instance, which is the 778, is getting created here. So this is sort of spinning the clusters now. It's trying to basically get things ready, and if you do a CF service, again, in the CF, you can actually, it's still created in progress, so it's actually still in progress. So if you go to the Matathon API or Matathon console, you can actually see the same cluster that's coming up here as well, just as a reference for us. This actually takes like a couple of minutes to actually spin. While it's actually spinning, I want to actually show you guys a couple of other things that we actually did. So the service broker itself has an implementation for creating an instance. It also has an implementation for scaling the instance. It might not be super valid for every single data store. Depending upon the type of data store, you want to expose those APIs. You can do a bind, unbind, and you can do a data recognition. Talk about that as well. Okay, so if you actually see the status here, it's saying there is one node that's actually starting, and the two other nodes are pending. So this is still coming up. Oh, yeah, sure. Yeah, absolutely, yes. So Predix, okay, it's going to be a broad question, so I'm going to actually take a stab at it. So two or three things. So Predix is a platform, which is an IoT platform. Predix also offers a bunch of industrial product suites, like asset performance management. There is brilliant manufacturing, which essentially gives you a way to essentially make your manufacturing environments much better. There is operational optimization, which is also an add-on to brilliant manufacturing and so forth. So for customers, for industrial customers, you could use Predix applications or Predix products to essentially go and start monitoring your own assets, or you can actually monitor Predix assets and basically do preventive maintenance and sort of reduce your unplanned downtime for your applications. So those are at a product level, and we do have some customers that are essentially creating their own applications, extending our Predix products and using some of the Predix platform components directly too. So both of those are customers, and that's sort of our business model here. So let me see. I'm going to essentially, we looked at the GUID. I'm going to actually create a service key here, okay, because the operation is still in progress, we won't be able to essentially create it. Okay, this one is prepared, so it's going to be done pretty soon. And then, okay, so the other thing that I wanted to show you guys, well, this is actually happening in parallel is what we also did is we also created a package for the open service broker in the universe. There is a Cassandra OSB package that also will be open sourcing it. This is for folks who are actually using the like a CloudFont infrastructure to be able to go and say, okay, I want to deploy my own service broker for CloudFont, the open source open source broker for CloudFont. You can just do a deploy and then it creates a sort of the API compatible version of a service broker for Cassandra. So there's going to be documentation and stuff that are going to be published on this as well. And the network is a little slow, so it's just picking up its own time. So what you'll essentially see once this is complete is we will be able to create a service key using this cluster of Cassandra, and then that gets exposed as variable within the app. What is next for us as far as this is concerned is we want to then take that and create a unique service mesh between an application in CloudFontry and a backend infrastructure or a stateful service within Asus. So we're working with partners like Avi Networks here to help us out in that journey as well. So what that also leads us towards is to build a secure mesh as well on top of that. What we will also eventually do is to take all of this implementation right up close so that anybody else who wants to go on top can stand on our shoulders and make this journey more easier for the next ones to come in. Okay. So I think we can also open it for questions while this is actually happening, so absolutely. You can. So one of the biggest things that we have is a platform for anybody to write an application that consumes predicts essentially. So GE has in-depth knowledge in every vertical that's out there. For example, healthcare or aviation, power, oil and gas, transportation, lighting. So we would expose out analytics that we've learned out of our assets. That would be exposed out as part of an analytics catalog that a customer that for example if you would say Kaiser for example, Kaiser then consume that, consume any analytic that is pertinent to your vertical. And you can go start using that to build more models on top of that. Did that answer your question? Okay. So I think in the interest of time is I think the demo guard is not helping us clearly. So there is actually another service that was pre-created before this. So I'm just actually going to use that service to essentially go and show you guys what I wanted to actually really show. So I mean that is another cluster here. I'm going to show you. There's another one called BN as a service instance. I'm going to show you guys that. So it's a three-note cluster as well. It actually has everything running and the deployment is completely successful. It's a Cassandra service as well. And I can do a create service key. And I can basically say create key one. What it actually does is it basically goes and creates a key for us. And then we can look at the key here. So it was instance name which is BN. So when I essentially go and say, okay, give me my service key, it actually gives you all of the nodes that were essentially created on basis. And all of the ports pretty much that you have to essentially connect to this. And the credentials and username and password. This would only be available within that particular water container. And if you only have access to the arg and the space and cf, you can even see this and execute this command. This is protected like that. And we can do a very similar thing with binding the application. So we can actually say, okay, I want to go and bind a service with just a seed application with BN. This, what this is actually doing is instead of us actually manually creating a service key, we're actually saying, okay, go and take these credentials and give it to this guy, this application and inject it as an environment variable. So now it's actually injected as an environment variable for that particular app. Okay. And then in the environment variable, you get to actually see all of these credentials as well. So from an application perspective, you just go and look up your particular service instance and then get the credentials and start interacting with it. And what we are working on as part of this journey is to create this service mesh on the fly as well so that there's no zero touch deployment as when you go create on-demand services. You just got a five minute flag. So any questions? So for us, I think from a cloud perspective, all of our clouds today are on AWS. But of course, from a predicts perspective, we want our customers to have sort of a unified experience. So wherever they are, they actually get the same interface and whatnot. But from a storage perspective, AWS does offers a few types of EBS volumes, like including provision IOPS, standard volume and so forth. So in this case, with Portworks, what we are able to do is sort of create a storage pool based on the type of EBS volumes and then expose it as a class of storage to our frameworks. And the frameworks essentially is going to basically say, I need an IOPS heavy storage volume and it actually gets the storage volume.  Yeah, awesome. Thank you. Thanks for coming in. Thanks.


The Professional Learning Project offers a collection of strategic pathways which educators can follow to build educator capacity, engage in learning, and create paths for success. Strategic pathways include professional learning opportunities, resources, and tools which reflect a regional focus in a provincial context. An individual educator, an educational community, or an entire school authority can use the resources and tools to guide their learning journey.


Good morning traders. So welcome back from the holidays This is J trader. So your mentor for stocks every Wednesday over here at Bookmap YouTube channel Good morning, everybody. So let's start right away Because we're still trading the market. We are trading this morning several small caps ABC, Sazi, FWBI Nexie and then on big caps we are on Tesla, NVIDIA spy Q's ES and NQ a lot to do over here. So Let's right away Join the two session the morning poll Again traders when you join the room, you're free to ask questions We can review things together, but this is going to be more a trading session together So we are right now You can see over here what My team did this morning. We are short on Tesla We'll cover what we did over here. Good morning Florian morning scissor I'm gonna start with big caps So I was screen sharing book map with the room And we're gonna put over here a few things So the first thing over here we had Plan to long and short Tesla Short was the A plus setup because it's trend following We shared in Zoom session The entire process plan Executing on Tesla and you can see over here what our team Results so we were a screen share with book map in the room and As you know, I like to trade big caps Futures and also small caps But today we had book map on Tesla up generally Tesla is one of the most volatile stocks And that is the reason why we have always book map in our watch list So what I like is that Tesla was in the low 20% trading range of the previous day and that gave me Enough confidence to start looking for a short We start then watching over here book map how it opened and as you can see I trace this rectangle Why so when it opens at 245 imagine that 930 everybody wants to buy and sell you have also Institutionals we have also traders who leave I would say Limit orders to buy or sell at the gate. So right away. There's a ton of volume Coming out and I suggest beginners not to trade the first five to ten minutes Of course when you're skilled when you're like more Experience you can trade also the open as it will give you so many great setups at the open we we waited a little bit and we saw this unwinding from 245 till 243 70 and Once we saw this pattern as you know, it's one of the usual pattern that we We look for in the room This is the V pattern. We decided to take the long over here. You can see that We have the reclaim of the open level We have bars in control. Look how many bars over here step in and then we before we took the trade I said Exactly in this moment over here. Take the long to 45 Let me Let me bring this up. So you can see over here at 930 so this is 330 talent time 930 New York time full-size long We took the long at 245 in 10 to 45 15 risking 245 and then few minutes later You will see how we instead shorted and I was guided over here some traders Step-by-step So we get then long over here. We saw this 245 holding We stood in we are 60 70 cents in the money and we were waiting this to push all the way up, but instead I start looking You can see over here what happens from Short to long and then from long over here To the support at this point. We have two possible Scenarios one bounces and you have a push the second one that it curls down and we have a fail What happened we had a fail over here so exactly this point I said reverse to short as The system that actually is a trading system You can see here The system gave us the short entry, which is that square and it also told us that it's a short setup That's a short setup So we flip short Immediately once we fail this support level and then we wanted to see that this support level became a resistance And you can see over here we fail and then we start rejecting This is still 932 so in about two minutes Okay are Long short and then still you will see how the market can change so look over here Good morning dream after we'll also cover what we did on the S&N queue But this is a setup that I would like that you track Because it can open and have this So you stay simply long from here, but of course if reverses instead You start looking to short all the lower high or if you're pretty good That you have a very tight risk and you're pretty disciplined Then I suggest you to enter long of it a short over here, and that's why we did we went long flip short This is a reversal And then we start seeing over here on this break and look at the major amount of sellers, right? They focused over here on this pullback We start seeing the the majority amount of sellers and there was no over here Possibility for longs to reclaim the 245. I didn't see any buyers Instead sellers were really aggressive and then I zoom out and all of this that I'm telling you I record okay We had this major level of demand this major level of demand and then 240 so that's the reason why when we get around 243 we decided to scale out the partial and Then we scale out more over here 241 so once we got to This level down here 241 this level Okay, so these are the levels where we scaled out And over here you can see all of these they form a major Demand zone. This is a wall of buyers But again doesn't mean that if you find this the market will bounce in the in the short term in the very short term you will have a bounce because The stock needs really to breathe even short sellers. They won't be Selling without any kind of pullback So there have been absorb over here and They push back to this 240 260 and then they start fading again. This is still 938 and I put over here this This another rectangle Because I wanted to share with you How over here we got to this level? You can see that we have a little bit more buyers, right? We see it from we shifted from all sellers over here to buyers making higher lows but again, I don't care about all these Fluctuations all these waves. I Want to look over here at the key levels where we can retreat for me the pullback was not enough We were looking at 243 to react. We didn't have that so no react. We took one full-size position And in this case that the trader here at the Academy They were looking at this trading range and I start saying traders if we have a reclaim of 243. We're getting out So if happens this sorry if happens this over here, we get it out over here If instead we break this trading range, so we are looking at this trading range The price was a fluctuating Between support and resistance Then I said, okay, then start looking for more and wine and at this 240s you can see the huge Demand zone over here where we have a lot of buyers ready We start to get out another part. Okay, so the point is pay yourself because you never know How much this stock will unwind or much this sticker will unwind? This is a classic setup that It will give you between at least four to five hour return Okay, I Don't really care that you take the I will say the top tick. You don't need to take the top tick short But take the major Part of the move and to when you have a confirmation and to when it's risk-free and then stay into the trade So once we had this fader look over here again, you may think It's gonna bounce back up again, right? Forms over here are low, but then instead my major point is not looking for our lows My major point is to look for always. Is it making lower highs? Yes And if you were with us while I was screen-sharing this I was pointing out traders look at the lower highs So there are major levels of absorption where you can scale out partials And that's the reason why we scale out as I said before But then look for lower highs the continuation of lower highs Will give you confidence even over here to hold still your position You can see that before that a screen show right here the team get out more into the 237s So down here because this is a key daily support and then we started to bounce some of it here Now what we're gonna do we're gonna trail everything if we break this trend line And we start making a higher high and higher low Okay, but until that moment we're still holding over here Because in average the low this can still unwind more. So there's no really Need to cover too much The other thing that I was pointing out for some of the traders in In the mentoring in the room is that when a trade is working let it run Okay, let it work in your favor don't cut it and Don't really cut your profits because let's assume that You have a 50% win rate And you're only making to our You're not gonna make it fees your time Commissions everything your expenses. So if you have a 50% win rate, you need at least for our Or even more. Okay To I would say have a good income So this was the point on Tesla This is the team. So we showed over here as we said around 245 Took over here 237 and the same yesterday. So we had two days in the road the same exact process And again over here the system tells us simply what to do over under And we look for short boom automatically. So you don't need really you don't need really to think Just very fast on in queue sorry On in queue this morning. We had several patterns So we discussed this in the room before we have a future training room We had some shorts over here and then the last short that we called this morning was the 620 So we got this level over here after the data So mainly short We had this long over here 930 And then from this moment over here only shorts So what I like about thank you that now is pretty weak So we have a potential over here on wine. You can see our cell zone over here. So we're actually below and The levels that I will be looking to unwind is the 16 500 and 16 400 Okay, if you have any questions traders, please reach out same thing on yes So the system you can see those dots red the system gave us those entries exactly all over here and That is what we're gonna For ward under a small subscription to the new traders coming out in the room So you can see the Entry here and entry over here. Okay, so definitely Short side position this morning We had also Nvidia plan over here this morning was to look for a long play and this is the on the over The v pattern, pardon the v pattern that we said This morning that happened also in Tesla, right? So you can see that we have this fail Again, we have a wall of buyers over here at the 473 exactly this low and Remember we have a support over here for the pre-market and then once we have this dip You can start seeing over here that it's making our lows It fails over here to push and then we have another dip But this is still like a v pattern if we zoom out over here We can see the v pattern Then it makes a new low Okay New relative low over here and they start breaking up and really pushing Once we reclaim the open level then it's Target over here. You can see that we get exactly to that level The setup over here was Explaining pre-market. So we were looking or for a breakdown of 472 and 50 and I remember I was talking about this with With the trading in the room. I was saying listen traders We need to see the breakdown of this 472 and 50 and a trader told me why forcing me to in 50 And I said because that is the pre-market low and then I want to see some rejections The second setup is we have instead of dipping to that pre-market low and then we have a push again All of this we discussed for about 30 minutes. Maybe sometimes even more for the For the entire plan you can see over here I was talking and the Ana asked me j y 472 because I want to Give it just a little bit more wiggle room Below that pre-market low And I said over here look for potential Long play on a fake breakdown and that's what we had. I mean Plan is important more important is execution and how you respect your plan We don't have always wins. I'm not sharing always wins, but that's what the system is giving us. I'm trading a systematic Trading system. So the system tells me how and what to trade based on the inputs on the setup that I gave him thanks to Some traders we put all this together and the system is working 70 or even 80 percent of the times so it's It's really money-making strategy and you can just come in check a couple of weeks and you see yourself That's the reason why cheaters are with us. They're a normal life for many months and years Small caps are a tough beast But what small caps are giving us are many long and short plays First of all, I would like to cover this morning with everybody here And if you traded this, please reach out because I would like really to share also that you give me your opinion yesterday in Just to show you the similarity of these these long plays, right? So yesterday we had this the setup long on ABVC actually, sorry BLP LBPH Okay, and the use of book map was simply incredible. This is Yesterday morning LBPH we long at 1340. I Called the setup so traders know what setup we were playing on In the room my screen share book map because book map is that extra confirmation that I need in order to take the trade Over here. I had a mentor student by me So the trader took the long with our alert so with 1340, right and You can see over here. We're holding that play and LBPH 1340 and then this is what happened Yes, this is the long we took We sold over here into the 19th then we were long over here into the 17th and Then we simply sold this is 22 24 and this morning that remaining at 20 23 and 50s 23 and 80s So how this is possible look over here what I wrote We have a base support and I'm explaining you this because you're gonna see the same today so we have a base support and The space support was but very low volume, but they were like refilling on book map So I saw a lot of sellers and then buyers, but this is what instead Gave me that extra Confirmation to alert this for the entire room this long time consolidation that happens between 1030 and 1130 You can see over here and it starts making lower highs lower lows and at this point We start basing over here that base was a key level on book map So we will see this morning on next see this key level of book map. Of course a lot of our traders were short So when they see this we start taking profits and we get out On the other hand this trading instead and I'm sure over here was only long bias So we're trading both longer and short He's straight over here long exactly on that break putting the stop below Selling partial over here and then over here and then as I said 24 and 27 So the base support. I mean base support on chart and also with book map we had the J lines and We had ILOs and then only when the trader starts into work. We have increased our volume now let's look what happened this morning and I can tell you that we started the idea over here to short and the first setup that we had this morning was a short So I'm gonna put over here up next see By the way, anybody traded this Good morning Steven Okay, I'm reading some of the DMs that you're sending me Thank you also traders for putting a like. I remember this is a free screen share So put the like in the screen share really appreciate smash that bid So stun is asking order book is unfilled or depending correct. So what you see over here on the right are all levels Place with liquidity. So let's say that you have Of eight thousands to share eight out of five hundred. I will see you on the limit over here Of course, this can be more than one participant. This is the normal easy current order book You can have extra tools that I share in other videos like the session rings one in profile You can have the quotes Delta that I use You can have the times in sales that I also use But I try to keep it over here pretty simple because I know that a lot of traders see this for the first time so let's start over here next see and How and why we traded this So I'm gonna explain over here a few things So let's go back Okay, there we go. So this morning Just like yesterday LBPH You can see that and we're gonna put this on a five minutes so that we can see a little bit more the Zooming out so you can see that green line. Okay, so imagine that you don't see anything else You only see that green line and over here where I wrote at this 90 make curl the system gave us a long I Missed this morning So I was not able to treat this because we were an in Q and yes, and we were shorting that time But we had a long of it here 755 from the system and you can see that as soon There we go as soon as we had that crack at 802. So At this point over here We had a cup volume coming in You see the volume of here rising and it started to make always higher lows and higher highs and this was a runner If you miss that first long It's gonna be pretty hard to jump on this wagon You can look at the woman at chart if you have for example dips bull flags I like very much to to trade bull flags for example, but you also have to know What is gonna be your risk? So if I want to find a bull flag, I'm definitely gonna use over here book map And the chart so you can see my template over here It's showing over here around 810 815 a series of lower highs a series of consolidation and over here That is the bull flag. So we have a push Lower highs over lows Then holding over here the same low and then a breakout look over here How we have bar stepping in I believe this is maybe an algorithm because we see too many orders really Stack at the same time and pushing so we have this and I tend really to analyze book map pretty in-depth when we're trading it and I cannot say for sure This is an algorithm coming in or not say these are more than one participants But the fact that that is so much control and we have a climax over here Volumes depending then we have the squeeze So this squeeze happening over here, and you can see the volume now is really pushing So what is the thing that you have to get from here? Don't buy simply the breakouts Because if you buy the breaker like in this case the market will kill you Instead once you see a potential breakout Wait for a pullback and then you start taking the long you start taking the long Again, I miss the entire move over here We got it yesterday on LBPH and days before but the long this morning. I missed it in the system over here is telling me green zone J lines look too long. All right. Let's go back to the five minutes By the way, next see if you don't know it's a none of float With a low institutional percentage low insider ownership, and that's a very small market cap It's not too important to look over here why this is up. I mean you can read it But a lot of times you will see pumps Newsletters not even important news that will move the stock I like this morning. We had FWB. I saw the AVVC see to all of these Who are in our pre-market plan and over here when I look at as a trade? I start looking at how it performing the past So the stock had two times a gap above 30% Just like this morning and one time it closed red and one time it closed green Okay, so we had one fail one a one runner Then at the gate 930 this is the moment that I really want to cover with you guys Exactly stun The COB the second column is on as unchecked. I keep it in this way. You see it and put aggregate.  Oh ask extended. I mean it's enough for the things that we're explaining today And at the gate I said traders are we gonna look too long at the J lines, which is this green line Or we're gonna look to trade a gap an extension. So where you see forecast of it here It was written gap an extension, which is a setup short that we like to play and You can see that once we open 930 The price start making this dip and they start pushing over here It pushed one time into the 775 and then I was looking we had liquidity 780 798 dollars. So if you look at this area, it's full of resistance So that resistance was here Okay, so that tells me that at this level over here we have sellers and That's the reason why the system interprets this and It tells us too short. Okay.  This gives you the confirmation So if you zoom out, especially you will see this better Make it Very clear. Okay, you can make it even like this for now But start looking at this We have a major seller eight another seller at 785 another seller 780 You can see the price gets to this level and then rejects And then it bounce from this level. So those are the things that you have to look with bookmark So try to combine bookmark together with a strategy and over here. We had the short exactly this point and Over here, we are waiting for online. I said cover 30% of it here 650 all with timestamps And then what I said traders start to put your stop break even this was the first concern Because over here at this point with this reclaim We are still below the orange line the orange line that you see on my chart is the open level So until we are below the 10 o'clock open level is still a potential fader But if we start breaking the open level and pushing then after 10 o'clock is not anymore for me in a plus set up to short Two things to say over here And now we're gonna use bookmark for this look the six dollar level Okay, and remember what I said before When we are trading Tesla remember the trade we took we are looking for lower highs and lower lows Okay, and until until this point you can see we're making lower highs and then also lower lows because these are relative lows But then we start changing over here and we start making the same low Higher high and a new higher high So it's not guaranteed at 10 0 5 which is this level over here Okay, that is gonna be a reversal because many times we see these spikes that they go near the pre-market high Which is this pink line over here. They go to the open level and they stuff and they short back again What I'm watching over here. I'm looking at book map and I'm looking at volume I Made a tweet that I would like you to to read it Because I explained this Just give me one second. I wrote this yesterday How to find the best runners and a quick guide and you can see for example that trade we took on LBPH And then I said in this week you can find more info go read it. I'm gonna Reupload over here The link go read it because it's a game changer if you're trading small caps and Look at these examples. So all these examples explain that we have a tight long consolidation VVOS if you remember MLGO if you remember Eminem and also over here. We have ALT. So read this and you will see this tight long consolidation Doesn't really happen only in pre-market or in the first I would say 30 minutes like this morning because you can see that we had a tight long consolidation Just like LBPH yesterday, but cat happened even midday or in the afternoon Generally, it will happen between 945 and 1130. That's the general I would say time where you have this tight long consolidation as we said before You're looking for lower highs and lower lows But when the price starts making over here are higher lows and higher highs Then you start reconsidering over here. What can happen? So You don't start shorting against the trend, but you start looking to embrace more the longs Of course, if you're short Like many of the traders were short exactly this point over here this morning Your only concern will be get out at this point at this point I said get out maximum break even in the money If anybody a short you can see that the system with a black square give you the long answer exactly over here and That entry happens together with the bookmark. Look how beautiful. This is we have the fake breakdown of the six And this is a bear trap. They're collecting over here shorts We have a previous low at six again. Okay, so we have a fake breakdown and then we start making higher lows If we zoom in run second and you start looking at the participants We have the majority over here participants being green. So we have over here buyers I was also looking at times and sales and at that moment over here We had a huge amount of buyers even block order passing and Once we break this level Why we have this major candle over here because this is the squeeze candle is not only longs Entering into the trade so breakout traders But it's also shorts that they enter not like us over here But short that enter on the crack of VWAP. They are stopping out of here So that is the reason why you should never show weakness or buy breakouts In this case you buy break out it works But I can tell you that if you buy the break up for example over here at the open you will have a big stop loss and That's the squeeze just over here happening. This is the squeeze. So you can see that we had that pre-market And then over here we have the breakout and look over here the volume coming in You start looking at the volume. This is the volume over here And then you have buyers buyers buyers and we start to top out in the 920s So this area So now is it too short is it too long the market is still holding the pre-market high We're around 11 o'clock Above the pre-market out. There's no There's no a plus setup too long right now Okay Sorry too long and too short right now If you long you had long where the system Gives you the long entry If you're short you're short where we have the setup coming out and telling us this is a gap in extension You can see that the system now Behaves and changes So it's not anymore a gap in extension just an extension play Extension play means runner Okay, so this is how the system is all automatic over here is Setting out the guidelines of course for you to read it and to understand based on the patterns that we trade So now if we see the The order of flow over here We can say that shorts are still trapped above this point and then over here we can say that We don't want to Buy these levels because over here longs are probably trap So we have short trap above this level and we have over here longs trap above this level What we want to do is simply wait Ideally if we start holding over here, we have another consolidation We will be longing this level and looking for new highs If we fail, we're gonna look to trade short later on Okay, I hope this makes sense traders Any questions? All right, let's go back to the small cap land over here. We have next thing See do also over here this morning is a very good runner So see the way here We're talking about a 560 million market cap 70 million float low percent off institutional low percent inside our ownership History of fader on gaps above 30 percent five times out of seven We had you can see over here 71 percent fader Again, we can bring up over here. See do on book map What the system gave us this morning was long over here and you can see that It came after the open with the square. That's the long entry and over here. We remain always green So let's go back on see do Stun is asking what time frame and support and resistance. Do you think? Are you use? I would say I hope to understand good the question but The major level of supports and resistance I look on hard time frame So I'm looking at daily and hourly chart I want to see where we have long trap and also short trap where we have bag holders Then of course, I will use more like a five minutes or one minute for timing the trades But I would say to spot the most important key levels Only using the hourly and daily chart I will look also the weekly chart monthly chart when I trade futures and big caps as well So this morning and put over here see do we had this morning next see a bbc, which was a very good fader We had nvidia. We had sasi So it gave a very good pop of the here and we had tesla for this major unwind The candle second chart are based on the actual price If instead we want to have on book map The candlestick Then you can use these but they're always based on the actual We say price, okay? I don't like to keep it too much complicated. So I'd like to Keep candlesticks over here. So let's see see do we have A no trade zone right now Yes, sir. I have a book map setting shared But we can look together one second. So I can help you out to think that's the best thing So let's put for example next see You have to distinguish between small caps and big caps. There's a major difference So when I'm looking or futures when I'm looking at small cap Something like a next see so $9 stock I would like you to Have this this is recorded so you can watch anytime So I have one corner of the book show bid show ask and extended I don't really to put you see the aggregate over here Because I'm looking at the actual timing of my entry with this The second thing I will add I don't have it over here because I just wanted to make a very simple Webinar today Go over here at one and you go into the times and sales and you create the times and sales Uh, when you have a stock like a nine ten dollar stock put minimal size over here So minimum size and you set this to 999 If you see that it's very liquid like this morning, you can set this to 4999 So that you have only the major blocks passing Now honestly when we have blocks that will be a 20 30 40 k plus But already seen at least 5 000 shares minimum That's a good way to filter all the 100 200 300 dollar Shares, sorry to 100 200 300 shares So minimum I will put 5000 If we have instead a one dollar stock two dollar stock with very high liquidity We can put this number to 10 000 or even 20 000. You want to see the block orders And the the last thing I like to add but not always Is over here the session range volume profile So if I create this You will see that I have the delta Okay, you can use this or not use it But what is good that you will have on your chart this yellow line, which is the show point of control So the level where we traded the majority of the volume Which in this case the 725 Okay, so you can see over here that it changes and moves of course Based on the volume that was actually traded And then when we go over here into the volume dots I like to keep its size to almost half Transparsive half Clustering smart. I don't like really time or changing that. I just like to keep it smart Volume bar is okay. All the rest for me is not that important if you want you can have VWAP But I mean rather than that I have the heat map over here basic standard ones, so vertical smoothing averaging Auto and that's it Let's see another question Stan is asking for answers. Do you check multiple time frame for confluence support and resistance levels? I find it so hard to check so many times in all day long concludes any suggestions. Yes In one of the last Podcasts, I really explained this how I use multiple time frames all together For Increasing the out of success of that trade now you have to have One Char that is the most important chart Choose a 50 minutes a five minutes or three minutes or one minute. Whatever you prefer That has to be like how you scan the market And then of course if for example, I see five minutes supply And also I see a five minutes bearish engulfing A one minute shooting star Book them up confirming for the short key level. I take the trade So the more things you put together The more all the success you will have Now this has to be Clear don't add too many things that you will they will confuse you But you have to find a correct trading strategy So what I do to my team is I have a manual I have a playbook and I simply Trade everything from the playbook this morning. We had envidia tesla. Yes, and in queue fwi Nexie and Think was a sassy That war in our plan and they respected the setups that is in our playbook Okay, so to give you an idea All right, let's go back over here and I believe Next see will be the most interesting one tesla as we said before We're already done with that So this morning along the reverse to the shore side And now we're looking at next thing A few things over here to To understand The system Gave us another entry just now You can see that we have a major level of liquidity over here into the 740 and 750 And also we have what we have the J lines over here So that green that green line over here, okay So system giving us Long entry here And what we're waiting for for this level over here of target a 60 right now. It's with uh 15 So let's analyze this together So it's pretty simple for me Because if i'm looking too short the system will give me too short if i'm looking too long In this case The line is green over here. We're pushing it's an extension I'm only looking too long So I simply wait for this Uh, I would say system to alert to trigger I'm looking for book map to see where I have support That has come fluence. Well, I'm taking the trade Of course now I'm done already with my day But that is actually why we're looking for it. So let's put over here next see from time to time I will scan over here As a trade so I will look at Gappers in big caps small caps I'm looking also at Pump and dump play so something that is going parabolic will come up over here By the way for traders like john that asked The trading session of this morning We recorded the entire session with our trading on tesla. Yes, and in q Next see and all and that will be shared On the website, okay Uh abbc Thank you joe for the alert. Thank you, buddy. So abbc You can see again, uh the system What is doing over here? It's very simple This zone is all pink So it tells over here to short. We have the perfect gap in crap You can see that's the entry of our gap in crap and now in the last 10 minutes we had a system of here changing from red to green So giving us a long entry And let's look on book map what happened So you can see that at this point the system turns green So the system tells us okay look for a potential long Of course, we're looking at book map if we stop making lower highs And we start making higher highs and higher lows You can see at this point So the trend is actually changing over here Because we're not making any more lower highs or lows but higher lows in our highs And then once we break the v-wap Boom very strong volume and pushed it upside Remember these are hit and run trades Because you enter for 20 30 40 cents Okay And my suggestion is for j for ou In the room try to have always some kind of template like mine This template will be released with the new website But I would say as a template where you have like four five six seven eight Tickers to follow. I know that for some of the traders that are beginners That's too much to follow But I don't say to trade everything I say to observe the market. So put the tickers that you're interested into Watch them and then of course, let's say that You have the idea today to trade only two stocks Then you will focus only on those two stocks and when the stock is playing Okay, now you can put the stock on a one minute five minutes 50 minutes and book map So using multiple time frames. So I'm trying to explain not only How book map works with these webinars, but also the process That I found useful for the trading for me and really for 100 of traders right now that I'm mentoring in in the room so On abc the only level that I've been looking to short is going to be a fake of 250 or pre market high 270 There's no way over here. I'm going to trade this Short unless those key levels because the play over here is long on abc Sazi, we are this major j-slam at 540 this morning fade all the way down Next see We are still holding the pre market high level, which is this level over here still holding Jalen's multiple times So this is the plan for me And I'm looking too long over here. If instead we're going to fail I'm going to ideally try to enter once we are Below the pre market high Below the open level and then I see all over high. Okay, so I'm actually looking too short over here And long over here. That's what I'm going to do Students asking Jay, do you know any of the trading indicators that contains all support and time retirement? So I market for us. I found it. It's okay The best for me Is that you tracing yourself, buddy That's the best way to do it. I know that everybody wants, you know The meal ready But the best way is really that you do it yourself Steve and I have a paper trading small caps using small sized and shears to perfect my execution get accustomed to having my stop hit Yes, that's that's fine Okay, let's go back on nextly So you can see that in the last minutes over here. We had Block sellers. Okay So let's see if we break the 750 and reclaim it fast Then we can look for a long play with this setup if you said it breaks down. Let it go Don't chase it. Thank you all the traders for the help this morning in the room To everybody that you know gave alerts explained shared I really appreciate this Enthusiasm from from the room. Thank you very much for the help so we got over here to the 750 750 Remember, this is a very small float is a nano float. We're a small market cap Uh, the gap right now is around 200 plus percent around 220s And we're still holding at 11 o'clock Dot pre market high So what means this no a plus setup for me? Too short. Okay, too short For all traders also that would like to follow us You know our trading lessons You can follow us at youtube j trader. Okay, so we have a lot of free content. We interviewed different six and seven figure traders and eight figure traders different podcasts Looking with the be the trader with andy with professional traders so reach out if you need and This is some of our work So again, you can see that we're holding at 750 We have book map over here levels on nexie Thank you. She's our good morning j Stan is asking is there any way to see who orders Are coming from so we can learn if they are all gourmet. No No, stan. There's no way to see Um If all the orders are basically retailers institutional or algorithms what I can tell you is that when you have and I shared often in these classes I shared often There are some patterns that market makers so algorithms tend to do Um I don't see over here none And this morning I I didn't see them But let me see but sometimes are very clear So according to the majority of traders you cannot spot the algorithm instead you can some you can not all but some you can And there are specific patterns that I look at and I started to recognize did they repeat over and over So in the next lessons if we have them I will share, okay Uh Good morning, Jan Can we see the current flow shorted at each minute? Okay, in order to do that buddy You will need to put over here the volume bigger. So just check the volume And of course we have let's say a float of a 400k. You see the volume 400k You see already that on that minute we have flow rotated But only in that way I don't know if there is a specific indicator with book map Where it tells you Uh, how many times the Like a mark on the chart. I know on trading view there is and I know that on tinker swim there is But it's not that important. I mean when you have another float, you know that Every single bar is let's say 200k. So every one two minutes are going to be a flow rotation Unless You're looking for something different. Okay, let's go back to next see 772 Let's check on tesla over here So you can see again what I mean by the system We had a nice over here pattern to short And that's the use that I like on book map that gives me that confirmation So I see over here our trend line I start looking for A fake breakout which is this over here And then I start looking for the system. The system is alerting me with this to short And you can see from the moment that the system tells me that we have all those sellers over here jumping in So I can enter with a very low risk looking for this target over here Hello, neem I have a question on the red black dot indicator is confirmation quick session is there a function to reduce that Yes, buddy. Yes The chart on our screen with 3d bubbles are only market orders, correct No limit orders all shown on that chart correct. So What do you see on the left over here is actually what has to be executed? So the limit orders what do we see over here are all the orders executed Okay, so you will see the price being executed over here All right, so just so I think we got to the end of our session it's 11 20s uh, I'm gonna go back Do a little review for a few mental traders and then See you back next wednesday. Again, if you have time start studying more On youtube there were many different lessons we made if you want to learn more how we trade you can join jtrader.co And we trade stocks futures and options You will see yourself. I promise is going to be the last trading room You will ever take because there's all to learn from there and we're generating a lot of profitable consistent traders Again, thank you very much for all your help Goodbye j by bookmark everybody and see you next week. Thank you very much


The study aimed to link international classification of functioning, disability, and health, ICF, categories to interstitial lung diseases, ILDs, resulting in 111 identified ICF categories for 10 patient reported outcome measures, PROMs, and three traditional objective measures. 34 new personal factors emerged, providing insight into the utility of the ICF in lung disease and possibilities for developing more streamlined instrumentation. The study highlights the importance of familiarity with the ICF in ILD as it prepares for the imminent harmonization of international classification of diseases, ICD, and ICF, ICD-11. This article was authored by Leslie and Siketku, Leslie and Siketku, Leslie and Siketku, and others.


A slow cook option is great for creating that perfect Sunday roast. The meat or poultry is placed in a preheated dish and transferred into the oven. It then uses a low fixed temperature to gently tenderize without over cooking, resulting in meat or poultry that is juicy and melts in the mouth, making that special family meal taste amazing.


The beginning of a long process, but good news today, two counties are now going to get assistance from FEMA. That's correct. We are happy to announce today that residents affected by the fires in Sonoma and Napa County will be eligible for grants and loans to help them begin their disaster recovery. Individuals affected by the fires can register online at disasterassistance.gov, or if they don't have access to the internet or prefer, they can call<PHONE_NUMBER> in English, Spanish, and other languages. They can also call using a video relay service. If individuals would like to register with a TTY device, they can call<PHONE_NUMBER>. We mentioned the beginning of a long process. You anticipate more counties to be added. We continue to assess damage in other counties affected by the fires, and yes, we do anticipate that additional counties will be affected. If people are unclear, if they're eligible yet to register, we encourage them again to go to the website or to call the toll-free number. Thank you.


The Brainerd City Council again talking about the fate of the historic water tower tonight. The future of the water tower was brought into question after Stucco began falling off its exterior last month. The consensus of the city is to save the tower, but the first step is to inform the public of the total cost of the rehabilitation. They hope by having an ongoing discussion they can work with the community to develop a financial plan to save the water tower. The time is now. It really is. If we wait, it's going to be too late. And we would love to take it to the citizens and do a referendum, but I feel like that's a little premature. I think we need to find as much funding as we possibly can before that happens in order to make sure that the citizens of Brainerd are not footing the entire bill for a structure and an icon for an entire region if not stayed. The public is encouraged to attend the next Brainerd City Council meeting which will be held August 20th. If you enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland PBS.