What's going on guys, got a brand new movie review for you guys today and that is for Mandy. He stars Nicholas Cage and this film takes place in 1983 where Red, played by Nicholas Cage, is a lumberjack who lives in a secluded cabin in the woods and his artistic girlfriend Mandy spends her days reading fantasy paperbacks but then one day she catches the eye of a crazy cult leader who conjures up a group of motorcycle-riding demons to kidnap her. Yes, this is all in this film.   Come on now. This film is effing wild. It's one of the most crazy films I've seen all year long and it's one of my favorites of the year too. One of that goes to the directing and the writing in this. This film is superb from top notch from the directing and the writing standpoint the way that the director gets the performances out of these main actors how great everyone is they're bringing their A level to each and every scene. Like I said this film is very different even though it does have that simplistic kind of revenge tail that you do here within there it's different. It's unique and it's dynamic it's not just because yeah you have a crazy cult leader no it's not just because there's demons riding motorcycles it's different in the way that it's shot and that the story is told. I've never seen anything by this director before and I'm looking forward to whatever the guy does next especially after this movie. This movie takes a lot of risk and now this is an art house this is an indie film so if you're not into these types of films this film ain't for you and this film is not for everyone it's a very hard film to recommend in that standpoint but I do think a lot of people should give this film a shot because it is on VOD but if it isn't a theater near you go and see it because it needs to be seen on the big screen. The vivid like portrait cinematography in here where it does feel like every scene in here is painted by a real life painter. The little cool nods in here that go to that homage 1980s grind house feel even though it's not an homage it feels like it's its own thing. Well the care and love that went into this movie and really this film is different it's the easiest way to explain it. Now I'd heard a lot of buzz coming out of Sundance earlier this year it has a high rating on rotten tomatoes but I never really heard any tiny aspects of this movie. Now I'm giving you all the gist of what I knew about going into this movie because this film is not needed to be spoiled. This film is unique and again it's hard to recommend it but it's a film that I want people to try and watch because it's so different. One of the big reasons that I think it's different is that the director makes a very brave choice in how he tells this story. Now this movie is two hours and one minute exactly and really the runtime goes up to that two hours and one minute the credits are not that long when the film starts everything I read in that synopsis really doesn't happen to probably 45 minutes in. First 45 minutes really feels like a prologue to the whole story as you are watching this it feels like someone who's reading a book or a painter is painting a story for you to kind of guess and what's going on but you get to know these characters you get to care about this relationship in a sense where you're as emotional as Nicholas Cage's in this situation. You get to know the cult leader you get to know the different dynamics between the characters and that's what makes this film not just your paint by the numbers revenge tale with dynamic and different demon scenes but very much giving you an altercation to a different light. Something as I was watching the film I did not really like the first half I was very kind of bored I was kind of zoning in and out but at the same time I was interested in what's going on I was just wondering okay where's all this Nicholas Cage madness trust me that's the thing that this film does so well is that it builds and builds and builds and the second you get to that which is pretty much the whole back half of the film is that Nicholas Cage madness that you want that's when the film starts. Again is very unique and I love that about this movie once you get to that Nicholas Cage madness that unhinged unchained Nicholas Cage one he gives the best performance he's given in a film since kick ass but two he goes into such different lights emotional unhinged unchained madness is what Nicholas Cage is and again yes we make him as a meme now but this guy was nominated for an Oscar this is seriously one of the best actors that was working in Hollywood and I for me this means he's back gives one of the best performances of this year the way that he brings this character to life this character of red is so dynamic you just believe everything that's going on on the screen as wacky and wild as it can get like I said he's taking on demons he's taking on cult leaders he has a chainsaw he has this cool brutal legends axe that he gets to slice people in half with awesome it really is awesome this film not really having any cons it's one of the most unique art style dynamic indie films that I've ever watched if you've ever seen a film by Nicholas wine boyfriend who's directed say drive or neon demon you're kind of into those films but you want something that goes even more absurd that's what Mandy is he not just contains one of the best performances of the year but it also has a first power to the film that builds up and seems a little bit too long at first but damn the payoff is so worth it it builds the relationship up so good between these two and it got me emotional it's effing wild it's different like I said this film is like you're watching a painter paint a vivid effed up art house comic book but man this film won me over in every type of light the score is superb the cinematography is amazing and super different and just vivid and portrait like it's one of the best films of this year again I loved Mandy I hope you guys give it a shot it's on VOD it's going into theaters check it out do not miss Mandy out so with all it said I'm gonna give Mandy an A minus absolutely love this film and it sucks that this film is gonna go so under the radar so guys make sure to share this review let's get it out there to go see Mandy tell me guys have you guys seen this film though comment down below and tell me what your guys thoughts are on it of course guys if you guys are new here hit up sandwich on films also down below because right down there you guys can get into advanced movie screens and also check out some movie news and even some movie reviews but of course guys until next time stay classy


