So I've been incredibly impressed with the support that this program has been given over the last eight years or so, and really that's, there's testament to that and the people around this room. They're really an impressive group of people. I really want to thank you for coming. First one, right, thanks. So, and the other thing is, I guess it's good that Eric didn't say that I was the scarecrow in the Wizard of Oz because then I wished I'd had a brain and today I'm going to tell you about how the UDP worked and how the UDN is now working and how we can map the UDP onto the UDN or should we essentially and I would say that this is a non-surjective function. So how many people in the room would know what a non-surjective function is? Good, because I didn't either. Tom Markello told me what it is. It's a function that doesn't map every X to a Y. So it's non-surjective. So we don't really think of those functions very often. So let me go through how we established the UDP and what it's characterized by and then how the UDN is moving from that or towards that. The UDP was established to help patients reach a diagnosis and also discover new diseases and because we're the NIH, we have to do some research and some science. So the way it works is that people apply and they apply with their doctor's recommendation, a letter. And then for the adults, I look at the records and for their kids, Cindy Tiff looks at the records, we give them the consultants around the NIH who are all intramural and then they tell us what they think, you know, it's just a suitable case or isn't it? And we reject about 75, 80% of the patients. We actually accept about 50% of the kids and only about 20% of the adults and you can sort of figure out why that might be in terms of the balance of subjective complaints versus objective findings. And then we give some advice to some of the patients, but we see patients for one week as inpatients at the clinical center and it doesn't cost them anything. We even pay for their travel. And then we do incredible phenotyping because the NIH clinical center has an infrastructure that allows that and genetic studies which can be commercial. We do SNPs to essentially inform our exome analysis and then we do functional studies and some of them that we can. And the conclusions that we've drawn over the years are that phenotyping is critical and important and everybody knows that. So really the issue then is how can we achieve the best phenotyping? Half of our diagnosis are not made on next generation sequencing. They're made because we have doctors who come together or talk with each other, see the patients in an intense fashion for a week. Functional studies are limiting. They always have been and they always will because sometimes a functional study to determine whether a variant is actually pathogenic requires a year or two or three years of work by a postdoctoral fellow. Sharing of sequence and phenotyping information is essential and undiagnosed disease patients are desperate. So how does this convert now to the UDN? Strong phenotyping is critical. Again, everybody knows that. We do inpatient admissions at the NIH because we can and because we think that it's incredibly important for the patients to be available throughout an entire week for our consultants to come and meet other consultants in the hall and have meetings over these individuals. This is not something that may necessarily be convertible to an extramural system and we're finding that out. So I think that one of the things that we need to discuss here is for the sustainability of a program like this, how can we, let's say, achieve the essence of this program, basically having physicians talk together about a patient in an extramural setting? Nurse practitioners play a huge role in our system, either NPs or PAs. And this is not something that's necessarily done in every one of the clinical sites that's being supported by the UDN. I'll give you one example of why we think it's important. When we do phenotypes, which is the ontology system that needs to be entered for all of our patients for searching and comparability of cases, the people who fill out those, that phenotypes is largely nurse practitioners at the NIH. In other centers, if this is given to attending physicians, it takes longer to get done or sometimes it doesn't get done. I mean, even at our center, it doesn't get done well by the attending physicians. It gets done by the people who are seeing the patients for probably maybe 15 to 20 face hours in a week. Those are the nurse practitioners. Critically important element, which again may not be recapitulated extramirally. A friendly user ontology is essential and in fact the UDN has picked up the ontology that we picked up at the UDP. It's not necessarily 100% sure that that's the best, but the point is that an ontology system has been picked up that's been made universal. The second conclusion was half of our diagnoses are not based on next generation sequencing. There's a misconception sometimes that the UDP and the UDN is a sequencing program. It's not a sequencing program. The essence of this is that we see patients as physicians and we get other physicians to come together and look at the patients and make a diagnosis. It's also not solely a genetics program. We'll see patients who have any sort of illness as long as it's undiagnosed. And in fact, the UDN understands that and has an environmental survey involved with it, also model organisms and gene function cores. And again, it's not necessarily, it's solely a sequencing program, although we now have exome and genome sequencing cores that provide us with service in the Undiagnosed Disease Network. There are some sites that do sequence the patients before they see them. And we're gonna try to determine over the course of these phases, whether or not that's a beneficial thing or if it's not beneficial. We really don't know that yet. Functional studies are rate limiting and the Undiagnosed Disease Program has used many different ways to achieve this. For one thing, we have some in-house money and therefore we have in-house postdocs and postback students who work on some of the projects that emanate from our program. For another, we have contracts that we can let and also the UDN has let supplements to RO1s and also RFAs by the R21 mechanism and we have collaborators who work on projects for no money at all. And the collaborators are experts in the field and basically what they wanna do, I think, is to tie their research to a human disease and a human being for the basically introduction to their next RO1. The UDN itself has a gene function core and it has a model systems core and the clinical sites have the purview to use investigators at their own institutions to pursue the basic research into the variants that they find in the patients. Sharing of data is essential. So the UDP has shared its phenotypes and its variants in a variety of ways, on a national level and on an international level now. There is an undiagnosed disease network international that's been established and there's a white paper and molecular genetics and metabolism on that. We share through the coordinating center and the network shares through the coordinating center and can share internationally and this was founded in the institutional review board protocol that we wrote. In other words, the protocol and the consent allow for two things. One is the sharing of personally identified information among the members of the network. So that's a bit paradigm changing and it was approved by the NHGRI Institutional Review Board and it really is based on our experience that the patients wanna tell their stories. They wanna find another individual who has the same disorder, another family. And the second element is that the protocol and the consent allow for the sharing of de-identified information more broadly, that is with collaborators at the research level, not really necessarily the clinical level, but at the research level. And the UDN has used language basically drafted from the protocol that we wrote a long time ago and has actually changed over the years. And then the protocol then has the UDN has a single protocol that relies upon reliance agreements by every one of the sites that's involved in the UDN. And again, we share the information there. And finally, undiagnosed patients are desperate and this is a function that does map from the UDP to the UDN. Everybody recognizes this as soon as you see one of these individual patients. So that's what I've got. I think I made it short. In case there were questions, are you taking questions? Yeah, we have a few minutes if folks have some questions. Yes, sir. I apologize if everybody else knows this except me, but I'm not in the network. But is the consent form written broadly enough so that you don't have to ever consider going back for further permission? I mean, it's written broadly for application of all the data out to other applications. Yes, we think it is. I think, you know, since I wrote it, maybe that's a little bit of a biased view.  Do you think this is broadly enough written for future changes? It was intentionally written quite broadly, although there, of course, may be some circumstances in which we need to go back to patients, but intentionally for educational purposes, for sharing with outside databases, for sharing with other researchers, all of those are encompassed in the consent form. Give an example, in a way, we had to change our protocol about four years ago or so when IPS cells came in, and we incorporated that into the protocol and the consent. That's already in the UDN consent, but if something like that came along in the future, we may have to go and change it. Well, one thing I would ask specifically, is there a continuing interaction with those patients? I mean, can you incorporate some outcomes data or continuing data about the patients? Is there a provision for that? We're allowed to recontact them, yes. There now are patients in terms of us actually being doctors to them. I mean, they contact us all the time, and they can, and we can contact them. In the UDN as well, yes, that's correct. Hi, Judy. Do you have a patient family user group that sort of continually kind of asks the question of, or gives advice, or you can raise issues with? Well, right now we have Matt Might, who helps us with some of the social media and gives us a perspective from that standpoint. And written in is to establish such a group. I think I should ask Rachel how we're doing on that. So, yes, we're in the process of forming a patient engagement group specifically for that purpose. The question that is giving us a bit of pause is how to engage these families without overburdening them because we would be asking for some of their time. So, of course, you wouldn't have everybody, but it seems like some kind of user group that meets a couple of times a year to sort of say, okay, how things have gone. And part of it is that's become the way to do business. But when you set things up, it wasn't necessarily. But I think my guess is that the parent support groups would really love to see you do that. And the other part is newbies, like just the desperate new ones, have a different perspective than somebody who the diagnosis has been found, from somebody who the diagnosis didn't really help. But, yeah, I mean, I think they have very different perspectives over time. Agreed. Walter? Yeah, so maybe from the neurologic perspective, there are numerous patients that nobody knows what they have. They go around from doctor to doctor and everybody has the same questions. Everybody does the same kind of exam. And so the question comes up is, is there an effective way in which you could capture that information, maybe even in a video of the patient interview and have that kind of storage so that people could access it. And I mean, I'm not sure if it's helpful for the non-neurologic cases, but to be able to see that kind of interaction, get that history, I mean, you can almost think of putting it out and having people around the world try and take a shot at what the problem is. Is that kind of thing, do you think feasible? Well, so Dennis Landis, when he was actively with us, actually wrote a bunch of best practices for the investigation of an undiagnosed neurological case. That was written, it wasn't video. Are you sort of getting at doing this for an individual case where you'd like that case to be solved? Or are you asking more for general principles that are illustrated by a video of how to do an exam and what questions to ask for a new disease? You know, I'm thinking for an individual case because I'm just imagining if it may be off, but someone might see something and they have an idea, but it doesn't gel until they see the other one. So to be able to have a library of these kind of cases, because I think that's how people develop their expertise over time. They start seeing different things and they're kind of correlating. I saw this case before and this one looks like this and that's how things come together. So I'm just wondering in a collaborative way, thinking with modern techniques as opposed to sending the patient around to different doctors, you bring all the data and then different doctors can all look at the same data. Right, I think that that is in a way data sharing. And the way that we're sharing data now is to have the phenotypes, let's say categorized by an ontology that allows searchability and also to have the variants put in a database that's shared. What you're suggesting is going one step further, I think, at having videos and we do take videos of many of our patients, especially the very special ones. Disseminating those videos maybe is a little bit more difficult. In other words, videos by and large are not searchable. So in that case, we'd have to be a little bit selective about whom we would give the videos to for a particular consultation. But I absolutely agree that that is the most poignant way of finding similarities and that's critical. Do you want to add something, Rachel, before I go to? So at the Coordinating Center and Anastasia knows this, I don't know if you, Bill, yet are aware of this, but we have been exploring potential partnerships with networks of doctors that are doing collaborative case-solving to potentially post either solved UDN cases to educate a broader audience about undiagnosed diseases and how they should be worked up, as well as unsolved cases to crowdsource. And at the Department of Biomedical Informatics, where I was previously at Harvard, they had done crowdsourcing around undiagnosed diseases that was focused at sequencing cores. This would be more focused at clinicians. And so I think that that is a promising avenue and including the videos is very important. Matt Merritt. I was just gonna comment that in the VA system, we use telemedicine pretty heavily and also, so that could be a one-on-one with a patient at a distant site with their provider, also perhaps in the room. And it might be a way of actually not having the patient have to travel, but that they can get expertise from a whole bunch of other clinicians. You could even do it all at one time where you have multiple providers in different places with telehealth technology. And then there's also store and forward technology so that you could send images or videos for a consultation with another provider. So it's clinical care that is provided in certain health systems that have that capability. So just maybe something, I don't know if that's anything anyone has considered. So we're right at time now, but I know, John Mink, you've had your hand up. So why don't we take that as the last question for this session? Just very quickly, because I know this is a topic for discussion later today, but one of the things that makes undiagnosed patients desperate is that their physicians say, I don't know what you have, so I don't know how to treat it. And particularly for the UDP, the intramural program, what is typically done in terms of treatment recommendations once a diagnosis is made or are those recommendations even made? We do make recommendations largely asking that the local physician pick it up. In fact, that's one of the criteria for acceptance that there has to be someone who's willing to do that. But sometimes the disease is so new that there's no authority in it. And then we do take over some of that. And for example, in the last fiscal year, we saw 20 to 25 patients a second time, basically for that follow-up because there was some treatment that, and I would also mention that sometimes the ancillary services of the NIH Clinical Center are incredibly helpful in that. Rehabilitation medicine, for example, or some of the consultations in heme or immunology, things of that sort are extremely beneficial. Rheumatology, when they have new drugs and sometimes even the clinical center can provide those new drugs and the insurance won't. Just, although don't tell anybody at the clinical center that. But that's what we do. Unfortunately, with these genetic diseases, there may not be an awful lot of cases in which the therapy is directed. Thank you.


