So it's getting 20 past four, so maybe time to start. As you can see from our slides, we are starting to set a number of world records here. First is for most speakers on a stage at the Linux conference. Most authors offer paper at a Linux conference. It's actually a collaboration of four people from Siemens, the Technical University of Applied Sciences Regensburg, some hobbyists from the ELISA projects who also happens to work at BMW and the University of Erlang in Nürnberg, and fortunately only three of us could make it here, so we're going to miss that world record for four speakers on a stage, but still we are setting out for another record and that is learning more about the behavior of kernel developers from their behavior on mailing lists and in Git, then the NSA already knows. And this is what we hopefully will be presenting you in this talk. Actually, this is both a talk and a request for comments, so we've been observing the kernel community now for quite a while and tried to learn from you guys and we're very interested in once you've seen what we're doing, what kind of questions come up from your side, what we could look into what benefits the Linux kernel. We've had some very good suggestions from plumbers already that will be integrated in this talk, but we're more than happy to hear input from you after the talk in the discussion. And with that, Rade Framsauer will continue to show the technical details. So Wolfgang, thank you for setting the world record for the longest introduction. So what we want to do is we want to formalize and assess the Linux kernel development process. So why would someone want to do that? We have different motivations from inside and from outside the community. So first of all, my personal motivation is to write papers and to finish my PhD thesis. And, but there is also interest from, for example, from safety critical developments where certification is needed. For example, if you have a look at the automotive industry or in industrial developments or applications, there are certification authorities' demand for development process assessment. And needless to say that companies cannot simply modify the Linux kernel development process to their needs, so all they can do is an exposed analysis of the kernel and its process and assess the process that is being used. Nevertheless, the results that we produce are not only valuable for certification efforts, they are also interesting for software monitoring purposes and or for software health analysis. So first and foremost, a preliminary requirement for an assessment of the kernel's development process is to understand the process and its peculiarities and being able to trace the development from the initial submission of a patch to the final integration of the patch in the repository. And tracing the development process is an issue that gained interest within the community. Recently, there were some discussions on how software changes can be tracked and how tracing can be improved by aligning the submission process. There were some proposals, how things can be improved, for example, by adding message IDs to commit messages when the patch is being integrated by a maintainer. Yet, this would lack information to earlier revisions of a patch, so they proposed to add links to previous revisions of a patch in the cover letter of the latest series, for example. So some subsystems also do follow these guidelines that may be inconvenient to some extent, but yet there is no common opinion on how those issues can be solved. So the community is already aware that there is a huge gap between the kernel repositories and the development that is happening on the list. So first of all, let's have a look how the development process itself works. So in the beginning, the patch is being created by a developer in private on their local machines and being sent to one or more of the kernel's mailing lists. Their reviewers send their comments and they start a discussion of the patch and in the end, the maintainers decide whether to accept the patch or not, and if, for example, further changes are required. Then the developer will amend the patch and add changes, rework the patch. This happens in private again. It's not publicly visible to us. He will resend the patch to the mailing list, the discussion starts again. So we have an iterative process until the patch is in an acceptable state. Everything within the blue box is visible to us, but everything that happens outside the blue box, this includes the rework of the patches and that includes the integration step, is not visible to us because we simply, we lack the trace between the patches. To make clear why this happens, let's have a look at the Linux kernel development workflow. So on the one side, we have the mailing lists where our developers send their patches and on the other side, side there is the repository that contains the commits in the end of the day. A patch on the mailing list is typically identified by a unique commit hash, by a unique message ID and the commit in the repository is identified by a unique commit hash. And typically, if you have several revisions of a patch, there is not only one message ID that belongs to a patch, but there are many message IDs that belong to the same functional change, so to say. And there may even be more than one commit hash in a repository that belongs to the same patch as several maintainers may pick up the same patch from a mailing list and apply them to their local branch and later when those branches are merged, a patch may appear twice in the repository. And we are missing the link between all those message IDs and commit hashes. So why is this important for us? Why is this important for tracing the development process? The commit in the repository is just the outcome of a process that happens before on the mailing list. So all those steps on the left side, where you can see the patches, all the discussions, all the remarks, all the tags that are being added, the act buys, signed off buys, the tested buys. This is lost when the patches finally integrated. So what we need, we would need a tool unless there are no guidelines how to add those traces to the commit. We need a tool to recover the relations between patches on mailing lists and commits in repositories. And we do have a tool for that. We call it tool pasta, the patch stack analysis. Initially I developed that tool a few years ago. And what we wanted to do is we wanted to detect similar patches on different branches in a git repository. And we did that for quantifying mainlining efforts of massive out-of-tree developments such as pre-empt or T patch stack or vendor kernels. We extended that tool to work with mailing lists and we are able to map messages and mailing lists to commit in repositories. So how does that algorithm work? So here's an example of two patches on the left side. You can see a patch, an early revision of a patch that first appeared on preempt or T side and later was integrated to mainline Linux. And it is obvious that the commit message slightly changed over time and also the diff changed. And what we do here to connect those patches is we calculate two scores, one for the commit message, one for the diff. We calculate the similarity of the commit message, similarity of the diff and combine those two scores to one global score. If you have a closer look at the diff, then we see that within the same file, the same lines got removed, but different lines got inserted. Let's have a look at the insertions. So from a first view, it looks like this patch would actually be dissimilar, but having a closer look at it, you can see that these lines introduced the same functional change. And we detect that by tokenizing, by simply tokenizing the two parts, and we see that they use pretty much the same keywords. Again, we use string distance metrics for calculating the difference between the two parts and for this patch, for instance, we get a similarity of 87.5%. And given two patches, if the similarity of those patches exceed a certain threshold, we consider those patches as similar. And what we then do is a pair-wise comparison of all messages on all mailing lists against all messages on all mailing lists and then compare those against the repository and recreate a graph or reconstruct a graph of connections of different patches. So on the top, you can see the similarity network where all similarities are included. And below there, you can see partitions of similar patches where we remove the connections of patches that do not exceed certain thresholds. What we have them are clusters of similar patches. So on the top right here, whoops, where is it? Here, for example, we have a cluster where we only have patches, but no commit hash. And there are also clusters with several patches on mailing lists and one commit hash or two commit hashes. The green nodes are the patches on the mailing lists and they may denote, for example, several revisions of the same patch. So, but I don't want to bother you with the techniques. If you want to fall into the details, you can also look them up in one of those papers that we have written. So that's about the technique. But where do we get our data from? So the repository is clear, we can simply clone it, but where do we get the mailing lists from? A few years ago, we still use gmail.org, but all of you might have noticed that from one day to the other, they went down and Gmail is not up any longer. But luckily, colonel.org, lord.colonel.org hosts public inboxes. Those are Git repositories that contain mailing lists as archives, so they are archived in Git repositories. That's pretty nice because the repositories that are available there, they contain prehistoric data from 1996 and downwards. But unfortunately, they are limited to just a few lists. And some lists include data from dumps from gmail.org. And unfortunately, gmail.org cut off some email headers and so this makes analysis a bit hard. So we started to create our own collection and we subscribe to all mailing lists, to all Linux kernel mailing lists that are more than 200 lists. So we are watching you. You can find those lists and your emails on github.com slash linux mailing list archives. Those messages are just from May of this year. So actually, all data that we need would be ready if those wouldn't be emails and emails are broken. So we can find all kind of weird stuff inside emails like broken encodings, base 64 encodings, emails claim to be UTF-8 while they are in fact ISO 8859. So it was really hard to normalize all this data. Just to give you a few examples, we can find headers like that one. It starts like a same message ID but ends up with a date. Happy parsing. Dates like this, I don't know which time zone this is. My parser doesn't know as well. Things like that. I don't know how that can happen. Maybe this is the reason. Yeah, but once all those things are figured out and are clear, we can start with our analysis. And this is where I would like to hand over to Sebastian who did most of the analysis part. So now when we are able to pass all the emails, we start our analysis and we want to analyze the Linux kernel from the release to 639. So from the beginning of the kernel version 3.0 until the present day, which are above 600,000 commits. On the other hand, we collect the emails as I said before from approximately the same day, so May of 2011, until the end of last year, which are above 3 million emails. But you have to keep in mind that's not all emails in the Linux kernel development because these emails are only the ones we have as public inbox available. So here you have a list of the mailboxes we have available and keep the bold ones in mind because we'll talk about them later. So now we have the 3 million emails and now you know it's not all patches so there's discussion, et cetera, and that's no patch, so we can exclude them. In the next step, we noticed that not all patches on the Linux kernel are patching the Linux kernel. For example, there are some patches for the userland tools, et cetera, and we exclude them as well because we want to analyze the kernel. In the next step, we noticed there are very much bots, there are Linux Nextmails, there are Git pullmails, there are stable reviews, and we will exclude them as well because we want to analyze the patches sent by people, by developers, for the new kernel. So we have like 900,000 remaining patches and now we will still exclude some because there are several patches in the answers which are like code snippets or stuff we don't want to analyze so we have remaining 800,000 emails and we passed all of them and now we have them stored and map them upstream so we did all the stuff he explained earlier and what can we do with them right now? We asked the research question, what are the specific characteristics for ignored patches? Why do we ask this? This is because we hoped to determine unmaintained subsystems based on the ignored patch data and to say it now, we were not able to because it's not correlating but let's go on with the talk. So what is the definition for an ignored patch? We have three requirements. First, the patch itself must not have a response by any other person than the author itself. Second, the patch must not be upstream because then somebody worked with the patch and the third requirement is that both requirements are met by all related patches. This includes revisions of the patches or other patches of the patch series. So example, if I send a patch now and it is ignored and I send a patch later and this is answered, both patches are not counted as ignored because one of them was answered so both are not ignored. So and when we did this, we found out that 2.5% of all patches of the Lore kernel org mailing lists in our timeframe were ignored and then we took a look at the years and we found out that in 2011, like 4% were ignored. In 2018, only 1.5% were ignored. So you see the trend that the amount of patches or the ratio of patches ignored is decreasing. So we thought, why not plot this? And we got this graph and the petrol colored line is the total amount of patches per week and the red line is the ignored patches per week. And you see this one spike here and there was a guy who sent a patch series with 1,300 patches at once and it was kind of messy because the patch series was not linked in a thread but each patch of this patch series was sent as one thread and of course not every patch of this was answered. So we have this spike and because this spike destroys all other graphs, we will just ignore it. So and now you have this graph which looks much prettier and you see when you look at the total lines, once a year, there's a spike downwards. This is maybe Christmas, I don't know. And you see each year like five to six spikes downward which might be the releases of the next kind of. So when you want to look at the ignored patches, we get this graph and you see most of the time each week 30 to 50 males are ignored. There are some spikes up and down but it's really steady 30 to 50 patches are ignored. And now we thought is this much, is it not much? We need to compare this. So we plotted the ratio between the total patches and the ignored patches and we got this graph and you see it's decreasing. It's trivial, the amount of patches ignored stays the same, the total amount of patches is increasing. So the ratio is decreasing. And in the Linux plumbers talk earlier, there was a number of developers, of maintainers who asked how many males am I ignoring? And to answer these questions, we implemented the statistics for mailing lists and we selected for mailing lists to architecture related mailing lists and to matriculating mailing lists and these are the graphs. And again, you can see the blue one is the total amount of patches and the red one is the ignored amount of patches. And now we can see three things. First, in all mailing lists, the amount of patches ignored is quite steady. So there are no new spikes, there is no increase, decrease, it's really steady. Second, the amount of ignored patches in each mailing list, regardless of the size, is quite similar. And the third one is that when you look at ARM and NetDev, then the amount of total patches is increasing, but the amount of ignored patches is staying the same. And now back to you. Thank you. And that's pretty interesting because if you have a look at the beginning of our analysis in 2011, the ARM mailing list received about 150 patches and now we receive up to 700 patches per week, but the amount of ignored patches always stayed the same. The same applies to the NetDev mailing list. We have some mailing lists that look a bit different, but for most of the mailing lists, this is how they evolved over the years. We took the ARM mailing list because this is a mailing list that gained an interest over the years, so there are more and more patches on that list, while in MIPS, another architecture, for instance, it was a steady amount of total patches, so this is why we chose the two of them and we chose NetDev because NetDev also did the total amount of patches increased and for Linux wireless, the total amount of patches decreased a bit over the years. Now, if we look at the ratio of ignored patches, it's needless to say that, of course, for Linux ARM, for instance, the amount of ignored patches, even though the total amount of patches increased, the fraction of ignored patches decreased over the years and significantly decreased over the years. So we can not interpret or we do not know if some of those subsystems are in an overload situation, but at least from these data, we can say that the process somehow still skates, so this seems to look good to us, but we do not know if there are maybe some problems within the subsystem, of course. So another analysis that we did is we wanted to know if it does matter when a patch is sent. So is a patch rather ignored if it is sent during a merge window or is it rather ignored if it is sent during the stabilization phase? It turns out that it is largely independent when the patch is sent, but there is a slightly higher chance that the patches ignored if it is sent during the merge window. Yes, so with this, we were able to show some first results of our analysis that we did, map things that happen on mailing lists to the repositories and we introduced some first metrics to quantify the development process. During that work, we observed some other interesting thing that I would like to present to you, off-list patches. So an off-list patch is a patch that has been included in Linux's repository, but it has never been seen on a public mailing list. So it doesn't mean that there is no mailing list where the patch has been seen, but there has been no public mailing list where the patch has been seen. We are able to map messages on mailing lists to commits in repositories. So we can also determine the commits that we miss so where we can find no email. And we analyzed the release, the stabilization phase of version 5.1 of the Linux kernel. This includes about 1,800 commits. And we found 60 commits that had no message or that had no patch on a mailing list. Some of them were errors where our tool failed, but 24 of them were really off-list patches. And the obvious thing is that some of those patches are reverting patches. So the reversion of the patches is cast on the mailing list, but the reverting patch itself is not being sent to the mailing list. That's obvious. Some patches from maintainers are off-list patches to fix up some tiny little things that are not being sent to the list. Every subsystem behaves a bit different. The less obvious things is that some subsystem tend to often send off-list patches. And of course, the most interesting thing is some of those off-list patches are indeed security-related issues. So we can automatically find security-related patches before they are maybe publicly... Well, for example, we found a dead patch during that merge window from Greg Rowe Hartmann where he marked some Siemens thing as broken. We asked Greg if this was really the case, that this has never been seen in a public mailing list, and he said, yes, this has been discussed on the list, but not on a public list, so indeed we can find this type of commits automatically with our tool, which was a side effect of our work, but still that's pretty interesting. So we were able to show a kind of formalization of the development process. We are now able to map messages, mailing lists, to commit to repositories. We showed what patches are actually relevant for our type of analysis, and we showed you some results from the patches that are being ignored on mailing lists and also made an analysis of some specific lists. So with this, I can again hand over to... Yeah, thank you very much for presenting all these details. I've mentioned that we like to have community input from you, so if you now come as companies and tell us, oh, you want to give us money, and we give you patches in the Linux kernel that have not been discussed on public mailing lists, we will not yet be doing that, but as an academic, I would also like to point out a certain problem that we're doing this type of research, and it's extremely hard to get public funding for results like this that may be interesting for the kernel community, but that are not really recognized as part of any institutionalized academic funding system, because interestingly, if you present results to conferences like this one, it has no impact from the scientific point of view. If you show it to five people in a workshop that have never contributed a single line to the Linux kernel, then it has impact. So we'll also be happy to not only take your questions, but of course also take your money that you would instead be spending on outlook. And with that, thank you for your attention and fire away with your suggestions and questions, if there are any. Sorry, which subsystems were off-list? You cannot map it to a certain subsystem, so it depends. Sorry, which subsystems tend to be off-list? I would not like to say that in front of that audience. Unless you give us money. Because I do not want to blame specific subsystems or person. That's actually not our intention, so we'll be happy to say to discuss with subsystem, maintain us how the subsystem does, but we really don't want to publish that in the sense of oh, this subsystem's doing bad, that one's doing good, you suck, you don't, and so on. Oh, there's this thing called code of conduct from the Linux Foundation. So if you would have asked us last year, then maybe that's what we also do. Our next step is we want to do a more fine granular analysis, so we want to look at the actual patch, execute get maintainers, map it to the subsystem, and then do some more fine granular analysis because a mailing list may be used for several subsystems, for instance, like the Linux ARM kernel mailing list, like the NetDev mailing list. Actually, so, nice episode, so we are interacting with the getmaintainers.pl maintainer, and one of the questions we got is, oh, is it academic research, or will you be doing any real work? So the interest is huge. That's illegal. That's illegal. You could do, but then we didn't recommend that. I want to ask that on record, we didn't recommend that. Frankly. There could be, so we did look into that as part of other research, so basically, we were trying to come up with how the Linux kernel developers form groups, who works with whom, and so on, and we did some partial analysis on extending the data from mailing lists and the get version control system with IRC logs with other data sources, and the results you get out there in terms of collaborative teams don't really change much if you include this kind of information, so of course it's a threat to validity. It could be that all these patches are, that there are some people who don't use mailing lists for religious reasons, what not, who only use IRC, but it would be extremely improbable that this really makes a big impact on the, by the other results that we have. So we didn't find any patterns regarding this question yet because we haven't looked in detail into that, but of course we'll be happy to do that. Yeah, not yet. So there's one pattern that we found during that window, there was a new subsystem, a new maintainer, and it looked like these were bootstrapping issues. So question, so the question was, did we look at the latency of patch integration, how long it takes for a patch from first submission to ending up in the git repository? Yeah, we have data on that. Yes, we have data on that, but in another presentation. So we have graphs and we have the data, but unfortunately not in this presentation. If you look into the references that we give in the talk, then it's all there. And if you wanna know, again, an offer from us, if you wanna know for a specific subsystem, specific aspect, we'll be happy to investigate that for you. Yeah, I think two years ago, he did that kind of analysis on I2C, as far as I remember. So any more legal or illegal suggestions. And thanks very much for the attention. And just in time.


