Right, so the purpose of this session was, I think, to talk about, in and amongst all of us, sorry, let me just mute my notifications, right, yeah, so the purpose of this particular session, I thought it'd be useful for everyone to, you know, that's been at this Hackathon and has given us your awesome contributions, but we'll also go over some of this in the wrap-up session of five o'clock Central European time and see exactly what we've achieved and how we've achieved it. But the purpose of this session really was more just, you know, now that you guys have had a feel for what we're doing on NFCOR in terms of using modules, some of you are quite experienced now with using them, you know, pipelines around the current syntax that we've got. I think there was always at the back of my mind and possibly others as well, is that we're not necessarily exploiting NextFlow as natively as we possibly can with the current syntax. And so there were some workarounds that I came up with sort of last year to attempt to figure some of this stuff out and make things work and it works, but it's not as native as I mentioned. And so to show you what I mean, I've got a prototype call request and now you guys have already, like I said, contributed to your own modules, you know what the syntax looks like, you know, how we're passing stuff around, you've got the tests working and all of that now. So can you guys see my screen? Yeah, okay, cool. So what we have, so I created this prototype call request now for a fast to see, well, probably I'm going to find it with all these new modules that we have here. So with the new syntax, essentially, what we'll be doing is getting rid of all of these customs. So we had this functions.nfr, which you guys would have seen now. That just contains some basic functions that allowed us to publish files in a custom way and also pass optional arguments around for each specific tool. So if the tool needs arguments, we'd initialize this map and then pass that to the module. What we can do now with what the new syntax is, get rid of all of this, dump all of this, all of this save file stuff and start using more next flow native options. And when I mean next flow native options, what I mean, essentially, you won't be able to see it on this, on this particular call request is that instead of saving files like this with custom options and so on. So this is essentially a custom function to save files that is coming from here. What we can do now is pass all of these options directly from a single config file. So if I show you an implementation, it's what that would look like. A lot of this is actually done by Mahesh, so kudos to him. And we had quite an in-depth conversation today with a bunch of other people, trying to figure out how to finesse this off and so we can actually push it into mainstream adoption. So what I mean by that is we can use process selectors like this, where we can then say that any process with this particular name, for example, instead of having options.args now, we can use the next flow task extension option to pass these arguments directly to the module. So if you see on that prototype call request now, we aren't using any options or suffix. This is directly, this is a known way of passing options directly to modules using this task extension. And the name of this can be whatever you want it to be, it can be suffix, it can be supercalifragilist, it's very dotious, whatever you want it to be. And so that offers a lot more flexibility in terms of how we pass these around. I mean, we're not then restricted to also three arguments, like args, three or args, or we can do whatever we want. For the most cases, we should just need one set of arguments for some tools that have piping and other stuff. Second sets of arguments and stuff, but I hope you get what I mean. So this is inbuilt next flow type functionality that we can exploit and use within modules. Another thing is also the publishing option. So as you can see, we've deleted a bunch of this block of code in terms of how we publish by default. So again, what we're doing really is just using process selectors to suggest how we'd like to publish these files. And there's a number of ways you can customize this. You can have patterns, you can change the mode, you can even enable publishing based on custom parameters as well, which is really neat actually. And it means you don't need an if statement. You can just say, only publish this if this parameter is set to true. So for example, I only want to publish this index if a parameter not saved reference is true. So now hopefully you get an idea that we're moving more towards using this. And next is amazing in terms of the functionality that it offers. I'm not just saying that because it powers the audience. I'll tell them straight up if it's not right. But the flexibility that we need to have this sort of implementation is already there. And it's sort of been bought out mostly like I said by Mahesh in terms of making this happen. So that's kind of where we're going with the new syntax. But what this also means is that what this also means is that we can get rid of a lot of the logic that we would have had the main script, the diff for the main script. So with the old syntax, I was defining all of these parameters here in order to pass them around. So we have this thing where we went from the modules.config file and adjusting any parameters in the workflow. And then that was then being passed off. So actually, no, it's going from the modules.config to sub workflows that are then being done in the workflow. And then, you know, it's just, there's lots of options being passed around. And we had this sort of include syntax where we were changing those options. But now all of this is happening directly by that modules config. So we can literally just do a massive delete. We don't need to use this add prams anymore, because all of these options are coming directly from that config file. And so you can see this massive red where now all of these options are now just changed in a single config file. So you can kind of understand why I'm really excited about this, because it just means that you don't, not only does it for beginners, you know, it helps them figure out how these options are being passed around because they're in a single place. But it also means that it's easier to maintain and update and develop in this way. And the first thought of all obviously was to do this type of thing in a real world implementation, which is why we chose the RNasec pipeline, because that tends to be sort of, you know, the cutting edge type implementation for anything DSL2 we've had. And so the first thing we tried to do was have an end to an implementation of the RNasec to try and find an iron out any issues. And it seems like pretty much everything is covered. So here at the workflow level, we basically deleted so much stuff there. And we don't need to pass these options now around everywhere and initialize them. We can just directly go from the config file to the module itself. Because you keep the config within the parameter within the config, how do you manage to replace the parameter thing? How? Because we're, because we're, we're using task extension to pass the, so all of the, all of the arguments that we were using for, okay, they are already there. Exactly. So, so don't link there are anything, and I think we need to talk to you about this, Paolo, as well in a second, this is, is the caching mechanism for this, but I'll come back to that in a second. So, so yeah, we can, another thing that was quite important that we needed to maintain was that if in a given workflow, you, you say you call sand tools index more than once in a workflow, we needed to be able to independent and change the options for both of those instances. So, in this case, for example, if you use bed tools, you know, cut covers the process selector, if you call this module twice in the, in the pipeline, then it would overwrite the options for both of these instances. However, again, Mahesh found this way whilst we're discussing and trying to iron out these issues, where you can use some quite clever process selectors to hone in on exactly the, the right version or incarnation of that module, you want to change the options you want to change. And so then that means that, you know, if you want to run, say, fast PC pre trimming and post trimming, you can have completely separate options for the one pre trimming and post trimming and even the publishing options and all of that. And so that was quite important because obviously you need to segregate, you know, where even the simplest level where you publish these files. I think this context would be also interesting to mention that what's your timeline to implement this? No, so we, we, we were thinking before Christmas. And that's not because I think also because we were thinking, talking about this stuff, there was a long discussion. In this context, instead of having this huge, okay, I love this fact that they're moving all these things from the script to the config. This is definitely a great idea. But still maybe it's not optimal. And the optimal would be to a config for each module. And that config, you could put the published here deciding to have this huge configuration with all the files, you know what I mean? We actually discussed this literally just now. So, so another thing that we want to do, I'll skip onto that now because we brought it up. So what we're thinking of, so NFC modules at the moment is specifically just for like units. So like fast to see or PWA index or minimap or something. So it may be single tool type modules, but what we also want to do is extend it to work with sub workflows. And a sub workflow is a chain of modules, right? So it's more than one module essentially. And so we've put this net next to a config with it. In anticipation that we could have some default options. I mean, this, this isn't representative what would be in here. But for example, you can imagine there'll be with name process selectors in this next one config file as well to set some default publishing options and extension of arguments and so on. But I think we identified that the problem with that is that the process selectors that we set in this config file will be specific to this sub workflow context, not the workflow context. Do you see what I mean? So if you, if you have this align both type to module here, say you set a process selector for, I don't know, both type to align. So you do something like process with name by two extension blocks to write things out. The process selector will be based on the name of this particular module that's been used in the context of the sub workflow. But when you actually use it in the workflow context, it could be, it could be, first of all, aliased, right? So you wouldn't be using exactly this name in the workflow. You can use both type to as both type to align once and then both type to align as both type to align twice. If you want to control, yeah, exactly. We'll get a warning saying that this process select isn't recognized. Something that you fixed just now with the process selector name warnings. That with this, if we try and use that, the vanilla version. So we had a chat about this earlier. Yeah, it would be nice. Maybe in the next iteration, we can figure out how to do that. But the simplest of purposes, I think we would have all sub workflow type options in this, in a config file like this for the purposes of unit testing type stuff. Okay, make sense to me. Okay. So we'll just, I think it's just the different context that you're running in my course to confusion. But it's definitely something we can probably, you know, revisit in the future. Right. So that's, that's basically the functionality. I don't think, have I missed anything, Mahesh, Grebel, Jose, anyone else that was in on those chats? Have I missed anything in terms of what we discussed this morning and what this can offer? Right. So that's, that's basically how the new syntax will look. Like I briefly alluded to earlier, we're hoping to get this RNAC pull request sorted out as soon as possible. And then to end, the test surpassing, which is always nice. But we're hoping to sort this pull request out as soon as possible. And try and find out all of these issues and stuff. And then we will update all modules on NFB modules, which means that things will almost definitely break if we try and update them. So there will be breaking changes at some point, just a heads up. But I think it things will just be much more simpler with this whole syntax. We're still playing around with a few things and the discussions this morning will really help work around just sitting down and talking about this. And then hopefully, so the process is update and release our NFCore modules all in one go. And so we can just do a find and replace because everything is standardized. And one of the reasons we insist on it being standardized is that it will make this sort of mass changes quite easy to do. And then, thank you for bringing us further. And then after that, we will release RNAseq because obviously, we need to update the modules first to install them in the pipeline. We'll release RNAseq as a proof of concept and then push those changes to the NFCore tools package to get a stable release out. So it's been a bit annoying that you have to use the dev version of tools to actually get the latest versions. And then it's basically because we're not releasing the proper enough. We're missing a trick there in terms of having more contributors to an NFCore tool. So if you like programming Python and using it can help with that, that would be awesome because all of this functionality with sub-workflows and modules and stuff will require some back-end tooling as well. And if you're up for that, that would be awesome. So yeah, the idea is update modules, install an RNAseq and then have a mass release of tools. So I don't think we'll have a release of tools now until we've implemented these changes. I don't think there's any point in having an intermediate release of tools because of the fact that we know these changes are coming. So that's kind of the process, the mind map I think we've been thinking about and implementing this. And then obviously in the future, we've just also had a session talking about this sub-workflow stuff and how we can have standard sub-workflows on NFCore modules. And I think this will be really cool because it means that not only are you just installing individual units or modules within your pipeline, you can install a whole chain of modules and just plug it directly to your pipeline with some sense for default. And so you don't need to worry about those individual units. You just got a chain of modules that you can just plug in and use directly. And so again, we've had some more discussions about that today which have been really useful. But I think that the key there is that what we want to be able to do is test these sub-workflows in the context of modules. So you can imagine if you update a FastQC module and that FastQC module is used by a sub-workflow that runs FastQC and Primvalor, for example, we want the CI to work in a way that if you change the module that it runs the sub-workflow as well. So you can fix both at the same time. And then that just allows the repository to be a bit more self-sustained that way. So people come into Contribute can fix all of this stuff. And everything is always working on a repository for someone that wants to install these sub-workflows. So that's kind of the plan. Edmund's done an awesome job in getting the CI hookup for that. And like I said, we still need to build a lot of tooling for that with this NF4 sub-workflows command. And that would be in the NF4 tools package. So anyone that would like to contribute help with that would be awesome to have on board. In terms of some potential things that we discussed so parallel, the main reason I guess for having you on this call is that for this for this adoption of this new DSL2 syntax, there are a couple of things that would be nice to have in the next minute. Most of the stuff you fix like ridiculously quickly anyway. And I think in our discussions this morning, we basically tested other stuff and ruled out a bunch of other things that we don't need now and closed issues as a result of that. So I think this is the main one left now. Otherwise, we're pretty, there's a couple of things here that goes through these issues with you. So we can maybe discuss amongst ourselves. So this issue is when you change, okay, so now say we've got a conflict like this parallel. We've got extension. Yeah, exactly. So if we change, if we say I run the pipeline once and I realize that for better tools, you know, I want to use different tool specific arguments that I use, resume with that and change this via a custom config, then what happens is that the workflow is actually still cached. It doesn't break the caching mechanism, whereas we would like it to pull down three things. Yes, I don't know, but I tried right now. Yeah, okay. So that's basically one of one of one of the again, it's not incredibly urgent because the simple answer is run the pipeline twice for now until we found the solution. But it would be nice, even if it's not via this extension.us, because from what I understood from my chat that anything that is task.extension or anything that is task.something isn't contributing to the caching mechanism. Is that right? Yeah, you can see what that is there at the point. So changing this via a custom config, say for example, this is the main one just conflict that comes with the pipeline. And you as a user want to update the command line argument for a tool because it's not working. You say you're working on a small genome or a large genome that starts behaving very well. And you need to be able to change this argument. But you don't want to remap all the samples or whatever else you just wanted to resume from where it left off. Then the idea would be to then have a custom process declaration. And again, this is another cool thing about this new syntax is that it will make it more easier to update the options for users as well. I confirm that not just for the any directive, if you change them across with you, they are not taking consideration because the ID or the next little task is only completed taking consideration of the input and the common stream that you're going to run. And I think also like as an exception, the global variable, the point that you are using them as a barrier. In theory that the script section should be changing, but it then comes down to variable replacement. So if we look at a module, so if we look at this module, this args coming in is coming in by task, by extension of args, which we now just specify in our config file here, for example. And then this args then gets passed to the script section. So the script section is changing, but that depends on whether this variable is evaluated. That would be awesome to have that sort of thing because it just means that it will deal with so many things in terms of options and positive arguments around. If we can get changing this to break the resuming ability or even have something else that's not necessarily fit into this, that would be awesome. So that's that issue there, which is just one there. And then, so these ones are niceties, not necessarily required. There's only one required. There's only one really required, which is that task extension one. This is more of a nicety in the, and I think we brought this up with you before, is that we have to have this params or enable condor wrapped in an evaluation because if we just have, and for those that don't know what I'm talking about, just ignore the comments that occurred to that. To make these modules as flexible as possible, it would be nice to declare all of these things in one place and to make them tough and close. So if we just have condor via condor fast you see, because there isn't an enabling mechanism for condor at the moment next well, it will automatically activate and run condor even though we don't want it to, right? Which is why we need this params to enable condor actually then enable it, otherwise set it to no. And all that's really doing in the pipeline files is just in the conflict what it's doing really is, it's just in a profile enabling condor like this. Maybe having like, I don't know, something like this. Yeah, I remember this part. So the point here, if we are going to change now, we create a big mess for all of these things in pipeline because we see that just specifying the possibility is enabling the execution. I don't think it will. So, I mean, all it would be, would be, we just trained these three states. So if, for example, you have a condor that enabled option in next well, right, we're similar to what we have for document singularity like this, or HODMEN or any other sort of packaging system. If we have something like this, then all we would have to do really is just comment out and replace this line. This line can be as simple as that. We don't need to evaluate it because this will only get activated if condor is actually enabled. Do you see what I mean? Yeah, yeah, something like that. I'm thinking how we could do this without regulating this in pipeline. If it is enabled by default, then it would probably mimic the current behavior. So we could just set the enable to false in our NFCore country file. Good point. Yes. So if it is like, so at the moment, if we do this in the module then this will by default use condor. So maybe it's by default in next row set to true and we disable it in the pipeline config menu, which is another option. But again, that's more of a nice idea. It'd be nice. It's sort of a nice to have type feature to get rid of the syntax. I mean, it's not a big deal having a parameter doing its evaluation for now. But I thought it's as we're on a topic of discussing, you know, where we'd like to get eventually with this. I think it's probably worth mentioning this as well. That's that. Yeah, so this isn't really a block like this. Yeah, we found a bug potentially in next row, which I think Gregor has submitted an issue for somewhere. Not yet. I created a note in our board and they'll make a red X one set up a bit more time. Okay, cool. And lastly, I think it's this custom script stuff that we talked about before. So it would be nice to have modules local or you have a folder for a different module like this. And so this is the module and that essentially all that's doing is calling this gtf to bed executable. It'd be nice to be able to have self-enclosed or isolated module type scopes, I guess if you put it that way, paths and stuff are exported on shared file systems or on AWS voucher anywhere else. And that automatically appends this bin directory to wherever this module is run somehow. And that will allow us to basically have custom modules on an app on modules as well, because at the moment it's, it needs, I think we've talked about it to death, but I think it might be that it needs some sort of next row type implementation to make it work. So wherever the module is run, the bin directory for the scripts for that module are also exported into path or whatever else to then run that module. So yeah, I think we talked about the fact that it would be different on the shared file system compared to AWS batch and stuff. But yeah, this is a nice city as well that we would like hopefully to have in the future to do work. And I think some other people requested it as well, but it's not urgent. So I guess to summarize, I mean, we don't need much for me, Paolo. There'll be a few things that would be great to have. I don't know if I missed anything that anyone would like to mention or say or ask Paolo for that matter whilst he's here.   Can you hear me? Yes, can you hear Paolo or not? Because I think you were not hearing him. I don't know why. He's too far away from the stage, I guess. That doesn't matter, no? Does it matter? I think you need to be in a spotlight that the whole group can hear you. Oh, maybe come on stage now, Paolo. Come and join me. I'll try. I'll give you, yeah, there's a jump in. With your official award service. You can pass to people.  Hello. Okay. So, Mela, something you've got. The most important one is this point about the review of the configuration settings. Yes. Yeah, it likely makes sense to allow this. I don't know if we should only do for this X group or for everything. So, the thing is, at the moment, because we're prototyping stuff, we can be quite driven by what you've had to next row. So, if you don't want to break existing stuff with how X is working, if there's another directive or another option that you'd like to add that isn't cashed, we can easily quite easily adopt that because we haven't really used this with any good force yet. So, we're quite flexible. I was also thinking it's consistent logic to not include or to include, but for example, if a task was executed successfully and you increase the memory, in theory, there is no reason to execute that task. So, changing the memory should not impact the caching. This was, I think, the direction of the same for the CPU. On the other hand, with the CPU, I'm not so sure, for instance, I recently had an example with single cell data where if you run it in parallel, it will get another UMAP block than if you run it on a single CPU. So, for reproducibility, it might even make sense to include the CPU and the caching like this. Why? Okay, because you will say you want to say perform better. That's an issue of the tool personally that one should use the proper, that the tool should be fixed itself so that it reproduces the correct. It should, but like if I change my next .contact file and rerun the pipeline and it says, yeah, everything is cached. It's all right and I've published the result and then someone else runs the pipeline on another system. But now if the result is not cached, but it uses the updated CPU value and it then gets a different result, then the pipeline is not reproducible. Agreed, but I would still record this as an issue for the tool. I did. But that thing, it really makes sense, it really makes sense that if there is one piece task, here it is mentioned in the command script, if that URL can change, surely we should validate the cache for that task because, yeah, people here are expecting that. Change that value, so we change the script so it should be executed. Yeah, I think it could be done. And so the other thing without the constraint is not so. The logic behind it should be possible. Yes, I mean, I guess then, you know, we can be driven by whatever you think is best on the next well end. It just works by flexible at the moment in terms of. The only thing we make sense of is if you could open our initial on-line flow for this, okay, I think my hash sorry already for that. I think I did, but I don't remember now. Okay, excellent. Yeah, cool. Excellent, thank you. Anything else? Any questions about the new syntax? Any objections? Uh-huh, it's very beautiful. Okay, clean up a lot in the logic. And above all, I think because in the future, it's always a plan to have a better way to manage the task at the output. So it's a good step to work on better things and I think that we should make sure to manage the output, not using the published here in the contents of the task, but that's a great mechanism, more configuration, so you're really on the good path from the man himself. So any other questions in the audience about the new syntax, adoption, anything else that you'd like to know or help with or just anything, just unmute yourself and speak. One thing I'm wondering about since we're kind of simultaneously discussing it, so there's a full request for fly in the moment and is there a method currently to pull in different types of data because I mean the initial tuple is the meta and then reads, but dry assembler, for example, takes in Iquio reads, takes in Nanopore reads, and it requires also like a label as well to differentiate between the two different types of inputs. And so when you pass the meta thing in, which would likely have the label as well, so Pacfire, for example, and then the reads, currently kind of limits it to one input set. Do we have a mechanism to kind of like be able to pass both Nanopore with the tag Nanopore and Pacfire with the tag Nanopore to the same process and that's in the current way of specifying input. Because I mean I know we can manipulate the channel inputs with like all the branch operators and more, but it kind of then moves away from how Nanopore is specifying the input. Yeah, I think this is in 99.9% of cases what we have in work, but then you always get these outliers that sort of want to do things slightly differently. And I guess the simple answer, so this module can take Pacfire and Nanopore at the same time and what sort of label is it? Is it a value or what is it? What is that label? It needs to be able to do each type of read input. You specify a flag, so you do like a dash dash Pacfire raw followed by the Pacfire reads dash dash Pacfire, sorry Nanopore raw or Nanopore corrected and that would kind of like be the type that would come in with the meta I guess. There's probably a way to do it. I can't think of a simple way. What you might be able to do is pass the reads in themselves as a list possibly where you've got, I don't know the first element is this mode like Pacfire or Nanopore and then you have a channel of reads within that. So you've got a nested list of a platform and reads and then you can have that to be as big as you want or as small as you want and then you can somehow read that into the channel context, sorry the module context and evaluate that to replace the module. That's what I proposed already but yeah. I think that would be the simplest option for Nan. It's separating out the reads in the channel by platform and allowing the module to figure out how to use that information. Any more questions or comments? So we've got an hour left now until the wrap up and I won't expect anything less than solving world peace in the next 55 minutes so yeah the last sprint. Thank you for joining I hope it's been useful and I'll see you guys back here in about an hour and thank you Paolo for coming and joining us. Ciao, thank you.