Hey everyone, what's going on? I am Greg Suspin joined today by Frank Stamphill. One more week left of the regular season in fantasy football season long. Frank, are you ready? I am ready, Greg. It is bittersweet right now in the fantasy football world. And when it comes to the waiver wire this week, I'm not sure that we have heavy hitters like Jonathan Williams and Bo Scarborough from a week ago, but I think we actually have a lot of really nice depth pieces here. So I'm excited. How are you doing, Greg? I'm good, man. Really, really excited to get to the playoffs, but I need to win this week. So I need your help. Let's start at the quarterback spot where I think there's one obvious play and his name is Ryan Tannehill. This is what it's come to week 13, Ryan Tannehill as the top streaming quarterback. And how can you argue against it? The guy is playing lights out right now, finished 14 of 18 against the Jacksonville Jaguars in week 12, 259 passing yards, two passing touchdowns, also rushed for 40 yards and additional two rushing touchdowns. Who would have funk it? Arthur Smith, the OC of the Tennessee Titans, getting the best out of Ryan Tannehill right now. He is number one in the NFL in yards per pass attempt. No, that is not a mistake. 9.2 yards per pass attempt. He is third in the NFL in passer rating at 111.4. He is currently the QB one in week 12. He's gonna finish at worst, a top three quarterback this week. He has at least 19 fantasy points in every single start he has made with the Tennessee Titans. And over the past three weeks, we're actually using him more as a rusher. He's averaging 38.3 rushing yards per game over his last three games. And you've heard this before. When it comes to rushing quarterbacks, that adds to their floor for fantasy football purposes. That's why a lot of people like Lamar Jackson coming into the season. Same thing with Kyler Murray. Well, the Tennessee Titans are actually using Ryan Tannehill in that regard as of late. He does face to Colton week 13 and on the season, they've been tougher against quarterbacks, but Tannehill has excelled in some tougher matchups. He's gone up against the Chargers. He's gone up against the Chiefs. Two teams that have done a good job of limiting fantasy points to quarterbacks, but he excelled in those matchups as well. Greg, fantasy football makes us say and do a lot of weird things. We're about to do something very weird. We are riding Ryan Tannehill to fantasy football championships. The Raiders, Texans and Saints up on the schedule in weeks 14 to 16. Let's go, Ryan Tannehill. It's literally come to this, week 13 of your fantasy football season. And we're riding Ryan Tannehill. Just like we drew it off. And as Frankie says, you gotta take the name off the back of it in Jersey.  But hey, Ryan Tannehill, he's your man in week 13. But if you don't like Ryan Tannehill, I'll tell you to start, Caroline is starting a quarterback. And if I would have told you this 13 weeks ago, you'd say, that makes sense. Let's go with Cam Newton. Uh-uh. We're going with Kyle Allen. Kyle Allen bounced back in a big way in week 12, Greg. Against the New Orleans Saints, a defense that had been tougher on quarterbacks recently, finished 23 of 36 for 256 yards and three passing touchdowns. He has a top five quarterback so far in week 12. There are two types of quarterbacks in the NFL, Greg. There are quarterbacks that can elevate the play of those around them, regardless of the talent level. And then there are quarterbacks who can succeed based on having the right pieces on their team. And I think obviously Kyle Allen fits into the ladder there. The weapons that he has here on the Carolina Panthers are phenomenal. DJ Moore, one of the most underrated wide receivers in the NFL right now finally got back in the end zone, scoring two touchdowns. Christian McCaffrey, I mean, the best running back in the league, the best pass catching running back in the league right now. Curtis Samuel and Greg Olson have a good role in this offense as well. So I think based on the pieces that he has on this team, Greg, this puts Kyle Allen once again in the streaming conversation, at least against the Washington Redskins heading into week 13, because this is a defense that, yes, they've played better, but two weeks ago we saw Sam Donaldthrow for four touchdowns against his defense. There have been five different games this year where Washington has allowed three or more passing touchdowns on the season. So I think that there is some upside here as well. I do like Ryan Tannehill a whole lot more in his week 13 matchup and just moving forward for the fantasy football playoffs. But if you're in a bind, if you were someone who was depending on Carson Wentz, he hasn't played well, he is banged up and you need a quarterback who has a good matchup. I think Kyle Allen going up against Washington is a very good spot, obviously, this week. And then after that, he gets the Falcons and the Seahawks as well. So Kyle Allen, based on the weapons that he has, I think that he can actually succeed here moving forward, Greg. I've used Kyle Allen a lot in Superflex this year. So I know the trials and tribulations that come with him, but over the last couple of weeks, he's got no fear, and he knows he's going to pass the ball. Todd and DJ Moore has been really, really hot as of late as well. I think you can do worse than Kyle Allen if you're desperate for a win. Up next, we get to the running backs and that brings us to Seattle where I took a shot in my draft under shot penny thinking at some point it could pay off. Have we reached that point, Frank? I think we're getting closer to that point. Chris Carson has a serious case of Tiki Barber-Itis where this guy cannot hold onto the football. He fumbled again yesterday. Now, he leads the NFL with seven fumbles on the season and he almost had a second fumble where he kind of messed up the exchange with Russell Wilson. Apparently, Russell Wilson changed the call at the line of scrimmage and Chris Carson didn't hear him. So ultimately, Russell Wilson got credited with that fumble, but Chris Carson could have had two fumbles in this game and Rashad Penny just came off a monster game. He rushed 14 times for 129 yards, including a 58-yard touchdown against a stout Philadelphia Eagles defensive line. They normally are great against the run, but that didn't matter to Rashad Penny yesterday. He played just three snaps less than Chris Carson. He had six more carries than Chris Carson in this game. Again, Chris Carson has been very, very good this year. So I'm not saying that Rashad Penny is necessarily going to take over as the workhorse of the Seattle Seahawks, but I think we are getting closer to that point. And if Chris Carson were to get hurt or if he were to fumble again, which is not out of the realm of possibility, then we could see Rashad Penny start to take over even more of the work. This is a guy who has the pedigree. He was a first round pick just last year for the Seattle Seahawks. He has shown explosiveness as well. And Greg, when he's been given an opportunity, he has actually paid off in those games. There have been three games this year where Rashad Penny has eight or more carries in those games. He is averaging 7.7 yards per carry. So I like what I've seen from Penny. And I think that we are getting closer to that point. Again, he is one of those handcuffs who actually has a role in the offense that needs to be owned right now. We know that the Seahawks want to run the football there. They have the fifth highest rush percentage in the NFL so far this season, Greg. So I don't think Chris Carson is going away yet, but we're one injury or one more fumble away from Rashad Penny having a legitimate role in this offense. Yeah, a legitimate role in this offense is what we're waiting for for Rashad Penny. And we said it before though, Frank, he's fumbled all season long as Chris Carson. So we said, all right, maybe this is the week and it hasn't happened. Maybe because of spraying ankles by Penny, his inability to stay healthy. But Pete Carroll has turned time and time again over to Chris Carson. And maybe this time it's different. Maybe it's not.  Yesterday for Pittsburgh, every fantasy analyst and their mother said, start Jalen Samuels. That was wrong. The right running back to start Pittsburgh was Benny Snell, what a career day. We don't know if James Conner's coming back anytime soon, if at all. So we're telling you now, it's all about Benny Snell. With James Conner out yesterday, Greg, we were left trying to figure out who to start against the Cincinnati Bengals. We knew that it was an amazing matchup for the Steelers running backs, but we didn't know who it was gonna be. Jalen Samuels, Trey Edmonds, Karith White, who is that? No, it was Benny Snell, of course, who finished with 21 carries for 98 yards. Look, rookie, fourth round pick for the Pittsburgh Steelers. There's something they clearly like about him. He is a stronger back, run between the tackles. Not gonna do much as a pass catcher, but he does fit that mold as a Pittsburgh Steelers running back, the Pittsburgh Steelers running back of old, that grinder who likes to run between the tackles. And he was given the opportunity yesterday. He led the team with 35 snaps. The next closest was Jalen Samuels with just 21 snaps. So again, they leaned on him. And I said this last week about Jonathan Williams, Greg, that when they give a young player an opportunity and he comes through on that opportunity, he's going to continue to have a role. Now, we don't know what the situation is with James Connor, but this is now the second time he has hurt his AC joint in his shoulder. I don't know that he's going to be back in week 13. And even if he is, there's a really good chance that he ends up re-injuring himself. Again, I mean, he has dealt with multiple injuries, not just this year, dating back to last year. So I think at this point, we can almost label James Connor as injury prone. I don't know that we're going to see him in week 13. So Benny Snell, based on getting 20 carries in this game, Greg, I think, you know, any running back that has a role like that, even in a committee, you have to be excited about whether it's Devlin Hodges, Mason Rudolph, they can't throw the football. They are going to continue to run the football. And if James Connor is out, Benny Snell is that guy. They have to run the football. That's their best chance of fighting in this playoff race in the AFC and ultimately getting into the playoffs. They have to run the football. They did yesterday. We'll see if they keep doing it as we expect they would. And hopefully if they do, Benny Snell is the man to own. Up next, we move on to the wide receivers and that brings us to the phenomenal A.J. Brown. Not the first time we've talked about him here on the hurry up, but maybe this is the time we get it right. He's our big play threat. And you just look at him. And he is built like an Anquan Bolden, like a Julio Jones.  And he's really, really fast. That's a lethal combination. The only question is can Ryan Tannehill get him the ball? Well, we like Ryan Tannehill. I think you have to like A.J. Oh, A.J. Brown, Frank is criminally under owned. Yeah, that ownership percentage in Yahoo leagues right now is just way too low when it comes to A.J. Brown. And you know, I would have thought that you were reading my notes, Greg, based on that introduction that you gave A.J. Brown here. Great combination of size, speed, explosiveness, athleticism, he can catch the deep ball. He can make plays after the catch. We've seen it time and time again. It really looks like A.J. Brown has surpassed Corey Davis. Whether Corey Davis is not 100% healthy. He's dealt with a lot of injuries this year. He hasn't been able to get on the same page with any quarterback. I'm almost done making excuses for Corey Davis. I think that he can be a talented player, but now this is two different quarterbacks that he has not been able to get on the same page with. Marcus Mariota or Ryan Tannehill. It's not working for Corey Davis. It is working for A.J. Brown, who just finished with four catches for 135 yards and a touchdown in week 12, going up against the Jacksonville Jaguars. I'm sure the Tennessee Titans wish that they could just face the Jacksonville Jaguars every single week because their wide receivers go off against them. Derek Henry goes off against them. But all of those marks for A.J. Brown led the Titans past catchers and he has at least 64 yards or a touchdown in four of five games with Ryan Tannehill as the starting quarterback. So he's been pretty consistent in those games. He leads the team in targets with 27, leads the team in receptions with 17, leads the team in receiving yards 308 and he has two touchdowns, which is tied for first on the team with Ryan Tannehill as the starter. Coming up in week 13, they go up against the Indianapolis Colts. We just saw Deandre Hopkins score two touchdowns against that defense. Will Fuller making a bunch of deep plays down the field over 150 yards in his return against the Colts last week. And then in weeks 14 to 16, we have the Raiders, the Texans and the Saints. So we love Ryan Tannehill. That means we love A.J. Brown. A.J. Brown next year in fantasy football is going to be a high upside pick that everybody wants. You're going to want a piece of A.J. Brown next year. Well, don't wait till next year. Get on it now. It's a guy that can really help you throughout your fantasy playoffs. A.J. Brown, certainly the top wide receiver pick up here in week 13. Up next spring, another wide receiver we're going to mention, it's Cole Beasley, he's certainly not as sexy as A.J. Brown, totally different style and totally different build, but he's been really successful. pairing with, paired with Josh Allen this year, he's filled his familiar role inside the slot last week or this yesterday rather. He went off, had a touchdown and he's been really good as of late. He's sneaky, not sexy. That's okay because he's productive. Yeah, completely different player than A.J. Brown, but getting it done recently from a fantasy football perspective, just had a monster game in week 12 against the Denver Broncos. We knew that it was going to be a tougher game for John Brown, but Cole Beasley really stepped up and excelled in this game, leading the team with nine targets, 36% of their target share, led the team in receptions with six, receiving yards 76, and of course he scored a touchdown as well. Since week seven, how about this, Greg? Normally Cole Beasley, not a guy that scores a lot of touchdowns, but since week seven after their buy, Cole Beasley has at least 74 yards or a touchdown in five of six games. So like A.J. Brown, has actually been pretty consistent over the past six games for the Buffalo Bills. Slot receivers have had some success against the Dallas Cowboys as well. We just saw Julian Edelman, eight receptions for 93 yards, about a month ago this time. Jameson Crowder had six receptions for 98 yards against the Dallas Cowboys. So I think we're going to see a decent number of targets. You know, it's a little bit of a tougher matchup on the outside here for John Brown going up against these Cowboys' corners, but I think that we could get some success here. And of course, Greg, we love the revenge game narrative on Thanksgiving. I think Brian Dable has done a fantastic job as the offensive coordinator of the Buffalo Bills, but I think that he's really going to make it a thing to get Cole Beasley in the end zone this week against his former team of Dallas Cowboys on Thanksgiving. So I think the targets will be there. I think we get some receptions. And I think we get a touchdown once again this week for Cole Beasley going up against the Dallas Cowboys. You know the Bills want to get Cole Beasley into the end zone once again, like you said, in a revenge match. We've been talking a lot on our network about how we think the Bills are in a good spot against Dallas. The Clappers needs a big win. Josh Allen here to make a statement. Bills trying to head back to the playoffs for the second time in three years. We'll see if they can get it done on Thanksgiving. But more importantly, we'll see if Cole Beasley officially gets his revenge. Titan has been a roller coaster all season long for us, Frank, and this week, well, we're back on the Jack Doyle ride as Eric Ebron on injured reserve. He's out for the year, which means Doyle steps up once again as the primary option until the squeaky wheel got its grease. Doyle was the more productive Titan. Now Ebron's gone, which means Jack Doyle should be a low-end, tidy end one throughout the fantasy playoffs. Absolutely, Greg, you hit the nail on the head. Eric Ebron landing on injured reserve for the Indianapolis Colts, and it's not as easy as just combining their stats. But I'm gonna do that right now, let you know where they would rank. So if you put Jack Doyle and Eric Ebron's production together so far this season at the Titan position, they would be the Titan two overall. We've seen this before, Jacoby Briss set. He's not really like to take many chances down the field. He likes to target those intermediate over-the-field routes. That's where Jack Doyle excels. T.Y. Hilton's still a little bit limited. We saw that in week 12 on Thursday night football. Now he's gonna have 10 more days to rest up and get healthy. So I think T.Y. Hilton will be more involved. But Eric Ebron, you're right, Greg. You know, he was the squeaky wheel and he asked for more targets and that's exactly what he was getting. Over the past three weeks, Eric Ebron was leading the Colts with 24% of the target share. Now those targets are gone.  I think it's gonna be a lot of T.Y. Hilton and a lot of Jack Doyle. Earlier on in the season, Jack Doyle was getting the job done. He was consistent. Not seeing a ton of targets. You know, he's right around that four to five target range every single week but he was being targeted in the red zone. And oftentimes, defenses forget about Jack Doyle because you have to worry about the run game and you have to worry about T.Y. Hilton. So I think there's gonna be some production here, Greg. And the next two matchups coming up for the Colts are against the Titans and against the Tampa Bay Bucks. Those are two teams that have allowed a decent amount of fantasy production to tight end so far this season. So I know we've been off and on with Jack Doyle and a lot of these tight ends but I think things are looking up for him now that Eric Ebron has landed on IR. I've been a Doyle guy ever since he burst out on the scene a couple of years back. Doyle shouldn't find the end zone more in the coming weeks. Eric Ebron is gone. Sure, Mo Alley Cox is there. Not something we're gonna worry about. Jack Doyle, now a reliable tight end option which we've been desperate for all season long. But Jack Doyle's not out there for you. There are other directions that you can go in. We talk about Noah Phantz a lot. We talk about Mike Koseki a lot. Who are we turning to this week, Frank? We're going back to Kyle Rudolph here, Greg. And normally we have to wait till the holiday season to get Kyle Rudolph in our lineups but he has scored a touchdown in three straight games. He has five touchdowns scored over the last five games for the Minnesota Vikings and he's been pretty consistent during that five game span. 15% target share. Not amazing, but again, he's four to five targets every single week. Adam Thielen is going to be back which could eat into some of the production here but we've got a good matchup coming up for Kyle Rudolph going up against the Seattle Seahawks who are allowing the seventh most fantasy points to tie in so far this season. We just saw Zach Erz and Dallas Goddard combined for 19 catches and 123 yards in week 12 for the Eagles offense going up against the Seattle Seahawks. So, yes, Thielen's coming back. Stefan Diggs has a role with the Minnesota Vikings. They want to run the football with Dalvin Cook but they've really found something here with Kyle Rudolph, with Irv Smith, you know, Kirk Cousins playing lights out football right now targeting Kyle Rudolph in the end zone, in the red zone specifically which is what you want out of your tight end. So, you know, I think defenses have to focus in on trying to stop Adam Thielen and Dalvin Cook and Stefan Diggs and a lot of times that leads to single coverage against Kyle Rudolph. I think he's going to be able to make the most of that opportunity going up against the Seattle Seahawks defense in week 13, Greg. Now, Rudolph's been really hot finding the end zone as of late. Those three consecutive games with touchdowns, as Frank mentioned, hey, this week Adam Thielen may be back but hopefully Rudolph can still find his way in an end zone and help out fantasy owners here this weekend. One last position to get to, Frank and that is the defense. Well, we've been pretty good picking out defenses here and not only do we have a pick for week 13 with the playoffs on the horizon, same defense is the right choice for week 14 as well. Greg, what is going on in the world when the New York Jets are one of the hottest teams in football on a three game winning streak? Sam Darnall has played extremely well but so has the defense. Jamal Adams has been fired up the past couple of games. He's making a ton of plays, sacking people, stealing the ball away from Daniel Jones. He played great in week 12 against the Oakland Raiders as well. You look at what this Jets defense just did against that Raiders team and offense that was playing really, really well on the season. They limited them to just three points. They had one sack in interception, a fumble recovery and a defensive touchdown as well. You mentioned the matchups coming up. It's hard to get better than this, Greg. Ryan Finley and the Bengals in week 13 for the Jets and then in week 14, they get their revenge against the Miami Dolphins. Ryan Fitzpatrick has played well for the Dolphins but at this point, 37 years old, he's just slinging the ball around. He doesn't care what happens. He's throwing interceptions. He's getting sacked as well. Jets are in a prime position over these next two weeks to really take advantage from a fantasy perspective and I think that they're gonna do just that. Jets are on a roll, three games in a row. We're riding the Adam Gaze train, baby. We're going right through the tunnel and we're making the playoffs, right, Frank? No. That's gonna do it for us here at the FanDoleHurry. Those are the players you need to pick up. So make sure you get on it soon. Tomorrow, I'll be joined by Tom Vecchio who's gonna be the top players that you need to know about on Thanksgiving Day. Three football games and we'll make sure we have you covered. You're in the hurry up. Have a great night. Enjoy Monday Night Football. We'll see you tomorrow.