Hello everyone, welcome to options with Doug. Streaming live daily on BookMap Discord and the BookMap YouTube channel at 1.30 p.m. Eastern Time. Before I get started I need to go through the disclosures. General disclosure, all BookMap Lebanon materials, information, and presentations are for educational purposes only and should not be considered specific investment advice nor recommendations. Riskless codes are treating futures, equities, and options involve substantial risk of loss and it's not suitable for all investors. Past performance is not necessarily a ticket of future results. And I need to pause for just a moment to announce the BookMap Academy March Madness crypto competition with over $2,000 in prizes up for grabs. To participate, users must register for both the competition and the academy and can also win prizes of $200 by sharing top-tier content. So there you go, the BookMap Crypto March Madness competition. Here's my contact information. The best way to get in touch with me is through Discord. My name is Doug P. Also on BookMap Discord, there's a great place to post questions, comments, and content related to the topics of my presentation and the topics of the channel that I'll go through in just a moment. I'm also on X, formerly known as Twitter. My name there is at Doug Pless. Here are the key tenants to my approach for trading. This is the basis of my approach to trading. First of all, I believe that options trades and market maker hedging activity are key drivers of price in many stocks and futures and certainly for the equity futures that I follow in trade, the S&B 500 and the NASDAQ and the large cap tech stocks that I also follow in trade. And for the S&B 500, SPX is the underlying index. SPY is the ETF version of that index and ES is a derivative of SPX. So when traders buy and sell puts and calls and SPX and SPY, market makers take the opposite side of those trades and they will hedge their delta exposure with ES futures. And for the NASDAQ 100, NDX is the underlying index. QQQ is the ETF version of that index and NQ is a derivative of NDX. So when traders buy and sell puts and calls in NDX and QQQ, market makers take the opposite side of those trades and they hedge their delta exposure within Q futures. The focus of my presentation today and the focus of the options-Doug Chat channel is options order flow, the impact of options markets on stocks and futures and the influence of market maker hedging flow on price action. I have a two-step process for trading and the first is planning and I use positional analysis. I look at how traders and market makers are positioned in the options market and how those positions change from day to day to develop a thesis regarding the expected trading range and volatility for the day as well as a directional bias. And the second step in my process is execution. I look at real-time order flow and book map and real-time market maker hedging flow and spot gamma hero to confirm my thesis and for setups for entries and exits. And when I talk about setups today, I will be focusing on an underlying asset. And for example, setups in the NASDAQ can be taken with can be taken with NQ futures, QQQ shares or QQQ options. Questions and comments are welcome and I will be watching both the options-Doug Chat channel and Discord as well as the chat and YouTube for your questions and comments. Please feel free to post. I'll do my best to answer your questions. And hello, Steven. Welcome. Glad you're here and thank you for posting the links to the crypto competition as well as the book map Academy. All right, here's my agenda for today. News items, economic data and events for today. And then I'll go through my positional analysis. Actually, I'll go over economic data and events for today as well as the rest of the week. Then I'll go through my positional analysis for today. Then I'll review some setups from earlier today. And then I'll take a look at the live market. And when I get to the live market, if anyone has any stocks they want me to take a look at, please let me know and I'll be glad to do that. All right, let's start with news items, economic data for today. Not much of a market mover, but durable goods orders did come out at 8.30 a.m. Eastern time. That number came in greater than expected, also greater than the previous number. And then at 10 a.m. consumer confidence came out and that was less than expected and less than the previous number. All right, then for the rest of the week, on Thursday GDP comes out, 8.30 a.m. Eastern time, Michigan consumer sentiment at 10 a.m. Then on Friday, PCE data is released at 8.30 a.m. Eastern time. That's normally a market mover. And then Jerome Powell will be speaking at 11.30 a.m. And note that is a market holiday, stock market holiday, Friday, the good Friday holiday. I believe I'm sure the futures markets will be open until probably 1 p.m. Eastern time, but the stock market is closed. All right, so that is the economic data and events for the week. Let's move on to positional analysis. I'm going to start with the SB 500. Note that I did upgrade to I'm on version 7.5 upgraded to the beta build 12. And there's an issue with volume dots, at least for me. Excuse me. So I'm having an issue with the volume dots, the clustering. If anyone is else is having this problem, please let me know. I sent a support request to bookmap support. They say they are not able to recreate it. So if anyone else is experiencing this problem, please let me know. I did change the volume dot settings. But it seems to every time I change from one symbol to the next, it seems to revert back to the previous settings. So when I right click on a volume dot, like I'm going to go to the volume dot settings that then it goes to the correct settings. So again, if anyone is having this problem, please let me know. Alright, so this is the SB 500 futures trading in an extremely narrow range today. Painful to watch. Right. Hello, trading trading for a living. Welcome. Glad you're here. Alright, so before I get a take a closer look at this chart, I do want to take a look at a larger time frame. And I'm going to go to the SPX, the underlying index. So this is the SPX in a one day chart. Green line is showing the current trend that began October 30th last year from the low to the high. That's about 1150 points from the low to the high. Alright, so that's a one day chart for SPX. Alright, let's take a look at a shorter time frame sticking with SPX. This is a 30 day one hour chart. I'm sorry it scrunched down. My point here is really to show the levels. So the pot wall did move down. I'll talk about that in just a minute. Alright, so here's the top of that trend line. That green trend line high around 52 61 again for good for around 1150 points. Note during this year, the SPX call wall has moved up from 4800 around the beginning of the year, all the way up to the current level at 5400. And again, more about that in just a minute. Alright, let's take a look at the levels now. Hello, Anirag. Welcome. Glad you're here and hello, Katinka. I'll get to your question in just a minute. Alright, so let me talk about the levels on this chart. First of all, the dashed purple lines are showing the lower and upper weekly expected move. That's based on the options market. That's also based on the closing price for SPX on Friday, and those levels stay in place for the entire week. And then the dashed blue lines are showing the lower and upper daily expected move. Also based on the options market, the closing price yesterday, I do post both of those numbers in discord the evening before. So SPX is trading inside both of those ranges today. Alright, the other levels on this chart are spot gamma levels. These are levels provided to spot gamma subscribers. They're available on a variety of trading platforms. And they're based on gamma weighted open interest. I'm going to point out the key daily levels. So first of all, here's the put wall at 4600. That's the strike where the largest net negative gamma that can be expected to act as support. And this level is really not a significant level. It's just fits the mathematical definition of the put wall. So not really significant support. It's it's way down and has a really have a minor amount of gamma. Alright, so the next level up is 5000. That's the absolute gamma strike. That's a strike with largest absolute positive and negative gamma. So that is where most of the gamma weighted open interest is concentrated. And the next level up is the volatility trigger. That's at 5095 that a spot gammas proprietary volatility flip level. Below that level market makers position on the game curve is negative and a negative gamma environment market makers have to trade with price to edge their delta exposure. And that tends to enhance or increase volatility. Above that level market makers position on the gamma curve is positive. In a positive gamma environment, market makers have to trade against price to edge their delta exposure. That tends to subdue or decrease volatility. And note that SPX is trading above its volatility trigger today. And the next level up is the call wall that I mentioned before. That's a strike with large net positive gamma that can be expected to act as resistance. So that's the potential ceiling for price. And that is a new all time hire for the call wall. And the put wall is the potential floor for price. And this call wall also fits the definition form. The call wall the strike with the largest net positive gamma, even though most of the gammas really concentrated between around 525300. And then again, the big gamma strike at 5000. Alright shifts and levels. So the volatility trigger and put wall both shifted lower. And the call wall shifted higher again to a new record high at 5400. Alright, let's wrap up our view of SPX. This time with a one minute chart. Let me zoom in a bit on this chart. It's really the only gamma level and play for today is this 5229 level. And that is a large gamma three level. So it has acted as support and resistance mostly price trading up and down around that level in an extremely narrow range today. Alright, so this is the ES futures and book map. I have my own cloud notes here. Alright, so that 5229 is actually a C three level combo three level combining SPX and spy gamma weighted open interest into one combined level shown there in terms of an SPX price and then converted to an equivalent ES price more about that in just a minute. Alright, so I have my own cloud notes. So I can show those SPX levels. This will spy levels. So there's the spy that's a 521 large gamma two level. There's that combo three level. And just above that is the SPX 5234 level. And then down below the next level is the SPX 5224 level. Alright, so note there is a difference a pretty big difference in price between ES and SPX. And today it is right around 58 points. So I'm showing SPX 5224 at ES 5282. And note that I do post the index relationships that I use every day in discord, I post the preliminary and the final numbers. Alright, so this 5234 level, more or less acted as resistance earlier today, then 5229 support. Now the S&P 500 is breaking below that level again, potentially heading for the 5224 level. Alright, so SPX ES now potentially breaking out of that very narrow trading range. Alright, shifts and levels again. For SPX volatility trigger and put wall shifted lower, call wall shifted higher and for spy the volatility trigger also shifted lower, but the put wall shifted higher. Alright, so kind of a mixed picture for shifts and levels for the S&P 500. Or let's move on to NASDAQ. Alright, again, remember volume dot issue. And if anyone watching this has experienced the same problem, please let me know. Alright, NASDAQ. This is the NQ Futures and Bookmap. And before I take a closer look at this chart, I do want to take a look at the underlying index charts. First, I'm going to go to QQQ zoom in just a bit. Here this combo level right below 447 acted as resistance earlier today. And QQQ has been making a series of lower highs today. All right, that that 446 98 level, that's a combo three level. So combining NDX and QQQ gamma weighted open interest into one one combined level. Let's take a quick look at NDX zoom in. So the only level in play for today is this 332 level, acting as support and resistance, support, resistance, support, resistance. Let's go back to bookmap now. NQ. Again, making a series of lower highs today. Here's that combo three level I just I just put that at 447. Close enough 446.98. Right, so NASDAQ making a series of lower highs today, that level acting as resistance. Next level down this combo two level for NDX, and then the QQQ 445 absolute gamma strike. And that's also the volatility trigger. And there's some resting liquidity shown with the heat map and and book map between those two levels. Alright shifts and levels. And we'll get to setups in a few minutes. We'll talk about some setups today. Alright shifts and levels for NDX that were done. And then for QQQ, the only shift was a shift lower in the volatility trigger, just like SPX and spy. So the volatility trigger for QQQ shifted down just one point to 445. Alright, so that is based on this. My thesis for the day is was really neutral as far as direction direction goes. And let's just take a look. Actually. Alright, so my thesis for the day was really neutral directional bias, and then also looking for a narrow trading range. And that is really based more on my expected move for the day for SPX was and also for ES, just right around plus or minus 21 points. Take a quick look at gamma notional mixed picture. I'm going to take a look at gamma notional market makers position on the gamma curve at the beginning of the day for the SP 500 and NASDAQ for SPX gamma notional positive in a positive gamma environment, market makers have to trade against price spot gamma assumes that traders are short calls market makers long calls hence the positive gamma they have to trade against price SPX just about an equal amount negative. So negative gamma environment spot gamma assumes that traders along puts more can make the short puts. Hence the negative gamma they have to trade with price dash their dog exposure. So this really these two really offset each other and then pretty neutral for the of the NASDAQ. So my thesis for the day was really looking for a very narrow training range. Alright, let's move on to execution now. So everything that we've looked at so far is based on static data spot gamma takes open interest data that's updated once a day they apply their algorithms to that data to come up with the levels that I show on my charts. Now let's move on to execution. So that's the the information that I use in my planning positional analysis. Alright, so let's move on to execution. Let me check for questions. Katinka ask Hello, welcome, glad you're here. Does the spot gamma trial period include the weekend? I think it's for seven days. So seven days from whenever you're start. Alright, dare to dream. Hello, welcome, glad you're here. If I'm novice and options trading, where would you say I start with the material? Great content. Thank you. You're welcome. Alright, getting started with book map book map has a great learning center. So I would go there if you need to learn more about book map. And then also spot gamma. There's no easy way to really get started with spot gamma. You can go to the free resources at spot gamma calm browse through that it's there's a lot of information there. Also go to the spot gamma YouTube channel. And then when you have absorbed enough of the material of book map and spot gamma, I would say anyway, watch my webinars every day. It'll start to sink in. I talk about the quite a bit of the same information every day. So just start with my webinars every day recordings available on the book map YouTube channel immediately after my webinar. Alright, so I'm going to move on to execution now. I'm going to start as always by looking at what options traders are doing today. So this is the hero signal hedging impact real time options. Again, we're moving to execution real time data. Focusing on what options traders are doing. So again, this is the hero signal. H I R O hedging impact real time options. This is what this is showing options trades and market maker hedging activity for a combined signal for SPX by XSP and ES futures all into one combined signal. The white line is the hero signal. I'm sorry, the white line is price price for SPX. And the purple line is the hero signal. Alright, let's zoom in on this chart. Alright, what I want to focus on. Alright, so just to make sure everyone is clear, a rising hero signal indicates traders are taking positive delta positions. They're buying calls and or selling puts. Market makers are taking the opposite side of those trades and they have to buy futures to hedge their delta exposure. And then a falling hero signal indicates traders are taking negative delta positions. They're buying puts and or selling calls. Market makers take the opposite side of those trades and they have to sell futures to hedge their delta exposure. Alright, so what I want to focus on is this. Let me zoom in on the morning. So a little bit of a grind up this morning. Traders were taking positive delta positions. What I want to focus on is this reversal here. Right around 1020, traders started taking negative delta positions and price moves lower. Alright, I'm going to change to puts and calls so we can get a little bit more nuance, a little bit more clarity.  Alright, so here's 10, actually zoom in more. Alright, so the call line is shown with orange. So a rising orange line indicates traders are buying calls and then the blue line is for puts. Alright, so notice from the open, traders were buying calls and then right maybe 10, 18, 10, 19, they take their foot off the gas very abruptly. They stopped buying calls. Notice the blue line is pretty flat and then just about five minutes later they start buying puts. So this setup was call buyers take their foot off the gas, they stop buying calls and they start buying puts. So the direction of these lines are in terms of options delta. Again, rising orange line positive delta and a falling blue line that's negative delta. Alright, let's go take a look at book map. Alright, go back to ES. Adjust the volume dots again. Let me zoom in. Alright, so let's go over this short setup right around 10, 20. Alright, so there was a stop run. Actually, let me adjust my chart. Stop run up toward this liquidity at 52.95. Those are limit sell orders. So a stop run up toward that level that's shown by the on chart indicator, also the sub chart indicator rising yellow line. Notice during this time as this is p500 is making higher lows. Remember traders were taking positive delta positions. Tumor to volume delta shown with a dark blue line is falling. So this is setting up a very nice CVD divergence. If that's something that you like to watch and train. Alright, the volume dots and book map are showing market buy minus sell. Green dots indicate more buyers and sellers. Image into dots indicate more sellers than buyers. Stop run up toward that liquidity at 52.95. Buyers are exhausted. Aggressive sellers start to come in. Tumor to volume delta continues to move lower. And remember traders started taking negative delta positions. And here's the ideal entry right at that 52.34 level. Leading to a nice sharp drop lower. And as price starts to move lower, sell stops fuel the move lower. And again sellers are exhausted. This is pretty typical of a positive gam environment. Narrow trading range, mean reverting price action. Alright, so there's the short setup. Call buyers take their foot off the gas. They start buying puts. Stop run up to the liquidity. Aggressive sellers. Buyers are exhausted and aggressive sellers come in. Alright, so that's the setup in the S&B 500 that I wanted to cover. Alright, let's go back to hero. So trading the S&B 500 today definitely took patience. There were much better setups and stocks that I'll get to in in just a couple minutes. Alright, Anirag asks, hi Doug, hello. My hero number for S&B 500 does not match yours. What is your rolling window set on please? Alright, so let's go back to the S&B 500. Alright, I'm going to shift back to total. Jump. Jump back to avoid the auto zoom bug. Alright, so first of all, Anirag, make sure you're watching the total combined signal for S&B 500. Not SPX, not spy. Alright, second asking about rolling window. I pretty much always use this one day look back period. One day rolling window period. I rarely ever change that now. I've talked about change again in the past but recently I almost always keep it at one day. Alright, so there you go. Alright, let's move on to NASDAQ. A little bit more range in NASDAQ today. Alright, let's zoom in. Actually, let me explain what this is. Alright, for NASDAQ, I use this combined signal. This is combining options trades and market maker hedging activity for a combined signal for the stocks known as the Magnificent Seven, Apple, Amazon, Google, Meta, Microsoft, Nvidia, and Tesla. These stocks make up a very large component of the NASDAQ 100 and this is the signal that I look at for trading the NASDAQ. Alright, let's zoom in. I'm just showing the total signal here. Alright, so let's take a look at the same short setup right around 1020. Here it's a little bit more clear. The hero signal was making a series of lower highs as traders were taking negative delta positions. Earlier I did separate outputs and calls and they were selling calls and buying puts. Both the blue line, orange line moving in the same direction and at this time, so while hero was falling, price did move up, made an equal high, and then began to reverse lower around 1020 the same as the SB500. Alright, so let's go take a look at NASDAQ. So no one else is having this issue with volume dots. Alright, let's zoom in. Alright, here's the reversal. Alright, Steven, what version of book map are you running? This is only occurring with 7.5 build 12. Alright, so here's the short setup right around 1020 at 447. So remember the hero signal was already starting to trend lower. NASDAQ made an equal high, aggressive buyers on the way up, then aggressive sellers start to come in showing by the magenta volume dots and price drops lower. So in this case, the hero signal from Mag7 was a great leading indicator for a short at 447.  NASDAQ continues to make a series of lower highs. Alright, let's go back to hero. Alright, Steven thinks, thinks we're responding. Again, I'm on just updated to build 12 today. Alright, let's go take a look at hero again. Hero from Mag7 continues to move lower. Alright, let's take a look at some stocks. First, I want to take a look at meta. Earlier today, meta was bucking the trend with zoom in. So there were a couple of good long setups for meta today before it started to roll over. Alright, so let's take a look at meta and I'm going to switch to puts and calls.  Alright, so first of all, notice the floor alert that came in just two or three minutes after the cash open indicating significant options activity. This is something that I've been looking at every day, especially in the first few minutes of the morning, first 15 minutes. A lot of these floor alerts come in and they get my attention for potential trades. So this is a big part of my process in the morning. So I saw this floor alert in meta. Traders were buying calls that shown by the rising orange line. They were also selling puts that shown by the rising blue line. Blue line, orange line moving in the same direction and price moves higher. That's a very powerful directional indicator. One thing about trading meta, it often pays to wait for very deep pullbacks.  So let's go take a look at the book map. Go to meta, let's zoom in. Alright, fix the volume dot settings. Alright, so there were a couple of nice long setups for meta. First one, remember looking for deep pullbacks, trend break. Traders resumed taking positive delta positions primarily behind calls. Good for about two and a half points, up to 509. Another deep pullback while traders continue to take positive delta positions. And this time a move up to liquidity at 510. This is pretty typical for stocks. These bands of liquidity, these are limit sell orders, were limit sell orders, shown in the heat map with the dark, dark shading. The darker the shading indicates there are more orders and limit orders in the order book. These limit orders often act as a magnet for price. So that 510 level was a magnet for price for the initial move higher and then again for the second leg up to 510. Those orders at 510 were consumed both times. So that's where traders wanted to sell meta. Alright, so a couple of good long entries there in meta. Let's go back to hero. So here are the three pullback entries. As traders continued to buy calls primarily driving price. So right around 9.55, 10.35, oops make that a little bit bigger, and then 10.50.  Alright, call buyers and sellers really driving price in meta today. Alright, the next stock I want to take a look at is NVIDIA. So NVIDIA call sellers were really driving price, let's zoom in on this. So traders were buying puts and selling calls today and call sellers much more aggressive. The flow alert that came in that's right before 9.40 as traders were again selling calls and buying puts. NVIDIA move lower. Alright, let's go take a look at book map. Go to NVIDIA, update the volume dots. Alright, so NVIDIA made a series of lower highs pullback entries to VWAP, good entry points for short. This one didn't quite make it as traders were selling calls. And then finally finding support around the 9.40 level. Or let's go check hero again. Alright, so let me zoom all the way out. Alright, so net for the day traders have been buying puts. Most of that activity was really in the first hour. And then the put line has pretty much leveled off since then. They have continued to sell calls up until about one o'clock. So actually right around 12.20, they stopped for a moment, sold a few more calls. Now they're starting to buy calls. And NVIDIA is moving higher. Alright, let me check for questions. Alright, Tony Kay asking a question for Anirag. Anirag says the onboarding video of Smart Gamma says rolling windows should be on 30 minutes to get the best signal to noise ratio. Alright, so first of all, I don't know, I have not seen that onboarding video. I know that Brent, the founder of Smart Gamma, has talked about that recently. And he has said that he always uses a one-day rolling period. So that's what I use. I think there's too much noise in a 30 minute. I always use the 30 one-day rolling window period. I know Brent recently has talked about just zooming in to get more clarity instead of changing the rolling window period. Alright, Redhead Shark wants to take a look at Tesla. Alright, that's Tesla's next one on the list. So we'll go to Tesla, zoom in. Now the long setup, so mixed picture here in the large cap tech stocks. And this is how Tesla reacted to another downgrade today by-by-by calls. So traders were aggressively buying calls from the open. Note the floor lord again. Initially they were selling puts also. Orange line, blue line moving in the same direction. Then they took the foot off the gas pretty quickly right around 945. Start call buying again for a few minutes.  So notice now that net for the day, traders are buying puts that's shown by the negative notional value.  So they're not that fuel driving price higher, the buying calls. When traders buy calls, market makers sell the calls, they have to buy stock. That has stopped and they continue to buy puts and Tesla moving lower. Alright, so let's go take a look at book map. Go to Tesla, adjust the volume dots. All I need to do is right click on the volume dot for some reason after the initial adjustment. Alright, so a lot of aggressive buyers in and Tesla this morning that's shown by the all the green volume dots, one of the green volume dots, rising cumulative volume delta, pullback entries if you miss that initial rush higher, pullback entries to a trend line, and then finally Tesla breaks making a series of lower highs retracing the move higher from earlier today. Alright, so there's Tesla very nice long in the morning and then a short as again traders continue to buy puts and the call buyers took their foot off the gas. Let's go back to hero. Alright, does anyone have any stocks they want me to take a look at? Alright, let's go back to SB 500. I'm gonna switch back to the total signal. Jump, jump back. Alright, Anirag says I wish Spot Gamma had a better screen interface. Spot Gamma continues to make improvements all the time. So this is, I started using Spot Gamma about four years ago and this is advanced orders of magnitude over what it was four years ago. So I think and Spot Gamma continues to make improvements to all aspects of the dashboard here and I know they are working on a new charting package for hero. So I don't know when that will be out but that is something they're working on. If you have any ideas Anirag for Spot Gamma they are very open to suggestions. You can send your suggestions to info at spotgamma.com Alright, so it looks like for the SB 500 mean reverting options trades taking advantage of the dip, taking positive delta positions. Let's just check. Let's compare all trades. That's what the purple signal is showing. That's showing all expirations. Let's now take a look at the zero DTE options. So that's making up somewhere between a third and a half of the total options trades today that's shown by the green or the teal line here. So again that's that's less than half of the total options trade for today and zero DTE options. Alright, net for the day, delta notion of value, mildly positive. Let's go back to book map. Go back to ES, adjust volume dots. Alright, so ES backed up to the 52-29 level. This is interesting looking at not many iceberg orders but there was this is pretty small but iceberg buys there 141 contracts executed and four executions. It looks like they're still on the order book. They moved the order down to 5280. So this is showing 100 contracts still waiting to be executed at 5280. Also the liquidity showing the orders in the order book. 290 contracts currently. Let's take a look at NASDAQ, refresh volume dot settings, cumulative volume delta continues to be negative. Also stop orders, sell stop orders, also negative. Here's another iceberg order that remained in the order book until it was finally filled right around one o'clock. Let's take a look at heroes, see what options traders are doing. Let's go to the mag 7. Alright, looking at the hero signal, maybe breaking that downtrend, making a higher low. Traders buying the dip, taking positive delta positions in the mag 7 stocks. Let's see what they're doing with NVIDIA. So NVIDIA often leads the way. Downtrend broken, traders taking positive delta positions. Alright, I'm reading through the questions, comments on YouTube. Alright, so NVIDIA mag 7, maybe taking advantage of the dip, dip buyers coming in. Let's go to bookmap. NASDAQ moved down to around the lows of the day. Summer between 530 and 535. Check on Tesla. Alright, here's the opening print for Tesla, right around 178.50. Tesla maybe heading down that way, but finding support at 179. We'll see if it makes a higher low. Let's check and see what options traders are doing. Alright, for Tesla I would really want to see the hero signal start to make higher lows, start to move higher before looking for a long. Alright, last call for stocks. Does anyone have any stocks they want me to take a look at? Back to NASDAQ, refresh volume dot. Alright, so NASDAQ trying to move higher, trying to break that downtrend. Alright, last call for stocks. Got about a minute left. Alright, just to wrap up today, the SOB 500 was trading in a very narrow range, and that was really what I anticipated today based on the expected move for the day, primarily right around a little bit less than 21 points, plus or minus 21 points. That is very low, and that has been getting lower from day to day. So, for example, on the FOMC meeting last week, the expected move for SB actuals plus or minus 38 points, and today plus or minus 21 points. So, much better setups I thought in individual stocks, and I covered those Meta, NVIDIA, and Tesla. So, long and meta, and then later on a short, and short NVIDIA, and long and Tesla, and then later on a short.  I want to thank you very much for watching. Thank you for your questions or comments, and I will see you tomorrow. Alright, thanks again. Bye.