man you guys already know what it is we at Chick-fil-A don't act like y'all surprised but anyway if you guys are new to the channel make sure you guys hit that subscribe button turn on your post notification but leave a positive comment down below for a chance to get a what? for chance to win a shout out in the next video that is right guys no we not breaking up that is not why we titled this video the way it's titled because our love is too strong over here that's right we cuffed on this side but you guys are gonna find out why we titled this video the way it is so basically we did say that Janice had a doctor's appointment for her endometriosis she wants to go see a specialist yesterday and let me just say that all the doctors she went to see this one is 100% straight up doesn't sugarcoat anything he's just like straight to the point he's just I feel like the perfect doctor for what you're going through but you want to tell them exactly why this might be the end why this is the title in short terms I might be getting rid of my endometriosis for a little bit for a little bit for just a little bit I have to get emergency surgery done and I basically have to get everything scraped off and taken off and it does grow back every couple years so this might be what I would have to keep getting done over you know the next couple years so like every five or every three years I have to get the surgery done again but that means that there is actually a solution to my pain and a solution to everything that's been going on I think I was falsely treated not a diagnosed I was falsely treated for my diagnosis and it was just not cool like my other doctor gave me loads of birth control I was on a lot of hormones I gained weight my breasts got bigger and more painful I've been in such excruciating pain for the past three months my emotions have been all over the place and honestly it was I feel all for nothing that doctor was jank bro yeah it was honestly for no reason because now that I went to the specialist he was pretty pissed off at what like I told him about the other doctor that I've been going to and I knew in my gut I was like this is not right my doctor pretty much told me previously she's like you can't get surgery done there's no surgery that can help you and I kept asking I'm like I've seen like surgeries done I've been doing research about my like condition there has to be something to be done for my pain she basically told me that I was crazy pretty much that I was going through pain while on birth control and I told her that prior to birth control the only pain I had was during my menstrual and yeah it was severe pain to a point where I was shaking vomiting and all of that but at least it was just for a week versus every single day honestly she said the only thing that could help me was birth control she put me on a super high dosage and she basically put me on birth control that shut down my ovaries completely so that I can't produce eggs or anything like that guys she said she wanted to remove her uterus yeah she's 23 yeah she told me the only way that I can help you is if you remove your uterus like I'm trying to have a kid hopefully in the future like are you serious like there's nothing that you can do for me and she basically was just like oh I'll see you in six months let me know how the birth control goes and if you have any breakthrough bleeding she was no that's it no help whatsoever so the past two months I've just been trying to find a really good endometriosis specialist that knows what they're talking about and that knows how to really diagnose someone and as soon as I went into this man's office yesterday he was like we need to get this taken care of now he basically told me he wanted me to get surgery this Friday but unfortunately I can't because I got a tattoo and that stays in your system I literally got it yesterday and perfect time yeah so perfect timing so now I have to wait a little while in order to get my surgery this means that there is hope it's very scary because I'm going to have an incision multiple incisions on the surface of my stomach so I'm going to have scars and it's really difficult like to deal with especially because like you know gaining weight throughout this whole process has been a struggle for me as well since I've always been tiny my whole life and then going from 120 pounds to 140 it was like in like a year less than a year and less than a year when I started taking my birth control yeah you like those 20 pounds came within like six months give or take yeah it was pretty rapid and I was scared so I'm like what is happening like I haven't changed my diet I always eat in the same like nothing's happened to me I thought we've been in the gym yeah we've been hitting the gym so like I'm like what's happening but it's kind of like contradicting considering we're at check for later it's alright um but yeah so like we said we feel like that doctor's like straight up he's not playing any games he's taking this very serious which as a doctor should be and not like that jank doctor that was trying to like falsely treat her but like she said the surgery is coming soon stay tuned for that we're gonna keep you guys updated with everything obviously of course but yeah guys that's um that's pretty much it this is a very short video we titled it the way we titled it because this could possibly be the end temporarily for her endometriosis but of course we're leaving everything in like God's hands he's gonna take care of everything and we just have faith that everything is gonna go well especially after the surgery we're hoping for a lot of positive effects after the surgery because the doctor did mention that a lot of her stomach problems could be because of how swollen her ovaries are on the inside it's not allowing food to pass through to get out I hope that after this surgery you're like you're good yeah you're like a hundred percent good I literally had like a blanket over me he lifted it saw my stomach he was like you're bloated that's fluid that's all fluid let me see what's going on in there instantly and I was like wow he really knows what he's talking about yes like he's he's not playing any games guys he's being 100% serious he's taking a serious I love that and the fact that he wanted to book her ASAP for a surgery but being that she got her tattoo we're not able to do that kind of sucks but I like how he's like he's on it already and this is the first visit we had and I was literally begging my OBGYN I'm like can you please like I need to get this taken care of and I hate surgery I fear surgery since my rhinoplasty because of my recovery so the fact that I'm begging for you to do something for me for me to get surgery is obviously means that something's happening she's like no we can't do anything like okay but yeah infinite fam I guess that's pretty much it for today's video short sweet to the point um like we said no we're not breaking up we just wanted to give you guys an update because we said we would as far as going to see a specialist and this is everything we found out as we go on we're going to keep updating you guys on this endometriosis journey that's pretty much it for today's video if you guys enjoyed it and you guys have hope for jenice make sure you guys give this video a big thumbs up down below comment down sign below sign positive if you guys are dealing with something similar to this or know anything about it we'd love to hear it or we'd love to read it you got anything else you want to say no that's it I just want to say like I know I've seen a lot of you guys DM me and like everybody who's commenting saying they've been through similar situations it like makes me feel so much better that I'm not alone in this because it's really scary going through something that is very unfamiliar so I just appreciate that so much and I appreciate you guys we appreciate it a lot when you guys comment and you guys like show love or share your experiences like we feel like we connect with you guys even more so spam up the comments below guys and we'll see you guys in the next video