What's going on everyone Sam here with late in sports cards. We are doing 2022 penini certified four-box hobby Hobby four box break number five random team style No, six six number six random team style. Here's a look again at your results As always you can find these on the website under the results tab as well as the Lincoln chat Let's do it. Nice. That is Three of ten on the gold jersey Congrats on that. What's going on? Did I type the results wrong? No I think I did I did the real one. There you go I think I'll just go in and change results. I think I just copy pasted the five over accidentally Gabriel Davis To 75 bills Gold team Kyler Murray 11 out of 249 and drake london to 199 Drake London rookie base. That is donovan people's jones certified potential 16 out of 75 browns The second year dpj nice face Or maybe third year dp no third year donovan people's jones 2020 right? Yeah I would have remembered him last year Uh, nice joey bosa game worn certified gamers To 199 for the chargers. Oh, no We disconnected from obs So they just have to go continue until it's over Okay. Yeah, we just got to keep the recording going damien pierce to 99 Yeah, I see now we're Um, when you get a chance can you just go on to youtube and twitch and double check that we're live Um, zamir white going to the raiders that is 80 or 65 out of 199 If not, I'll just stop streaming and start streaming. Uh, it's a 399 boy in mafek face We got three viewers four viewers Michael pitman 2275 We're not live This is we have seven viewers things is now playing but it doesn't It says streamed six seconds ago streamed six seconds ago. So I don't think All right. I don't see it on here. Oh, it's back. It's back. Start streaming That's fine. All right. Now we're Start streaming now. It says we're live. Okay. Uh, snoop connor that is six out of 75 gold team herbert Pros for a minute. Yeah Cam acres to 99 red rams thick one right here That's gonna be tray mcbride Nice eight out of 10 with the cardinals That's sick Congrats cardinals That is tim jay on the combo. That's such a cool card man Dalvin cook and that is uh, chiante ingram cardinals again bugged out for a minute. Yeah It happens Can't be perfect That is scoring machines matt stafford on the short print very nice.  So it's back up now though Brandon cooks to one two seventy five gold team brady to 149 bucks That is maryon barber That's awesome man r.i.p 77 out of 199 what a legend Yeah, josh, we're gonna go and fix that after Yeah, it was me. I just like put the wrong break in for the the number wise r.i.p maryon barber nice Hey cowboys Gold team derrick henry not numbered Stream has haven't had enough of me Calvin awesom the third that is the 399 uh steelers Greg uh bulch itch to 275 david davis mills to 349 And last pack of box Should have an rpa.  Oh, yeah numbered to 249 Face that is james cook nice bills to 149 Jersey card uh andrew booth jr. 16 out of 50 for the uh Vikings gold team is the vante adams and rock party the 349 Paul Kraus nice there you go vikings 19 out of 60 Kenton certified all-time interceptions leader It's another record. That's going to be very hard to break There's paul kraus's interceptions. What was it? It's got like 80 something or no No, he's gotten way more than I don't know how many it is Wow james cook 34 out of 50 nice patches there congrats bills two james cooks now No, it's more than that forget how many it is three interceptions Elijah Moore to 275 Mahomes gold team ill robinson that is 80 out of 299 going to the giants and Trent mcduffey to 325 chiefs That's elie mitchell dark horses uh 15 out of 50 nick benito Broncos the 149 rookie And base box four 81. Thank you and anthony 81. I appreciate that. So yeah, that's a tough one to break. Yeah That's a career career. Yeah No, that was season So you're in dames price the 149 could imagine dude Christian Watson true true. It's uh 325. This is another one that feels like it's like chrome on the back Yeah, the next closest right now is like debon mccordy. He's got like 30 something Clio Shakir that is 30 out of 75 going to the uh bills That's karson strong to 199 eagles Uh, justin simon certified gamers 135 out of 199 broncos 30 patch there Kenneth walker Aaron donald 29 out of 50 rpa johan dotson nice 83 out of 199 looks similar to what i got. Oh, yeah Yeah There you go football team or commanders nice johan dotson kupra cup gold team uh not numbered Andre kwan brisker bears the 390 This one got a better patch though Does it Mine's very similar though Anra same brown to 349 star courses in the anra same brown That train the broad is really freaking cool Kind of jealous of that no like no collector reason just i think it's a cool card Uh harrison smith 4 out of 5 on the purple That's sick harry the hitman congrats vikings Tim jay on that combo spot 249 is uh isaias filler chargers and last pack of the break Really sick color match filler kyle hamilton And base Let's do a quick recap here guys You can toss it in after yeah, uh jesson simons broncos That's james cook bill's james cook bill's calvin austin steelers tray mcbride. How cool is that man? With like part of the uh the chess piece on there 8 out of 10 cardinals harrison smith the five vikings player one joey bosa and jaylen wall Autos we had johan dotson commanders Kaleel Shakir bills wandale robbins and giants paul kraus vikings george pickens steelers maryan barber rip that's countless snoop connor jags zamir white raiders and donovan people's jones for the bill or browns That'll do it for the break guys. Thanks again for the fill next up more certified