and welcome to Lady Aida. Hey everybody and welcome to my desk. It's me, Lady Aida, at my desk, doing all sorts of engineering this week. So let's check out some of the cool stuff I've been working on. So let's go to the computer. Okay, so on my computer, let me just like move some stuff around here, make some room, a few, wow, it's been two years, a few years ago. I did a great search on finding an alternative for the seesaw chip that we used historically, the SAM-D09, which we used in like, let's see, we use this in the soil sensor, the stem of soil sensor and also the seesaw, like rotary, sorry, rotary encoder. Oops, not that one, this one. So like this breakout here, if I look at the back, it has a, you can barely see the SAM-D09 on it. And this is the original firmware that Dean, who was at Aida Fruit a couple of years ago wrote, that allowed us to do I squared C to anything conversion. So like I squared C to ADC, I squared C to rotary encoder, like you'd program firmware onto this chip and then it would turn it into an I squared C, like extender and this was basically because you can get I squared C to GPIO, you can get I squared C to analog digital converter, but like there's no such thing as an I squared C to rotary encoder or I squared C to NeoPixel adapter. So originally we used the SAM-D09, but then chip shortage hit and like basically any ARM Cortex chips were nearly impossible to get. And so we did that great search to get, when we found the AT-Tiny 818, I think, or it's 1618 or 808, yeah, 816. And this is actually a really great chip and this was also unavailable. Of course, now you can see there's tons in stock.  Let's see if it's just the store or the shop. So I made the 816 and 1616 breakouts. So these are both in the 817 as well. Turns out that I actually like the 816, it's much smaller, it's much more available than the 817. It's a tiny chip, but it has analog digital input, it has GPIO, it has interrupts, it has tons of pins. One thing I really like about this chip family is it's three or five volt compatible because it's an AT-Tiny. You can program it with one pin, the UPDI, and it's like a serial port. So it's like very easy to program it. You don't need like a whole shebang, it's like any USB serial adapter will work. And there's a great core for it by Spence Kandee who built the teeny mega core. So this, the 816 has a AK flash, a half a K RAM, and even has an EEPROM, which is also great because we can use that to store like the I2C address or specifications. And I did this breakout, the 816. And then I did the 1616. And these are both, the same pin out. The 1616 has 16K of flash and 2K of RAM. So it's actually kind of close to an Arduino and capability, but again, the chip is only like 80 cents on Digi-Key.  So the first one that I designed that I wanted to revisit was this ANO Rotary Encoder adapter. So the ANO Rotary Encoder is, which I think I showed, it's a really cool like iPod-esque wheel. It's got up, down, left, right, and a button and this is a scroll wheel. So it's a rotary encoder, it's all mechanical. It's not like a modern iPod, the more recent iPod. This is like the original iPod with the classic rotary scroll wheel. Really fun and tactile, but you need like a ton of GPIOs to use this because you need two GPIOs for the rotary encoder and then you need five GPIOs for the switches. And you also have to constantly be checking them and doing interrupt stuff. So I thought this would be a great candidate for rotary encoder support. So this is the prototype. Let's go to the computer. Sorry, the overhead. So this is the design for the PCB and you see there's the holes for the rotary encoder. This is the AT-Tiny816. There's a slot here for the NeoPixel, but I didn't solder it and I'll show you why. I did for one and then I'll show you why for the others. And then STEMQT. Normally I like to have the STEMQT centered, but because of the weird hole locations for the new ordering encoder, you can't. And then this is the final built version where it has the NeoPixel. So the NeoPixel I thought might shine through, but like it totally doesn't at all. It's extremely opaque. So I'm just gonna remove it because it would have been cool to have. Like it actually does, this demo does have it change color. You can kind of see it changing yellow and then it's like green and then it's blue. But you can't see it from the other side. And then there's also a interrupt over here. I think if I, you can see it flashing when I press the button. What's nice is this is all over I squared C. So what I do is, let's go back to the computer and I'll show the code for this. So the way the code works is that this example here, the ANO encoder, I want this in Arduino. And I have all these like pound defined configs where I set which pins and like which NeoPixel, you know, if there's NeoPixel support and the default I squared C address and the product code. You can read the product code from over I squared C to verify. It's the thing you think it is. And you know how many encoders and what pin it is. And then I programmed this again with this core called teeny mega core. And I have to like select all these things, that, you know, the frequency and the chip and whatever. But thankfully the core that Spencer wrote is like almost completely Arduino compatible. And so I can even do stuff like have serial print debugs, it's over UART, not USB, but it's very handy. And then I have just this, you know, initialization code and then the one loop that just constantly listens for I squared C and then does whatever the command says to do. So after I upload this and you upload it over serial UPDI, which is, you know, this is just a USB serial converter. Then on the separate IDE, and this is a great thing about Windows gonna have multiple IDs open. This is where I, you know, define the code that actually connects to the I squared C device, verifies that I have the right chip. It looks for that again, that version number 5740. That's the product ID. And then sets the switches to input pull-ups and then reads the encoder. So if I go to here and I'll reset it. So you see the output. Okay, found a seesaw, found the right product code, turned on the interrupt. So now when I spin this around, you see the number goes up and then if I spin it the other direction goes down and then if I press the buttons, they print out. And so this is a great, you know, it's over I squared C and I can have multiple devices on one I squared C bus. So if you want to have multiple loader encoders against them, that'd be very hard to do in Arduino without having an assistive like device to do it. So this design, other than the fact that the Neopixel doesn't work, works pretty well. Okay, and then I've got a couple other designs. We can go to the overhead. Okay, so another design that I haven't tested yet but that's next, because this is the one I was working on today, the ANL. This is a I squared C to Neopixel adapter. So a common thing that we have is people who have a Blinkett compatible board, like an orange pie or like an onion omega or like some rock chip Linux, what's your my jigger? And they're like, I want to use Neopixels with it but Neopixels need that like specific pin timing that's like very, very delicate. Like it has to be, you have to have the interrupts off or you have to use DMA and people figure out how to do it on the Raspberry Pi chip set because there's like billions of people with Raspberry Pi's and so it's worth the effort but it's not worth the effort to like add Neopixels to support to every NVIDIA chip set, rock chip, all winner, there's so many of them and not enough users and frankly it's just a lot of work. So instead, as long as you don't need very fast updates, this has an AT tiny 1616 and which has 2K of RAM and so you can like control, you know, 500 pixels or something even though like it's a very slow update because you've updated over I squared C, you can at least set this to like, you know one megahertz update and then you can control pixel so you can do basic lighting effects like you could do basic animations like it's not going to beat having a standalone native Neopixels support, but it's okay, you know and then you give it five volt and power and then, you know, power in and then power in, data out so these two are connected. You can't power the Neopixels over the STEMI QT because these connectors are only really good for like a hundred milliamps. I wouldn't even let people do it. I'd say, hey, you have to power the pixels separately but you at least will be able to control pixels if you just want to get them tested or working or you want to do some basic ambient lighting. Again, not good for like precision division, high speed stuff, but you'd be surprised. You can update quite a few pixels pretty quickly and then this is another design. So this is a joystick DE-15 for a PC joystick like an old style like a Sound Blaster 16 style and it's connected to another AT Tiny 816 and this has two potentiometers in it and then a bunch of buttons but I thought it was kind of cool to make it easy for people to connect to old style PC joysticks and then, you know, you could use like the buttons or like, you know, whatever flight sim controller stuff with modern electronics and you can control this. So I connect this through to any like a QT Pi which is running a native HID program and they could convert it to HID. So this would be your little adapter helper. So those are the three seesaw designs and don't forget the seesaw code, the peripheral code is open source and it's on GitHub.  So this is the code that you run on the... Oh, can you go to the computer? Sorry. This is the code you run on the AT Tiny chip and it reads I squirt C commands and there's a lot of examples for different devices so this might be handy for some people. You're like, you want to do Neopixels or some of the products we have PWM encoders, fast Fourier transforms, et cetera. Okay, so that's the stuff I've been working on and then I thought we would go into the great search. All righty, here we go. Where in the world is that part I need? The great search brought you by Did you get an AT for it every single week? The lady AT is your private engineer and they'll be as you find everything you need to find on digikey.com. Lady AT, what is the great search that's awake? Okay, so this is a, let me find one second. Terry, watching. Okay, so we had a question. Okay, this is a great example. We had example, sorry, let's go to the computer. Sorry. We had someone write in on, I think the comments to this video and they said, hey, I want to get a panel mount button that's like lit up that has latching action where you push it once to turn it on and push it once to turn it off. And you can see here, like the button gets indented, it latches in and we call this like a latching button as compared to a momentary button which is like a tactile switch where you press it and then when you release it, it opens up. And they were like, it's really tough for me to figure out how to find, I just want to find a panel mount on off switch like this with a press button and maybe some sort of light in the background to let me know when it's on or off. Can you help me learn how to search it? And I was like, that's a great idea. So we do take user requests. So let's show how to go to digikey and find a panel mount switch and one that has latching on off control. All right, so we're at digikey. So let's look for, let's just start with panel mount switch. So we don't have to search panel mount first but I figure it's a good, it'll give me a good start to what I'm looking for. So there's key lock switches. These are like ones that have locks and there's toggle switches.  Locker switches are also always gonna latch, right? Because you have to mechanically move them up or down but this person particularly wanted push button switch. So push button switches are gonna include both momentary and latching and those are the two kinds. Okay, so first up, let's of course only look at active. I mean, there's a lot of products and let's, just because there's so many, let's also only look at in stock and non-marketplace just to, because there's 176,000. So let's pare it down to some reasonable number. Okay, so these are some push buttons.  So for sure there's gonna be something here. So the first thing that they wanted was again, that switch function, they don't want it to be like press and then release, which is called momentary. Like it's only on when you press, they want it to hold whatever they press it. And so that's under switch function and this is very confusing because there's a lot.  Like there's all these different types. Basically momentary, when it says momentary, that means whatever is the opposite, like if it's off, momentary means it's normally off and when you press it momentarily, it turns on. So let's just show you that even though it's not what this person wanted, this is kind of what most people think of when they think of over the switch. So these are push buttons and they don't latch. When you press them, the two contacts connect and when you release, they disconnect again. So off momentary. And sometimes it's also called SPSTNL normally open. So single pull, single throws, there's only two contacts, they either touch or they don't and normally open and when you press, they connect. Okay, but that's not what they wanted. So let's turn off that switch function and go back. So what we want is non momentary. We want it to be when you press, it changes. And so we want it to go from off to on. Now you might want to know what's off, on, on. That means that there might be multiple modes or might be like multiple switch connects.  So also there's like, why is there off, on, off?  But let's assume that either one of them is okay. So these are the two options. On, on would mean that there's two switch contacts, so SPDT, so go between two different throws, which is also maybe what they want.  Okay, so now they've gotten rid of the momentary contact stuff. Some of these look familiar like Adafruit stocks, you know, stuff similar to this.  It's got an LED illumination ring that's very nice. This one doesn't. This is a latching push switch from JEDCO. I love JEDCO switches, those are really great. Square ones as well. We wanted one that had an illumination, it had LED. So incandescent is used often, like it's like neon for high voltages like 120 volts. You'll see often like power distribution strips, you know, you'll have the switch has like a flickering red-orange light that's like an incandescent or neon 120 volt. We want something that's LED. So we're just going to select LED, not incandescent. But let's say any color is fine. It can always be picky later if you want red, green, or blue. Actuator marking, don't really care about this, but you know, if you want a power switch labeling on it, that's a common request. Let's say we want rounded and let's see a couple of options. And there's the voltage rating. This person didn't write up and say what voltage rating they want. But of course, if you want it to run 120 volt or 220 volt power switch, you would select it. But let's look here. Okay, some nice options. So then let's look by pricing. Just let's see, like let's get, because they were like, oh, I want an inexpensive switch. Ooh, so a couple of nice options here. Just gonna go switch. And then, yeah, these are all going to be a couple of amperes. Let's see, LED red. Looks good. This one is kind of nice. This one, this is, this is kind of cute looking. This one looks good too. Fairly inexpensive. These switches, this one has, you know, the illumination within. I will say like, you know, I'm not gonna, I'm gonna pick one, but to be fair, all these are very good. Like this one might be a really good option if they want a metal button. But I did kind of like the look of these e-switch buttons. They can do three amps at 125 volts.  And then you have a lot of space here to drill a hole for them on the bottom. You can barely see it, but there's a plus or minus for the LEDs. And then, you know, the power switch itself available in red, yellow and green. This is the diagram. And then this is the data sheet.  These are gonna last many, many, many cycles and be able to handle very high current and have good documentation for all of them. And then of course, if you need slightly different specifications, you can check those out. But this was my pick for the great search. I think this is a good option. So there you go, dear fellow email writer. Lots of switches available. Pick this one, but there's also many more available for under 10 bucks. That's a great search. Where even part I need. Oh, Kidoki, that is our show for this week. Thank you so much, everyone, for joining us. We have lots of stuff ahead this week and more, including some surprises. So we'll see y'all online. Thanks, everybody. Bye-bye.