So my beautiful people, today I am back with another Alder Ring video and today guys, this is the one. This is the best rune farm so far we have seen in this game. Without a shadow of aid there, this spot is utterly craziness now. I'll explain exactly how you get here in a quick second. It will take a short mini quest to get here, but you can earn a minimum, I don't even know. There's so many adds, the elements quickly count in 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14. There's like 20 enemies here, all dropping a minimum of 2000 runes each. They're easy to kill and you can do this over and over again. Today I explain all. How's it going guys? My name's DPJ and if you do enjoy the video, leaving a like really helps out and if you like what you see and want to see more, be sure to subscribe. Okay so this part of the map is right here. Palace approach, ledge road.  There's another method in getting here but it's way way way longer and it means that newer players just ain't gonna be able to do it. So yes. Okay so firstly guys, firstly the one major thing you'll have to do is defeat Radon. That's it, once you've done that you are good. You know where he's located right here, chamber outside the plaza to start the quest you come here. Impassable, great bridge to get across here guys. Bam, start it, kill him. Is the boss in this big area here. Loads of cheeses guys, you'll find loads on YouTube. It's not too bad to be honest but yeah I'd say so once you do that guys you want to go back to the first point, under map, right here. The first step upon you getting back here guys you'll see a stone on the floor, go touch it and it'll give you the bravo email but it also starts off a new quest where it says find yourself maidenless. After Luina with you then, seek the rose church west of the gate town. So that's where you need to go. So from here guys you need to go to this rose church which you can see located right here on the map. Now upon you getting to the rose church you'll see the vendor right here. Upon you talking to him you need to select where they'll give you two options, you always need to select the top one. Now this varies for different people, for me it said something different to what my friends said but it's along the lines of the fingers seemed a little off. So always select the top dialogue option.  Five of these, these are used guys to invade other people's worlds and you have to do this three times, you have to invade three people, at least three people.  I found a couple of people sat down next to them for a bit had a little chat you know what I mean and then they just killed me simple as that. So yeah do this three times and then you are good. You then guys need to go back to that rose church. This time he'll give you a new item called the Lord of Bloods Favour and what this is for is you need to use this item and dip it in the blood of a maiden. So from here guys you want to head up the map and if you've got the checkpoint or the grace the grand lift of deck test you want to go to here and from this position guys you need to follow what I go because we're going to the church of inhibition but you do have to be careful here guys because you will build up madness running up a couple of the hills so you have to be careful but when you actually get up to the actual church that we're getting up to you'll be invaded by an NPC called festering fingerprint vike who you do have to take out so take him out people but once you are done with him guys go inside of the church as I do on the screen now you'll get a sacred tear on the statue to the left of it you'll get the finger maiden armor set but also guys this continues on the quest we dip that cloth in that blood so you guys make sure all dialogue options are done and continue on with this quest then you have to head back to the rose church and here guys you then have to offer this dude your finger and he basically goes off you get for this uh the bloody finger but if you speak to him again guys you'll get the pure blood knight's medal and this is actually the item we use to teleport to this said area so go into your infantry guys and use it now when you appear here it's very important that you follow the path I take I mean I do go here and there just to grab a few items we're ultimately to end up at this grace so you can trigger the grace so you can do this farm so go as well I go on screen now and you should be good people so once you have this grace activated you can do this farm indefinitely like I said 2000 plus runes per enemy you kill now if you do have the gold scarab talisman which I'll post the guide in the video description this actually buffs your rune gains by 20% indefinitely as long as you've got it equipped you can also use the gold pickled foul foot as well this again I believe is an extra 15% for three minutes on runes and so yeah make the most of it people so if you've killed radon and you've done that quite a while back and you go back to the point of the very first step grace and this npc or this thing in here to trigger try going to the rose church and see if the vendor is there the vendor in there or you've accidentally killed in people you still do this farm but the actual trek is unbelievable and I mean it's absolutely unbelievable you will have to go through a few bosses the first one being phantom god free you'll then have to kill morgue at the almond king you then guys will have to traverse all the way up to the top here and go into castle soul and defeat a dude called commander neola believe it is he will then give you an item I think it's half a medallion you'll then have to go to an npc I can't remember where the npc is but there's a guide on youtube and I was watching it the npc I think will fulfill the whole medallion you will then have to go to the grand lift of road I believe you get an alternative option to go down and it goes on from there guys so yeah it is a crazy quest if I can find the video I was watching I'll link it down below but this is definitely your best bet especially if you're around the level 40 to 60 if it ain't I wouldn't even worry about this farm yet and I'd do other ones it's as simple as that guys but there we have it people and I hope the video helped you out if you did leave a like really helps me out if you're new around here want to see more be sure to subscribe and hopefully people I will see you on that next one


