So we're here with Ortiz and So how so who are you? My name is Claire Ortiz So you're talking about what are you talking about? This is a so what we do is we are a design development and essentially apparel experts in performance materials in innovation in Engineering and in garment development. So here's an example of one of our garments, which is It's a fully integrated fully functional performance wool We don't do anything that isn't high performance. This is a 7-in-1 material that we Essentially formulated our own fabrics. Everything is laser cut same-sealed even our buttonholes are not sewn They're actually a sonic weld. So we utilize the highest end technology in laser cutting in motion dynamics as well and in the way that we construct all of our garments seamlessly, efficiently and pretty high-tech. So here at the wearables, printer electronics, ID Tech X and so what's going on? What's going to happen? So what we're doing now is we're taking everything that we have done with our collection in high-end high-performance materials and embedding printed electronics. Our goal for our collection is that Anything that you wear that is functional should never be obtrusive. It shouldn't feel like you have technology on It should feel integrated as if it's part of your body. So all these can have technology inside? Yes, and as an example, we're working with only printed electronics. So for instance, this is our Fitness garment. It's already integrated with a lot of details that include zoned cooling. It includes zoned protection for the muscles, lactic acid control so that a person can perform at a high-high level and reduce Injury to the body as well as allow someone to perform at a longer time span. We add to that then the printed sensors and printed electronics. So when you look at it from the outside, you know, people are coming and saying, well, what is it? There's there's no electronics here, but in fact, there are. It's all Six areas of printed sensor. So this is a silver-paste ink. It feels like nothing on the body These are the sensors here that would take bio readings and then a small central module, which we don't want to show the actual electronic because the whole goal is that everyone can see that this is the most lightweight and literally seamless way to build electronics intuitively into a garment. So the idea is this this will take the the bio information like the heart rate, breathing, body temperature and we can essentially create so many things inside of the body, but then also with our expertise in apparel design and development, we understand that it's not just about the electronics. When you put it together with all of the functionality of engineering true performance for human body as well as integrating it so that it is really, truly seamless that's what we're talking about, you know high-end intuitive motion-dynamic electronic wearables. So this is the most exciting area of wearables, right? It's getting into the clothes. Yeah, we're we're, you know, essentially challenging ourselves and the industry I would say in the electronics world to try and build things that like I said that are completely intuitive in the apparel world, especially in performance apparel, you want to feel like you have absolutely nothing on. So all of the devices should feel like they're actually part of your body and not that extra. The other thing that's really key is that everything that we're building has to be machine washable. It has to be able to last a very long time. So we take a lot of care in the testing and the development and making sure that from a quality perspective, France is going to really last a very long time and be useful and affordable. What's this demo for example? So this is an example of what we call burnout printing. This is not normal dye stuff. This is one fabric. These are the same fabrics. This is a burnout technology. So what we do is we burn out portions of the fabric to allow for breathability. And we do it in what we call artistic formation.  You add to that that these prints, you see these flowers here, could impact to be a silver-paste electronic ink that would have conductivity in any way that we want. So we're displaying the fact that technology and printed electronic innovation doesn't necessarily have to be so I'd say electronic looking, it should be art. And in fashion, if it isn't stylish, if it isn't really beautiful, then it's all for not. So this is the trick. You want to get all this technology into stylish design and nice looking. Exactly. And then there will be lots of sensors in there, potentially. Exactly. And with all of the technology that exists, what we want to do is make sure that everything that we're building feels like it is just the most, you know, comfortable and performance-driven product without feeling like you're wired up or wired in. Right. So next year, potentially, people can start buying these with all the sensors in time. How long is it going to take? Let's hope in the next six months that we can get all of these things to market. And that's a really good question. What we have done is taken a lot of time to make sure that all of our products are already tested and approved. We're working with a lot of agencies to test and develop brand new electronics. This is an example of our printed electronic. This is a silver-paste ink. And imagine that something like this is essentially printed onto a garment directly. It will be inside. Yes. So this is what you see on the inside of that garment. And how to make sure that all these sensors have real functions and can do all the stuff that people would not have? Well, so that's where all of the expertise comes in, right? We have worked with a lot of folks on our side, as well as our key partners. And that includes the DuPont team in collaboration so that we're essentially bringing together some of the smartest people, I'd say, in printed electronics industry to make sure that the sensors, in fact, do work before we go to market. And even the shaping and where they're placed is critical. And one thing that we know that is very different about the electronics industry or the tech industry is that the human body is dynamic. It is in motion all the time. And no two humans are built the same. So when we're developing our electronics, we have to take into consideration sizing. Sizing is key. It's something that is our technical expertise. And so when we're developing all of our prints into the patterns and into the fibers of our clothing, we're taking into consideration the size of the human body, how it's going to move, and what it could potentially do after garment is washed after it's worn. So the the react and retract effect is really important. The first generation, there would be a small box here, right? Yeah. So this is where the electronic module sits. And so it'll be in the middle of the shirt. It would be module, right? So the module sits here and right now we're working with a few partners to develop a fully encased and washable module. Because again, what we want to make sure of is that all of our products are machine washable, easy to care for, safe. And so all of the elements that go inside, whether they're accelerometers, or Bluetooth, or even the batteries, they have to have a long life, have to be able to be washed, worn, and easily cared for. And really important that, you know, these are not Tesla prices. Not that we don't love Tesla. We all would love one. But the idea is that we're bringing technology to everyday working people around the world. So 2016 is going to be exciting for smart clothes. Very exciting. Yeah.