Okay, we're back here live in Silicon Valley, San Jose Convention Center. This is day two coverage of Hadoop Summit. The hashtag is Hadoop Summit. Tweet Hadoop Summit, hashtag Hadoop Summit. And we'll be following that and we'll answer any questions. If you have any comments or commentary you want to participate, use the hashtag. This is theCUBE. This is Silicon Angle and Wikibon's exclusive coverage of Hadoop Summit. It's our flagship program. We go out to the events and extract the signal from the noise. I'm John Furrier, the founder of Silicon Angle and I'm joined by my co-host. Hi everybody, I'm Dave Vellante of Wikibon.org. Scott Houser is here. He's the vice president of marketing at ADAPT. That's a company that we've been following for quite some time now on theCUBE. Born out of Yale, Daniel Abadi, Justin Borgman, moved up to Massachusetts. Scott, welcome to theCUBE. Thanks for having me. Yeah, good to see you again. I'm going to start right off. You guys are substantially different than anybody else in this community. You're very unique in the way in which you attack the problem of interactive queries on Hadoop. Talk about the problem that you're solving, how Hadoop solves it, and why you're different. Sure, so fantastic question. I think if you look at what we've done since the beginning, I think we sort of evangelized the beginning of this market trend. And what we talked about from the beginning was this notion of the database for Hadoop. And if you look at what we've been working on for the last couple of years, it's really about giving the value and benefits of a relational database engine inside with all the value and benefits of Hadoop. So we co-locate a real relational engine on every node where Hadoop exists, and give you the benefits of being able to work with all the multi-structure data that may exist in that query, or excuse me, in that cluster. Okay, so contrast that with, let's say, kind of a pure play query engine that you might see, the plain vanilla query engine, let's call it. How is that different from what you guys do? So I think one of the key differentiation there in that context is the query engines look at HDFS as one source of data, or potentially HBase, but they're tied to looking at and materializing data from those files at query time. And what we focus on is building a real relational engine that has all the benefits of a relational engine, things like indexes, materialized views, et cetera, and gives you all the benefits of SQL without necessarily being tied to some limitations. So if you think about our storage layer capabilities, they're really, they're really agnostic in that we can work with data inside of HDFS. We obviously materialize some data into tables that we manage ourselves. We also integrate natively with the HBase solar. I mean, one of the things that was talked about yesterday during Murph's keynote was this notion of text. We've been doing text for over a year. Well, search, right? Yeah, absolutely. I mean, search is all of a sudden the hottest thing going, and you've seen that for a while, actually. I mean, Oracle's acquisition of Indeka kind of woke the world up and said, wow, search must be really important and be a fundamentally embedded part of all applications. So now you guys obviously have been doing search for quite some time. I think you announced probably a year ago. So what I want to understand is from the standpoint of the Hadoop customer where, you know, search, everybody knows Google search, but what is it that's special about search in Hadoop and why is it that you guys were able to come out a year before pretty much everybody else? So I think one of the most unique things about what people want to do with search with respect to analytics is leveraging the unstructured free flow text and context within the text as an attribute and a query. So when you think about analytics, you think about all of the traditional things that are available to query, things that are very structured, right? But the ability to use search as a filter on a SQL query is a very powerful thing. And so we see in a bunch of different use cases, you know, one of the largest media companies in the world leverages us to be able to correlate events and behaviors via one channel and then effectively filter that based upon another channel of engagement with that same user. So what's the sentiment around things that the user may be commenting about in forums, in chat, et cetera? And how do I use that as a filter against a different channel behavior? In a, I won't say real time, but a near real time interactive. Interactive, yeah. I want to come back to that example in a second, but before I do I want to go back to the sort of, just really understanding the differences of ADAPT. So you guys, you said you bring a lot of the SQL-like capabilities to Hadoop. But there are some trade-offs. You don't bring everything. Can do things like, if I understand it, I mean, certainly search is an example, but you can do user-defined queries as an example. That's right. So we have a complete framework that we call the HDK or the Hadoop development kit that enables users to write their own analytic functions and we can call them as a procedure, if you will. But we also embrace the entire ecosystem of Hadoop and there's a bunch of things going on in the machine learning world that now we also make that accessible to the common business analyst via a SQL function.  Is it performance? Is it simplicity? Is it integration? All of the above? And how does that translate into a business outcome?  I think what we see in most cases is, there's this, you know, we talk about unification and we talk about bringing all these tools and technologies and making them accessible to an analyst via a common and well understood interface, which is SQL. But that's just the beginning, right? And so when you start to look at what people want to analyze and they want to get their arms around all of the data that exists in the enterprise, a lot of that doesn't fit into structured tables, right? So what we give people the ability to do is bring that into one unified platform and take advantage of it, irrespective of how it's being stored or what engine it's being used to store it and make all that accessible to an analyst via a well understood common language like SQL via tools that they know and love. Okay, now let's go into maybe some customer examples. You mentioned a media company. We talked about multiple channels. Let's unpack that a little bit. Talk a little bit more about kind of what the typical customer is doing, how they're using Hadoop, what they're doing in big data, what the life was like kind of before and after you guys. Sure, so I think in many cases, what I've seen in a lot of the folks using Hadoop is they've sort of been relegated to the ETL space, right? And so a lot of folks have focused on the two vendor approach where they say, you know, I've got an MPP analytic database and I've got Hadoop over here in the corner and I'm only doing batch-based ETL type workload on Hadoop and then if I find something interesting, I extract that and I push that over to the MPP platform. And what we advocate for in our customers and what we talk about a lot in different use cases is the merging of those worlds and the fact that with HEDAPT, you don't have to have a two-platform approach and you don't need connectors. We bring all of that together into the one platform. All right, so let me double click on that. So what's wrong with that two-platform approach? I think so there's a number of things that are wrong, right? So you end up propagating this notion of the data silo, which has been a problem for data management for decades. You also complicate things around enterprise features around availability, disaster recovery, scale, performance. There are a tremendous number of attributes that- It's complexity. It's hugely different. It's hugely difficult for the user. But it's also one that if the analyst wants to be able to truly manage all the data and get access to and query all that data and find the relationships that were otherwise previously undiscoverable, the only way you're going to do that is by giving them access to all that data. And if the analyst has to figure out which platform do I put what in and how do I move it around, right? You're never going to get the mass market adoption.   So you cut your teeth as an IT user of this technology. So you have some chops there. So let's put you in that position of a customer. So you've got this two-platform situation and you talked about some of the complexities. Can you give us a little bit more color on the kinds of things, tasks? What's the day in the life of that individual like if they've got that two-platform situations and how does their world change with ADAPT? Well, I think, you know, imagine that you have to operationalize two disparate platforms, right? It's double the work. So when you think about- So you need a bigger team. A bigger team and diverse skill sets, right? Because you're going to have to have specialists in these different areas and you're going to try and follow all the enterprise standards around availability, disaster recovery, accessibility, scope control and data management. And you're going to have to do that in two separate occasions. And what happens is there's this feedback loop that occurs between the business and the tech guys where the bigger those systems get, the more complex it becomes. And if I'm an analyst and I want to get access to some of the data, what traditionally would happen is, you know, there's been an ETL job that's been written. There's been, you know, some data's been called inside of Hadoop and I pushed something into my MPP database and now the analyst has found something that's interesting and they want to double click or drill down on that. But the data doesn't exist here. So now I have to go back to the IT guy, tell me, hey, can you re-run that job and here's some other stuff I'm looking for. Can you find that and give it to me? Whereas contrasting that in ADAPT now, you walk in and it's all the data lives in the ecosystem of Hadoop and is accessible to that same analyst so that as they find discoveries and they're doing this interactive, you know, sort of analytic workloads, they can dig into the raw detail of information and do all that without that communication loop, having to go back and involve somebody in IT, having to go back and write another job, having to try and materialize the data yet again. So what you're describing then, let's talk about the business process, you know, ripple effect of that. So you've got multiple databases and you're building business processes around each of those databases. And you're essentially wiring your business process to the limitations of your IT infrastructure. That's correct. So, okay, so now ADAPT comes along, you sort of unify all that and simplifies it so you get less people, you know, more focused skill sets, great. Is it your vision that essentially Hadoop becomes the data we just had Herb Cuniton from Hortonworks and their vision when they launched was 50% of the world's data will be stored in Hadoop. They're couching that a little bit now, saying stored or processed in. But okay, a lot of data is going to be stored in Hadoop. So is it your vision essentially that you can, you know, essentially replace traditional data warehouse system? Yeah, I think, you know, obviously long term that's our vision and our belief.  And I believe that Hadoop is effectively the operating system for big data. And I think what you'll see over time is that it will continue to eat away at the traditional infrastructures and change the way that people look at data management of the future. I think obviously as that occurs, you know, giving analysts and business people access to the information and letting them have the discoveries and insights is what makes it so critical for a tool like what we provide to the industry to take all that data that will reside inside of Hadoop and make it accessible and actionable to all the people who can, you know, change business outcomes based upon it. So the obvious sort of follow up question there is people think of Hadoop, they think of Batch. We've heard, we've been hearing all this week about Yarn and Hadoop 2.0. And we're certainly hearing a lot about interactivity around Hadoop. I like the way we talked to Merv in the cube yesterday and he basically said, you got Batch, you got real time and in between you've got Interactive and that's where a lot of the action is today. So in your view, Hadoop from a performance standpoint will be able to compete long term with the traditional data warehouse business? Absolutely. And I think, you know, we see, you know, in situations today and customer accounts where we're augmenting some of that workload now. And I think over time, we'll continue to eat away at that. I think there's been a lot of interesting research done in the financial services world where they talk about, you know, some of the incumbents and pressures that they're feeling in the market based upon these emerging technologies and some of the sea change that's occurring in data management. Yeah, well we certainly written about in SiliconANGLE and Wikibon, you know, some of Oracle's issues and have asked the question, is it tied to some of these, you know, the ankle-biter of Hadoop?  At the same time, those guys will likely respond, they'll buy companies, you know, they'll hold their ground, so to speak. But I want to dig into the economics a little bit because to me, to the extent that you can perform and do the same work, essentially, which is what you're saying long term, then it comes down to the economics. That's right. And it seems like a lot of the economics in traditional data warehousing is around the infrastructure, you know, pouring dollars into infrastructure. To proprietary systems. That, maintenance, and also just making the stuff go faster because of the architecture, right? I mean, one of our clients at Wikibon calls it chasing the chips. It's like a snake swallowing a basketball. That's how they describe their, you know, traditional data warehousing environment. So what are the economics of this new world?  I think there's a balance to that because it's not just about the cost reduction. It's also about the revenue opportunities that you're missing otherwise. And I think that's fundamentally going to leapfrog the savings. There's absolutely, I believe, significant savings in the core infrastructure. But I think by providing access to the data and the insights that are discoverable based upon access to all the multistructured information, I think the revenue curve dramatically changes for the customer. So you're arguing essentially that you can do things in a timeframe that you couldn't do. It's not just about time, right? It's about not even being able to do so. It's physically impossible. Like what, give me an example. So looking at multistructure data, right? Taking a look at and saying, I want to take and use search as a filter on a SQL predicate, right? That's not something you're going to go and implement inside of a legacy piece of infrastructure, you know, and anytime soon or in any easy way, right? Changing the processing paradigm that's been built over decades in products isn't going to happen overnight. And so for the customer, when you start to look at the disparity of the sources of data where they're finding value and the relationships that they're able to define based upon seeing these different dimensions, that's powerful. And you're not going to be able to do that in legacy pieces of infrastructure, you know, anytime in the near future. Okay, so my last question. So we've been watching you guys for a while now.  What should we be looking for now going forward over the next, you know, six to 12 to 18 months from Hedapp? What should observers be focused on as measurements of your progress? I think the most important one is seeing the customers themselves speak about the things that we're doing. One of the biggest challenges that you have in this space right now is that some of the things that people are able to do are not just mission critical, but also very differentiating for them in the market. So they're very tight-lipped about the things that they're able to accomplish. But I think as we continue to push more mainstream and we take over, you know, more of these traditional sort of use cases, I think you'll see more and more in the public eye about the things that we are disrupting. And I think that will be very powerful in the next, you know, six to 12, 18 months. Awesome, all right, Scott Houser from Hedapp. Really appreciate you coming by theCUBE and good luck with everything. We'll see you around at all these events and keep plugging. Thank you very much. Right there, this is theCUBE. We'll be right back with our next guest. Avi Metta, I believe, is up next. And if you've never seen Avi, you should definitely watch him. Keep right there, this is theCUBE. Silicon Angles Continuous Production. We're live from San Jose at Hadoop Summit 2013. We'll be right back.