What is your best advice to give someone to move on from a relationship or friendship that was toxic? To move on from it? Yeah.  You know, you have to get rid of that person. I mean, not like that. Murder. Yeah. So if you subscribe to the channel, you may know I've been reading Jessica Simpson's recent autobiography, Open Book. And what better time to finish it than during this global quarantine? It's a great read and just making me love her even more. We know that Jessica's lived in a handful of lavish mansions from Beverly Hills to Hollywood and more. But her current home is the nicest one of all. In this video, we'll be taking a look at her massive estate in Hidden Hills. She resides in with her family, her previous homes and more. Jessica Simpson or Jessica Johnson considering she's been married to football star Eric Johnson since 2014. It's a singer, actress, fashion designer and now author. She's one of the pop princesses of the early 2000s and many of us consider her America sweetheart. Although Jessica was well known in her younger years for her relationship and previous marriage to Nick Lachey, she made sure she wouldn't let that define her even despite their hit MTV reality show Newlyweds. I suggest if you want to know more about all of that and what it was really like, definitely read her book. Which, might I add, made it to number one on the New York Times bestseller list. These days, Jessica and husband Eric have three beautiful children and she's been looking better and happier than ever. Besides her music career, Jessica launched the Jessica Simpson collection in 2005, which was a fashion line of clothing, accessories and more. The brand has earned over 1 billion in revenue, making it one of the most successful celebrity brands in history. That being said, Jessica's current net worth is at an estimated $200 million and that doesn't even include her husband's money. Hey guys it's Karen, today we're doing another house tour here on Famous Entertainment. Today we're going to be taking a look at where Jessica Simpson calls home, including her current Hidden Hills mansion and more. And Christina Aguilera isn't the only pop star who bought a house from the Osborns, but I'll explain that a little later. If you like these videos, make sure to subscribe, then ring that bell to be notified when we post. You can always be up to date. We've also done house tours on the likes of Christina Aguilera and Britney Spears, and we'll have links to some at the end of this. Follow me on Instagram because I love getting to know you guys. I've also been reading all your comments and I'm going to be responding to some at the end of this. I need you to let me know who to do next in the comments down below and whose home you'd like to see. Now let's get into this video. So like I said, Christina Aguilera isn't the only pop princess who bought real estate off of the Osborns. Jessica's current mansion in Hidden Hills actually used to belong to Ozzy and Sharon Osborn and Jessica took the house off their hands in 2013. So we're going to take a look. According to records, the mansion set Jessica and hubby Eric back $11.5 million, but it's well worth it. Located in the elite Hidden Hills, a celeb-filled neighborhood next to Calabasas, she has no shortage of famous neighbors surrounded by the likes of Kris Jenner, Drake, and more. Jessica's mansion spans about 11,000 square feet of living space and is so massive it resembles a five-star hotel more than a family home. There are six beds and 10 baths, and the house sits on a sprawling 2.5 acres of land. Not to mention the property is protected by a guarded gate and security system to keep intruders and paparazzi out. The cape, cod-style mansion was built back in 2001, but had plenty of work done to it since. Not to mention the feigned interior designer Martin Lawrence Bullard helped to reinvent the home's design. When you first walk into the home, you're greeted by the grand staircase framed by floor-to-ceiling windows, which Jessica has shown off on her Instagram before.  The house is full of features like high-invaulted ceilings, natural light, open spaces, sliding barn doors, and chandeliers. Other common spaces in Jessica's home include more than one living in a family room, a dinner study room, and offices. There's also a home movie theater and a recording studio where Jess has been working hard on her upcoming album. Most of the bedrooms in the home offer balconies to enjoy the views of ballet, and the master bedroom is especially luxurious. Jessica and Eric's master suite is complete with a fireplace, French doors opening to a private veranda, and a Victorian-style master bath. There are his and hers walk-in closets not to mention Jess has a separate one for all of her shoes. If that's not enough space, the property holds an additional guest apartment complete with a kitchenette. Apparently it wasn't enough space for Jessica and her family because last year aerial photos revealed they were adding in an additional wing on the already massive estate. Now the mansion is not one but two wings coming from the main house. Workers were seen laying down panels of wood for the new space that connects the main house to the separate section of the home. Outside Jessica's home somewhere on the large manicured lawn, you'll find a cow statue perched there giving the home a ranch feel. And the animal statue remains in the property to this day. I'm guessing Jess loves it because she's from Texas. Jess loves throwing parties at her mansion in its perfect entertain. Whether it's for Easter or Halloween, her home is the gathering spot. Outside the home there are covered patios, a large built-in barbecue, and additional spaces to dine and relax. Of course there's a large swimming pool and spa offering perfect views of the hills. For her kids the yard also includes a jungle gym, a basketball hoop, and a swing set. Looking at Jessica's main house I can see it's one of the nicest celebrity mansions I've seen by a landslide and I doubt her and Eric will be moving anytime soon considering they've made it a dream home. Prior to Jessica's current family dream home in Hidden Hills she lived in Beverly Hills in a home she purchased back in 2005 for about 5.2 million post divorce from Nick. The home looks something like a life-sized dollhouse and has plenty of feminine charm. Jessica's previous home was spread over 5,500 square feet of living space and had 5 beds and 5.5 baths. The cozy entryway leads guests into a main boy with a grand spiral staircase and the design appeared to be chic and girly but still with a homey feel. Inside there were plenty of French doors, white marble, chandeliers, and new appliances throughout. Other features of the home included a gourmet kitchen, home gym, and outside there was a koi pond. The outdoor courtyard had an ivy covered wall in the home and a cobblestone walkway. Not to mention the unusually shaped law had a long private backyard with a large pool and patio. This home served Jessica well for quite a few years but in 2013 she sold it to none other than actress Jennifer Lawrence for around 7 million. Before I wrap up this house tour although I don't like dwelling on the past let's quickly look at where Jessica lived during her filming of MTV Newly Weds just in case you were wondering. For the record Jess admitted in her book that it felt more like a ghost house to her and she was rarely there aside from when they were filming. Her next Nicholas Shae's formal marital home was located on a secluded drive in Calabasas and this is where many of the scenes for their hit reality show were filmed. So if you watched you may consider this home a landmark. Built in 2001 the Newly Weds house spanned 6,438 square feet and had 5 beds and 7 baths. They got the home for only 1.7 million in 2002 but by 2005 they were headed for divorce and needed to sell the place. Passing it on to Malcolm and the middle actor Justin Bearfield for 2.1 mil. Secured in a gated community the mansion offered an eye-catching swimming pool and spa, fountain, outdoor lounge area and barbecue. Inside there were all the fixings of an elegant mansion like a grand foyer, winding staircase and high ceilings. Other features included a wine cellar, movie theater, recording studio and games room. Not to mention an impressive master suite complete with fireplace, balcony, two walking closets and equally nice attached bath. Although this home may not have been Jessica's happily ever after it lives on as a little piece of pop culture history. So now we've seen Jessica's citizen's palace in Hidden Hills where she lives with her husband Eric Johnson and their three kids. Like I said it's hands down one of my fave celeb mansions to date. The whole home has a classy feel and everything you need and more. I love everything from the yard, the massive pool and the elegant designs like the Victorian style rooms, even the giant cow. What did you guys think of Jessica's mega mansion? Also I wonder what they're using that new wing they added on for. We also saw the house she lived in way back with Nick Lachey for their MTV show Newly Woods which feels like a lifetime ago and her previous Beverly Hills house. Be sure to tell me which spot is your fave. Okay guys now I'll read out some comments from previous videos. On our recent Christina Aguilera house tour, Sejuani commented dang. You remember back in the day when Kelly Osborne was like Extina's greatest hater. Imagine how she felt when she bought their mansion. What a queen move. Kelly must have been so pissed. And the same video Michael Trudeau wrote. I love the wood in the second home. Both homes are amazing. It's always amazing how a woman can have such a large collection of shoes. But I'm just a guy. Very true and I probably would have more handbags and shoes personally if I was a celeb. But I'm not so I don't need to worry about that.  Yes finally the video I was waiting for. I would love to see Cher or Celine Dion's house. Great suggestions Justin. Thank you. Alright guys that's all I could find on Jessica Simpsons houses including her mega mansion in Hidden Hills and the houses she used to live at. Honestly I never knew how massive her current home is but I love it. Which part did you guys like the best? Let me know in the comments as well as what other celebrity houses you'd like to see. Follow me on Instagram if you want to chat more and I'll see you on the next video. Bye.