So, you see four of them, and I'm already familiar with it, is any member of David's that's built in a really, really fast. And the other thing that's still in my background, I was at CMS underground. I'm really interested in the legacy of Dan at TDU. Actually, I wasn't born on the 5th, but we used to work more on the 5th. So, I'm currently on the 3rd of the year at NSQA. So, we're going to start talking about it. The first thing we're going to do is have a stage for why an individual can do matters. And the best way I can remember is who is the future leader of my partner, called Hybrid Regression, which is actually a medical process for the first time. And each time is essentially, the memory's been out for a while, and probably the point is for it to really matter is to think that these two friends, like Dan and I, are trying to clarify the importance of, you know, the point that standard enterprise companies can understand. So, it's a really good way to set the stage for why we're trying to develop a medical system. And that's really what Dan and I, this is kind of the meat of the presentation, is where the key innovations that are in the people that enable us to kind of deliver on being a kind of very powerful, very exact, sort of a database.  First, one memory. Um, probably speaking, there's two great categories of database workloads, um, all of them being, such as online transactional processing, and OLAP, which is online analytical processing. We actually found that in both of these great categories, people are really hungry for what they're going to do. So in all of these places, in every position or in every section of the project, you can push forward, connect in six seconds, do an internet assistant, and return on the line. And you guys can just do a data perspective, process a little bit at a time. Just for building an application, collecting data on one of our purchasing states is the most powerful thing that's going to try to help us work on. When it is necessary to store more data in memory at a faster rate, in memory kind of enables us to do that. And then we also have people who are low data faster, and they want to generate a course faster. When you load data faster, this is called data latency, which basically means the time from the state of the board to the time it's available. When you load data at a course faster, this is called program latency. And that's the rate at which we're going to receive results of queries. And it's really kind of a combination of these two. Let's be kind of an accept, and why do you are interested in addition and whether or not. If you want to do the same, these problems are pretty well solved. If you want to just literally pass on different bits of data, you can use extreme processing systems. But if you want fast queries, but it takes a long time to run the data, there's plenty of old-school program databases that you can all describe them for you. So if you want to know more about what those are, a lot of these workflows are not what you find in a textbook. So why do people use databases? And if you go on the field and try to present them in every database, just click on the link in the box. Let's say this is a kind of stuff I want to do. This is the way I look at it in memory. So one thing is just interested in processing data in real time. This is only a case amount of data from when data is born to when it's actually used. And this is pretty much the standard across enterprise companies. And they want to go and do this in real time. Another thing that's generally the most of the processing data sets, the standard today is that after collecting data all day, and not being able to use it, you do like 4 to 6 hours of preparation overnight. And what you can use is sort of an O2, the materialized approach that I was going to tell you in the next day. But for processing data that either comes in, there's really not a lot of flexibility. And all these connections are successful. The time it takes to react to an event tends to be too long. And this is only a stretch of forwarding when it defines a part of the business. So from the perspective of traditional technology and physical, it makes it really easy for us to provide value on an organization where it's actually only accessible and able to save money in the event of a failure. And finally, dashboards are really slow. So if you look up again, a financial analyst to allow such a company, you really need to be able to access more data. And doing that in a sub-second manner where hundreds of users can currently fill in as many as you can, is a very hard problem. And so all this energy in the American place, around the kind of non-characterized workloads has led Gargoyle to use this tool on HVAP, which is hybrid transaxle and local processing. So for new category, I think it's new as of this year, actually. And what's really cool is that in all of the documentation in the recent part, let's see if there's a hard line in the space. So it's kind of been really cool to see technology working on drying how the industry looks at this phone as a whole. So, again, this is kind of feeding the last line, but HVAP is all about animal rights over concurrently changing data. And then there's two kind of really interesting results of HVAP that an HVAP-driven system needs to be able to provide. One is predictable performance and scalability. Because you're playing with data latency and query latency, and you're trying to power hundreds of users controlling access in the backboard, and it's really all about performance, being able to predictably excel and perform at the same point. And that's why one thing was distributed for scalability and a memory for predictable performance. Memory is a very, very predictable basis of how it's going to be used. And finally, and the one thing, it's not, each hour is kind of your own. You don't really have time to move data from multiple sources. I mean, if you want to process it manually. And so, it's just like when you see who are going past having to do an exam. So essentially, I'm going to talk about a lot of adults at the end. We're trying to create things that traditionally take 44 hours. When it's 24 hours, it'll seem like it's going to be one party, but seriously, four days. And so, it's an application that, yeah. So we're trying to take things that have to be taken 24 hours, playing with data, and either be able to do an ad-hoc or do an ad-hoc once a quarter of a time. And that's how much more we do really work. Yeah, you're doing it, and you're doing it, changing data meaning the, out of the data, you're doing it in a period at any time, sudden time. So you don't have to wait for the previous days, you're doing it in a period that you want. And what you're seeing is very, very much. So it's all kind of up to the user and how the person actually wants it. You can also try to track, transform the load. And basically, a generic process of getting data from multiple sources on the system. There's a whole industry around ETL. And so initially, we have a separate data industry, so it's actually a separate data industry and a local system on the data warehouse. And you use ETL, essentially to get data from one place to another. And you just have, you don't really have the, one area where I guess, for data that are to be able to ETL. And finally, it kind of, in that way, it's a great way to deliver the data that we've prepared for, like actually, by the gate center. So it's also a sign that you get a higher throughput and a lot of latency. And most importantly, at which was always. On this space, the first, with same kind of time and time again, you don't get flexibility. At certain times a day, on Amazon, for example, a PDX is having a bad day. You're working on the high speed. And depending on predictability, like those from memory and the transactional world is a very, very important. On the other side, in memory it enables you to access data as it is written. And another point that's very important to consider, and it's kind of the first thing we talk about, that's part of what we talk about, many analytics and memory, is obviously, I don't want all the data that I'm analyzing to sit in memory. And being able to kind of have a high throughput of more latency, maybe less, there will be a lot more data as it happens. For one solution that we're proposing, we're going to say for, is having a planner so that as well. And that's something that we can talk about in that, but essentially a planner format enables you to most likely be able to move between memory and the client. So, here's the place I'm going to show you the SQL. It's an email address for it. It's distributed. Here's kind of the basic picture of what it looks like. There's two tools called aggregators and leaves. Aggregators are kind of closer to where and where the cluster looks like. And you sort of play with aggregators. Under the hood, they put a couple of queries and then intermediate results create for leaves and then combine the final results together. Each week, they expose slices of data and processes on those slices, which is a little bit too much about the platform because it was distributed so far. And then SQL is a very quick and simple set of online D&L operations. Prevent things like taking point-of-time snapshots, scrolling across the algorithm, even up and through the wall. We enable you to do all of these things while you're both reading and writing to data. This is something that makes building a system a lot harder, but in the context of wanting to have a lot of flexibility and wanting to work on changing the results, it turns out to be very important for a system that's already in production. It also leads to a pain point with the system that I think helps to help with the technology. And finally, we made an investment in the end-of-class answers school. Now it is a lot of databases that have different interfaces. It's something about teaching tools and people don't. Signal is hard to build and it's quite complex, but it's usually so standard and it opens up a lot of doors so it has a database right up. So in this app, I'll make it over five big flybacks or a team of eight students in the school and then we'll take that and we'll be back in time. So the first one, which is pretty popular if we were to read about the system, is one of the two abstract values in a luxury checklist. Another really cool part of the SQL is that we do code generation to try to keep queries. The most important in memory system or durability and replication design is pretty different than a traditional disk space system. So some of the products around that are going to help us to build really efficient durability and replication. Most of the memory system is one of the really interesting topics. How we think about distributing at the same time and how we think about fast between distributing to someone and distributing query to people. So distributing query to people is a lot of fun. And we can jump over there in some kind of data exploration in the school for our long query jobs that people try to run. So I think people here are part of the SQL. Let's see, both are pretty cool. So that's pretty cool, it's pretty simple. There are a lot of useful events here. We've been here in London about 20 years before that. And roughly the same problem with the three. So one event I expected to look at is going to be. Then we have lots of room to build and kind of think about and read about in a balanced way. And this is the first one that applies to a lot of rehabilitation. So we can expect to look at the SQL SIPPOS indexes. There's a really big blog post on our website and this is kind of a paraphrasing of the information on the blog post. So I'm going to encourage you to get interested in a lot of quick signals to check out some of those. But this is one of the reasons we have teachers around why we choose SQL SIPPOS indexes. So one thing is SIPPOS are very, very, very optinized. Random access in any other role is very feasible. And SQL SIPPOS is still running on access to staff. That's because every role in a SIPPOS is good for people going to work. There's not a lot of kind of, we're obligated to engage one person immediately. Data storage, I have to deal with the desk. They don't have the money to run my SIPPOS so we have to build this extra loop. So this extra layer of interaction is in between all the buffer pool. So buffer pool has complexity and obviously access to performance as well. SIPPOS are very simple. So a new implementation for a lot of SIPPOS is in SIPPOS of about 1,500 lines of code. You can create a new implementation in SIPPOS to 100,000 lines of code. SIPPOS, those things are involved with it. Building a lot of SIPPOS is kind of a very active way of research. And here is the paper for Microsoft's SIPPOS, and here's the root space. You don't need to register your SIPPOS but again, any more complex type of data. So one of the really important things about investing in a fairly simple data package is that you can use your SIPPOS. And then people will be able to go from zero to a maximum and they can start out in there. And SIPPOS index is a major reason why we're able to do that. SIPPOS are, I can, not free. Not free means that this is going to always be a problem, no matter how the explicit, right, this is going to be. And here, building something that is making you go to print and work on retaining datasets, what's good is a good example property because it enables a lot of concurrency. SIPPOS are kind of, they're always going to be a simple, but anything that won't take from the SIPPOS, there are quite a few reflections on a lot of other data structures. And as a result, it's going to be really, really fast. And when I, SIPPOS isn't very flexible, one really interesting sort of innovation in SIPPOS is what we call the SIPLIST diagram. And what we do is we use the higher level powers of the SIPLIST as kind of an estimation of the incarnality of different filters. And if there's not really this problem, generally it's just over in database by maintaining SIPLIST over just a decent amount of data. And in SIPPOS, we can compute this really cheaply by the structure of the SIPLIST on the slide. So it's safe for us to go through the process and build the inexpensive SIPPOS. And multi-level concurrency. So the way that we do it in SIPPOS, every way that the SIPPOS is a lot more robust. And a lot more robust is just the rest of the region. So there's a lot more there.  It's quite a lot for you to all of you here on work. And then another really important thing to address in SIPPOS is a lot of comments and terms stand to present for why would you pick a SIPLIST index? As far as we know, we're the first commercial to actually really contain this system to actually offer SIPPOS indexes. So we do get a fair amount of SIPPOS. The first thing people ask about is memory overhead. SIPPOS are towers that you need to maintain. So the answer there is that the average SIPPOS tower is two. So the average overhead is about 16 bytes. So the 8 bytes per point are one point per tower. We also do this anti-trip where because we're totally aggregated every cable row, we get in line pointers to towers within the SIPLIST structure. In a commercial, if we came back into SIPPOS, you have to restore all of the towers and turn them here next. And we avoid that when we're in SIPPOS. SIPPOS has efficiency. I like to detail the data as it can be local. One of the traditional SIPLIST jumping pointers for every row. This is a very interesting concern because it does have SIPPOS. It turns out that for OLTP, SIPPOS is not as well used as for OLAP. In grouping and joining numbers, you have to have enough reference where you can get feedback from the performance by just asking for performance. Expensive execution performance is also very, very important. Again, standard performance, SIPPOS does not disappear when we do it. Every time we move along the SIPLIST, we shift to an effort-based system. That will do one important part. We use bashing reads, especially our garbage-like weights for non-overlaping read-and-write accounts to be able to improve that memory. By switching to the SIPPOS, we can see that we are able to do that. You know, that conversion in these early days is a more online type of RCU. It comes to the solution down into RISCAP, everything that you read. So, RISCAP, in two weeks' time, it turns out that you take a good amount of time on every, you know, if you want to do a RISCAP operation, you generally need to have a backwards point on your SIPLIST. And that's very, very low-free. I don't know if there are any papers right now about how to do a low-free, but it also increases your total memory over that number. So one of our engineers appeared on the way, it's helpful to scan a pointer and every time you need to go backwards. So the advertised product is still available, but it's about twice as low. So that still is a problem low enough. The most common mistakes for a RISCAP operation is really, like, give me the highest ten lightnings. In that case, there's no answer to both of those. And then you go back to the SIPLIST, which I know. So, if you were scanning backwards, you would keep a pointer here, here, and here. And then to visit this one, you would see, okay, I don't have anywhere up to here. I have a pointer here, so I'm going to go this way, and I'm going to go back from here, you need to go like this, like this, and like this. So the expected energy response is still available. And, you know, we were, you know, we didn't have this feature. So people would go running and it'd be cool to tell you that you could enter it forwards and backwards. So people would travel in queries and enter it forwards and backwards and then SIPLIST would easily run into this problem and try to get it through all of us. The answer was on SIPLIST, which is kind of where we ever had it. I also included the process of the SIPLIST solution to not be much simpler and hence much better. So that's kind of the basic idea of the SIPLIST. Again, they're very simple, very fast, and if you want to build a data that you can enter in the market and you're in a good position, it means you need to do it fast and you need to build something that works. So building a lot of SIPLIST is another technique that really matters to just a lot of people. In the database, where I listed this really major factor for performance, SIPLIST matters a lot as much. And the system where you're just getting a memory it really really starts to matter. And so we invested in point generation from day one basically which is kind of comparable to the difference between SIPLIST also and SIPLIST. And that's why we're interpreting according to what I'm not the pilot of. So there's a few areas where point generation really really helps. The first one is timeline standards. So in the SIPL, I will talk about this in a bit. We invested very heavily in using SIPLIST best efforts. As well as push things like massive functions and preventable crisis. We're into the definition of the SIPLIST. So pretty slowly, next row in a data structure is a different function at all. In SIPL, we can use the SIPLIST to file a depressive order down into any one of these operations as we innovate in the SIPLIST. The really common reason that you want to use point generation is to be aware that everyone is aware of what is expressed in the SIPLIST. So we see databases that say to do point generation make sense. It's the same reason that you want to use key systems that work by benefit, building a machine learning workload. One really interesting remark on point generation is we need a very, very powerful point cache. A point cache is something that takes a point screen or a 10-pointed point screen to an already compiled plan. And the reason this matters is that kind of the compiled query is very, very different from the SIPL, a simple tech query can see right from the 1 to 2 seconds to the file. So just having a wild application is really, really interesting. So we actually can invest a lot of engineering effort into identifying and prioritizing plans in such a way that many, many points will be in the same compiled plan. And try to do that point. I'm curious on the technique because we really benefit from all the key workloads that took a 50 to 200 unit price. But the data was not your workload or you want to set the risk to your environment that play with the data base. But the directs is pretty high. So in SIPL, point generation is putting into two big categories. One is growing and this is a bunch of headers which define what the SIPL is, the allocators, all the things that we need to be able to inline with respect to indexes. And the other one is the basic one. The pencil soon lets us do things like have arbitrary decimal points that are fully defined at the final time and that are no social dynamic overhead with respect to their size. Again, we really have to be investing in the SIPL's most complex to come to everything. It has its pros and cons. The pro is that it enables to build a lot of things on a very fast and a code that's compiled as a result is really pretty fast. The downside is that people who don't work so much on the performance of a completely complicated table. So, cogeneration in SIPL is really, really slow. And finally, to go over the basic model, each table we generate a value file. The value file includes the table definitions and a bunch of different functions that we can expose and ensure in one operation in the table. And other time is a best SIPL file. So, if you go in and download these SIPL files, you can actually look at what those files look like. In the last trick, you're going to build an opportunity to store people's costs. You should definitely look at the SIPL pre-compiled headers. Pre-compiled headers are essentially GCC will post their payment and essentially four of them will sell. So, it's actually between cost and state. It's fairly limited.  But I'm just going to tell you how many of these are included. They used to prove it of what this table tells me it looks like. So, to give you the idea this is a pretty single query I ran on my laptop. First time I ran it, it took 800 milliseconds. By the second time I ran it, it didn't require a useful laptop that ran immediately. I don't know what's in it, but this is just to give you an idea of what lots of people's SIPL files are going to make people look like. So, I ran it for ABC, I guess it's a little way. So, I ran it for GDF and I ran it for 100 million dollars. Generally, GDF is only about a lot of people access an email system they even have in the building. The answer is no, they don't do a building. It's running in an email system. It's not as important as a sign-off they will have in a display system. The most important one is we don't have to read through this error. So, we don't have to write things and we don't have really important costs of doing randomization results. So, we're designing around these write-offs and built-in doing-multi-design that we can do and we'll actually be out of this. So, the first thing is that the primary thing that we like to reduce is for the transaction log. That's three standard data from one interesting data so, the transaction log is just offering the primary two data. And the reason is as we read the transaction log we can reconstruct all the errors state of the indexes that we need. So, to introduce community and not to look kind of too past-long, relevant and against-price. So, the actual lines are very inefficient to report and the reason is in a transaction we need to learn a bit about. So, again, the pretty standard thing is to press a transaction log periodically into a snapshot. We need to see if we have a way to look at that transaction because we need to have a competitive computer and have three X-rays of long, three-statical database at that time. And of course, that happens when you're putting it in parallel. It's essentially the case of replaying from the most recent snapshot and then the remaining transaction logs to the overall state. So, this is a fairly different world of databases. Generally, if you write the style of your kind of nexus of disk, you can read them on-site. But in most people, we need to provide the guarantee of all the things that you really are safe to learn. And therefore, we have this problem. So, the conclusion is we've invested three times closer to a non-linear right. The transaction log is a basic differential pattern. The snapshot is a basic differential pattern for both reader writes. And the benefit is, the disk actually tends to keep up with the memory of one workflow. So, we just test how many people in the same place. So, we're going to put more transactions on the disk as well. So, going to the pattern to display state-based. Replication follows. We support boxed events and instrumentation. And answering this application, we have a transaction buffer in memory. And you can guarantee to have written to that transaction buffer in memory and we have a good point in the background that is how much transactions to do. It comes up in every solo conversation that we have. And the main reason that we have signature loading is to check off a checkbox for when to go ask a question. 100% of the questions are whether you signature a building. Including like a screen. And anybody that has data. As a result of using a signature of a building, you don't really end up with signature loading. You limit the ingest right into the system. And so you use data by not being able to ingest it right into the system. So you have to continuously discard data. With incrementability, you can kind of account for spikes that take advantage of the other values. And the number of transactions you can put through the system and capture density higher. That's all I have to say. I think that's what the SEPA performs. We can sacrifice that last 100% to a point that the average rated ingest to the best stages next slide. I don't know. I don't know how to call those words. I haven't looked at it for like three years. And replication, as we discover in the moment, is actually the most important building block to the disseminated system. We have to figure out a way of thinking about it. The answer is 100% next. We did not have replication. And then the release started three months after we had replication because it was such a pressing request. And everyone is running from replication. So replication is built directly on content durability. Essentially the master in the master in the master master. So the master screens start finding more files in the storage. And the slug is the same as the continuous recovery load. So it's exactly the same compact as the control on the C4 and the recovery is not found in the log. In this case, it's continuous recovery and it's possible to read or not like. And because replication is very simple, it's also very robust. So we built a 2012 release and then completely changed because this design worked very well. So one thing I did show aside is replication is actually being built back to possibly. For new data for redundancy, for cost data for replication, all of the things like you need to move around data after it's been created, both synchronous and asynchronous applications are in the cluster for you as I've already done it, but synchronous in different places. So our question was all in part as many as one of the others with pre-tune or deduction were in aggregators and leaves. Both tiers are available. So UCL needs to add capacity and compute to the cluster. And UCL aggregators to add is the network bandwidth that we can't use as a cluster. So UCL aggregators is able to do different sets of things. We support both inter-data and data center hybrid mobility. Before I start, I already was enterprise teacher at the age but these things really do matter a lot. So two kind of data center hybrid mobility, essentially you need to get a team of machine guys who will transparently replace that with non-data and non-data cluster. It's one match here and one it's like, and it's only exposed to views. So you get a different set of trade-offs using these two different features. Obviously you can use the future as you can use our intro data center that the patient request is and is of new wish. And other customers that do re-establish them. In general, our question is is there to stay out of the way? So there are systems that will automatically use different data and release data or do all the things we want to see into a cluster. Our design is not to do that. And that's based on people who would help with that which we'll talk about in a moment. In general, while we're doing question, we did a lot of research about the problem of non-data and non-data. And we discovered that the more automatic system as you would with your cluster, the worse the user experience would be and the lower the average performance would be. So let's come over some basic questions that we have. This is a basic setup with aggregators and leaves. We have a leaf pattern. So we have more than two or a parent, at least three and four or three. This means that they have the same set of predictions, half are massive and half are quads on different nodes. So it's very simple. But we, as guys, we just blow graphically on this graph. Anybody want to read from that? The flow of the time depends on the effect. If it fails because it's unreachable over the network, it's kind of immediate. If it fails because it's unreachable over the network, then we have a threshold that you can compare there. So the default turnout for a very basic measure actually only do a sort of 4 to 1 point per leaf. It will be a default time after that is 10 seconds. Depending on the weather and depending on the requirements out of the cluster, it will be good. In the same expected case it's going to be it. Our leader is a leader of product success. I'm thinking that's why if we want your caring as a way to strengthen our predictions, there are serious benefits especially for older people with why and when they vary. So we're going to visit that at the end. Any questions? We can turn it on automatically because we want to make sure that we have a good response potential which we'll do this for you. If you want to read this, I'll get to that later. Okay, that's kind of an innovation that we're going to do where it comes from. We don't do trade fairs. We do trade fairs. Yes, it's an awesome thing. We want to generalize it and make it more public outside of the data center. There's a different side of that after the data center. You don't ever want to have to take at least three or four different data centers. Some of you might be going to be three or four of you have fairly unpretentious performance and spend more than every day there is. So we've spent a spread of measures to see if it works really well. We've got a lot of these and a lot of people say across data centers we're going to provide where the nodes are doing the data center and we're waiting for the data center center to adopt. And that's why we do read, write, and that's what I'm going to do. This is what I'm going to do. So in the scenario, it's kind of the same that the latency between ads, leaf, water, and the fewer the closer the application ensures that the secondary cluster may really impact the performance of the primary cluster. And so one great scenario here is we have professionals in New York that are running like trading applications and those trading applications need to do the needed latency and it need to be really fast. But they have many analysts in Texas who also want access to all data in real time. And so what you can do with the secondary cluster in Texas is use this cross answer and do all the number trading in Texas on your secondary site without ever affecting the performance of the primary site. It will have the same number of positions but it doesn't have the same number of nodes nor does it have the same redundancy configuration. So again, we're going to have redundancy two replicating to redundancy one. But today is a tricky one because we're going to get us out of it. So the idea is if you're looking at the Texas in one aquarium in Texas you don't want it to ever use as you can use in New York. So you can even have a different kind of machine that may be better for an M.O.F. workload than it was for an O.T.K. workload and just engage those racial groups maybe in a multiple ways that you are running on a secondary site. The secondary site is always going to be the kind of work in your primary site. Either redundancy scenario or redundancy active. Which is this one. All of these four nodes and three nodes are active. Not because of replication and active-active, but because we have master positions on every node. And then people praise always one of these master positions. And so we don't have to think about those like a visual consistency because we always read and write to master positions. We just spread the master predictions so that every node and every CPU and every location scenario there is no master and master. So you tap right to the secondary site. Essentially there is no way for any action on the secondary site to affect the primary site other than obviously using something similar that works in the source as a way. So I think in the kind of the end-up topics that I want to cover in this part of the piece here. So the most important is actually what makes those your part of the pieces of the chart piece. So one of those databases is a very, very complex idea like between indexes and countless indexes. And it's part of that the users would sort of superkite us and sort of want to use indexes. You know, people all have a special part of the index called the chart key. And the idea of the chart key is any index is not only to affect the site but at least one of them is in the chart key. And in two ways with the same value of the chart key are guaranteed to be on the same value. And you can use this property to keep up with doing and drawing operations. So basically you make a trade-off around how you want to distribute data and based on what you select for your art piece, you're required to be slower and people are required to be faster. In terms of innovation, the index is between every years and weeks as a single. So weeks are actually what we call which has been originally also a very super product. And so that the people is very similar to my people as I've said, it's it's very similar to my memory, et cetera. And these are just working in a city where we don't know what the question looks like. And the other way to keep people to the leaves is to keep people with their local data set and the chart you're doing yourselves. In secret between those as opposed to the standard of innovation, like sterilizing operator free and sending across the network is important because it's a very large entity. So in a single, you can write explaining on that paragraph what's going on in the editor and see exactly what it's doing on the leaves and going entirely to those results. And the interesting thing for them is that any operator free can be expressed with a small amount of data. In terms of what we can express in order in this slide. In fact, we have this clinic in the engine for free SQL. So just like we can take that as free from an operator free in the SQL plus we can also generate the SQL. In the sense, again, what kind of a building block for how our engineers own this community. We pass the query on the aggregator we're going to pre-proceed into what we want around the leaves and then we just run two SQL on pieces of the tree and send those SQL queries to the leaves. It's also a great primitive value that's going to be a useful tool in general. We have some of the parts that are going to impact the SQL. If you mention that one of the key investors of the main operator was to SQL, first of all, we can look at SQL to SQL tree transformers and kind of validate correctness. So if you do all the knowledge that we have I highly recommend investing in SQL and then in terms of joins there's sort of two techniques that we exposed. One is called reference tables. It's particularly for running a broadcast join because we're going to take a smaller side of a join and send it to the entire table to the partner. A reference table is kind of a pre-broadcast joinable table. So it's a small table. These are usually less than 100,000 rows and that kind of dimensionally would mean we want to be present in full on every day. And they're very cheap and available for running any kind of on-the-carry join. And the other thing that we exposed is called a forward-shark key. The forward-shark key essentially lets you define the same type key in two-fold tables. And if you join exactly on that index then join is particularly vocal to band-aid and there's no network traffic that possibly needs to be integrated. So forward-shark key joins are usually for use cases like in TBC of orders and one-hands where you can co-locate a order with other one-hands and still get some amazing starting properties of putting one-hands across the cluster and not have to reshuffle that table every time you run a join. So this kind of example query will just let camp start. It's a pretty simple query. In fact, all we do on the index table to complete this query is let's let camp start on what we put this line and just sell these results together. I think we're going to get to work on what's in there. And finally, I'd like to mention that when we looked at these really long-running SQL workloads that take like two hours the simple model that we have with reference tables and flow showcase starts right down. If you're building a web application then reference tables and flow sectors have been completely covered. You can express pretty much any application available performance with these techniques. But if you're doing more complex on a little bit of data exploration you need to be able to shuffle a table across the cluster. So only investing in over the next six months and going forward is to learn cool new projects in the execution of the last half of the legacy space. So one thing that we're building right now and finally this is being built by some of these students is the SQL Blaster Shuffling project is entirely taking place. We're building the ability to express and reshuffle our operations across the cluster within our model of sending people from MVAs to leads. And so we've got this primitive code arranged and we've disclosed the results of the SQL query as a discriminative test data. So this is an example of a simple bootback that we've been mailing to shuffle to complete. Generally, you want to shuffle bootby queries for very, very high probability. So listen back to this rationale which is for like and this right there. There are more tables where you extract a result of your simple queries and the end result is basically going in an only pool to get an average for the specific shard data that you're looking at. With these two queries you can express all the reshuffling that you need to be able to do the standard to meet and shuffle going and shuffle bootbyes, finding the introduction of all of the antennas and your discriminative query execution techniques. The other thing that we're investing a lot in is an optimizer. As of now, an optimizer is very good at simple heuristics. Very good at complex optimizations to a node. Very good at index selection and azure ordering on a single node. That is no concept that's intuitive. The next major project right now is really pursuing a possible optimization. And the other really good project and it's been an engaging movement where we have today is we don't want to have a line on the standard SQL to SQL transporters. So that's the thing that's being reached into the face. There's like subparings in correlation and tonsil folding of expected and all of these kinds of transporters. This way every database and remember unfortunately I'm talking to a lot of database people basically starting with the transaction of these pre-transporters and going for that. Now you can pass these cross-transporations as well. A lot of the pre-transporations are subparity defilations. You just always want to do it. Or changes are like an in-subparity to a subparity to a tree. There's certainly a lot of that too because you're a little bit of a flexibility in executing a play. Only then you want to do something out of the companies. The one thing I'm actually right now is not cross-transporters but we will do that at least. You can have a table and the other thing is your next selection. So you can have a table with cross A and B and I'm going to give that to you on these columns and maybe a query which starts with a cross A and B and X will be your next. We actually have a week to generate this into the plan and because it's a quick question we can do a quick check on the other columns which the index would be more effective based on the queries on the query. That's a great question. The question was how do we kind of straddle between queries that run in memory and queries that we can do that between memory and disk? We're actually talking about this right before the top. What we do right now is this real story is in memory. So real story data must run in memory and if you try to go past the capacity in memory what do you do in memory? You can't write any more data from this real story than in memory. The plan store transparently is moving data between memory and disk. And right now the way that we expose the distinction between the real story table where I want this to be conversory level we don't transcribe new data between these two stories. And the reason we do this is we want to get the market with what we can produce so we can see what customers are interested in. So we're trying to find out who are used to data plans like that. But the things on the record capacity is almost always the driving factor for customer enforcement decisions almost always the driving factor of the welfare system. And the reason there's once you enable people to write home this data and tell them it's real and it's one of the people that are not used to the idea of the fact that they're running a biome's memory in the system. So the principle of data planning is really trying to find the continuity and then continually kind of struggle with the fact that they're running the biome's memory in the system. It's very fun to do that right. And so it's fascinating that in any of these systems there are really, really important problems. So it's like the simplest we've shown where the power for data directly in the system be able to see that there's one allocation per row. And so we've put a lot of memory effort into like parts throughout the inventory to reduce the memory over that per row. So literally some of the typical communities are things to think about after the talk. In memory, a lot of the new kind of work was almost ready to be called possible. So any able to do things like having an application running on a database and putting it in at the same time to keep designing or architecting a system you've never do before. But now these things are so much possible and they're constantly pushing the bounds of what people thought were possible and what people thought were as possible. And the thing about taking real problems and taking measures is about applying new solutions. And then doing booleans is a way to keep crystals out ways of looking at this where they're still doing booleans. We still have to straight out and figure out what the solution is. But because we're already reading out the disk we won't be right to the distance completely different than on the databases and it's up to different ways. So we kind of have a call out open to our new data structures but I'm still surprised with the boolean and the SQL that we were put a lot from kind of to show programming. These people come in and they kind of apply the techniques in different areas of the engine because this is probably not a lot of work that we've done yet that would be kind of tryouts available in SQL. And then storage is sort of completely different than we did before. There's all kinds of new solutions there and it's new tryouts. These are things that tend to be the kind of platform where everybody is saying what you think is based on the set of tryouts that you're out there looking for. But these components and these tryouts come out into very good components and a specific set of workloads. So when we try to change the world of these systems will completely change this. And finally, we're obviously hiring and so I'm interested in talking about projects in SQL around SQL today and what we're going to be able to talk about. And so I'll be there if you still will be there in two or three years we'll continue moving there as well. But I think we're out of time, but I do want to discuss something. I know many of you are crossing. We don't. We do handle and we take on a focus. The reason is in the storage format that's much, much, much more likely to have some sort of core-core barrier. We tend to not have this problem. And if we do we only just work just a little bit this is because I can pretty tell in practice that it is involved more than just in SQL. It's a rare enough resource and solved enough by checking all these here that we like to disk and start with the engineering or performance of what I said earlier. For in SQL, what we do is kind of teach them. At the screens that we are in the way that we think about some problems we look at the issues that are really running for stores at the time that we have them or we sell more of them. The largest questions that we have are the comments and notes. Whereas Google is dealing with like hundreds of thousands of notes. So the average question size for in SQL is more than 10 notes. And then there's a question of what's in your clusters. And that's a problem that we have to invest in. And that's what we've done in other cities. We've also dealt with SQL and other related databases like Renaissance and White. I will answer this question on this slide. What are these features present in other digital databases? So, essentially we've been investing very significantly in performance, usability, strong learning and following the key for a great optimization. Key for white is kind of designed to be a menu, but it's not even available to people who might not like to. What is, doesn't let you address the question areas. But it's also a movement of scalability. So, when it comes to 10 notes to come up, outside of a very difficult competition. So, it's most of you are thinking about how to respond to that. It's very straightforward for us to come up against. That's the kind of suggestion that we need to try out.