This is Dr. Mahesh Kallanshiti, Associate Professor, Department of Civil Engineering, Valchin Institute of Technology, Solapur. In this session, we'll discuss about analysis of indeterminate structure by moment distribution method, wherein we'll focus on sway frames. The learning outcome will be, at the end of this session, students will be able to analyze sway frames using moment distribution method. Let us take an example, as shown here, frame subjected to a point load, and we have to analyze this frame using moment distribution method. So before we start, we have to first decide whether it is a sway frame or non-sway frame. Now from the loading condition, it is clearly indicated that it is a sway frame because the loading is not symmetric. Therefore, there will be a sway produced in the frame. Therefore, we have to adopt the sway frame analysis for this case. Now we have to follow certain steps here for the analysis of sway frames. These are given here. First of all, the frame shown is first held from the side sway by applying an artificial joint support at sea. So this is our problem actually, but first of all we have to prevent the side sway by assuming one artificial support here, and we have to carry over the moment distribution process. So the moment distribution is applied and by static equilibrium, the restraining force R is to be determined. The moment obtained thus are called as non-sway frame. It means here in this sketch you can see here, we have to apply the restraining force here and then we have to carry over the moment distribution and based on that, we have to calculate the moments produced in the members. So these moments, we call it as a non-sway moments. Later on, once we get this reaction, now after the analysis is over for the restrained case, we can determine how much R is produced here. Now in the second step, we apply the same force here on the frame and we do the moment distribution again. So the third step as it is shown here, the equal but opposite restraining force is then applied to the frame here as shown. The moment in the frame are calculated. The moment obtained thus are called as sway frames. So in this way, we can calculate the non-sway frame and sway frames. The summation of these two gives us the final moments. So this is an logical process of the sway frame. Let us apply these particular steps to our problem. So first of all, as usual, we have to calculate the distribution factors for the member, sorry, for the joint B and C. So as usual at B, we have two members. So the distribution factors calculated as 0.5, 0.5. Then for C also, we have two members. So the distribution factor is again 0.5, 0.5. Since all the members have got the same length and the same conditions, therefore we get all the distribution factors as 0.5. Then we have to calculate the fixed end moment. So from the figure, we have only fixed end moment for a member BC, rest all there is no lateral load. So we have to consider only the fixed end moment for the BC. And again, we have to consider this particular frame as a non sway frame by applying an artificial support here. So this is a restrainment which we have produced here for the sway. For this conditions, now we calculate the fixed end moments BC, since it is a case of eccentric load, therefore these are the fixed end moments produced. Accordingly, we get the fixed end moment BC is minus and minus 10.24 and for CB, we get plus 2.56. After that, we go for that, our conventional moment distribution process wherein we write all the joints here, all the members and the distribution factors are 0.5 as we discussed here and the fixed end moment we got only for the BC member. Therefore BC and CB, these are the fixed end moments that we get. Then we proceed with the balancing of the joint as usual and carryover wherever applicable. So in this way, in this case, from B, carryover is possible towards A and from CL, so carryover is possible towards D. And from B, carryover is towards C and from C, carryover is towards B. So all the carryover is taken care of and the distribution is continued and this iterative process where to continue till we get a very small and negligible amount of moment left. So after the moment distribution process, we got the final moments here in all the members. So these moments will use to calculate the restrained force R. So the equation of equilibrium are applied to the free body diagram of the columns in order to determine AX and DX. So this AX and DX means these are the shears that you can see here. Now these two members, we got the end moments. In the previous slides, we have seen that MAB, MBA, all the moments we calculated. So these moments are shown here and the free body diagram is drawn and from the free body diagram, we can calculate the value of R. Basically here AX we can determine and DX also we can determine by applying simple static equilibrium conditions. So by doing this, we get the R that is a restraining force as 1.73. So actually AX we get 1.73 kilonewton and DX we get 0.81 kilonewton. So by applying the equilibrium conditions, we get the restraining force R 0.92 kilonewton. Before we proceed, let us go for this review questions. I request you to take a pause and answer these review questions. The first question is, if three members are meeting at a joint and the stiffness of the members are K1 is EI, K2 is 2 EI, K3 is 1.5 EI. The distribution factor for the member is, member 1 is, so these are the four options. Then the second one, the distribution factor of the member OC of the frame as shown in figure. So in this figure, the distribution factor of OC you have to calculate. So four options are given here. So the correct answer, these are C for first question and 0.4 for the second question. Let us proceed further. Now, once we get the restraining force, then the same restraining force will apply here. So then equal and opposite values of R equal to 0.92 kilonewton must be applied to the frame at C and the internal moments are to be computed. So now for that, what happens actually, our job is to get the moments produced due to the restraining force. But for this, we need to calculate the sway which is produced because of R, which is bit complex process. Therefore, we adopt the reverse process wherein we assume some arbitrary movements are produced here because of the R. So sway is taking place towards the right side. Therefore, the moments are forming anticlockwise direction and arbitrary moments we assume. And later on we'll use one distribution factor for that and then we'll calculate it. So assume a force of R is equal applied at C causing the frame to deflect as shown. Then as I told that we apply the arbitrary moment 100 kilonewton meter anticlockwise for AB and DC.  Then we go for the distribution process.  All the moments are anticlockwise in nature. Therefore, it is considered as minus. And then distribution factors already determined. Therefore, these are to be calculated. So based on these all we get the moments here. We have to do the same process. We get the final moments at the end. Now these final moments actually are due to the assumed value. That we go for a next concept what is called proportioning of moment. Now from the equilibrium, the horizontal reaction at A and D are calculated. So here you can see the moments we just draw plot here and corresponding value of reaction R we calculate. Before that we have to calculate AX and DX by static equilibrium conditions. So AX we got 28 and DX we got 28. So again, as a whole, if I apply the equilibrium equation R must be equal to DX plus AX. So that value comes up to be 56 kilonewton. So R dash is 56 kilonewton which creates a moment as shown in free ball diagram. However, we need to the moments corresponding to R dash as 0.92 because we got the restraining force as 0.92 kilonewton but we got the restraining force as 56 kilonewton based on our assumed arbitrary moments. Therefore, the moments caused by R equal to 0.92 kilonewton can be determined by proportioning. And this proportioning can be done using a multiplication factor as 0.92 upon 56. So based on this concept, we can determine the final moments. So final moment is equal to non-sway moment plus the modification factor into moments corresponding to arbitrary fixed end moments. So if I consider AB, so the non-sway moment for AB is 2.88 and this bracket, this 0.92 upon 56 gives me a multiplication factor and minus 80 is the moments corresponding to arbitrary fixed end moment. Therefore, we get MAB as 1.57. Correspondingly, we calculate the moments of remaining members as shown here. Then this is what is the free body diagram from these particular values. So once we get the free body diagram, then based on this, we draw the bending moment diagram with our conventional assumption that tension outside is negative and tension inside is positive. So you can see here, this is a diagram. These are the references which are used for the presentation. Thank you.