Sorry guys, the promo randomizer is gonna be in a separate video now because I ended the first video So let's give away those two spots as this one was given away two Super Bowl spots so let's Get the original customer names that bought in That's how you usually do it. I got him over here and let's give away the two spots Roll it and it is a four to three seven times. All right. So again top two names We'll get a Super Bowl square spot Good luck one Two three four five six and seven the final time Boom seven times Sad times with John McGill and Jason. Congratulations. You guys both bought sprayed up. So there you go Let's say sad times from three down, but Jason and Gail, boom didn't call your guys's name out that I know of so it's nice to get a little Super Bowl square out of this So let's go here 21 22 Goat hip parade goats And I'm players number two So there you go guys Again, appreciate it guys So the first video is gonna be the break second video would be just a randomizer for the hip parade Giveaway for the two Super Bowl squares. So appreciate you guys Jaspis case breaks calm


Dw i'n meddwl i'r Bradfordau. Roedd ydych chi'n meddwl i chi gael gwaith ffasgol perrwydion ar yr unig. Felly, dwi'n meddwl a'i'r ffasgol i'r seithio. Rydyn ni'n meddwl i'r ffasgol i'r seithio? Wrth gwrs, rydyn ni'n meddwl i'r gwneud i'r yrhyw i'r club wedi'i Bradfordau. Rydych chi'n meddwl i'r ffasgol i'r seithio, ac yn ymddangos i'r rhan o'r dda i'r gwneud. Sometimes and I'm just excited to get started and wouldn't really do you know about this deal? Is it something that's perhaps happened quite quickly? Yeah, it's happened pretty quickly to be honest. I've obviously had a couple of other offers elsewhere, but for as soon as I heard Bradford and the manager and stuff and the fan base that they've got, it was a no brainer.