Good morning, Canada. Squadron reel, Canada. It's a very exciting day, not because there's anything particularly exciting going on, but just because I say so. What do you mean? True. There's totally exciting things going on today. True. I think we're going to work on part of the subfloor today and we're going to try and get the window in. That's exciting. Because we don't have a... Because we're outdoors, we've basically been doing musical chairs with all of our equipment, so when you do a build, try and find something that has a place for all your stuff with no rain. In other words, don't do it outside in Alberta, Canada. Also, a side note, after a couple weeks of being sick, I finally feel absolutely 100% cleaning up the floors. And we're prepping for subfloors. We're using this stuff. Seven Gray used a stuff called Ice Shield. We're using Henry's brand something. Basically, the last bus I had, the sound insulation was very expensive. This whole roll, I think I mentioned it to you before. I got a deal. If not, it was funny. You should replay that video. 50 bucks. So we're just going to put it down. Mike's never used it before. What are your initial thoughts on it? It seems like the sound-freaking stuff I've used previously, it's pretty darn close for the cost, so I'm assuming it's going to work. Mike, by the way, didn't use sound insulation like this, but because of the density and thickness of floors and subfloors and having a different bus, this bus the engine is in front, so it's not as noisy as my previous bus. His bus is super quiet, but he also has a different engine and all kinds of freight liner, so I'm thinking about a freight liner on the next bus. Oh geez, he's already talking about the next one, huh? Isn't that weird? I always do that. Even on my first one, I'm like, yeah, I wonder what the next one's going to be. It's kind of like, I don't know, boys in their toys. Anyways, enough of you happen. Let's get to work. Tiki, once you fold it, here, let's see the other side. Once you fold it over, you can't get it out. So, when you're doing the wheel wise, this is our technique. I'm just going to cut another one and fill it in. But how cool is this stuff, huh? It feels interesting, right? It feels like it should work. So this is an ice shield. This is Henry's product, and it's a water barrier for the walls. Now, let's, here we go. Here's a real test, right? Here's without. Here's with. Yeah, a little different, right? So, I don't know. Whether it works or not, it's worth a 50 bucks or not. It's up to you. It's up to us. It's really subjective. Without any instrument tools, we have no measurement. It should work in theory. A little bit, right? Yeah, it should work. I mean, 50 bucks for 200 square feet, that's pretty cheap. I made a mistake. We have now demonstrated the wrong way to put this stuff on. Do not cut the whole length. We got it creased. We're going to do four to eight foot chunks. It's very tricky. Because putting this stuff on, you're just asking for trouble. This is a tutorial for yours, too. Yes. So let's roll out the next one. Okay. All right, so what do you think? Here is what this, I don't even know what to call it. I'm just going to call it noise control, right? Here's what the noise control, this particular product, as you can see, it's right there. I was looking for ice shield. They didn't have it in Canada, whatever. But as you can see, it has a whole different, even though it's very echoey up here, it has a whole different sound because it's there, right? It's all adhered. What are your thoughts on this stuff? It's definitely not the expensive stuff you can get, but for the cost, I'm thinking at the moment, it's worth the cost savings in terms of how many decibels are less made for cost. I mean, what did you get? This is like, well, you got for 50. Well, let's just say even the regular price stuff that's like 150 or whatever is one-tenth. One-tenth of cost, if you got like Dynamat Extreme Pro or whatever the heck that stuff's called, right? Because it's like special audio acoustic stuff. This is like a knockoff that's not exactly the same material, but one-tenth of cost, I happen to get 60% off just because it was like a trash roll. You can see it looks like, I don't know, some chipmunks ate it or something, right? But for the money, I mean, why not, right? For the money, it seems like it's going to do what you want and get the decibels down for you.  Yeah. And if it does absolutely nothing, or even just a little bit, it's 50 bucks. 50 bucks. It's not going to, if anything, it's a good waterproof barrier. It's one of the things, so here's the thing with the bus, right? Like, it's one of the things you can't upgrade.  You either do it in the very beginning or you don't do it at all. But anyways, what are we about to do? We're going to water test the bus and make sure that every single window and seal is solid so then we can then start putting it in our wood. All right, let's get to work. Yeah. Lake testing the bus. We're looking for any issues. This was an issue, but we'll probably get that with more silicone. No big deal on that one. It's mimicking, driving in the rain. It's coming through the rivet itself.  Then that will be new. Anything else looks pretty good. These are the deck supports. There's nothing coming in here yet. So let's say so far, so good. This is back. Yeah. Bad chat the morning off. It was taking a little vacation. It's not really off. You're good. So now we're just going on the outside of the bus. Mike's spraying it. Yeah. Yeah. There's a little gap in there. You're good. That one's leaking. Oh, yeah. So we got a little leak there. Isn't that fun to see leaking before it puddles up after you're building? No. That's just a little, could be a gasket issue or who knows. Actually bad. Oh wait, no, that's not the problem. Yeah, minor. You're good. It's mostly, oh wait. Look at that leak right there. Look at that leak right there. So you know what we do with that leak? Let me just put a little mark on it. That's a big one. That's a good one. Yeah. That's a pretty big leak. Big leak. Got a big one here. Okay. That's a big one right there. Yeah. Yeah. All right, now we're moving on to this one. We got lots and lots and lots of caulking on that. I don't think it should be leaking. Let's just make sure you look up. You look over. Okay. Mike. Yes. Do you know the moral of the story? I'm pretty sure they call it leaks. My God, almost every single one of these things was leaking. And that's fine. So ladies and gentlemen, I don't know if Mike would agree with me or not, but I would recommend heavily caulking all of the windows. I would recommend that if your bus is organ like an 07, to most likely re-caulking windows, because this is what happens. Yeah. This is even after re-caulking. So I think, I'm not a pro, but the way these windows are made, there's like a little gap in between the metal and the outside.  What do you say? So you get the rims where we re-caulked, then you actually have the metal inside. Yeah, the actual window frame. So I was hoping that your windows were better shaped than it seems like they are. By the way, no caulking came from the part that we installed, which was like the part where it meets. It was in these corners. It was only the corners. And back here, if you see, well, guess what? We got a leak. And that is an old leak coming down there. That thing's been leaking for centuries. So it is a manufactured defect. Well, it's just, over time, they don't build these things the last for us to re-purpose them into homes. They build them to last for, you know, 10, 15 years. Yeah, this guy knows what he's talking about. It's absolutely correct.