So here's the deal. I'm in the new studio right now and it's a project. If you can't tell, the audio, the echo is miserable. I'm going to do something about it because I want a quality show. If you're new to the channel and you don't know, I had a studio prior in my basement. It was a very small room that I was able to paddle the walls and it sounded good. It was very no echo at all. This is the complete opposite. The room is much bigger. The walls are thin. We got almost 10 foot ceilings to work with. So there's a lot of room for the sound to carry. It sounds miserable. I already had this room populated. I had a desk. I had a TV up and I just had these kind of makeshift padded little wall things that I could move around really easily. Didn't do the trick. Did not sound good. So we're starting from scratch. The only thing that's staining is this reclining green screen. So here's the plan. I got packing blankets I bought. I got PVC pipe and I got some clamps for them and I'm going to build a studio out. At the end of the day though, this is a studio to work in to get things done, not to sit back and show off a collection of action figures or DVDs. I needed something that's practical and easy to work in. I then figured out the dimensions I would need to work comfortably and I landed on 10 feet by seven feet. So what I ended up purchasing was 20 10 foot three fourths inch PVC pipe. I got a bag of three fourths inch PVC elbows and teas to connect these guys. I'm not gluing them together. This is something I want to be able to maybe modify in the future or move if I need to pretty easily. I got around a dozen three dollar clamps and then six big packing blankets I could suspend from these things. The packing blankets I believe are seven feet tall.  The studio lights are one of the few things I'm utilizing from the old setup. Those came with they made the move they were relatively cheap on Amazon. I got a cheap new desk and chair on Amazon plus I grabbed some heavy duty zip ties just to just to make sure things are secured. Okay it's been a long night. I don't have the lights on in the studio but as you can see I'm now in a blanket for it baby. We're fully ensconced in blanket. Here's how it sounds from inside. Is it perfect yet? No but I think it really deafens the sound the echo. Watch what happens when I step outside here and into another adjacent room that was very similar. It's a complete disaster. Here I am in another room. How does this one sound? Pretty terrible. Here's Adam. Like here's Johnny. Come on come on in. Okay I'm in the new blanket fort studio. It's all set up. A little bit more than I wanted to spend but I'm very happy with how it turned out. I have suspended my mic it's just out of reach. You can't see it. I'm going to turn that audio on in a second so you can hear all the blue yeti sounds. I'm going to turn on the studio lights and I'm going to fully shut my fort here. Put down the green screen and you're going to see the whole thing play out in real time. So here we go. Lights are going on. Boom. Camera will take a second to adjust. Green screen goes down. Beautiful and then I'm going to move my clamps. I basically just have to adjust two of them. So I can have my workstation, watch some tv, do some twitch at twitch.tv slash Adam Olinger and you know that we have the studio here. All right so here you have it. Now the audio is coming out of the blue yeti. I got the lights set up green screen down blanket fort fully surrounding me and now we knock out the green and here's the final thing after some color correction because I'm still white as a ghost even though I live in South Carolina. There's a pretty dramatic quality difference in the audio so I'm very happy with how it turned out. I want to once again thank people that are patrons at patreon.com slash Adam does movies or right here via youtube join because of the monthly support I'm able to do things like this up my game a little bit. I moved into a new place if you didn't know the audio was super echoey as you can see throughout this video. So the last couple videos I did didn't turn out to my liking so I restructured everything put in the extra effort and now hopefully I can put out some quality content that entertains. So hopefully I'll see you very soon and thanks once again. Oh and if you are a supporter there is going to be an extra video for only you that's going to show the whole house and how that's working out. It's a disaster so far but we're getting there.