Happy Sunday morning. It is 1034 a.m. ish. Bob is already off to the kids house to help with construction again today and I'm going to go drop off an Amazon return and run a couple of errands and then we'll be home for a day of crocheting and trying to work on my sweater and a couple of other projects. So yeah it does look like it might rain again although we're not supposed to get rain but then we weren't supposed to get rain, thunder, lightning, or hail last night. That's right hail. Here are the clips. Fun right? Alright so I'm gonna go get done what I need to get done and then we'll get back and we'll take it from there. Alright let's get to it. I got a couple of different small crochet projects done. A bunch of chores done and got a loaf of bread in the bread machine cooking. We are going to I could sit and be lazy that's my first instinct. Gotta be honest there and I am still working on my crochet sweater. Did a couple rows and thought instead of sitting on the couch crocheting and eating we should probably go get some steps in. Bob's still over at the kids working on their construction project so I'm gonna do just that. I'll be back. Junior's gone home for the day. He'll be back tomorrow for a couple hours and also on Thursday. Yes I'm not getting as much creative stuff done these days because I'm playing Oma. Can't say I'm too mad about it but now that he's gone while Bob is still working I'm working on my sweater. Yeah I'm good with that. Using my free time hopefully wisely. Maybe? Alright I'll be back. Hey everybody it is 10 30 a.m. Wednesday September 6th. I think I have been up for a bit. I had counseling this morning at 9 a.m. and before and after I was doing that. I was cleaning up my crochet bag. I'm this close to being finished with my current sweater so I was kind of getting ready for the next one. I've also got a bunch of scans of air and I've got to wind up in the cakes and put into their socks and we're going for a quick weekend trip this weekend. Don't have a problem with telling you because by the time you see this I'll be back. Eating taking drawing stuff with me or crochet. I'm not taking both we won't be gone for that long. I have to figure out which one I want to take with me. I'll also say if you do multiple forms of arts and crafts like I do and you love them all when you do go on vacation and you want to take one of them with you which one do you take? Let's do a survey. So anyway all right I'll be back. Oh hey you guys I'm a hot sweaty mess now. How many times have I said with my art room space and probably yours too? You get the main fixtures in place that make you happy and then the products that are in the fixtures get turned on a regular basis. Mine certainly did today. So now the lower part of the bits bank is all fabric and yarn. The upper parts, small bits. This is different kinds of collage bits and paper and there's a few things I put in the closet that I wasn't ready to get rid of because I do use them occasionally. But they don't need to be out on the floor because I'm not using them that much. Mostly it's like cardstock and handmade paper stuff like that. So it's in the closet now. I also purged. Oh the stickers are in here too. I also purged. Are you ready? Art bags. It's not something I do often but yeah it was time I was ready. I do have a bunch of stuff now that I have to relabel but I'm not sure I want to do that today. I'm a hot sweaty mess. The grandson's gonna be here in about an hour and yeah we'll see if I get it done. I don't know. In the meantime that was a much needed but good purge.  I'm probably gonna list on the local buy nothing group. See if there's any mixed media artists out there that want any of it. So all right I'll be back. I did get the labeling done. Now I'm a hot sweaty mess. I have the yarn left out that's for my next project. After I finish this sweater I'm working on which I might take with me on our trip that we're going on. Unless I finish it then I might just take the drawing. We'll see in the next couple of days because we leave on Friday. I'm gonna just sit for a bit. Yeah about an hour and just chill. I need that. I'll be back. I got up a bit early today. Well for me because Junior's coming over and Oma's babysitting but I wanted to finish my sweater which I did. I instead of long sleeves I put short sleeves which I really love. I like your all feedback about maybe having him cap sleeves and then I'm gonna be doing another one of these for sure. Cap sleeves maybe would be on the list next time but this is an inexpensive wool sweater. I think it's like a number two. It's pretty thin and a little bit uneven but it wasn't hard to work with and the pattern is fairly easy. I will link both down below and it's not a super soft wool but it's not scratchy either. I don't know if that makes sense. Anyway I have my next project ready to go. I'm hoping I can get this on the blocking board before junior gets here because I do want to block it a little bit but we'll see. Anyway what do you think? I love it. All right I'll be back. Good morning. So I can tell you this because by the time you see this we'll be back ready but we are headed out to California to have a long weekend. We're going to visit with an old college friend. We have a Masonic event. As I said before if you are new to my channel my husband's a Freemason so we have a Masonic event.  You know we all wish to have such a long life right? So anyway we're going to check up on her and visit with her and his brother and his brother's wife and all that stuff. So anyway I'll bring you with us where I can respecting people's privacy and of course we're going to stop at Daiso. I mean you know and while he's doing his Masonic thing I'm going to do a little walking around and probably shopping in a little town that's over there called Murphy's. I think that's the name of it Murphy's and maybe I'm glad we left that was the Xfinity truck. That was. No internet connection probably. Anyway so yeah I'll bring you with me where I can and we're gonna fight Portland traffic and head to the airport because that's a thing. All right I'll be back. I'm in a little town by the name of Murphy's California and this is near Columbia California. We're here for a Masonic event in case I didn't say that yet. There's a little yarn shop here called Maisie Blue. If you like needlework and that sort of thing check them out. Cute little shop. I happened to walk in there when they were having a sale 50 to 65 percent off. That was a problem so yeah good thing I brought an extra bag because now I have yarn to bring home. We're gonna hit a thrift shop and then we're gonna head back towards Columbia and wait for the guys to finish their degree and have a cup of coffee and all that. I'll be back. Two dresses and one I'm gonna leave as is.  I'm gonna just make what I want so I'll just cut off the top of the the dress and um adds molastic and there you go. Anyway we're gonna go find a grocery store now because I need a couple of things and then head over to Columbia. I'll be back. I stopped in the town of Columbia for a little bit and walked around but the guys are not nearly done with their Masonic stuff meeting things they were doing so I'm gonna head back to the hotel and Bob can get a ride with one of them. I'll be back. I'm sitting here in the hotel room once I got back I had a snack I got some coconut water and drank that. I bought 12 skeins I know it's a lot of yarn some really great wool silk and alpaca and I on average they were on sale they were like clearancing them out because the colors are not available anymore and I got them for about seven dollars a skein you guys I got enough for two sweaters such a deal anyway I'm sitting here watching some youtube working on my coloring book and I just heard the loudest crack of thunder and it's raining and we're coming we came to california and it was not supposed to rain it was supposed to be in the 90s and we brought brought shorts no umbrella only flip-flops this is gonna be fun I'll be back hey guys so yeah you can't see me we were in the midst of our masonic dinner and an unexpected thunder and lightning storm again I thought it stopped but it didn't power went out every time we come to california we bring the rain with us we do and we never remember a coat long pants or an umbrella so anyway I'll get you a better video in the car but yeah oh there I am so yeah so we have no power we're oh there we go more lightning we're pretty sure we can still get in the hotel room but we'll find out in a few minutes so yeah this is me sitting in the dark again do we have oh we have a light a little bit of a light anyway we're gonna see if we can get into the hotel room hopefully we can the electronic door lock should be running on a battery our medications are all in the hotel room so that's a thing yeah so anyway it was a great dinner and we finished dinner before the power went out we did and they were bringing dessert up so we got desserts which was great I would have loved a hot cup of coffee but there's no place to have it there's no I think maybe all of Sonora which is the city that we're in right now it might be without power yeah so yeah anyway interesting end to this week's vlog if you want to see what happens tomorrow and how and getting home and how that trip is that for next week's vlog you got to stay tuned all right that's it for now I hope you had a great week um that you're having fun being creative and enjoying life don't forget to like share and subscribe check out the video descriptions for relevant links um leave relevant comments down below I do answer all the comments and above all go out and have a great day have a great week do something nice for yourself because you deserve it we're going to try to get back to the hotel room now let's try yep see you next week