This study uses field data and satellite imagery to model lichen cover for a 583,200 square kilometers area that encompasses nine Karibu ranges in interior Alaska and Yukon. The researchers found that Karibu avoided lichen poor areas and showed stronger selection as lichen cover increased. They created a landscape scale map of lichen cover that incorporates extensive field data for model training and validation, which will be useful for understanding trends in lichen abundance and distribution, as well as for Karibu research, management and conservation. This article was authored by Matthew J. McCander, Eric C. Palm, Gerald V. Frost and others.


Now, we're in chapter 9 here in the gospel of Mark. We're going to be looking today at verses 14 through 29. I chose to entitle this particular installment of our Bible study, Help My Unbelief. Many years ago, I can't even tell you how long ago, it's been quite a number of years. Over 40 years ago, there's a comment that is made, and we'll be seeing that in just a moment in verse 24 here of chapter 9, where the Father cries out with tears to the Lord Jesus Christ. And he said, Lord, I believe, and I memorized it in the King James Version. He said, Lord, I believe, help thou mine unbelief. And so we're going to be looking today at that cry of the Father, Help My Unbelief. That's a cry I believe that many fathers in this place today watching online. It's a cry that many of us who are fathers might have made ourselves in the past.  We'll be looking at verses 14 through 16, and then I'm going to lay a foundation and introduction. I want to stress in my introduction about the importance of faith and things that relate to it so I can lay this for us as we get to the point where the man is saying, I do believe, but it's unbelief I'm dealing with. And that's something that I believe is a very, very common phrase that many believers might be able to make themselves. And so we're looking at the subject of this man's unbelief. So let's begin reading together here in chapter 9 of Mark's Gospel. At verse 14, we'll read to verse 16, and then we'll get into our study. Mark chapter 9, beginning at verse 14, reading to verse 16. Mark writes, when he came to the disciples, he saw a great multitude around them and scribes disputing with them. Immediately when they saw him, all the people were greatly amazed and running to him, greeted him, and he asked the scribes, what are you discussing with them? Now I mentioned recently that there are various ways that Christians are referred to in the New Testament. We have a tendency of speaking of us now simply as being believers or Christians. We especially say, well, that person's a Christian. I was mentioning that there are various ways that Christians are referred to in the New Testament, and I was sharing with you that the most common word in Scripture to refer to a Christian was the word disciple, and we spoke of that. The word Christian was not necessarily commonly used to speak of followers of Jesus. Even believers or Christians were simply referred to as the church, and that term, the church is used in the New Testament around 114 times. So that was a very common way to speak of believers, a community or fellowship of those who have committed themselves to Christ. And so believers are referred to as the church and are called Christians, but even as I just said, they are often referred to as simply believers because that's how we were saved. We believe in the Lord Jesus Christ, and that's how you're saved. Acts records that when Paul and Silas were jailed in the city of Philippi in northern Greece that they had been jailed because he had cast out a demon from a fortune teller, and when that happened that provoked a near riot. While in jail Paul and Silas were praying and the Scripture says they were singing hymns and the other prisoners were listening. At midnight there was an earthquake and the prison doors were opened. Well when that happens the jailer awoke and he saw the cell doors were opened and he thought the prisoners undoubtedly had all escaped and was about to kill himself.  But when he was about to kill himself Paul said, we are here, don't harm yourself. Well this jailer was so amazed that he said, sirs what must I do to be saved? And that's where Acts 1631 all of us have heard this Scripture. They said believe on the Lord Jesus Christ and you'll be saved you and your household. Believe on the Lord Jesus Christ and you shall be saved. Believers are what we are to be but believers is a common way to speak of us. This is because we are known by whom we believe in and what we believe and believers are those who have trusted in Jesus Christ and have become part of the Christian community. In John's Gospel John records that after Jesus' resurrection that Jesus appeared to some of the disciples and Thomas wasn't present when he did and he didn't believe when they told him that Jesus had appeared. In John 20 verse 25 the second portion of that Scripture he said to them unless I see the nail marks in his hand put my finger where the nails were put my hand into his side I will not believe. Well a week later Thomas was with the apostles when Jesus came and he stood amongst them and he said to Thomas touch me see that it is me and stop doubting he said and believe. In response to this Thomas said my Lord and my God and then John 20 verse 29 Jesus told him because you have seen me you have believed blessed are those who have not seen and yet have believed. Now there's an old saying all of us are familiar with seeing is believing but in Christianity believing is seen. This is because as believers we live a life that is built on faith. We believe in God we believe in Jesus we believe in the Holy Spirit all of whom we haven't seen the whole foundation of our lives is built on faith in God and what he has said. In 2 Corinthians chapter 5 verse 7 Paul said that we walk by faith. Peter said in 1 Peter chapter 1 though you have not seen him you love him even though you do not see him now you believe in him and are filled with an inexpressible and glorious joy. And so this is a subject of belief we're going to be looking at at a father in a moment who says I believe but I'm having a problem with unbelief. You see at this point Jesus has been with his disciples for over two years they've been with him they were taught by him they've seen his miracles they served with him but he's about to depart he's finalizing his ministry to them they'll they'll soon be entrusted to take the message of the gospel not just to Jerusalem or Judea or Samaria but unto the uttermost parts of the earth and he's no longer going to be with them and they're going to have their world rocked because Jesus is going to die they have critical things to learn from him especially in the realm of faith and what he's going to be teaching them in just a moment once again is a lesson concerning the power of faith. And so it begins at verse 14 in this way when he came to the disciples he saw a great multitude around them and scribes disputing with them. Now remember with me that Jesus had camped overnight in the mountain Peter James and John had been with him. Luke chapter 9 verse 37 says the next day he descended the mountain and rejoined his other disciples as he's descending this mountain there's a great multitude that has formed below and now as we see it his men are surrounded by a crowd and religious experts are called the scribes are arguing with them. Now as is so often true mountaintop experiences are often followed by valleys it seems to me that the enemy likes to stir up problems after God blesses us. We used to go to our men's retreats and perhaps in the future when everything flows again we'll do it again but we used to go to a mountain for our men's retreat and I would tell the guys I would say okay guys we're about to go home you've been in the mountain and the Lord has met you in a mountaintop experience. I said but don't be surprised when you leave the mountain you go back down don't be surprised if the devil begins to attack you sometimes he's wearing your wife's dress just kidding I see those claws I'm just kidding but the fact is we need to take our mountaintop experiences and put them into practice when we're in the valleys and that's what the Lord is going to teach these men because the lessons that are learned on mountains are lived in valleys. Jesus arrives as he arrives there's a multitude but notice with me there are also those who are called scribes arguing with him the scribes were the experts of the law of Moses and they were the ones who pronounced doctrine and teaching and all very respected and there they are arguing with his men now these religious leaders were often looking for something to discredit Jesus with and in Luke chapter 11 verses 53 and 54 Luke writes as he said these things to them the scribes and the Pharisees began to assail him vehemently and to cross examine him about many things lying in wait for him and seeking to catch him in something he might say that they might accuse him well since Jesus wasn't there they took opportunity to argue with this men and they would do that because they wanted to undermine these men's trust in Jesus Christ as we saw in an earlier passage we saw this happening in Matthew at Matthew's house when Jesus had gone there for supper Matthew had invited his friends who were tax collectors and sinners and this bothered these religious leaders in Matthew 9 verse 11 it says when the Pharisees saw it they said to his disciples why does your teacher eat with tax collectors and sinners so this is an old tactic if you can't defeat the teacher undermine his students trust in him in Mark 3 25 it says if a house is divided against itself that house cannot stand so this is a common tactic Jesus isn't there so the scribes begin to argue with Jesus as men the nine who had remained behind well in verse 15 it says immediately when they saw him all the people were greatly amazed and running to him greeted him when Jesus arrived on the scene the people saw him they came and greeted him and this has become common because of his amazing works and his teachings but as they're greeting him Jesus immediately approaches the scribes in verse 16 it says he asked the scribes what are you discussing with them now that word discussing is a Greek word that means to debate or argue they weren't just having a conversation they were arguing disputing they were causing problems with his men and so Jesus as a shepherd immediately protects his disciples from the onslaught of these religious leaders your bible teaches you that that Jesus is the good shepherd and as a good shepherd he watches over his sheep in Psalm 91 14 it says because he loves me says the Lord I will rescue him I will protect him for he acknowledges my name in Psalm 121 verse 8 the Lord keeps watch over you as you come and go both now and forever he's a good shepherd watching his sheep and so his question reveals to us that he takes the tax on his disciples very personally now we see an example of this when when Jesus confronted Saul before he became Paul I was mentioning this to you recently this man Saul who later is the apostle Paul Saul had received authority to bring believers to Jerusalem that he might try them as religious heretics and he was on his way to a place called Damascus and the bible tells us in Acts 9 3 through 5 as he journeyed he came near Damascus and suddenly a light shone around him from heaven and he fell to the ground and heard a voice saying to him Saul Saul why are you persecuting me he said who are you Lord the Lord said I am Jesus whom you are persecuting it's hard for you to kick against the goats when you're hurting one of mine Jesus was saying you are attacking me he takes it personally he took it personally then by the way he still does to this day these religious leaders were undermining their faith provoking Jesus to action in Matthew 18 verse 6 he said whoever causes one of these little ones who believe in me to sin it would be better for him if a millstone were hung around his neck and he was drowned in the depth of the sea when you go to Israel we have an opportunity to go to a place called Capernaum and while you're in Capernaum there is a millstone that's on display there it weighs several hundred pounds it looks like a a large wheel and that was the picture Christ was giving he said it would be better for you if this several hundred pound stone was tied around your neck and you were dropped in the midst of the sea of Galilee for offending one of these little ones who believe in me he takes it personally and so Jesus challenged the scribes to answer but they didn't have a chance to response notice what happens in verse 17 he had just said what are you discussing with them then when in the crowd answered and said teacher I brought you my son who has a mute spirit wherever it seizes him it throws him down he foams at the mouth he gnashes his teeth he becomes rigid I spoke to your disciples they could not cast it out to cast it up but they could not and so he answered him and said oh faithless generation how long shall I be with you how long shall I bear with you bring him here now I want you to notice something here Jesus had challenged the scribes but they didn't have a chance to respond because someone from the crowd cried out I brought you my son so when you combine other accounts of this event we get a better picture again Matthew 17 verses 14 15 speaking of the same thing Matthew writes when they had come to the multitude a man came to him kneeling down to him and saying Lord have mercy on my son for he's an epileptic and suffers severely for he often falls into the fire and often into the water the word epileptic is actually word that is translated moonstruck it also could be translated lunatic it was not specifically the disease of epilepsy but the symptoms of it that are being described here but he's falling into the fire and often into the water in Luke 9 38 suddenly a man from the multitude cried out saying teacher I implore you look at my son for he is my only my only child and so that adds a layer of emotion for us this father's frantic he knows that this isn't simply physical he knows that what's taking place is spiritual he knew his son was demon possessed and was under incredible attack by demons in Luke 9 39 it says the spirit seizes him and suddenly he suddenly screams it throws him into convulsions so that he foams at the mouth it scarcely ever leaves him and is destroying him that word destroying literally means crushing or mollying him he's abusing him is what he's saying this is what has taken place Matthew 17 15 again says he often falls into the fire and often into the water so the demon is abusing this little boy driving him to kill himself and in the hurting of the son there's a hurting of the father because any man who has a son and loves his son if something happens to the son it's something that guess it hurts and affects the father we're very protective i'm going to talk to you as a father for a moment i'm going to share some things but i can tell you this that i have two sons my biological boys and i can tell you that they're men now they're not children in any way except emotionally no they're not they're not children anymore but i can speak to you and this to me is a highly personal highly personal passage because i began to learn this in layers many years ago prior to being saved having small sons and being where i am now so i've learned layers of things as i've gone through this particular passage many times in the years that i've i've ministered and been a believer and i can tell you that you have a very protective feeling for your son and when your son gets hurt in any way it hurts you i still remember when my daughter Corinne came running into the house Corinne was just a few years old she wasn't that old my son joseph was maybe four years three or four years old at the time and she came running into the house and she said daddy daddy the next door neighbor just hit joseph and the next door neighbor was in high school and hit him in the stomach and my son was about four years old and i went out like a lion i have to be honest with you i was going to kill that kid and i was going to take his father too i mean i was saying i'm telling you the truth marie can tell you that you know so i understand when you see your child hurt you know i talked to the mother settled the problem god was very gracious kept his father didn't come out because i was really going to take him out i'm not kidding because the guy had been acting the punk for a long time but that's a different story i shouldn't even shouldn't even bring that up pastor dave you had a temperate well that was many years ago you get protective every daddy knows this you get protective that's my baby that's my baby you get protective it's just there if you don't get protective ask that god will give you a heart for protection for your kids you get it's natural it's something god builds into a man that's the way it is and when my child's hurt i get hurt when i can't do something i get hurt i want to take that on myself i want to do something and that's what the father's feeling i want to build this with you because that's what's going on right now with this man my father the father's saying my son is very ill he gets thrown into the into the fire he gets thrown into the water he convulses and and when you start looking at all of the things and i read this to you but i'm going to point them out again you'll see what's going on because there's a situation taking place and and it's something that is is beyond their ability to to handle these men can't do it when when peter james and john were on a mountain these men these others were involved in warfare and their lack of success reveals that they're still unprepared to handle this kind of attack you see when people think that that's serving satan is good this is how satan treats his subjects and i want you to see this look at how the demon abuses this little guy the spirit makes him mute robbing his speech so he can't call for help it seizes him which speaks of eagerly taking him and possessing him it hurls him to the ground which causes bruising and cutting he foams at the mouth which causes dehydration he gnashes his teeth he's grating his teeth causing bruising of his mouth and his gums his body becomes rigid the word rigid speaks of being withered or dried up causing cramps he suddenly screams because he senses the demon shrieks and there's nothing the father can do it causes violent convulsions causing him to choke on his own saliva it scarcely ever leaves him which means he's hurt and tortured night and day he's he's he's got a sense of isolation because he's looked at as being a lunatic and he has no friends he throws him in the water to drown him the fire to burn him tries to kill him the fire burns him and because the fire has burned this little guy's skin he may very well have become scarred this is my son shrieks isolated in pain possibly scarred bruised gums teeth that have being are being worn down by his grating constant gnashing isolate no friends nothing listen i i spoke to your disciples that they should cast them out but they could not i brought my boy to you but you were on the mountain so i brought them to your men but they couldn't help him and jesus has answered verse 19 it's interesting because he says oh faithless generation how long shall i be with you how long shall i bear with you bring him to me he answered faithless generation the word faithless is unbelieving that's what the word means it means those who are not trusting god interestingly enough he's not primarily rebuking the crowd he's speaking first and foremost to his men his disciples their unbelief actually causes him anger and is frustrating and even painful to him this is really what would be called an expression of exasperation and he's exasperated frustrated with his men remember he had sent them into ministry he had already in chapter six sent them out to minister it says that they had in verse 13 of mark 6 they had cast out many demons anointed with oil many who were sick and healed them they had already cast demons out this is something done they had done they they they failed this time but they done it in the past and so he says how long shall i bear with you how long must i put up with your lack of faith why are you not learning the lessons i've been teaching you and then in verse 19 he gives a command a simple command bring him to me well it says in verse 20 they brought him to him and when he saw him immediately the spirit convulsed him and he fell on the ground wallowed foaming at the mouth he asked the father how long has this been happening to him he said from childhood and often he's thrown him both into the fire and into the water to destroy him but if you can do anything have compassion on us and help us jesus said to him if you can believe all things are possible to him who believes and immediately the father of the child cried out and said with tears lord i believe help my unbelief this is the part where i can get emotional i know you've never seen that here these this is one of those portions of scripture that i've been aware of for a long time i've been aware of this scripture for over 50 plus years now when you're young and the lord i was unmarried you you read it in one way and you highlight certain things as you grow older your life continues to blossom various experiences occur you get married you have your children things of that nature ultimately for me you your grandchildren and and so layers of experience begin to occur as you grow older in the lord so there are levels that i've personally seen the lord do things in my own life and so because of that it's i have emotion that's attached to that so i'm going to try my best not to make this about any emotion you might see come out of me hopefully it'll make some sense to you as i'm trying to share these things i want you to notice in verse 20 they brought him to him and immediately the spirit begins to tear on him convulsed him begins to tear him the the bible tells us here that the spirit convulsed him and he felt the ground the spirit within the boy recognized jesus and knew what was about to take place so when he saw jesus he tore the boy he convulsed him now we saw this kind of thing when jesus had cast out a demon of a man in a man in a synagogue in mark 126 it says when the unclean spirit convulsed him and cried out with the loud voice he came out of him well the boy fell on the ground he began to wallow he was foaming at the mouth and the spirit made one more effort to destroy this boy he'd been tormenting him for some time he didn't want to let him go as this is taking place and you can imagine i mean this taking place of father's watching his son and jesus begins to speak verse 21 how long has this been happening to him he said from childhood now he's calmly speaking to the father how long has this been happening this wasn't a way to gather information it was a way to communicate compassion jesus cared about the pain the father endured he knew that that man needed to unload how long how long and the father said from childhood that word childhood can be translated from boyhood but it's also word that can be used to speak of infancy this has been taking place all of his young life since he was an infant he's been in this condition it's often throwing him into the fire into the water to destroy to kill him and so this is where it becomes personal for me i put myself in this father's place he's desperate he's desiring more than anything that jesus would deliver his tormented son put yourself in that place if you're a father for years you haven't had peace your only son is suicidal driven by a demon my first born was a little girl whom i love with all of my heart my karin my second born was my son david we didn't know we weren't we weren't going and finding out is it male or female or anything like people do today oh we know the sex and then you have those reveals we didn't do that we just kind of wanted to just let nature have its course in boy girl and that's the way we did it now i'm kind of a traditional person in a lot of ways and one of those things about being a traditional person is i wanted a son to carry on my name maybe he'd do a better job with it right so marina we're talking my wife and who do you want to name the baby if it's a boy i said erin erin is my favorite name i love the name erin it's a beautiful name she said don't you want to name him david i said i'm not really in love with that name seriously i it's just yeah i'm gonna name him erin she said you want to call him david mentally and i said okay we'll call him erin david that was it was settled it was settled right we're gonna have erin david that's what we're gonna have and so there i am captive when marie's having the baby they force us now to be in there and i'm just waiting for whatever and the doctor says you had your boy and hands me this little boy what are you gonna name him david and that's how he got his name david erin david erin when my joseph was born my second son and the doctor delivered all four of our babies same doctor he walks up and he hands me this little baby my joseph it's the only time that i ever felt this impulse but i he handed me my my son and i looked at him and i lifted him like this and i said this one shall serve the lord this one shall serve the lord i prophesied over my son there is something every daddy has this there are dreams that you have this one shall be blessed have i got to bless you that's how i am i've been that way for a long time that's not unusual this man was the same way i'm sure when he was born he blessed god you gave me a son my my only child you gave me a son and i deeply i deeply love this this baby and you have your hopes and you have your dreams one day may this this this boy grow to be a great man but since he was very young in this man's life his dream became a nightmare and his hope was lost you are forced to watch him constantly because he may kill himself if not on the alert you look at him and and this beautiful little guy is scarred he's been tortured he screams constantly he falls he hurts himself he can't go near water and he can't go near an open fire his mouth his gums are bruised he has no friends who wants to play with a little crazy boy right who wants to play with him so he's alone and sometimes you're outside and the other children in the village are running by and they'll they're laughing and they're playing and running but your son can't join them he can't run he can't play he doesn't laugh he shrieks he's alone and it hurts it hurts your son but it hurts you because he's your only baby and the hopelessness that you live with is overwhelmed you and then one day you hear you hear of a young rabbi a man named Jesus and you heard this is a man who casts out demons and you summon everything within you and and you come to see him but he's not there you're told that he's got some men that he's training they're over here so you go and speak to them and you say can you help can you help me and they try their best but they're unable they can't and the disappointment overwhelms you causes greater pain and now you're almost completely without hope but you take one last shot because a master has come and you say I need your help can you help me he says in verse 22 he has thrown he often he has thrown you in both into the fire into the water to destroy him but if you can do anything have compassion on us help us if you can do anything and he cries this out help us because you're not only helping my son you're helping us I've given up hope and to be honest you're you're my last chance I'm at the end of my rope and I'm not even going to pretend to have faith I have it but not that much my faith is almost gone it's nearly exhausted but Jesus in verse 23 says if you can believe all things are possible to him who believes you've said if I can do anything you say if I can do anything but the reality rests on whether you can believe and by this statement he forces him to deal with this lack of faith I have enough power to do what you're asking but do you have enough faith to receive it the father is seeing the compassionate way that Jesus had spoken to him and now he's asking him to show compassion in a tangible way by delivering his son if you can do anything he had said but Jesus responds if you can believe you see Jesus is willing but we often simply don't believe that he will help us Psalm 50 verse 15 says call upon me in the day of trouble I will deliver you you shall glorify me so when Jesus says if you can believe immediately verse 24 the father of the child cried out and said with tears Lord I believe help my unbelief help my unbelief the word unbelief means my unfaithfulness my faithlessness my lack of faith my weakness of faith I believe I have things I believe in I believe you can do that for others I'm having a tough time believing that you can do it for me my faith isn't what it's supposed to be I I ask that you supply me with the grace to put my entire trust in you not only am I pleading for you to deliver my son but I also ask for you to deliver me and in spite of the father's plaguing doubt God is not limited by our faith Ephesians 3 20 says he's able to do exceedingly abundantly above all we ask or think and Jesus is going to move notice verse 25 when Jesus saw that the people came running together he rebuked the unclean spirit saying to a deaf and dumb spirit I command you come out of him and enter him no more and the spirit cried out convulsed him greatly came out of him he became as one dead so that many said he's dead but Jesus took him by the hand and lifted him up and he arose I command you deaf and dumb spirit come out of him enter him no more you resisted my disciples but you cannot resist me in Psalm 33 8 and 9 let all the earth fear the Lord let all the inhabitants of the world standing of him for he spoke and it was done and the spirit cried out convulsed him greatly came out of him but he could not resist tearing him one last time and by the way this is how the enemy treats his victims and he still draws people to follow him the child appeared dead but Jesus gently lifted him to his feet and as this is taking place the disciples are wondering what's going on here verse 28 when he had come into the house his disciples asked him privately why could we not cast it out so he said to them this kind of this kind can come out by nothing but prayer and fasting why couldn't you do it it's interesting that they want they wondered at their lack of success while ignoring their own lack of faith they didn't see that faith in results would be linked he said it's your unbelief you only trust when i'm next to you you need to trust always faith trusts when we have nothing faith trusts when we feel forsaken when we don't know if he's listening or when we begin to doubt that he even cares in Psalm 91 verses 14 through 16 because he has said his love upon me therefore i will deliver him i will set him on high because he has known my name he shall call upon me and i will answer him i will be with him in trouble i will deliver him and honor him with long life i will satisfy him and show him my salvation why couldn't we succeed while this one doesn't come out except by prayer and fasting you relied on your previous victories and the result was relying on your own power matthew gives us more insight in Matthew 17 verse 20 he replied because you have so little faith truly i tell you if you have faith as small as a mustard seed you can say to the mountain move from here to there and it will move nothing will be impossible for you listen you need to learn that God's power is revealed in response to faith and believing prayer you relied on your prior experience but not on my present availability spiritual warfare is not momentary so be prepared for the battle remain steadfast trust God for the victory in 1st John 5 for everyone born of God overcomes the world this is the victory that has overcome the world even our faith men if you're going to be taking the word of God out you need to understand that when i'm not with you i still am with you you need to learn that you need to learn that you can do all things to christ who strengthens you you need to learn that you need to learn that it's not large faith at all it's a small faith in a great god that gets things done and if you're going to take this message out to the world you need to know that i will never leave you nor forsake you and you need to know that you can do those things because i gave you power to do those things hope fast don't let go the enemy has a way of trying to cause you to think it's hopeless that's what he does he steals your hope but jesus christ is our hope and he lives forever and some of you perhaps are going through some tough times but remember you're going through them you don't stay there you're going somewhere greater than anything that you've ever experienced you need to understand that hold fast hold fast hold fast and see what god can do these men needed to learn to trust the lord jesus christ but so do we we need to learn that he never never fails he always gives us the victory sometimes it comes in ways we didn't expect sometimes it's a different victory than we thought we were supposed to have but we always at the end of the day realize he didn't leave us he was with us and he provided for us why because he loves us he loves us don't forget that your god loves you he loves you so much he gave his son for you he loves you if you walk out with anything walk out with hope and the love of god all things are possible with jesus christ hold fast father we ask that you would


Okay, I found this, it's called bi-poo, this is not a hated advertisement, but it's actually saying to spray it first and then poo and it won't smell.


Functional assessment folks often known as functional behavior assessment or FB small a or small FBA whichever way you want to do it. It's a systematic evaluation of behavior in the context to figure out what you think is maintaining the responses and then you can start to target the problem responses or the the desired responses to increase or decrease them depending on which one you're trying to do. This allows when somebody says well why is Billy Bob engaging in that behavior? Well let's do an FBA and find out. Actually it should be more like well let's do an FBA and make a reasonable educated guess about what we think is really maintaining the behavior because you don't really know until you do an FB big a which is a functional behavior analysis. So functional behavior assessment, systematic evaluation to try and find out what is maintaining particular behaviors probably problem ones and then which is different than the FB big a. Anyway we often call them functional analyses which is why we have two videos on the same topic.