Gambling What's up money geeks mr. V here welcome to another video guys so into this video we're gonna take a look at Draft King ticket symbol DKNG Draft King came out and I think the stock came out at about 20 $20 somewhere around there 18 or $20 and then just kind of like slowly But has actually moved up to about 30 something dollars, which is kind of crazy, right? We would the fact that it is no sports going on so Before we get started guys if you're new to the channel We talk about how to earn money how to save money how to invest and build wealth So if that's something that interests you go ahead and hit that subscribe button any notification bell so you don't miss out on new content So Draft King is like a sport betting company So they do kind of like an online betting platform for people to Place bets on any kind of sport So it's a market that is really really growing in the United States research shows that about 20 in about 2025 that market cap will be about eight billion dollars just in sports betting Right now a lot of states don't allow sports betting But when they start seeing the revenue is that seeing how other states are getting a ton of revenue from that more More states will open up their doors to allow for sports betting. So that's why I'm looking at Draft King So this is what clear I'm not gonna look at any numbers like we normally do here in the channel This is solely just from an emotional standpoint and looking at the future of sports betting People like to be involved with sports. They like to make money. So whether you like it or not Whether you make it bigger or not Give people an opportunity to bet or not people will still do it You go to the bar two friends sit there and say $20 that the guy's gonna score touchdown Just amongst friends and then we you can do that with other people that you don't even know but the platform like Draft King it makes it even better. So again guys, I'm not looking at this from a numbers perspective I'm solely looking at it from an opportunity perspective. So again, that's my point of view And I hope that if you go do your research and see if this stock is something you're interested in So if I look at it from that perspective, how much how much people are spending in in sports betting in Vegas and now Going across the nation. I think Draft King is up to something. So I'm gonna put some money in drafting.  So so I'm looking at it from I'm gonna buy it, but cautiously. I'm not thinking I'm gonna retire from this I'm looking at say, hey, this this there's something in there that I can actually make some extra money And the money that I'm putting in there if I lose it, I'm not gonna sweat So that's just my personal opinion on drafting. So question of the day guys, let me know what you think What do you think about drafting? You think that hey, mr.  Why would you make investments something like that gambling is bad or do you think that there is an opportunity? therefore people to make money because Again, it's just like here in the stock market, right every time you invest and make money One of two things are either that money comes from somewhere, right? It's it's kind of gambling you can you go in with the idea of making money and sometimes the market can crash Right when the market crashes you lose money and if somebody would rather instead of doing the stock market to say I'm gonna go gamble I'm gonna watch a game at the same time take my chances on that game to make money So it's not it's an opportunity And just again, it's you put the same strategy like here in the stock market You put in just what you feel like you're willing to lose and I think that it would be good And if the government can tax it and take that tax dollar and do important things around The country and around the community. Oh, hey, that's a win-win for everybody. So That's it for this video again Is this more of just looking at market opportunity? I'm not doing any numbers. We're not looking at any numbers So you should do your own Personal research before you pull the trigger if you want to invest in Draft King like share Subscribe and as always guys stay safe and stay motivated