All right, Sabra traders welcome on back here this Tuesday Valentine's Day, of course right February 14th Once again, happy Valentine's Day to all the ladies of our live trading room. We had Carol before we had Barbara before we had Bell before Leda Kathleen and all of our ladies here if I had missed out on you I apologize, but great to see all of us here collectively including the males Ron here lad and clear at least representing the male side But either way folks, let's hop right into the thick of things here, right? We have the market kind of flat now taking us into the afternoon But BWV make a nice move back up and over my 176 line you can see here on the screen So, you know, this could be a nice trade to work with going into the afternoon on this one coming off our traders talk workshop This one ended up working out really well, you know from where we left off I know I have a lot of lines on this chart. So pardon me there But if you could focus on the price 162, you know coming off traders talk our weekly workshop conducted in the cyber group room every Tuesday morning Well, you know, we ended up saying what happens if this re breaks above 162 What if it could afford us the chance to see it retest re break that level? So after seeing buying coming in there mainly from the market open was off because there was a nice perk that popped up After 8 o'clock there. So that's what kind of created that resistance But no once it re broke over that level it was shortly as I really quickly after our traders talk concluded We jumped in right off 162 and I still have some shares left from that price I ended up taking part of my position out half out at 180 181 pretty much where it's trading at right now Just earlier I had another line at 180 and I thought it was gonna I thought it was gonna give me a lot more Trouble around that price. It kind of broke right above it and flew up much higher So that's where I ended up holding on to the second half and thankfully I guess it's making the second wind type of move to keep me alive on the straight It was kind of slumped it off a bit just a moment ago So, you know, at least from the morning, it was a great morning and this was kind of the icing on the cake This was more of a gift Than anything, you know, normally you don't tend to take advantage of such an easy simple run in like garbage time The late morning early afternoon. So, you know, if it ends up snapping back towards 170 I'll pull the plug on the rest of my shares from 162 entry, but this is actually a pretty good sign You know over 176 here. That was a pretty big level from earlier today as well So let's just continue to see higher lows. I'll put this back on our list for right now the BWV All right Now really quick little trivia at least if you were joining us earlier inside the trading room, you know I was focused on this BWV earlier today This I was really intent on following going into the market open like from pre-market If you were in traders talk with me, what was the other stock? I was pretty heavily in Invested in or not like literally but you know, what was the stock I was vested in otherwise aside from BWV It was this and one other stock Ron saying Palantir PLTR he hits it absolutely So Palantir coming off a traders talk Well, it ended up teetering around the opening print price right off of 857 yellow line I know I got a bunch of lines on this one too. So again my apologies But no, nevertheless it ended up shaking off of that now I ended up missing an opportunity on the trade myself because I was jumping in on the BWV at the time thankfully that worked out but Called one of our students and we were watching this in the moment and nailed it We just didn't jump in together So it was right off 868 right here big buying level and very similar to like BWV and that price You know the more times it needles its head off that level more times that we see buying off that level not only should it break that level break above resistance, but That's where resistance gets flipped into So this this was so takeable here right off of the 868 870 I was calling that out in the room I was telling you that my my student and I on a call we're looking for that move to happen I was just in on the BWV So now Palantir for right now is still looking really strong and going into the close I mean hey on the web towards nine big level It was a big buying level from pre-market as well So, you know, I would look for that to be a big resistance at least for the time being probably see a false break Out at first there if not multiple and then perhaps the squeeze higher so give it a little time But yeah, BWV and Palantir both look really good going into the close All right, I don't have lines at every stock So you'll have you'll have to just bear at the regular chart going forward here But let's go from top to bottom. Let's see what else we can get here. Otherwise. It's cheapy here a big I didn't really see it until now MST it's actually making a really good squeeze right now from like 48 or 50 cents more more of a pre-market move I reckon I didn't really even see this until right now my first look on the stock Normally a cheapy like this we don't put as much focus on but outside This thing has been having a pretty active day to say the least You know more of a pre-market move and more of a late-morning bounce and it's worked out extremely well so far from there You know, I'll come back this if anything, but I'd rather focus on stocks over A buck you know the nice trend here, but we'll see if there's anything looking better All right, OCFT. Well, it's over a dollar just that Spreads looking a little wonky there the order book as well Just I feel like the spread will open up suddenly. It's like five or eight cents the the chart looks great I mean it's moving up steadily It's not really trading a whole lot of volume on the whole day. That's the concern on this one here if anything It's only trading about 400 plus thousand so far on the day I mean, I guess that's more compared to its average, but Yeah, I mean just because it's at the highs doesn't mean we're gonna put it on our list So nice chart, but I wish the order book was a lot better Just to go back. I mean hey again BWV All you need is like one of these and a PLTR. We don't need to build up a big list here So, you know, we'll take it kind of in stride take things slowly The Irene stock I know if I was to had called this one out earlier today and actually the order book filled in a little bit more on this On this one a bit of an iceberg actually you could see on level three here at two sixty seven So for about thirteen thirteen plus thousand shares, you know, that could be a big support level for the time being I'll keep this on the side list and I'm more inclined to put this on our main list than anything So I'll definitely come back to this one by the end of it all Just want to kind of cherry pick more see if there's anything looking even better Definitely not this thing this FUSN. This thing chopped me up around this exact level 450 earlier cheese. That is a mess So yeah, I'm gonna pass on this one for right now Well times water break there as well. We'll keep it going Now this is a good trade DDL and it was one from yesterday in the morning We had our eyes on so to go back on this trade It was a pre-market mover it popped going into the open It was kind of looking similar to one of these other ones We were just looking at like the OCFT like kind of thin volume grinding on up a popped up higher, but Came right back down. So pretty interesting pretty surprising as well to see this run right back on up Right up towards six and for right now. This thing is looking really strong I'll definitely put this on our main list the DDL trade the high of the day from yesterday was off of 616 if you're interested in that all right Again, we got Palin tier on the way up towards nine Dbd here is one that Fausto had called out earlier today, too It's kind of towards the end of the audio commentary we had and it's still holding well So that part I like it does have good liquidity. So that obviously I care more about even I'll just separate this from the DDL stack my traders dyslexia. We'll probably trip those two up DDL dbd Si Wow, this is looking really strong still a nice display of higher lows still off of 1660 pushing back up and over 17 right now You would assume resistance off of 1750 But you could see it right there on the ask right off the high of the day big block order for about 15,000 shares right there and It just melted through it like butter. Alright, there we go blasted right over that at least I was at 1738 You could see the prints on the tape there That order got broken through all right now. This has been a really volatile stock of late I don't have level level for open book map open for this one here. So my apologies on that If anything it looks like right around here seems to be a bit of a level with 1750 the low back from the third 1739 the close back from the eighth last week I know just generally that could be more of a you know level to watch But the more buying we see off of that it should lead to a lift higher So You know more go the more it goes up I would assume your next major iceberg level would be off of 18 if anything keep it to your whole number levels All right What else we got here in the meantime folks now? We have a good list see this is why we cherry pick this is why we look like to kind of go through the best ones and kind of Say I will keep it on the side and we'll come back to it because again another one That's looking pretty strong right now one of the AI stocks SOUN this is pushing right back on up making a pretty strong run here And yeah same with AI this one trip me up early this morning, too off that damn 2250 So we were expecting a much better run on this heading into the mid-morning We just didn't get it and you know hey there could still be time on this the SOUN looks just a lot stronger So I'll put this on our main list. I'll put the AI on our list BB AI I don't have a need you know the other two just look way better Don't force it on this. So you know SOUN and AI will make the cut if this one makes a much better pop later I guess we'll focus on it then All right, let's see what else we got here.  It's up over 11% right. I mean it's having a good day It's at the highs too. So that part you got to respect. It's just so slow So I'll at least write it down on our side list come back to it if we need to MREO to wrap up or maybe I saw Mara here as well. Just to kind of look at M.A.R.A Yeah, it's actually looking pretty strong now. I mean yeah, I'm gonna yank my own leashes I say that at least because you know these crypto stocks rarely ever make a clean squeeze up higher into the close Right. We've seen that historically over the many years You know one day. I'll eventually have some egg on my face and it's a nice trend. So hopefully today's the day You know Mara looking pretty strong Coinbase taking a look at that. We'll take a look at Riot and other crypto stock You know what kind of healthy moving up Mara definitely looks the best in terms of just being at the highs running up pretty well Up over 13 and a half percent That back trade here to BKKT. I guess if Mara is on the main list I'll slip this this one on as well. This one would probably be second best crypto stock All right, I'll do that Yeah, another one here last one BITF. This one's not really looking too great All right, let's hop over to the loser's side right now seeing if there's anything looking, uh, you know better I mean markets are grinding on up right now. So see if there's any name brand down big off of earnings MGNX, you know dropped off earlier today, maybe later on it could be a short, but I'll pass here for the meantime Geo small dead cap bounce. I don't really see much else here on the loser's side folks really I mean you got the ETF cold dropping off. I mean It's not a day trade really. All right, I'll tell you that's pretty much it folks That's all you got from me SI is already on the list there Wendy. It's looking pretty strong So we had talked about that briefly a moment ago looking pretty good pretty good Gonna pop on maybe this one stock SOBR sober Yeah, it's not much of a pop. I mean it's a nice daily chart when you look at the daily chart This thing's been running up really well Since we first focused on it from the end of january. So I ended up making a nice bounce Maybe this could be a squeeze higher, but I'm not a fan of the volume per minute It's not really trading a whole lot of volume right now. So, you know, we'll keep this on the on the side list here Write it down here on the side All right, so bkk team made the main list. I gotta scratch that off the side list there this one The iren Not going anywhere. It seems and then the ocft. I'm pretty skeptical of this There's no need for us to focus on this right now at this point All right folks, so I'll tell you we got a really good list going into the close I'm not just you know selling you on that.  I mean, there's a bunch moving to work with going into the close So I would start and stick with this list. There is literally no need to go anywhere else There's a you know level one stocks on here level three or four stocks on here level five if you're You're looking for a more volatile one But you know, nevertheless, there is no need to go outside this list We just scan the market for you for the last 15 minutes With that in mind though for all this inside the live trading room We're going to post the tweet post the picks right now We'll tweet them out momentarily, but you know rich will be on the mic going from three to four o'clock I'll be in the chat all throughout the day going into going into the closing bell as well For all of a sudden social media facebook live twitter linked in youtube I appreciate your participation as always each and every day each and every afternoon If you have any questions, feel free to shoot me a quick email josh at cttrading.com I always like to post that here at the end of these streams Then on top of that if you're interested in joining our live trading room continuing the audio commentary with us Whether it be today tomorrow or next week just go right down to the link on the green banner below the stream right there There to get yourself set up on a small week long trial Again, we do audio commentary all throughout the day from the morning into the close So we look forward to seeing you there. All right for all of us there right now Again, I look forward to talking to you folks coming up momentarily talk to you soon