It's hard to do anything after listening to Lana Del Rey. I just want to go lie down. All right, but we're going to have class instead. So today we're going to move on to the third unit in the class and start talking about stable storage. This is part of the class where we'll spend most of our time talking about file systems. But today we're going to talk specifically about disks, the actual device that file systems are built to operate. And that's because, unlike the CPU in memory, there are a lot of properties of disks that are things that we need to be careful of thinking about when we design file systems. And we have one of the classes with some fun videos, very cool YouTube videos. All right, so assignment three, DesignDoc and code reading are due Friday at 5. I think everybody knows this. Please don't leave DesignDoc points on the table. I mean, you may or may not want to implement assignment three. That's sort of a personal decision. But there are points for just pretending that you are going to implement assignment three and writing up two pages about how you plan to do it. And that's a generous number of points because we're trying to help you guys out. So don't not do that. Don't leave those points undone. Bring your DesignDocs in tomorrow and Friday and the TAs will be happy to look over them. They know what the rubric is. And you guys have seen the rubric. If you turn it into DesignDoc for assignment two, you've seen the rubric for assignment two. So you know the type of things that we're looking for. Yeah, Kaila? There are five or six questions right before you upload the assignment. I don't know. I think that probably is like a subset of the rubric. Because you get points for not having more than two pages, for example. But yeah, that's a good question. Post it on Piazza and we'll look. But the rubric's not intended to be a secret. But we don't show it to you until we grade partly just because we want you guys to think about how to do it. If we give you the rubric, then what we get are people who have basically just written solutions to the rubric rather than solutions to the overall design. OK. Any questions on virtual memory before we plunge onward? I decided to just skip over the part on copy on right that was at the end of last Monday's lecture. You guys are welcome to go check that out on your own time. It's on the notes. Any questions about virtual memory, memory management before we go onward? OK. So today, let's start talking about disks. And the first pretty important piece of terminology that we are going to use when we start talking about disks is, well, let's introduce a couple of different terms. So stable storage is storage that does not lose its contents when the machine is powered off. This is to distinguish it from what kind of storage? Memory, unstable storage. Memory registers anything that's going to lose contents when the machine is powered off. At this point in human history, we have several different types of stable storage available to us, several different types that we'll talk about in this class. And there are other kinds, obviously. But here are the ones that we care about when it comes to file system design. So hard disk drives, HDDs. These are stable storage that consists of typically a spinning that's a magnetic medium. It's a spinning drive. It has moving parts. And HDD stands for hard disk drive. And that was a great acronym until these other kind of drives came along, which we refer to as SSDs, or solid state drives. The big difference between flash drives and hard disk drives, well, you guys are computer scientists. So a couple of things. What's not on this list? What other types of storage media are not on this list? Yeah. Tapes. There we go. Got a really retro answer here. But there are organizations, including UB, that still do backups to tape, believe it or not. Yeah, now we're going even back farther. Floppy disks. Whoever used a floppy disk ever? Weird. You guys are not as young as I thought you were, apparently. Or for whatever reason, you guys all grew up in a computer museum together or something. I don't know. What else? Punch cards? No, OK, whatever. That's for programs anyway, not for storage. There's other types of storage you guys use on a regular basis. What's that? RAM is not stable. RAM loses its contents when I'm powered off. Paper. Yeah, I guess you could technically print out the contents of your email inbox. And I don't know how you would get them back into the computer. You need some sort of fancy OCR stuff. I'm thinking of something you use with a computer. Well, maybe you guys actually, it's possible. And I'll have to admit, I have not handled one of these for a while. But my computer is still ready. Yeah. CDs. CDs, DVDs. How many people use CDs and DVDs anymore? Oh, yeah. Well, you guys got to get to the future. Streaming is awesome. Yeah, I was thinking the other day I was going to go to Red Box and get a DVD. But then I was like, I don't even have a DVD player on my computer. So that's not going to work out very well. All right, so these are the kinds we're going to focus on. Because these are the things that we build file systems on top of. And do we build file systems on top of some of these other types of stable storage media? Of course. But for a variety of reasons, those file systems are sort of less interesting than these. And these are the dominant form of media, including the most personal computers today. So what's the big trade-off between these two guys? If you guys have bought, well, that's one of the trade-offs. OK, speed. So we say speed is the trade-off. Which one of these is faster? SSD is quite a bit faster. But is another trade-off? Yeah. Yeah, so in general, hard disk drives are bigger, slower, and cheaper. There's also a form factor consideration here. I don't know if you guys have ever taken apart one of those solid-state drives. But it's kind of amazing. It's this 2 and 1 half inch form factor. But then there's nothing inside. It's mostly air. And there's a few microchips sitting there that are providing all of the storage that you paid an exorbitant amount of money for. So yeah, hard disk drives, bigger, physically bigger, slower, and cheaper. This was, well, projected for 2012. I guess I could have looked up the real number, given that 2012 is three years ago. But there's still this gap between the price per gigabyte for flash and for hard disk drives. And that's why people are still buying hard disk drives. That's why companies are still using hard disk drives. It's just that, particularly when you start to really think about bulk storage, that's what people are still doing. And yeah, if we ever were talking about anything, you guys are confused about what type of storage we're talking about, please ask. Because the differences between flash and hard disk drives lead to very different system designs. So I want to sort of return to one of the questions that we posed at the beginning of the semester. So we had this question of why studied operating systems at all. And I hope I answered that question at least somewhat. But of all the things to study in operating systems, this is the thing where you should be really scratching your head. This feels very retro. Let's study spitting disks. Because look, at some point, there was a prehistoric version of me up here who was saying the same thing about tape. Well, we still need to study tape because tape is still with us. And it will be with us for a few more years. But that's not really true anymore. Nobody studies tape drives. So why are we still talking about hard disk drives? And why? Because flash is the future. Well, admittedly, there's still a lot of hard disk drives around. You guys will probably continue to encounter them. Partly that's because they're cheap. And there's aspects of file system design that are changing.  Because hierarchical file systems don't seem to be helping you very much. I mean, how many people regularly use spotlight or some search feature on their computer to find things? Instead of having a very carefully thought out hierarchical directory structure that starts in your home directory and is incredibly well organized into different directories, how many people still do that? Yeah, OK. Maybe we're at a tipping point here. But when you look at local storage, we still have these hierarchical file systems that underlie this. So that's still how things are actually stored and organized. And but there's also, I think, a lot of ideas from this space that we want to talk about. And that's really the reason to study file systems. I mean, look, I am not going to try to claim the detailed understanding of how the fast file system implemented in the 70s is going to help you in the future. But there are some really nice design principles. And there was an enormous amount of time and energy spent by the systems community into designing file systems and to designing file systems that had robust properties given some of the challenges of the underlying device. So that's really what's fun here. And I hope you guys will enjoy studying this even and learn something from it, despite the fact that no one is going to claim that the future is in spending disks. You've got researchers that are claiming then the future will have data centers that don't even have stable storage at all. Only memory, because they're super fast. But in the meantime, we still have some stable storage around. We still have some spinning disks around. And there's a lot to learn from studying these file systems. And so I hope you guys will agree once we're done that this was a worthwhile exercise. All right. So before we can talk about file systems, we have to talk about disks. Because a lot of the things that make file systems fun are based in the things that make disks irritating. Irritating properties of hard disk drives. Old spinning drives. So parts of the disk, the platter. The platter is the thing that where the magnetic medium is mounted. That's where data actually gets written and deposited. Most, I don't know how long this has been true. But at this point, platter is going to have data on both sides of them. So a hard disk drive consists of a series of platters. The spindle is the drive shaft. That's the thing in the middle that's rotating the platters around at a variety of different speeds, depending on what class of drive this is. If you look at server drives, they can move quite rapidly. And then the head is the part that's actually doing the heavy lifting here. So the head is the part of the drive that's reading and writing data onto or off of the platters. And the head is positioned, depending on where the head is positioned, that controls what part of the disk you are actually reading or writing from. So here's a picture. I've got my platters here. It's hard to see, but there's a stack of them. The spindle is in the middle. The heads are mounted on an arm. So when you guys hear the disk running, you can probably hear a hard drive. You can hear the rotation. There's a certain noise that that makes. But that sort of grinding sound that the disk makes, that's this. That's this moving around. I'll show you a video of that in a minute. And then there's all this other stuff that you don't really care about. So you can imagine the engineering challenge here. These platters are, in order to increase the amount of data on the disk, what we've done over generations of hard drives, it's not like hard drives got bigger. You don't have a computer with a massive hard drive. In fact, when you were a kid, you were my age, you saw the drives getting smaller. We went from these 8-inch disks to the 5-inch disks that held 10 times as much data to the 3 and 1 half inch disks that held 100 times more data. So essentially what was happening is we were getting better and better at writing smaller and smaller pieces of magnetic data onto these platters. So the denser we can write data onto the platters, the more data we can store. And other performance aspects of the disks improve as well for reasons that you guys will hopefully understand by the end of class. However, that means in order to read or write a particular byte of data or a particular block of data from the disk, I have to position those heads over a tiny, tiny, tiny area. I have to be really precise in terms of how I position the heads. On the other hand, in order to make performance good, I need to move that arm quickly to get to different parts of the disk. So it's pretty impressive that this stuff all works, period, as well as it does, even if it doesn't work as well as we might like. All right, so when we talk about locations on the disk, there are three different places. I have a track. So think of a track is one lane, quote unquote, on the platter. It's a circle on the platter from the same distance from the spindle. And so if I don't move the heads, it's the path that a head will follow as the disk spins. A sector, so a sector resembles a slice of pie that's come out of the platter. I'll get to the diagram in a minute. And the cylinder is actually, imagine that I took a soup can and just sliced it all the way through the disk. It's essentially all the tracks on every platter that are at the same place. And the reason why cylinders are interesting is it's all the data that can be read or written from the disk without moving the heads. Because remember, there are heads, or don't remember it, I haven't told you this, there are heads between every platter because I need to be able to read or write from every platter. So that disk arm that you saw right here actually has parts that go through in between every platter on the disk. And there's heads mounted everywhere so that it can read or write from every side of all the platters that are part of my disk. So here's the diagram. Probably we're envisioning this track. The cylinder is this, again, the sort of vertical projection of those tracks through all the platters, and there's a sector. All right, so you can find all sorts of cool videos of disks online, right? And here's one of them. So before I show this, what part of the disk is this? It's the arm, right? This is one of the heads. It's the head you can see, right? The other heads are in between the other platters. Here are my platters, and this is the spindle that's driving the whole thing, right? And this is going to show you, my favorite part of this video is it inadvertently shows you how messed up early Windows file systems work, right? So that's a little bit to enjoy, and maybe we'll come back to it later, right? All right, so a little bit of advertising. All right, so I'm gonna fire up the disk. It's not me, by the way, this is some guy on YouTube. Actually, let me put the sound on. Cool, you can hear it. All right, so that's deletion. Copy in between two files. So what's cool here is you can kind of, you can see that those files, you can sort of see where those files are located on the disk, right? You can see that the disk head is, when I deleted, so sorry, when I deleted the folder, that's what's so messed up about Windows. Why is it so hard to delete a folder? It's not that hard to delete a folder. Other files systems do that way better. There's no need for so much disk activity in order to delete a folder, but anyway, you saw that, so when I deleted the folder, the arm was sort of flying all over the place in this area. When I do copy and paste, you can sort of see, it's hard to tell, but it's localized over a couple of places, right? So it's like one of the files is over here, the other file is over here, and in order to copy and paste, I have to pick up data from one part of the disk, move it into memory temporarily, and then write it out into a different part of the disk. So you can sort of see this happen. Quick format, impressive. All right, any questions about this? So again, you can't see it, but there are, this disk maybe has like eight platters, 10 platters, some number, and that arm, if you could rotate it, you'd see that arm looks like this. So it looks like a comb, and it's sort of sliding in and out of the gaps between all of the platters on the disk. Yeah, yeah, so the arms on this disk, and I suspect on most 99.9% of disk, the arms are all synchronized, right? So it's one arm, right? And what that means, of course, is that the heads are always at the same location on every platter, and that's why the cylinder is so interesting, right? Because the cylinder is all the data I can read and write from the disk without moving the heads, right? To every platter, that's a great question, yeah. So the heads, it's one actuator arm. I mean, again, it's hard enough to throw that arm as fast as you can across the disk and then settle it rapidly over a tiny, tiny little track. It's hard enough to do that with just one arm, right? Doing it with eight would be really a nightmare, yeah. Why is it shaped like a triangle? I have no idea, right? I wish there was, do we have any mechanical engineers in here? Answer this question. I don't know, because it's a great question. I have no clue. Yeah. Wait, hold on, did someone answer the triangle question? Yeah, that's probably true. I think he's right, because I think if it was small, it would wiggle too, right? Yeah, because remember, it needs to be rigid, right? So imagine you take that arm and you throw it all the way across to the disk and then you try to stop it. If it's too thin, it's gonna sit there going, so it's gonna be a little woozy from that long trip and they just take a while to stabilize. You can't see it, but it already takes a while to stabilize, right? That's one of the slowness involved with the disk is actually waiting for that arm to stop shaking. But it's shaking at a level that you can't even see, yeah. Isaac, I don't know, I have no idea. That's one of the mysteries of this video to me, right? Why does the Windows file system require so much IO to delete a folder? I've never understood this.  It's like, oh, I'm gonna throw that folder in the trash, right? Better go have a coffee break, because it takes like 20 minutes. Why? I don't know. There's really no reason for that. Unless it's like cleaning up the contents or like you set up the disk in some secure way that it needs to overwrite the files, but there's really no reason for that to happen. Yeah. Don't act separate from the disk. Oh. So maybe it's actually, yeah, maybe it's actually. Actually, you actually, you don't. No, I know that, but okay. Let's come back to this later. That still does not require that much disk activity, right? I will maintain. It's a great observation though, yeah. I have no idea. I think I read it was NTFS. Yeah. So, yes, in general, and now we're getting to like electrical engineering aspects of this I don't fully understand, the, all the heads can be active at once, right? And in theory, some of them could probably be reading, some of them could be writing. At some point, I think the bandwidth back and forth to that might start to exceed, it might hit, you might hit other bottlenecks, right? You might outstrip the buffer capacity on the disk or you might outstrip the interface capacity, right? But yeah, and if you, and this is something that we'll come back to when we think about how to lay out files for a file system, right? Because ideally you wanna use all those heads at the same time, right? Because otherwise I have to do a lot more movement to get the same amount of data. What's that? Yeah, yeah, yeah, yeah, yeah. Again, I think there's something deeper, a deeper problem at work here. Yeah, so this is a great observation, right? So there, I don't think I go over those in detail in this class, but there are algorithms that people have designed to essentially determine the order in which the disk head should move, right?  So hopefully this video sort of points out that spinning disks are quite distinct than the other parts of the system that we've discussed, right? So disks move, right? Discs are, and again, and maybe, you know, the disks are the last part of your system that will ever move, right? The next system you buy, if it isn't already, may be a completely solid system that doesn't move. And I have to say, it's awesome, right? Particularly when you drop it, it's like that, whatever, right? I have dropped that laptop so many times and I just feel good every time I do, right? Because I think about how I would feel if it had a spinning disk in there and it was potentially toast, right? Yeah, I know, I have one of those, too. If you drop it enough times, you'll catch it on a bad day, right? Yeah, but that also makes a great point. Drives have tech, newer laptop drives, I shouldn't say newer, like 10-year-old laptop drives have technology where they would actually detect that the drive was being shaken or falling and they would do things to try to protect it, right? Because I'll show you in a few slides what happens when this goes wrong, right? But imagine, again, you have these heads that are flying around the disk, like nanometers away from the surface, reading and writing data, and just imagine what might happen if you like whack the disk, right? Bad stuff, right? So, and disks are slow, right? And this is sort of a consequence of moving, right? Having moving parts makes you electronically slow. You are not gonna outrace an electronic circuit with anything, right, regardless of how fast it is. The last part and the part that I think makes this sort of fun to talk about and file systems fun to talk about is disks are really programmed by the and controlled by the operating system in a way that other parts of the system are not. So that allows us to do a lot more software engineering on top of disks, right? For example, operating systems now maybe they have support for some of these things, but you can't, you know, you can unplug a hard drive from your computer. You can plug in a USB hard drive and that USB hard drive just sort of shows up and you can use it and you can unplug it later. You can't do that with a core, right? I can't buy my new i7 core and like plug it in, right? And then unplug it later when I wanna move to a new machine. That'd be very cool, right? But yeah, I can't do that, right? Same thing with memory. There are probably systems now where you can hot plot memory, but still like, it's not something you guys normally do, right? You gotta reach in there, grab some sticks, move to another machine, machine gets faster, put it back later. So yeah, because of how disks are integrated into the system, there's a lot more of a software challenge here. And again, I mean, one of the reasons to talk about disks despite the fact that they're a little bit of an old technology is the fact that so many smart people spent so many decades working on them. And in a lot of ways, some of the techniques that they came up with are still with us and have been applied in other areas. Okay, so, disks move and therefore disks are slow, right? And this is particularly true when you compare it with sort of electronic time scales. When you think about the amount of time it takes for electrons to flow from the RAM to the cache or into a register, right? Who cares how that happens, right? It's electrons flowing through copper, okay? On a disk, I've got to get this aluminum thing to move, right? There's no way you're gonna win that race. The other really interesting property of, all right, I should have guru do that every day. All right, that was awesome, actually. What's up? I don't know, later today, yeah, this will be on there. Did you pause it? Okay, good, okay. I hope I handled that well. I mean, it's sort of awkward, right? Okay, well, I have my beads now, so it's been a good day. Okay, so, disks fail, right? So, disks like our friend move, and disks like our friend also fail. So, yeah, and this is actually something that file system designs spend a lot of time thinking about, right?  But, of course, the thing that you bought the disk to do is to store things reliably. And so, if that property of disks causes the reason that you're using the disk to fail, that you're gonna be sad about that, right? And disks can fail in two ways, right? So, one interesting thing about hard drives is a lot of hard drives ship with parts of the disk that already don't work, right? You guys probably don't know this, but, all right. A little redux. Shall I just go home, right? That just made, that just made my day. So, the disk in your computer, if you bought a spinning drive, one of the things that might have done at the factory or the first time it powered on is checked itself, right? And discovered, hey, I've got some broken parts, right? There's a couple sectors here and there that don't work. And so, what does the disk do with those? Ignore them, right? Don't use them. And this can actually happen over time, right?  That could be caused by just a sector going bad, right? For whatever reason, that part of the disk stops working. Hopefully, you didn't have any super critical data there, maybe a file or two vanished and you just went on with your life, right? However, yeah, so sectors can fail over time and the disk can also fail catastrophically, right? So, this is what we were talking about before. There are plenty of ways to break a disk. You could take it and just throw it on the floor and smash it to bits. But one of the more interesting ones is something called a head crash, right? So, a head crash takes place when there's some sort of violent event that causes the heads, which again, the heads are designed to just float over the surface of the disk. If you suddenly jolt them, what they're gonna do is they're going to crash. They're gonna crash into the surface of the disk and they're going to take off plenty of material on their way, right? So, you've been spinning that disk as fast as possible. Suddenly, you push the head into it and you lose least the whole track. You've destroyed the platter and I was hoping it was that guy again, but somebody different. And yeah. And so, I don't know if you've had this happen before. The sad thing is the computer continues to work for like an arbitrary period of time. So, you can sort of like sit there and look at it and be like, bye-bye, right? You were a good computer. I enjoyed you and now your days are over, right? And then the thing freezes and you can never boot again, right? I've done this to machines. I know exactly what it's like. So, okay, so let's look at this. This has got a cool video too. Yeah, so check this out, right? So, this disk doesn't have a racing stripe, right? Despite the fact that that's how it looks. This is not normal, right? Your disk doesn't have like a two-tone color scheme. Oops, sorry. Yeah. Yeah. So, in case you didn't see the thing with the filters. I assume that this disk spins in a counterclockwise direction. And so, the filter here is designed in case there's any sort of foreign material that gets in the drive, like a little piece of dust or something. You know, the force of the disk is going to throw that off into this channel and hopefully it ends up back here behind this little dinky filter where it won't end up back in the disk. And so, his point about the filter being dark was that when this head crash occurred, all that material that was scraped off by the heads got flung out there and is trapped in the filter as well. So, again, a classic example of why you should back up your data. All right, so, and again, I mean, the thing that's cool about disk failures was that the disk was one of this early component that had this property and it was really mission critical for the system to work. And so, a lot of people spent a lot of time thinking about how to make this work, right? So, maybe this year we'll actually read the raid paper. It's a pretty cool paper and it spawned essentially an entire industry, which is not normal for research papers. But so, there were a lot of interesting ideas about how to improve fault tolerance with disks. And a lot of them, even if they're not necessary with solid straight drives, have sort of survived, right? They survived, they flourished, they moved on into other areas. Their ideas that were used to protect other systems and do other things, right? So, a lot of ideas that started in this area have lived on, okay? The final problem with disks is that disks are slow and disks have the potential because of how slow they are to bottleneck and slow down many other parts of the system, right? So, and operating systems play, you know, we play some of our normal games with disks and we'll see this in the example file systems that we talk about to try to address the slowness, right? So, what are examples of some of these, our usual tricks? What are some things that we do to make, to try to improve performance? What are some of the system design principles? Yeah, use a cache, right? That's one thing. What else? We have other tricks. Yeah. Yeah, so layout, right? Figuring out where to put things on the disk, remember, the disk is a physical device and so where things are matters because I need to go where the data is, right? I would say that's an example of what design principle that we've tried to apply in the past. Use the past to predict the future. Know where things actually, the best place to put things is for the next pattern of accesses but I know how things have been used in the past, right? I use a cache and then I also have places where I can do some procrastination and we'll see this come up when we look at log structure file systems as well. And the other, in case I haven't convinced you that file systems are sort of fun yet, despite being sort of antiquated, is all this stuff's done in software. So with memory, for example, and the way that the processor hides memory latency is super cool, right? And if you don't know about out of order execution, you should find out about it because it's awesome. How many people know about that? Oh, look it up. It's super cool, right? So believe it or not, the order in which instructions are being executed by your CPU is not the order in which you executed them. Modern CPUs play all of these games internally to try to minimize memory latencies and it's super interesting and super off topic, right? So not something I'm going to talk about but you should learn about it because it's cool. But the point is that that stuff's hidden from the OS, right? Because memory latencies are pretty short and so getting the operating system involved and trying to address memory latencies is not really very effective. That's something you have to do in hardware. On the other hand, with the disk, the disk is so slow that the operating system is really who gets to try these things out, right? So when it comes to making memory look faster, that's really something that the processor does internally. When it comes to making the disk look faster, that's something that you guys get to play with in software, right? Or if you were a file system designer, that's something that you get to address, okay? So let's talk about reading or writing data from a physical disk. So what are the steps involved to accomplish this? And we'll think about the speed required for each. So what's the first thing that has to happen? Before anything else takes place? Before anything moves? Before anything... What's that? Well, it's actually not an interrupt, right? Interrupt is potentially how this is all going to end, right? But how is it going to start? Yeah. Yeah, I need to issue a command to the disk, right? The disk is a device. So in some way, based on some interface, and again, the details of those interfaces are uninteresting, and not something we're going to cover, but I need to be able to instruct the disk what I want, right? I need to tell it, read this byte, and it's usually not a single byte because it's too small of a unit. So read this block, maybe 256 bytes, maybe 512, at this location, right? So there's an addressing scheme that the operating system has to know about the disk. Like how do I address things on the disk?  And that goes out over the interface, and then when it reaches the disk, the disk has to figure out, based on its own internal geometry, where is that block? And that allows it to do several things. First of all, it has to pick which head it's going to use, right? Because not every head can read every block, and in fact, none of the heads can read every block, unless you have a very old and very small disk. So I have to choose the head, and I also have to figure out where to position the arm in order to capture that data. The next thing that needs to happen is the drive has to move the heads over the appropriate track. Once that's happening, after that happens, I have to wait for the heads to actually settle to the point where the heads are usable. So if the heads are still vibrating a little bit, they're going to be picking up data from multiple tracks nearby, and I can't read data at that point. So I have to wait until the heads are stable. Then I have to wait for the data I want to come underneath the head, because the disk is spinning, and I'm only reading a small part of the data at any time. And then I need to read and transfer the data back to the system. So first of all, what's the slow part? Yeah? The seek and settle. That just dominates everything else. So these two. The only other physical part here is the rotation time. To be frank, it doesn't really improve that. I mean, that's why you don't have disks that are at 100,000 RPM or something. If you look at disk capacities and if you look at disk speeds, disk rotational speeds have rarely been a selling point for disks and stopped improving at a certain point. Because they just don't really matter that much. It takes so long to get the heads to the right track that once I get there waiting for the data to come around just doesn't really add much latency. So the seek and settle time, this is my problem. Over time, interconnect speeds have gone up. I mean, I have had a series of faster and happier disk interconnect interfaces. I don't know how many of you guys ever tried to build a machine using those old IDE cables. And it was terrible, because they're this thick. And you have to wrap them around stuff. And you know, like, sad as, like, thank you. It just made things a lot easier. But certainly, the bus, just getting data back and forth to the disk, that's something that we've thrown some engineering and some hardware at. Seek times, where do we think those have gone? Nowhere, really. They've improved. They've improved a lot. But there is no Moore's law hiding here. These have certainly not improved at the speed at which processor core density and other types of the system have been improved. Hortation speeds, again, these vary, but they're just not really, they're not the bottleneck. And of course, again, the power required to spin a disk at that speed starts to become an issue. So at some point, there was an interesting moment in system design. And actually, this led to some file system designs that we'll talk about, or some design choices that we'll explore. And I remember I was working at Microsoft at the time. And people, they were really terrified by the sort of intersection of these two trends. So one trend was hard drives got bigger, like, quickly. And that was partly due to density, but partly due to just adding platters and making the disk bigger. So disk capacities got bigger. I remember when I was in college, I had a 20 gigabyte hard drive, and I thought that was huge. That was where I was going to store my music collection that I would have for the rest of my life. Now it's like, I don't know, and now you can get a 20 gigabyte thumb drive. It's just the amount of space you guys have. Now you can buy one and two terabyte drives for probably less than I paid for that 20 gigabyte drive. So really the market is sort of fed consumers with a steadily larger and larger disk. The problem was that seek times were really making it difficult for disks to keep up with the increasing capacity, and it was causing the disk to become slower and slower relative to other parts of the system that were getting faster. I mean, CPUs were getting faster. People were putting more memory in. And so Microsoft was terrified of these big, slow disks, they called them. And the impact they were having on system performance. And they did some clever things about this. This is just a cute little graph showing you the evolution of capacity. Now this ends in 2006, so again, it's a little outdated. But this is a log scale. This is not linear. So essentially a linear curve here is an exponential increase in capacity over time, which is pretty fun. Here's a terabyte. And these are 3 and 1 half inch form factor drives, not really sort of consumer style drives. But now this line has sort of gotten to the terabyte, a multi-terabyte point as well. So it's kind of a neat story about how we gave people so much storage. What they do with it, I don't really understand. And again, going back to the idea of file systems and software, the low level disk interface is really limited. Disks force me to read and write 512 byte blocks using this very limited address scheme. All the things you guys think about when you think about disks, file systems, file names, file types, all this stuff is all layered on top of that in software. Reliability, check pointing, all sorts of things. Why one file system can move files quickly and the other one takes a lot of time or delete things? These are all software properties, because this is all done in software. So the file abstraction, which we'll start talking about next time, is really something that's implemented entirely in software. And so it's kind of a fun thing to think about. And another thing to point out is that this is why there's so many choices when it comes to file systems. Other parts of the system, for example, even when you start thinking about the memory management data structures that we just finished talking about, those are constrained by properties of the hardware that the operating system has to meet. Here we have this very low level capability of reading and writing 512 byte chunks. And that's created this ability for people to write all these different types of file systems that this list is out of date. And still you have new file system designs that are shipping and new people who are still working on this problem. There are still people. There are people that started working on file systems in the 1960s and are still working on file systems today. And still solving cool problems. There are file systems that are still shipping with really cool features, where you're like, ooh, I wish my file system could do that. So this story is not, in any sense, over. And again, this is why a lot of systems people, not necessarily me, but a lot of them have a soft spot for file systems, because this was a big, hot area in systems research for a long time. And I would argue that's pretty much over, but still persisted for a long time. There's some really nice things to talk about. So just as a coda, and I want to come back this year to talk about Flash a little bit before we move on as part of this unit, but Flash, right? So you might think Flash is going to solve all these problems, like it doesn't move, it doesn't break. Yeah, so except that Flash has some issues, right? So most commercially fashion available Flash chips have this process, this problem where in order to write a byte of data, I have to first erase this huge piece, like 32K or something, right? So that's interesting. That makes things a little more interesting as far as how it's done out of the system. And here's a fun fact about Flash. Flash wears out. Have you guys ever found this out, or had a smart phone that stopped working after a couple of years? For real, right? I mean, Flash has a limited number of cycles that it can be read or written. And once you exceed that number, it's done. And so this has created all these interesting opportunities for what they call wear leveling. So your Flash drives that you use have software on them that tries to make sure that the entire Flash chip fails at once. So it tries to spread out accesses to the chip in an intelligent way to make sure that when one part of the chip starts to fail, the whole chip is essentially used up. Otherwise, your storage would have this interesting property where it would shrink over time, which most people don't really like. My disk is a little smaller today than it was yesterday. So yeah, the biggest problem with memory, of course, is that it's volatile. So when I power the machine down, the contents are lost. The other problem is that it's expensive compared with these. If you look at the price per byte of memory, higher than the other two alternatives. But you're right, that's not stopping some people. So there's a project called MemCloud that you can go look up where people have designed a cloud system that has no storage at all. It's just memory. What's that? Well, you'd use it for backup and stuff like that. But during runtime, it doesn't use storage for anything. And again, you understand why someone would want to try to do something so insane. It's because it's super fast, super fast. And with the cloud system, you never shut it down anyway, so who cares about the volatility? So next time, we'll talk about file systems. And we'll talk a little bit about scheduling algorithms for hard disk requests.