All right, we're going to spend this morning up until lunch working on AMR. We're going to go through what's out there and how to do the analysis, and then we're actually going to play a bit with some beta level stuff, sort of see where the field's going as well, stuff you'll see in the next year. So learning objectives, I'm going to do this out of no glasses. So we're going to review the available tools out there. There is a lot. There's a diversity. It's sort of a chaotic time in the field. We're going to look at our own resource, the card database. With that, we're going to look at the diversity of mechanisms. This is really the trouble of doing AMR bioinformatics. It's a very diverse type of mechanistic thing. We're going to do some analysis of genome, some clinical isolates, and then we're going to look in the challenges of metagenomics because a lot of you are going to start generating metagenomics, whether it be clinical or environmental. So background, no real surprises. Audience, we're losing this battle. We're in the losing phase in here. It's essentially evolving resistance faster than we can bring drugs to market at this point. The UK did a review on antimicrobial resistance. So right now cancer is sitting at around 8.2 million a year, AMRs and fatalities, AMRs sitting around 700,000 mortality a year. By 2050, AMRs predicted to be about 10 million annual deaths and about 3.5% global GDP. So this is, we're losing and we're losing badly on this war. But it's not like we're seeing things we haven't seen before. It's not like brand new pathogens that are coming at us. These are pathogens we've been fighting for decades, right? So tuberculosis, making a comeback of completely drug-resistant strains, gonorrhea. So six years ago, one high school in UK at 14 cases of untreatable gonorrhea. Now it's in Hamilton, Toronto, Detroit, you name it, it's all around. Pseudomonas, basically every 10 years, just like staff. We tend to lose a drug class of antibiotics and treatment of pseudomonas infections. And then of course entrobacter. This is all exacerbated by the fact that while bacteria are evolving resistance to everything we expose them to, we're not finding any new drugs. The drug discovery pipeline has shriveled up. In fact, there's only one company really putting real R&D money in antibacterials. All the easily found compounds have been found, right? So you spend tens of millions screening environmental isolates hoping to find a new drug. You keep finding streptomycin again, right? We keep finding the same drugs. So very little money's going in this, very little, few investors. It's really becoming a government endeavor, not a for-profit model if we're going to bring new antibiotics. But we haven't found a really new antibiotic class since the 80s, right? We've had one interesting drug in the last couple of years that's phenomenally different. So even if we keep finding same compounds of the same class, bacteria already know how to evolve resistance to them. What we need is new classes or maybe something completely different from antibiotics. So how does it happen while it comes from misuse, overuse of antibiotics, whether it be at the clinic or in the farm or environmental settings? It's all about population biology. Every population bacteria has a tiny fraction that inherently have a mutation or something that causes resistance. You use antibiotics, you select and they survive. From what you end up as a population of resistant bacteria if you don't use your antibiotics enough or you're constantly using them as a gross supplement in a farm environment. But what's worse with bacteria is once they have them, they often use conjugation or plasmids or other methods to transfer them to other pathogens. So what starts as a Klebsiella infection quickly becomes an infection that drug resistance in 20 different pathogens and they tend to get residents in populations. So the key thing is that it's really all a genetic undertaking in bacteria. The targets can be anything from the cell wall to the information machinery of the cell. It can have to do with biochemical pathways like folates or the membrane or even protein synthesis. Antibiotics cover a large range of the cell but generally the cell has a way of coming back to it. It can protect the target, it can close the membrane, it can metabolize the drug. There's lots of things it can do and these are all genetically based resistance. The real problem is how fast this occurs. So this map is for NDM-1 beta-lactamase. Now we only have two drug classes left, two drugs of last resort with carbapenems and polymixants like Calliston. So NDM-1 appeared in 2008 and took out one of those classes. We lose our fourth generation carbapenems. It actually was one individual, a Swedish gentleman of Indian descent visiting India got ill, gastrointestinal disease, got reasonably well enough to be flown to the U.K. undergo treatment. The infection, it picked up a gene from Lord knows where. It was Klebsiella and E. Coli. It picked up this gene NDM-1 probably out of soil or water and it completely knocked out this drug class. And from there it broke out into the hospital in the U.K. and now in every country, this is old data, but every country that is in color has issues with NDM-1 and I just saw my first in Hamilton in clinical sequencing. So we're only talking 10 years. And in that 10 years, I just checked our database yesterday, it went from being known as Klebsiella and E. Coli to being known in 20 different pathogens. So this is a rapid evolving system. So we need to move fast, we need to be informed fast. So which regimes are in Canada? Which ones are moving about? Which ones are a threat? This is why we do bioinformatics and genomics levels to answer this question.  He got made fun of for this statement, there are known knowns, there are things that we know we know. There are known unknowns, that is to say things we know we don't know. Then there are the unknown unknowns, the things we don't know we don't know. And he got mocked for this, but this is actually black swan theory. How do you prepare for the unexpected and the disastrous, right? And this is the world we're living in and we're all doing this. So you're a public health lab, you're working with the known knowns. You have assays, whether they PCR or sequencing as a method. And you're looking at genes and pathogens that you are tracking, a very small suite. There are thousands of resistant genes, we only PCR for the most common threats. So we can do surveillance for the known known. But if non sequencing methods, PCR and the rest, it's a pretty limited battery. The known unknowns are all the other genes, resistant genes that have been published and characterized in the literature that we're not routinely screening for. Maybe we don't expect them in our community, though an airplane can change that in the night. Or maybe we just can't afford to run that many assays. But we also know there's natural variants occurring. The gene that's described in the paper, there's probably sequence variants out there in nature that we need to think of that might have slightly different functionalities to them. Maybe they're a little more effective, a little less effective. So we know those are known, but we don't know what they look like because we're not looking for them. And then we have the unknown unknowns. We have the emergent threat. So NDM1 is a good example popped out of somewhere into a clinical setting and became a global threat. A few years ago, MCR1 came out. So we talked about NDM1 taking out the carbapenems. Well, MCR1 takes out the polymixin. It's like Calliston. And about a year in a gaffe ago, we had our first patient with a plasmid that had both, and she was not savable. There wasn't a drug on the planet that could save her. We lost both. The drugs were last resort. So the unknown unknowns, thankfully rare. We only have to find them only maybe one or two a year, but they will quickly become a massive public health problem. We often find them too late, while after we have patients or animal problems, and we can't figure out the mechanism. Six, eight months of biochemistry and lab work till we figure out what's going on. So the advantage is that with sequencing, genes can't hide. We have a chance at surveillance to take a look at this data. And the real advantage is that this is a market force we can take advantage of. Sequencing cost is plummeting. It's getting cheaper, higher throughput, and the devices are getting smaller just by market forces. So that technology is moving into we can afford it even at the local clinic level. So in Anipore, we use it at a clinical level. They'll look at clinical positive in there. It's going to come to the day where we can embed a sequence at a northern clinic or even at the back of a pickup truck in an outbreak in Haiti again. So we can take advantages, and we need to prepare for it. Essentially, whatever you're doing, this is your pipeline. You sequence using one of the many platforms, Illumina and Anipore or PacBio, you name it, even old school Sanger in our case. You need to compare it to reference sequences to make sense of it. And you predict the resistome. I'll use both sides here, actually. So the resistome, this is the catalogs of genes and mutations that may cause resistance to it. And this is genome. The real tough one, the holy grail, is to go from there and predict phenotype, exactly what drugs will not work and why and to what degree in this cell. If you want to learn more about that question, spend some time talking with Kara, who there's PhD is on that end of the site. This is the holy grail one we get to, and that's where you get to machine learning and all the more interesting sides of computer science. So that reference part, that's what my lab's really fundamental job is. We do lots of other things, but really we work on the reference side. So we built the comprehensive antibiotic resistance database. This is an expert curated molecular reference database. The sequences, the mutations, the regulators, everything that undergoes in different pathogens around resistance. So when you get sequence data, whatever it's quality or quantity, you can compare it to the card and figure out what did I just see, what's in my isolate. It really has a couple themes. You can browse, so it's a knowledge base, we'll do that. You can perform different analyses, we'll definitely do that today. And the data comes in many different download formats, so you can build your own pipeline. So you can see it used in ARIDA and other platforms on that. We also do surveillance, so we routinely, we're gonna talk about this data, surveil many pathogens, actually know which genes and variants are out there. So what it is is a high quality sequence data based on the molecular basis of AMR. It is expert curation, so there's a full-time human curator and lots of junior curators, but it's also guided by text mining. So we wrote text miners to make sure, every month we look at PubMed to make sure we didn't miss a paper or miss a mutation. It has breadth, so that means we try to cover everything. The word comprehensive is in there, so we gotta do it. Every type of mechanism, whether it be plasmid boron or a mutation in a gyraase, an intrinsic regulatory factor, things like that. On top of that, once we build the reference data, we do work on software and analytics and work on the discovery zone in particular of emergent threats, but underneath it all, we really work on data harmonization. So we've heard a lot about ontologies, right? How to standardize and share this data. So CARD is built on an ontology underneath, and we have a commitment. Essentially, unless it's a really busy month, we release every month. We update, even if it might only be one or two genes on the slow months, but we're always cranking out data, we have this commitment to keep it going. This is an evolving threat. It evolves on a daily basis, so this is not like traditional curation, like a human genome. You sequence it one and curate it forever. Our, the ground changes underneath our feet every week in this battle. Quick bits of what it looks like. So this is a shot of the ant-6, aminoglycoside resistance change. You're not meant to see all the details, but this is an AMR gene family, and you can see there's all tons of classification about the details of the mechanism and the details that drugs of interaction interacts with. And there's terms saying, you know, which drug classes that it's known to interact with. You have this high level classification, which you can use or you could not use, depending on what you need. But you can zoom into an individual gene within that family, so the ant-6, 1A, and you have an ontology term. Here's the ontology assessment, it's an arrow. There are known synonyms. The language is horrible in this field. There's synonyms for everything. There is a written definition. It tells you what gene family it's in, what drug classes interacts with, what resistance mechanism, and even what pathogens it has been observed in at the genomic level and whether it's seen in a genome, in a plasmid or a whole genome shotgun effort where we can't tell the difference. If you clicked on any of these buttons, you would bring up that higher level information. It tracks the key publications, not every paper on this. It's really the ones that define this gene when it was first studied. And down underneath, you can find the sequences, the DNA and protein that define this gene. We'll talk a little bit about the model context. So you have this massive knowledge base. Underneath it all is the ontology. So here's a graph of the ontology. You have, in this case, we're looking at mutated gyrates. So we can follow mechanisms. We can look at it evolve from a drug-sensitive gyrates and we can see what drugs it confers resistance to and drug class, what targets it evolved with, what gene groups like the toposomerases, what mechanism it evolves with, and then up to the individual compounds. And this means you could be a drug discovery person. So you would enter the card through the drugs part of the ontology and do your searches because you think from chemical space. You might be a molecular biologist thinks the mechanism. So you enter the card through the mechanism. You might be a sequence person. So you enter at the model of the individual sequence. Maybe you're interested in topoisomerases for your PhD. Essentially you have a knowledge network. Ontology standardizes the terminology and connects them all. So you can enter and analyze the data from any perspective. It allows it very easy for a human to work through the data but especially for algorithms to mine the data because it has a knowledge network. So this effort underneath card the ontology is part of what we've heard about is the genomic epidemiology ontology, this higher level ontology led by Will to bring in the food on ontology, mobile home, virulence, et cetera. So we have a standardized language for harmonizing data and surveillance. And as well it's part of the ARIDA project that you had your first taste of yesterday where you can standardize data and standardize your metadata. What's a little unique about card compared to the other resources, not a little, it's a lot unique compared to the other resources, is most resources are essentially a collection of sequences, a fast A file, and you figure out what you want to do with it. We actually provide detection models and parameters. How should you use this data? Not just give you the data. So here is one model to it. So we're giving you the sequence in this case. It is a ant6. So this is an aminoglycoside resistance gene. Here's our protein to it. This is a protein homologue model. So it says if you want to predict whether you have one of these in your genome, you're essentially gonna take this reference sequence and you're gonna do blasts or some similar sequence comparison to it. And we're gonna provide you a bit score cutoff which is right here. So clearly if you blast and you get a perfect match, you know you've got the gene. But what if you have a variant of the gene? What point is it too distant in sequence that it's not actually functional? So we hand curate all these cutoffs. And a bit score is essentially a measure of similarity. How much information is similar between your sequence and the reference. And if your bit score is above, in this case, 500, our curators predict that the variant you saw is functional. That this is some related ant6 aminoglycoside to it. If it's below that cutoff, it's related to this aminoglycoside, but probably working on different small molecules or we're not really sure, you probably should clone it and be sure to it. So this takes us a ton of effort, but this gives you context to say because you're gonna see lots of variation when you sequence your samples. Is that variation probably functional? To be absolutely sure, you probably have to clone and sequence everyone. But if it's within the cutoff, you have a high likelihood that that can explain your phenotype, why the drug didn't work. This is the most common model type in the card. So beta-lactamases would cause that since they're the most abundant resistance gene. The second model is the protein variant model. So this is the second most abundant model. Very similar, I have a reference sequence. So in your case, we're looking at, what are we looking at? TB, ethyl butanol resistance. So the reference though is often a sensitive wild type. The normal gene that every bacteria carries to it. And then you do blast to find it. In this case, you get a cutoff and this cutoff requires a bit score of at least 2000 to say, yep, I found the EMBB gene in this strain. But that's not enough. Every mycobacterium carries an EMBB gene. So you get a positive for every single one. Then it compares it into a matrix of curated SNPs. These are mutations that have been characterized in the literature to cause elevated MIC, these cause resistance. So this model is a two-step model. Find the protein, screen it against the knowledge base of substitutions and mutations or insertions in deletions. So GI raises, immunocumen resistance, ethyl butanol resistance, fluoroquine alone resistance, all use these type of models. These are the most common to it. As well as mutations and regulators is another common one. This data is really rare. CARD is really the only one that cranks that with the exception of tuberculosis. So if you're a tuberculosis researcher, there is an American resource. TB evolves so fast, we can't keep up. And there is a well-funded American resource for TB, so we let them do that. And we're gonna hopefully get the data synonymizing between the two of us soon. But I would need 50 curators to keep up with TB. So at this point, we have eight different types of models in the CARD. So we've heard about homolog protein variant, well the equivalent for ribosomal RNA gene, so fluoroquine alone, immunocumen resistance. So mutations of ribosome RNAs. Protein overexpression models. So CARD can talk a little about those if you want the details, but essentially E-flux proteins, they all exist in all the strains. It really has to do with the regulator is mutated so you overexpress the E-flux system. So you're kicking out the drug at high rate. So we're looking at this. This model will find the existence of the E-flux protein and tell you that, but it will especially tell you if it's mutated so you get higher levels of E-flux. We have protein knockouts or non-functional insertions, so acinobacter, and then higher level things like van clusters, where you have to need a whole battery of genes to cause resistance. Or E-flux systems, where you have five or six components all at play, including the regulators. In orange is where the models that we put in CARD are in use by our software. So you can predict this with our software. The asterisks indicate there's a few mutation types we've yet to write code for. We're not very good at deletions yet to it. The blue is where students are generating new algorithms part of their thesis. These higher level, like do I have glycopeptide resistance in my enterococcus. The two here is we've curated all the knowledge in the CARD, we haven't written a line of code yet to use that, and that's open game. Anyone can do that if they want. So where are we at? So we're just over 4,000 ontology turns in the knowledge base. Just shy of 2,500 reference sequences, 1,200 mutations. 2,300 publications are tied to the original definition. There's, of course, many more publications we go through, Lord knows how many. And about 2,500 detection models. So that's your rough estimate of how big is the resistome out there. We're dealing about 2,500 resistance types. That's actually a little higher as a few of them are private. We published a paper last summer for the students in the room. This was an undergraduate that got first author, did redesign the whole thing. We are cited at a very high rate, which is great. You'll see the data is used for genome analysis. People use it themselves in their own pipeline. We'll see people to make brand new models. So we'll talk about the ResVan models to it. You'll see our data used to enrich a database. We saw Fiona talk about Island Viewer. But we have a formal collaboration with NCBI to use our ontology. And we trade data back and forth to make sure NCBI and us are on the same page. For the Americans in the audience, how it works in the US is we curate like mad, pour our data, collaborate with NCBI, and then it goes to the USDA, the EPA, the CDC. So they're the conduit we go through. NCBI is starting to take a lead. And we really are working on the ontology standardization. And lots of people use our software. From Adele Valley, this is Tricky Science. So those of you interested in how to be a bioinformatician, you need to be biochemists and cell biologists first. Most of people come into my group from that perspective. You've got to understand these cells. We have to know the enemy. Biocuration, which is a sub-discipline of bioinformatics is really about standardization and building data structures. Build data so humans can confuse it. It's an growing and urgent field underfunded field as well. And then, of course, the data sciences and software engineering to build all of it. So you've got to think from multiple perspectives. So we have two full-time staff, a software engineer, a properly degree in engineering to it, and then an evolutionary biologist who's really the lead curator. Because this is an evolutionary phenomenon or battling. So you have the resistance reference database built. We have all these structures. How do you use it? How do you do AMR prediction? So essentially, you have three axes. I'm going to go on this side. The top axis is whether you want to just screen for perfect matches. Do I have NDM1? Do I have MCR1? The ITM72? Or are you looking for functional variants? So I want to be a little more open-minded. I know there's sequencing variation out there. Or am I looking for truly emergent threats? I'm trying to look for the things that are going to scare the daylights out of me. The next axis is what type of resistance? So am I just looking for dedicated resistance genes like beta-lactamase disease? They're often born on a plasma, so protein homolog models. Or am I looking for resistance by mutation, the protein variant models, gyrase mutations, and all the rest? Lots of software doesn't do this one. Or am I trying to work on the subtlety side? Things that make the cell just intrinsically resistant to the drug. The drug just can't get in. Or regulatory changes. And then how good is my data? Am I got a whole genome sequencing or assembly? So I have huge chunks of the genome resolved. So I'm getting whole AMR gene so I can find the whole thing. Or am I doing community sequencing, metagenomics of lung or water or something like that, where I'm just getting fragments? You have these three axes. The green boxes were essentially the communities doing very well. There's lots of players, lots of people building tools and software. It's the low-hanging fruit bioinformatically. So finding the known and just saying, hey, you've got NBM1, where, and that's a plasmaborb, dedicated gene, and it's from sequencing and isolate. We can do that with our eyes closed. When you move into novel variants, essentially we're talking about curation of the SNPs. So it's us in the Argonaut database, a little bit of the res finder guys in Denmark. And we share data and go back and forth. This is a tough battle. This, these things have mutated at high rates. We're constantly have to curate new mutations. I can never tell you that we're comprehensive. We're caught up. We're always trying to keep up. The immersion threats, really, there's only two groups working on it, us and the resfans, and very different perspectives we'll talk about those. But what we're not covering very much is intrinsic resistance and regulatory. We're the first to work on it. We have those protein over expression models. Really has to do about mutations of the regulators. So we say, not only do we find the genes, but we're predicting they're overexpressed. So CAR gets all the credit for that much. Somebody intrinsic? Not so much. Well, we're going to improve on that in the next year. We're going to do a pathogen identification, more often than it is about resistance. Metagenomics is a mess. There's lots of, we're going to play with it today. I'm going to tell you the limits. There's lots of papers, not done well. And there's some real technical challenges. But it's going to be a good year for many groups on this front. So resources, there are tons. So when I sequenced in Giardia 14 years ago, we get the genome out. And there was this plethora of tools and databases and everything. And after about five years, it settled down. And there were two or three really good reliable things. We're in that state for AMR. There's lots of money in the pipe because it's a severe health crisis. So every week there's another tool or a critique database, really hard for a researcher to figure out what to do. So Cara, I promised to review with me last year. I'm just going to highlight a few. So tools that I like. First of all, the Argonaut folks. Really good curators. They have a nice tool for genome annotation. Their SNP database is a little small. We got Resfinder. These are the names. Really was extraordinarily good. Very commonly used for plasmid-borne resistance, but they're starting to branch out. They got some funding to go to that. Ours tool, we'll see the resistance identifier this year. I highlighted this. I probably are not supporting as well as they should, but this is a good preliminary metagenomics tool. We're going to talk about the AMR++ today, too. The TB profiler. So TB, really, you want to use things like TB profiler, not card or Argonaut because these guys are really focused on that pathogen. Databases. So fine, you got tools. You need data to compare. So there's really three. Argonaut, fantastic group. We collaborate. We send data back and forth to it. We're going to come to the table NCBI. Us, curating data of the card. You have the Resfinder, which is, again, predominantly plasmid-borne one in Denmark. Getting them to come to the table and share a bit more, a little tougher with Danes. I did highlight the Resfams. We'll talk about that. These are a specific thing called hidden Markov models. They don't generate data. They amalgamate all our data sources and build Markov models, which we'll talk about a little bit later, but a really computationally intensive tool but quite powerful. And then NCBI has made a real commitment, particularly around beta-lactamase, is because the people that curated it have all retired, like Karen Bush and the rest. And NCBI has stepped up in making centralized resources. And we all collaborate with NCBI. All right, our software. We're going to play with the resistance gene identifier today. The RGI, basically things like a black swan, right? So when you do RGI, you can make hits on three paradigms, perfect, strict, and loose, or what we call discovery. So a perfect hit where the sequence matches the reference completely. It's a no-no. So hey, I've got NDM1 in my isolate, right? So if you are doing public health surveillance and you're really using sequencing to track known threats, this is what RGI, that's the level you're interested in. You may not use the rest of it, right? Then we have strict, where the hit is not the same as the reference, but it's within those bit score, those model cutoffs. It has all the things that different model parameters say it should. So our curators are predicting it's functional. So if it's 97% similar to a known gene and that's within the cutoffs, it's probably a functional variant. If you're doing clinical sequencing more, you're trying to understand which drugs will or not work. You probably need the strict window because there's lots of variation out there in nature, right, to it. Almost the majority of it on character drugs. Majority of users never move outside of that window. It's a tiny minority that turn on the loose button and it's because they have something they can't explain. When they look at the perfect and the strict, they still can't explain why their drug doesn't work. There's something new, right? They turn on the loose and these are all the hits that are outside of our model cutoffs. So a lot of them are spurious, complete nonsense. They're related proteins that are working on some other small molecule or something like that. But if you come down to no resort, this is where you go and this is where you find your emergence. Right now, this is a really a massive data. It takes a lot of work and you got a cloning sequence that we're now starting to collaborate with the protein database that have structural level data to say, okay, out of those 4,000s looses you got, these four have a good structural profile to actually be your resistance gene. They could physically interact with the molecule that you're working with to it. So people like Jerry Wright, whose sequence really bizarre pathogen or ancient pathogens and never been exposed to humans, he's always in the loose zone, right? And spending, doing a lot of cloning as a result. So this is what it looks like on the website currently. You can put in a session, it'll just grab data from GenBank or load your own files. You can say, well, I've got DNA sequence so it's gonna find the genes for you or I've already predicted my genes. I'm just giving it my predicted proteome. I've already done my annotation to it. You can say I want perfect and straight or turn on that loose button, right? To see all those loose hits to it. And recently this sort of high coverage. So if it's, you've got good quality coverage, like a good shotgun assembly, well coverage of your genome, big chunks of genome resolve, no problem. But if you're doing small plasmids or it's a quick and dirty, slow sequence coverage of your pathogen or maybe even it could be merged metagenomic reads, so tiny contigs to it, you can turn on the low quality. And then it will actually look for partial genes. So in the high quality it says, no, I gotta find a complete gene, start to stop before I'll consider it, right? And that's a rule. But so if you think partial genes because your data's small, it's plasmids, it's low coverage, you turn on the low quality to find partial genes and weak hits to it. And this is actually, workshop way better than I thought it would, to be honest. So this is a visualization from the web. This is a multi-drug resistant salmonella from a patient in Hamilton, Ontario. The wheels is a snapshot from the web. So we don't have leucine, so not showing any, but there's one perfect hit of all that. So this is a multi-drug resistant strain. I only see things when three drugs fail. They come to me. Tons of strict hits. Genes that are in our cut-offs around model. We haven't seen that specific sequence before, but it's within our cut-offs. It's a lot of genes. And then you can use the ontology and literally click on the website and it goes to this. It reorganized by ontology and now it's organized by gene family. And we look, most of the gene families only have one hit for acrylon-resistant penicillin. But if you look in the R and D e-flux, there's 14 genes. There's always a lot of e-flux in bacteria. Or if you look in the MFS e-flux, seven hits there. Two hits for that looks like a, we lack them over there. So you can reorganize the data on the fly using the ontology to break it down by gene families. Well, maybe that doesn't mean a lot to you. So you can reorganize the data and say view it by drug class. And what's scary is that one perfect hit covers seven drug classes. So it alone is causing multi-drug resistance. But now we take a look and I've got 15 genes contributing to chloroquine, 17 to ribomycin, I've got aminoglycaides, I've got macrolides. I've got basically everything that's super bugged. Chloramphenicol is even in there. You've caused, obviously we've never used chloramphenicol on a patient, but we predict that resistant nonetheless. So you have that context that really, and key thing about resistance, one gene can lead to many drugs and many drug classes, particularly e-flux. So it doesn't take, this is a super bug that has a large battery of genes, but it actually can take a few genes to generate a very complex phenotype. If we still couldn't explain why a certain drug worked in this clinical pathogen, and so we were at a loss, then we could turn on the loose. And the loose, you can see how many weak hits to resistance genes there are in just one salmonella isolate, right, among this list. But if we know it was macrolides that we couldn't do, we could cross-reference this with the ontology to reduce this list to all the ones that are weak hit to a macrolide resistance gene and maybe get it down to 12, 13 candidates. Then hopefully in the future, right now by hand we would look at structure, in the future we'd have it just the website work, look at structure to narrow it down even further. We fortunately don't have to use this much, right? It's only when something scary shows up that we turn this on. But we sort of usually have running bets how long till the next one shows up in the lab, and I usually lose the bets to it. So you have this capacity for those of you who have the unexpected. Okay, what about metagenomics? So here, how am I doing on time, man? What about metagenomics? So what I just showed you was an isolate that was cultured on a plate, DNA isolated, we sequenced an alumina, we assembled it with something like space, so it was high quality data on a purified isolate, right? Metagenomics is where I get a cystic fibrosis patient and ask them to cough in a cup and I sequence that DNA, right?  So you've really got a noise and signal problem in this data. On top of that, we don't know how to assemble metagenomics very well. So we have short fragments, aluminum sequencings are 250 base pairs long, so most genes are longer than that. So we all have partial hits to it. So it is fragmentary, highly noisy data. So how do we deal with that? So where the field is at is essentially there's three methods out there. First of all, if you've got a big server farm, you could just blast X the whole thing. Every fragment into protein space compared to the card or Argonaut or whatever. This is computationally intensive, we do it to baseline analysis, but very few labs have this capacity because the average metagenomic data set, it's gonna be 160 million sequences, right? This is gonna take forever. So we don't have the algorithmic space and the reason that you'll see things like the Brosewieler transformer BWA or bow tie, all these alignment softwares, it was simply because this was too dang slow, we had to do something smarter and faster. If you really have a lot of computing, you can use the resfams. Now what the resfams is is really some excellent bioinformatics in a way. So they take card and others and they say, I'm gonna build a model, a statistical model of what a beta-lactamase functional domain looks like and an amino glycoside is settled transferase functional domain. So it's a mathematical model and this is what hidden Markov's models do. They're usually used for looking at proteomes to say, I wanna find a distant relative to my histone. I wanna find a distant relative to my beta-lactamase. They're really good at reaching an evolutionary space and finding weak hits. These guys take in those resfams, build an excellent resource of them and they're great for protein annotation, absolutely. But then they throw them, they use a huge amount of computation to throw them against metagenomics because these are fragmentary and says, I think I just saw a bit of a functional domain of a beta-lactamase. I think I just saw a bit of a functional being of a subtle transferase. So they've done it in soil and they came up with a huge list, right? And the trouble is no one knows when you do this what the fault's positive rate is when the data's really fragmentary. So when I look at their list and say, hey, there's 470 putative beta-lactamases in the soil sample, I go, yeah, but is it 3% correct or 97% correct? No one knows. So when Fiona talked about the amortyne project yesterday, this is the problem they're trying to solve. They're trying to build these advanced models for mining soil and water and clinical metagenomes but to reduce the faults positive. That's really fundamentally what amortyne's about. But if you look at the resfand papers, that's the grain of salt. First of all, almost everyone in this room doesn't have the computing power to run those against metagenomics. I don't do it in my lab and I got a lot of horsepower, but also you're dealing with a false positive rate problem. So what you'll see the vast majority of literatures, people using the Burroughs Wheeler Transfer, and you'll see software called BOTI or BWA, these type of things, or they'll call it read mapping. These are high intensity, fast bioinformatics algorithms but they're high stringency. I have my little fragment gene, align it to the reference, but really don't even consider anything below 97% similarity. They gotta have a high matching rate. Therefore the algorithm can be fast is the key. Unlike Blaster says, look at everything. So takes forever. This one says don't even consider if you're not even within 90% similarity. It's all about high stringency read mapping. So it has very low levels of false positives, right? It's very good to a reference database. What we don't know is what the rates of false negatives and there's nothing wrong with the algorithm. Then false negatives have to do is the thing that it's 97, 98% similar to in your reference database in the first place. So if you're sequencing a clinical sample, like a CF patient when we expect Pseudomonas. Card and others is really good at the sequence diversity of Pseudomonas. So the Burroughs Wheeler Transform is gonna work great. It's gonna align the C-serif bonus. If you go to a farm, right? And you sequence the microbiome of a pig, right? Medijones, as you're looking at AMR transmission in a farm, the sequence variants that are in the wild in a farm might be a long way from the sequences that are sitting in card because it's generally the published clinical sequences. And so the sequence that you've got in your farm might be a perfectly valid AMR gene, but it only might be 93% similar to the reference and the BWT fails, right? So the false negative rate, what is the real problem of that literature is it's highly dependent upon the reference database. So stringent read mapping is a sense of sequence diversity in the reference database. And this has been really, really under examined. Every database out there, Canonical Card, Argonaut, Res, Fine and all the rest, what gets in the literature, and 90% of the papers in literature are clinical sequence variants and they only publish the first sequence they saw, not all the other variants that are out there in nature. So card traditionally attract the published canonical sequences the first time it was published, right? That is actually our curation rule. Our algorithm is our text miner says, looks for new things, not information on known things. So it's really underestimating these variants. So we looked at even a CF patient, it was CARs undergrad thesis, and we found that even at the CF level, when we knew a lot about pseudomonas, we missed things on this because the CF we saw in the clinic was a little sequence distance from the pseudomonas we had put into the card. So we knew this was coming, we knew that the bioinformatics was making nice progress, and Amartime was gonna attack the false positives here, but we as curators had to attack the false negatives to it. So what did we do? I'll show one more. So this is CF data from Canada, showing you the diversity. So every row is an isolate type from a Canadian cystic fibrosis patient, pseudomonas infection, every column I should say. Some of the isolates are more common than others, so most of them are one-offs, but a few isolates are seen in more than one patient. Every row is a different resistance gene to it, and this is using the RGI software. If it's green, it's a known sequence, it's a known node, right? If it's red, it's a strict hit. It's a sequence variant that's not in CAR or any other database. So that showed just even in clinical CF patients looking at pseudomonas, close to about, it's almost three quarters of the kids of AMR genes were brand new sequence variants that CAR, it was naive about, doesn't have that individual sequence. And you can see some of the more so others sort of whole drug class picked up by this one right here. It's an interesting variant. So this bar along here is predominantly E-flux to it. So what did we do about it? So CAR released resistomes and variants. Every month, gonna switch to every two months because it's taking so much processor time. We grab every chromosome, close chromosome, close plasma and shotgun assembly in NCBI for up to 76 pathogens. And we're just every month we keep adding more pathogens to it. We take that data set and there's just a screenshot of a few of them of where the density of the data is. And we run the complete CAR RGI against it and we predict every perfect and strict, right? And we find, so at this point, we have over 70,000 chromosomes, plasmas and shotgun assemblies for 76 pathogens. When RGI, so at the last release, just a few days ago, we have over 130,000 allelic variants of all the things that sequence. So we're building a database of sequence diversity to make the work on that false negative problem that comes with doing metagenomics. The reason we built this other than we get a lot of great epidemiology data out of it is really about solving the metagenomics problem. This data is all available on the web and downloadable. So here's an example where you're going to do this yourself today. But here is again, another pseudomonas from CF. So at the left, we have the predicted gene in the metagenomics data. On the right, the number of sequences. This is just a subset to test software. So not many sequencing reads from the Illumina hit. Normally you get much higher numbers to it. So lots of genes in the CF patients community, some data to it. Most of them are homolog models. Some of them, the Burroughs Wheeler Transform mapped it to a known card sequence, a canonical published allele, right? But the vast majority of them, the closest sequence was actually one of these resistance invariants from genome mining against GenBank. It was much closer than the card one. In fact, if you lose these, you lose whole rows because they're outside of that 97% similarity window. So this really illustrated what was key about it. Then you get further because you've done resistance invariants, you know where they came from. So two of them we know are found from plasmids in GenBank. But on top of that is we have context, not just a sequence match. You can say, well, two of these appear to be plasmid born are known to be associated with plasmids, whereas most of them in this case are not. But on top of that, we said, well, where are those genes known, right? Now I happen to have submitted a pseudomonas infection. So, but a lot of these genes have only ever been seen as pseudomonas. Others are much more broadly distributed and no surprise, look at that, the two plasmid born are the ones that are spread out amongst many pathogens, right? So that's a step towards pathogen identification. Now this is a control, I knew it was pseudomonas, but if you're sequencing a gut infection, you don't know who your player is at, right? So that you have in metagenomics, you have two issues. What resistance genes do I have whose carrying is often really the hard part to figure out and we're starting to make some steps and you're gonna use some, I'm not even gonna call it beta alpha software today to look at this issue. So that led to the question is we built these alleles, are they diagnostic? Are we getting down to a real level molecular epidemiology? So we went to Jerry, right, our colleague. So Jerry leads a clinical sequencing effort, anything that we have third drug fails, we get it from Hamilton's offer, so it can be any kind of infection. And so we looked at this and we said, fine, we'll take all your collection of pathogens, we'll run them, we'll sequence them, they'll run them through the RGI, we'll find all the sequences that are in the wild in a clinical, diverse clinical setting and we'll ask of all those alleles we see, how many are only found in one pathogen according to all our resistance and variants? So if you look at Kleb, about 55% of the AMR alleles in Klebsiella have only ever been seen in Klebsiella according to everything in GenPang. They're diagnostic for Kleb. Another 20% are from Horiscomus plasmids, right? So these are alleles that are on a plasmid and are just leaping around between pathogens. This is another tiny fraction we couldn't diagnose. Pseudomonas, really, I didn't realize how different in sequence space a Pseudomonas is. Almost every AMR alleles we find in Pseudomonas is diagnostic for Pseudomonas. We don't find it in any other pathogen. So we can do really well at identifying Pseudomonas. Up here you'll see Proteus, well we didn't have Proteus in our reference database so it was really bad then, but it's better now. So this really comes to the question, can you actually, by doing this massive computing and providing the database to our users, can you get down to pathogen ID and AMR detection in metagenomics? And we're gonna do that in the lab today. Okay, so let's scale it up the last little bit. So Syria, we're starting to see the first real papers coming out of Syria. So if you're in a combat zone, a refugee zone, a medical camp zone, reliable and consistent use of antibiotics is almost impossible. It's a breeding ground for resistance. You have people who are in movement who are using their drugs, not finishing their courses and getting to another location being assigned a different antibiotic, being shipped to a different country that has a different antibiotic they tend to use. We have the early evidence that we're breeding drug resistant strains. The combat zones and refugee camps need special care. We're gonna learn the hard way that we need to treat antibiotic usage different than these type of environments to be reliable, save the patient and save the community, so to speak. But how are we gonna deal with the fact that what do we need, what informants need to look like when we sequence at every clinic, a hospital, outbreak or war zone, right? How do we build a surveillance network for drug resistance? This is partly motivated out of the Haiti study, right? You guys talked about Haiti, that cholera did not exist in Haiti till after the earthquake and we now know from Canadian work that it was a relief workers to introduce cholera, right? But we found out way after the fact, how do we build a system where we find out the next day, right? And close that camp down. So we've been lucky to have some funding to work on this, to think on the big scale around AI and big data approaches to it. So essentially what I want, we'll go over here, is working with groups like the GenFBO and ARIDA to build work towards a big surveillance. And this is ARIDA's goal, that we could have ARIDA instances in sequencing become routine. As I said, the price is plummeting. So what's my job is to get governments and rest to put bags and nanopores in northern clinics, right? Your community hospital has a regular sequencing surveillance system for infections to it. Hopefully we can get into metagenomics surveillance. So if you think every clinic, every hospital, we're constantly generating that data, right? So companies like Cisco, my sponsor would be very interested in that. What would you do if you were collecting data in that volume and that philosophy and that diversity just within a country or even internationally? So first of all, you could have rapid response strategies. So you all know we had a bad TB outbreak in the north, right? There is a delay. It's a hard to grow on a plate. It has to be shipped to an Ottawa lab. It takes a long time to come back and say, hey, it's TB and it's a new resistance stream. If you have a child coughing a cup and there's a bag of sequencers in your clinic when the nurse practitioner visits in every two weeks, you can have them cough. It goes on the end. An algorithm could say this is TB and it's got these mutations to it. You would have rapid response and inform it. So early detection, emergent threat. So this is a no-no, right? It's a TB strain. It's got a mutation in it. Hey, we should be scared. But also, as we build our discovery models and we start to put structure, routine sequencing, you want to learn, say, hey, a gene just showed up in a patient in Winnipeg that looks like a brand new beta-lactamase. Go take a look. Maybe it's nothing, but maybe you really look closely before it kills people, right? So we can get to that world. Informed public policy. So drug-resistant gonorrhea is a great case, right? We find out, secondarily, as we start to get case numbers up, public health starts saying, hey, we've got multiple strains of this. Often it's in the community long before we get enough public health data to change to inform the community. So sequence-based, tell the community, look, 80% of high schools in Ontario have drug-resistant gonorrhea in them. That leads to a public information campaign. Better data, right, to it. Clinical practice. So this is a tricky one. Clinicians don't need us. They really don't. They know what to do, right? Clinicians know when they have a strain that doesn't respond to drug. They know what kind of resistance they're used to seeing. They know what drugs that they could use. They generally know what to expect in the community. Where they struggle is where they have four drugs that they could treat their patient with. They have an opinion which one's best for the patient, but they often don't know the stewardship side. Which drug should I use that causes the least long-term harm for my community? Because right now we have no genetic data to it. But if we're sequencing on surveillance, we can inform stewardship that please use dug number one because there's very few resistance genes in our community for that drug, right? Or we know from sequencing efforts that it's the least likely to generate new resistance, right? It tends to be a fairly irresistible drug. We need better data. So this is what we hear from Royal College of Surgeons all the time. What's the genetic landscape resistance so we can make better stewardship decisions? The long game is actually this one. So drug development is almost dead, right? You have a few innovators in academia, a few little companies do it. I don't know if antibiotics are going to be the succeeds. There's a lot of interesting kind of looking at phage, right? There's alternate strategies or immunoboosting strategies. But one of the most interesting is our resistance killers. So NDM-1 came out of India. Global threat now takes out an entire drug class, right? And a big worry. So Jerry Wright at McMaster a few years ago found a compound that turns off NDM-1. So you can go back to using your carbapenems. So you can use it as a mixture, as a cocktail. So it's a resistance killer. And it's a compound we know a lot about actually. It's been through preliminary trials. It's in trials now with the NIH and the states. So through Jerry doing screening of looking compounds that shut down resistance, Jerry might in the end up save millions of lives by generating this. There is a lot of hope of resistance killers, compounds that shut down the resistance mechanism. So you can go back to our usual drugs. The trouble is economic.  It's just a Valley of Death in drug marketing. And they all said, oh, great. So it targets this gene, this resistance gene. How common is that gene? Is it pediatric patients? Is it elderly? And you go to P. hack right now. And they say, we don't know. We do phenotypic surveillance. Not genetic surveillance. When we sequence everywhere, we are able to say, yeah, that's a pediatric resistance gene. It's 80% of cases in Canada. Or it's general population. Or it's the elderly. Or it's CF patients. Or it's cancer patients. That will give you the data where investors will come to this company and invest to bring the resistance killer to market. Or it's a rare case. And so it'll become a non-profit partnership with government, kind of like all the Ebola therapeutics had their funding stream to it. So essentially, our long-term plan of getting all this sequencing going is actually to encourage the resistance killers. So we actually combat drug resistance genes directly. So we take them out of place. We can go back to our old drugs. And specifically to work on the economics of how you're going to re-boost that by proving better data. So you have real numbers. You can take the VCs who will put money down and bring that drug to market. OK, a few practical things before we have some fun. Recent releases in the cart. So curation. I'll never end in curation. I did 600 curation. I didn't last night listing. We actually, you'll see that we've done a new classification around the ontology. So everything resulted by gene, by gene family, by mechanism, by drug class. So we're making some better ways to organize your results. You'll see now we have in vitro versus in vivo mutations. So in vivo, our mutations that we're seeing in clinic or in farm, something like that. In vitro are ones that people did selection experiments at the bench. So that mutations never cause clinical resistance. But it could. But we don't have that. And selection experiments tend to be rougher. The ontology, we didn't talk about it today, but we added an entirely new branch for harmonizing phenotypic testing methods, disk diffusion and all the rest. This is with GenFDO. So if you actually work in a public health surveillance lab and you're doing a lot of phenotypic testing, you're running out of harmonize your data for sharing with other agencies, talk with Will and I. We just completely released that branch. The RGI software, so we added that low coverage part, so we've got fragmentary, low coverage data. Merged metagenomic reads. So when you sequence, you get a foreign reverse read and metagenomics is short. So they tend to overlap. You get a little fragment.  You get $80 million of $160 million. We can support that with RGI. Small plasminates, which generally don't do well. A little bit of barf management, if you don't like blasts too small, you can switch to diamond. We added our everzonal RNA mutations and E-flux over expression, so it's the only tool out there. So every tool didn't do fluoroquinolence immunocuberance before we added that to it. Better documentation, some of that. And then the big one was resist zones and variants. 76 pathogens, it's gonna grow. So what are we working on now? You're gonna get a glimpse of this. The great one is, for those of you who are in the agricultural and agri-food, so CARD has really had its funding base on the clinical side. Now we're funded heavily on the agri-food agriculture side, so we're gonna round it out and we're gonna look at the One Health perspective when it comes to AMR. This pathogen origin idea, allelic aminology, we're gonna work with camers, we're gonna do it today, of ways to say, it's an AMR gene, but I think it came from salmonella, so I'll talk about that. Resist zones and variants. If anyone uses AMR, use the AMR++ metagenomics. So you guys have had a look here, there's one. So galaxy frameworks, very popular. Colleague in Florida wrote the AMR++. It's a metagenomics pipeline for AMR prediction that works in galaxy. It's quite nice, but the data's stale. So we're gonna collaborate with them this year and to make sure AMR++, which is a pretty, it's a first pass decent metagenomics galaxy tool, will at least be up to date with CARD data, and be a little bit smarter with it to it. New visualization tools, you can do some heat maps today. Particularly, what CARD has not done is really look at the relationship with the mobile home and with virulence. So we're gonna collaborate with them in this room on a mobile home ontology, virulence ontology and virulence gene identifier with CFIA actually, it's gonna be our major collaborative. Prediction from phenotype from genotype, we'll use that one to try. So we just got funded a little more recently, not as recently as we'll did yesterday. One of the things we're missing is if we have a gene or mutation, it just tells you what drug or drug class it works with, but it doesn't tell you the known MIC. Like really, how much does it change resistance? So we're gonna curate that level of data in, so you see the severity of it. A lot more mobile home and genomic violence with Fiona's group. Alila Kepidemons we talked to, and then a lot of the stuff we talked about, metagenomics, amortimia, and our plus plus. But really about context. Our big drive this year is, yeah, you found it, but what does it mean? Is really essentially what we're doing as engineers. So the challenges I want you need to be aware if you're gonna do AMR surveillance, essentially of this, what's tough? So bio-curation of reference data is difficult to fund. NIH does it well when I was there and CIR HR, not so much. But without gold staff, the standard reference data, the whole thing breaks down. It's a reference base. Now Carr can talk to you about machine learning, other methods where there's no reference data, but really we're in the reference world still. The challenge is that unlike sequencing Drosophila and annotating it for the rest of life, it's not static. The resistome evolves on a daily basis. So unlike traditional bear creation, where actually the target's always moving. So this is never gonna go away. We need a constant funding stream on bio-curation. Sequencing technology is getting cheaper and smaller. We'll be doing increasing amounts of it. So storage, right? Storage and sharing has really been gonna come to challenge on how to do this. And that's what RIDDA is all about. That's why we partner with RIDDA. Metagenomics is difficult and computationally costly. And right now, anything you've got that you use that's out there, even what we're gonna demo today is really only using the easiest subset of AMR mechanisms, the protein homolog models. So when you do metagenomics now on any tool, it's not screening for mutation-based resistance, which is at least a third of the resistance out there. So you're grossly underestimating resistance. It's just saying, hey, I found a beta-lactonase. It can't say, hey, I found a mutated gyratris to it. So we need a lot of progress. We need a lot more translational tools to make this easy to do. What we're not doing well right now, tracking MICs, how much resistance does it cause? Very poor data on plasmids and other aspects of the mobile. We haven't done a good job on that on curation. Transmission dynamics, how things move around the one health. We just got a big grant funded, but very little out there now. And metadata, right? Where is it seen? What does it done? Who does it infect? And there we go. And so we have lots of collaborators, both Canadian and otherwise listed up there. So a lot of our, a lot of you, and if you wanna be a beta tester, let me know, we'll put you on the beta test list. But Rob Biko, who wasn't here this year, but Fiona and Will are our big collaborators, NML, Gary's group, USDA and NCBI, our big American colleagues, Biri Meru and France, and then many, many academic teams to it. And there we go. Perfect. Any questions before we pack some data? Cool. Okay, question. So we're seeing resistance emerging candidate species. Is that included? So we're prokaryotic so far. So we have an attack yeast. We're talking about that because we have a group partner with us working on sepsis and of course it's not always bacteria, sepsis. The challenge we have is our algorithms were designed from a bacterial perspective. So the concept of an intron is foreign to our data, so far. We do, there's actually a nice little database I saw of proof of resistance in yeast came out. I have been being attracted down. We haven't made a commitment to that yet. Yeah. I think that's one of our lines in the sand for finding. Until I get money to work on the fungal side of things, we probably won't do much. But there's not a lot out there. It's tough. Yeah. Just a question about, it's hard to develop companies or how do you envision that this field wouldn't work? Yeah, so card up until recently, half of cards funding was industrial. We licensed to at least 30 different companies, our data or software. About a quarter of them are in drug discovery pharma. A lot of them are machine learning or food safety. It's to it. So we basically talk with industry a lot and say, okay, what do you need? What kind of data do you need to speed up your pipeline or not tools? And then we write, and we basically have three players. We have academics that we produce for, we have public health people we produce for and we have industry. We talk to all three and that's why we resist them. So it was a needed bit of data to it. Do they also share data because you're not in a pharma company? I guess you're some sort of secrecy. Yeah. Peri-Merry-U. Actually they can claim a good, maybe 5% of the card Peri-Merry-U helped generate to it. We have a couple others that the data will go public at some point, but they're not yet. It's case by case. So the rule for canonical card right now is that it's gotta be published in a peer review journal, the sequence in Genovank and clear, well done experiment to illustrate MIC. So a lot of industrial data has not passed one of those marks they have published in paper. So we're building the class to say, okay, here's an unpublished data set. And here's what it says. We actually have a few of those private now. I have to do it. But we keep those lines really clear. So if industry wants it to be in-card, they got to publish it. Get through period. Anymore? Okay, possibly break. I think they hit that button. There we go, coffee break.


Hello everyone, it's your girl Kenzie here from Layton Sports Guards and I'm ripping 21-22 Panini Immaculate basketball hobby 5 box full case break number 30 pick your team. Got Adam E. Sixers, Alex L. Jazz, Brett B. Pistons, Chiakai, L. with the Knicks, Chung Way, W. Blazers, Ezekiel M. with the Warriors, Lakers, Thunder, Felix, Felix N. with the Pacers, Kings Rockets, and Raptors, Harper B. Magic, Heng-Y, Spurs, Jeremy H. Heats, John K. Nets, Jonathan Q. Clippers, Ken I. Sons, Kyle M. Cavs, Marvin N. Pelicans, Matini N. with the Bucks, Minsu K. Bowls, Nick N. Hornets, Oren W. Celtics, Nuggets and Grizzlies, Tommy L. Wizards, Tony Y. Hawks, Weiting L. Mavs, and Wing C. with the T-Wolves. Alright, grab our case, we'll get ripped in here. Good luck everyone, we got two more case breaks of Imac basketball. 11 teams left on the next one. Let's fill it up. Here we go, box one. Let's see, let's see something crazy. We had back-to-back breaks with a lace and a Nike Squish, so let's see something crazy out of this one. Got a rookie base for the Pistons 70 of 99 K. Cunningham. It's K. Rookie base. Rookie patch, 21 of 99 Herbert Jones Pelicans. The patch here, 9 of 25 rookie Aaron Wiggins for the Thunder on the four colors. Aaron Wiggins, a Mobley case. Yeah, that'd be sick. That would be sick. We've got Patch Autographs, card 16 Julius Randall. Card 16, that is a New York Knick. Go to the Knicks. And Shadowbox Signatures, one of 98 John Collins for the Hawks. John Collins. Nice one here. Horizontal RPA, 14 of 25 Quentin Grimes. Beautiful patch there. Three colored patch auto. The horizontal patches are way better than the vertical. I feel like it's a bigger space. So it's a little bit easier to have nicer ones. More space you have, but yeah, I agree. Box two. We've got base 98 of 99 Emmanuel, quickly for the Knicks. The standard patch, going to the Hornets. This is 86 of 99 Miles Bridges. Got team logos, 25 of 25 bookend, Brandon Boston Jr. Ego Clippers, that's nasty. Roll over, BBJ today. We really are. That's sick. We'll mag that one. Nice one there, Clippers. We've got Inaugural Ink, 9 of 10, Gold Rookie David Duke Jr. for the Knicks. BBJ, modern marks on the red, 10 of 25, Danilo Gallinari for the Hawks. Nice. First time seeing him today. 63 of 99 Inaugural Ink for the Warriors, Jonathan Kominga. Very nice. This is one of the guys you look up for for the Warriors. Little JK action. Fresh, this is great. From 11 to go now, 11 to go on this next one. Again, five box full case break immaculate basketball. Pick your team style.  Most of those teams remaining are on sale. All right, here we go. We got Ricky Bates, 30 of 99, Scotty Barnes. Scotty Barnes. We've got Patch for the Spurs, 75 of 99, Jonathan Murray. Spurs. Going back to the Warriors. Little JK again, 6 of 99, Jonathan Kominga Patch. Warriors. Past and present signatures, 33 of 99, Larry Johnson for the Hornets. Nice one there, Hornets. Got modern marks, 88 of 99. Can you see here? What a heart. That thing is so nasty. Nice. We've got signature moves as it's a four of 25, Jason Tatum for the Celtics. W. Wow. If it can't be a logo man. Yeah, that's nasty. That is so nasty. Oh my gosh. Sign that huge. Huge auto on there. Yeah. Huge auto on there. Signature moves when you throw it up. It always does that when he hits a three. I think Jake is, or Jake, jeez. Blake is a fan, fanboying over here on that card. All right, box four. Again, everyone, we got two more cases going after this one. Cavs, Mavs, Pistons, Warriors, Rockets, Pacers, Lakers, Heat, Kings, and Raptors on the next one. Eleven to go.  There is the link for you. There you go. We got Bucks, 7 of 99, Chris Middleton, Ricky Patch for the Thunder, 53 of 99, Jeremiah Robinson-Earl, we got the Joker, 31 of 49, Nikola Jokic, have Denver. We've got Inaugural Ink, 8 of 10, Gold, Rookie, Usman, Daruba for the Rockets. Shadow Box, Otto, Jerry Stackhouse for the Pistons, 87 of 99. I think I can see the Otto. Super, super. Going to Adam E. Scorer's Club, Acetate Otto, that is 5 of 10. Helen Iverson, nice AI, beautiful card there. We'll mag that one as well. All right, last box of the break. Our Beg is a bit nastiest. Yeah, they have. AI to 10, JT to 25. See a big RPA here to end it. We got Boyan Bagdanovich, is 83 of 99, Patch, 19 of 99, Devin Boecker, Sons, nice patch here. Jersey Number, this guy's been on a roll in this case, 20 of 45, Jonathan Cumiga, Warriors, Jersey Number, Patch, Modern Marks, 26 of 49, Akeel Alexander Walker, Jazz, Horizontal, RPA, 26 out of 50, nasty patch there, JT Thor for the Hornets, pre-colored patch, Charlotte, and last one of the break. Break, Past and Present Signatures, CJ McCollum for the Pelicans, 28 of 99, CJ McCollum. All right, nothing to random there. Let's go ahead and do a recap. We've got our relics here first. Got Devin Boecker, Sons, Yokech, Nuggets, Robinson Earl, Thunder, Jonathan Cumiga, Warriors, Dejante Murray Spurs, Herbert Jones, Pelicans, Miles Bridges, Hornets, Aaron Wiggins, Thunder, and Jonathan Cumiga for the Warriors. We have Redemption for the Knicks, Julius Randall on the Patch autographs, Charlotte Hornets, JT Thor, we have McCollum for the Pelicans, Akeel Alexander Walker, Jazz, Jerry Stackhouse, Pistons, Usman Garuba, Rockets, Kenyon Martin, Jr. Rockets, Larry Johnson, Hornets, Quentin Grimes, RPA for the Knicks, Shadowbox Signatures, John Collins Hawks, Jonathan Cumiga, Warriors, Galinari Hawks, and David Duke Jr. for the Knicks. In our Mags cards, we had the Scorers Club, 5 out of 10, Allen Iverson, Sixers, the Jason Tatum signature moves, that is 4 out of 25 Celtics, and then the Brandon Boston Junior Team logos, 25 of 25 bookends. All right, that'll do it for number 30. We've got 31 coming up in a bit. Thanks everyone.


Welcome to this guided meditation. This meditation is looking specifically at working with the healing fountain. We all know that water has the beautiful and amazing potential to cleanse, to heal, to wash, to open our hearts, to cleanse our mind. And I want to welcome you to this relaxing meditation. And breathing, as we know, is the most important thing that we do. Yet we tend to forget about it. Never consciously breathing the best we're able to. So let's begin this meditation by taking three nice, big deep breaths. Paying attention to your belly and your lungs, expanding and contracting as we do so. Let's take the first nice deep breath in, fully breathing in. Taking it to the top, holding it for a second, and then exhaling, letting your body just become calm and relaxed. And the second breath, let's just take a nice deep breath in. At the top for a few seconds, and as we let it go, we let any of the worrisome thoughts just fade away. Anything that we no longer need or serve us, let it fade away. And the third breath, just filling your body with as much oxygen as you can. And then just letting the air escape from your body, relaxing you even further. And then just find your own breathing rhythm, just breathing in and breathing out. Every time you breathe in, you feel more calm and relaxed.  Just breathing in, relaxation and calm, and letting go of any tension or stress that you may have. And if any thoughts come into your mind, you can accept them, you can acknowledge them, you can let them go, and then just come back to your breath. And we're going to allow our mind now just to calm and relax. Every time we breathe in, we feel ourselves becoming calmer, we feel ourselves relaxing more. And allow yourself just to drift away, drift away on your natural breathing rhythm, breathing in and breathing out.  Just imagine yourself that you stood on this beautiful Mediterranean hillside, in this wonderful building, in the courtyard outside, feeling the warmth of the sun on you, smelling the beautiful olive groves. You could hear the birds in the trees, as you look around you, you see olive trees as far as you can see, leading down to this wonderful coastline, and grapevines on the other side. This beautiful Mediterranean spiritual space. And just to the left of you, you can see an archway. And you and I are going to walk to this archway. And as we do, we enter into this greater courtyard, beautiful gravel and stone all around your feet. But in the middle, there's a beautiful fountain. You can see the water just dancing as it falls down into this glorious looking fountain. It's the most beautiful fountain that you've ever seen. And I want you to picture it even more vividly, in as much detail as you can. You notice in the water, it's crystal clear. But it also seems to glow with this beautiful golden worth. And as we walk up to the fountain, we can see how sturdy it is. You can touch your hand on the side and feel that the way it's built. It's ancient, it's old, it's spiritual, and it's sturdy.   And you can dip your entire hand into this healing water. The pleasure that this water brings you is so wonderful that you might just have some more. So gather some up in your right hand and splash it onto your left forearm.  The moisture when your skin is glistening in the sunlight. Similar to how diamonds reflect there. Just do the same with your left hand, cupping the water and soaking your right arm with it right up to your shoulder. And you know that this water is not only extremely soothing, but its appearance is stunning. Cut both hands together and gather some more of this glowing substance in your hand as much as you can. Just watching it slip through your fingers a little, spilling over the edges of your hands.  Water touches your lips and it feels sublime. This water is heavenly. It nourishes you, it relaxes you. Take another handful, drink some more.  And the water seems to wash away all the worries you've ever cared. Everything you've carried over these years. And as you look around the fountain as it's just jumping you can see that there's a way you can just walk in. It's just built so it's hip level. I ask you just to step into the water. Feel this warm water coming up, this beautiful healing thermal water.  It's dancing all around you. Giving you this ultimate feeling of healing. Releasing any negativity opening your heart and cleansing your mind.  And at this moment I want you to allow for yourself to experience any special messages that you need to hear right now. Anything so you can gently and kindly open your heart, cleanse your mind to hear anything that you need to hear right now. And I'm going to leave you here now for a few moments just to enjoy this healing water, to get those messages, to feel the healing. So sit back, relax, and allow this water to cleanse deep into your soul. Extremely grateful and humble for everything that we receive with gratitude, with love. I ask you now to stand and look around you to take on board this beautiful spiritual space. A space that you can come to any time you so desire. I help you out of the fountain and just to your right you see this beautiful lounger with two of the most comfortable looking towels we've ever seen. Across I wrap the towel around you. I allow you to dry yourself, feel in the sunlight and warmth on your face. I'm going to leave you here now. You can lay down on that lounger and just allow your mind just to drift away, to heal, to cleanse, to rejuvenate. And find that spiritual space of love and light. And when you're ready, you can come back any time you like. There's no rush. This is your time. This is your time to spend healing, rejuvenating and giving yourself some love and self-care. As always, be love and give love. Until the next time, enjoy these moments.


Esoteric Chicho, do you recall your favorite volume of death gate cycle novels? Oh man, I started working my way through the series part way into the second book now. Do you like it Esoteric? It is amazing. It's an amazing series. What an amazing series. Into the Lamberth was amazing. The one with the red, oh my books are there. I forget which one. Oh, you know what? The whole thing is just, I don't know which book I read, what? And I don't want to give away any spoilers. Really. I can't give away any spoilers. You're only into the second book. You're in for a, what a ride. What a ride.  You don't want to completely shut it out. You've got to become anti-fragrant. You've got to know what's coming. But if you need time out, you need a break. You need to know what life, how beautiful and how brutal it can be. Read, market-wise, and Tracy Hickman's death gate cycle. You will not be disappointed if you like sci-fi fantasy.


What is going on guys, it's your boy the E.P.J here today with another Destiny video and in today's Destiny video We're gonna check out what Zer brings to the table on the 26th of June 2015 Now if you guys are new to Destiny and don't know who Zer is, Zer is a vendor who visits the tower for my Friday morning And leaves on a Sunday morning and with him he brings along exotic items that you can trade for strange coins and moats of light Now he's located in the tower this week straight down the middle On your right in the vanguard room and I don't know what the fuck I was gonna say then and let's just see what he has this week Okay.  He has one of the three exotics Actually need the peregrine greaves. Okay, these are leg armours for the Titan costing 13 strange coins Muds are carrying more ammo for heavy weapons and shoulder charge deals bonus damage when activated in the air These also offering 152 intellect not bad whatsoever. I actually only have about two strange coins But I've still got the weakest to run So I'm gonna have to grind at them weeklies just to get this a peregrine grease. Okay for the hunter We have the crest of alpha loopy this offering 158 strength costing 13 strange coins Muds are revive teammates faster spawn more orbs carry more ammo for special weapons and carry more ammo for hand cannons Okay for the warlock. We have the heart of praxic fire this one up in a hundred and fifty two discipline Muds are further decreases or ability cooldowns while radiance is active Carry more ammo for fusion rifles and carry more ammo for heavy weapons. These also costing 13 strange coins Weapon of the week. We have the red death pulse rifle one of the best weapons in the game in my opinion for PVP This thing is an absolute flipping beast if you guys do not own this be sure to buy it This will cost you 23 strange coins. I would if I didn't have this spend my last 23 coins on this I really would okay. We also have an exotic shard and costing seven strange coins This is used to upgrade your pre-existing weapons and armors, and then we have an exotic How me engram this costing 23 moats of light you'll buy these take it to the crypto And hopefully get something you need out of it But guys that's what Zeus brought on the 25th of June 2015 quite pump the Haysport the Peregrine Greaves That's made my date really as now. I only need two exotics to have the complete collection But guys that is it for another video. Hope you guys enjoyed it Deserving anything you guys needed let me know down below in that comment section Thanks for stopping by as always and peace out until next time. Peace


Hi everyone, my name is James. Some of you may know me over here. I spoke at Hackware yesterday. Every year I try to give like at least one talk in Singapore. I currently work in the US states for the last like six years. Currently I'm at Roblox which is well it's like a game platform but you know you don't really compete with JavaScript but it's a game platform where you build games and you play games and there's like a micro payment system and many kids actually build games using lower script. Yeah, this is Jerry. He works in Singapore and he's sorry? No, we go carry on. I'm trying to connect to the Wi-Fi. Yeah, because we have a demo that actually uses the online stuff. Yeah, so this is actually a project that started off a few years ago. I decided that I would rather like you know like release it as soon as I can. I have to make a commitment to release otherwise it will sit at the bottom of your project's bin for eternity. Yeah, so what is this? Snapcache is basically an open source alternative to Firebase. So how many of you actually use Firebase over here? Oh nice, quite a few of you. I was worried that no one would understand what I'm doing, right? So I used Firebase many years ago ever since they were a startup. There were some hackathons and they were probably the first real-time database before parts came out. I'm not so sure which came first. After that, Firebase was bought by Google and they are now part of Google Cloud. In my previous company, we actually use Firebase in production. So we have quite a bit of experience with it. Yeah, so yeah, there are two other people on my team, Frank and Theron. Theron couldn't be here today. He had national service commitments. Yeah, so history, right? The Firebase is on Google Cloud and the story is like this, right? Usually I wouldn't rewrite something that already exists but when we were running, using Firebase in production, what happens is that Friday evening, I'm not sure who in Google decided to push and update their service and it broke our service with like 10,000 users using it. So naturally being one of the few backend people on the team, we had to hack out some fix and we fixed it over the weekend and on Monday morning, they reverted whatever they changed on Friday. So it broke again. So naturally like our higher ups were very happy and it's not really our fault but we just decided, okay, it's time to DIY and we want to in-house this core component. Why? Because Firebase is like a real-time database, a real-time communication system that we use it to support our applications. So the key components are essentially Redis and Snapcache. How we started off as, how we started off doing this is primarily when we were looking around for Firebase made backend source code which doesn't exist but however, there was a repository created by an ex Firebase engineer which created like a stub, like a stub, how would I say, a stub library which allows you to test Firebase offline. However, it doesn't have persistence and it doesn't scale. It's really just for you to do like a test, part of a test driver or something. And for our architecture, the current architecture, you usually use Firebase as part of Google Cloud. Typically, you have your app, you have a Firebase SDK, you could use the JavaScript SDK or the Java SDK. The SDK is really efficient at communicating with the backend because it uses web sockets, not your REST HTTP stuff. And when we wrote our own Firebase backend, we essentially want to replace it. So what do we do? We actually have a Node.js server which runs Snapcache. We are able to reuse the web socket protocol. In the past, when it was closed source, the web socket protocol was kind of like obfuscated but after the open source, the SDK, understanding the protocol was much easier. We use Redis as the backend persistence storage primarily because we are able to scale. I'll explain more about scaling later. Setting this up is really easy. I just like released it publicly earlier today. And you just need to start with Redis, start up the Snapcache instance. You can run multiple but over here, let's assume you run one.  So it's really just these two components. One of the key differences, if you have used Firebase before, you would have known this thing called the permissions setting. The rules. Rules basically define which node in your Firebase database is a particular connection able to read or write or both. On Snapcache, we don't have any nice user interface. So you actually modify part of the JavaScript on the server side. So how do we scale? We actually use this in production in my previous company. We have like 10,000 concurrent users. We simply add more nodes to the Redis cluster and we have just launched more instances. Snapcache is designed to scale horizontally, which means that you just add more instances to it as you scale. We are primarily bound by the number of nodes. The number of subscriptions because Firebase, you are able to like subscribe to a particular data node. And when there are changes on it, your client will receive those changes. The number of subscribe nodes and the Redis write throughput because Redis is like single trailer and you can only like, how would I say have like only one instance in the Redis cluster would be the master of all the writes going to it? So our production architecture is not too complicated. We simply horizontally scale the Snapcache instances, which is just more node.js instances of it. And for Redis, we just add more nodes to the cluster. This primarily helps with the read throughput because usually for most real-time databases, you have one write, but then the read is distributed to multiple clients. For example, if you have a chat application, when there are 10 people in the chat, you send one message to it, nine other people need to receive it. So for future work, we know that this is kind of like a really like simple, how would I say? Not really simple, it's more like we did it primarily for our own use. There is no dashboard.  Some dashboard will be nice. We definitely need test cases and documentation, which usually the last few things most people have. Yeah. And one thing I do know that is that we do not currently do not support sharding. So if let's say you have multiple Redis clusters, you would want to enable sharding to basically increase your write throughput if let's say you have a really large pool of users, maybe 100,000 or 1 million depends. Yeah. So now it's time for the demo. Yeah. I'll pass over to Jerry. All right. Thanks, James. So I'm Jerry. I'm a developer, full stack developer. I actually contribute actively to the local startup scene. I take quite a lot of hackathons in Singapore. Some of you may have seen me before. Yeah. So basically today, I'm going to talk about like, okay, if you're sitting here, maybe you're a front-end developer, maybe wondering how am I going to integrate or use this on a front-end, right? How do I call the Firebase or how do I use the Firebase SDK and like call or use Snapcache? So this is any like React developers here, just like show hands. Okay. Cool. Good. So I know that basically, yeah, I just did the tutorial like last night or something. So this is the demo, demo app that I did in React. Yeah. So to just show you guys how, basically how you do it in your, if you're a React developer. I'm sorry, I'm not a ViewJS developer, so I didn't know how to view. Okay. So basically, AppJS. All right. You have your props. You put your state, right? Simple boy plate code. Okay. Actually, it's very simple, right? It's like all your five days as SDK all works out of the box. The only thing you need to change is like the configuration and point or where you point your data of these two. You have your subscriber. You subscribe to, you have a value subscriber. There's also the, what's the other one where you have like more, but these are the value subscriber on, you mount it, you edit when, you know, on component amount, just remember to amount it. And then you have a value callback basically when something changes, let's say, so this is a do-do app, right? Yeah. So we have a list of tasks and then somebody, and you have many people that's trying to add things to this task, do this list of tasks. Okay. So what happens is somebody else adds a task. It's actually subscribing to the entire collection. So the entire collection is actually returned in the snapshot. Just iterate through your snapshots and then you set state. This is where you set the state, right? And then your react component will be rendered. So pretty basic and very simple. Yeah. Okay. So the only thing you need to do is basically, basically we are replacing five days with like our own, it's like five days server, right? So basically you just change the database URL to the whatever IP address or whatever pod that you mounted your snap cache on. Okay. The rest of the stuff is, yeah, you can implement it if you want. Yeah. Okay. So this is like, okay, the last piece, just make sure, so you just make sure you have the Firebase SDK as your dependency, you download it, install it. It's the usual stuff, right? It's on like the Firebase tutorials. Initialize the app with the config, with the new config. And the last part is very important. Like, okay, so this is like where you put it on your database API. And they just remember that you have to make sure it's a single turn. Like you don't initialize it multiple times. That's what a try-catch that is there for. Basically Firebase doesn't like it when you try and initialize multiple times. Yeah. And you got it. So let's see how this works. Okay. Enough code. Hold on. Right. Okay. So, right. So you're going to use like two separate browsers to like simulate two different clients. Okay. And all right, let's try and add some tasks. Anyone volunteer some tasks? Like, so one of the tasks that I was doing just before I left for this talk was writing a readme for this repo. If you go and look at the comments for our repo, the readme was just updated like at 5.30 today. Okay. Yeah. Okay. It pops out on the other screen. Yeah, it works. This real-time database. Okay. So, yeah. Essentially, yeah, this is like what we're doing. Like you have sockets, like sockets subscribing to changes on a database and then you have changes on one, it shows up on the other, all the other clients. Yeah. And then maybe another one like arranging something for Valentine's Day. Okay. Yeah. So, I think that's it. Right. Okay. Oh, I don't know what to spell this. Yeah. So, that's the demo. Yeah. Okay. So, any questions? So, just to confirm, do you use the actual security rules in the same format that Firebase uses? Yeah, that's correct. And two, how do you handle the off, the fact that you can do authentication with Firebase that's tied to the security rules? Yeah. So, this was built in a time where, sorry, this was built in a time where we weren't using OAuth. I'm not sure what new authentication methods they used. In the past, we would actually use like its own internal keys. Yeah. So, there is no OAuth support and moments. Yeah. Any other questions? Yes. This one is for the Firebase web plan SDK, right? The real-time database? Yes. Just as one is also for the back end part, the Firebase admin. So, will it also work with Firebase admin? I haven't really used it for quite a while, but it doesn't really have like the new stuff that Firebase introduced. Yeah. This is purely for the real-time database. I think the SDK we're using, what version was it? Five more, right? There's a version basically you and me. Okay. Right. Yeah, there's a version that we tested until. I'm not sure if the newer stuff actually works. Yeah. But usually, I think what we like to use this for, for example, like one of the use cases that I actually want to try to use this for home automation, because previously, my home automation would run off Firebase and would like go over the internet and I find it's quite kind of silly. So, if I wanted to like bring it down into my own like, you know, run it locally, right? There isn't any other way except using this. Yeah. And if let's say you want to give a demo that purely runs on your laptop without the internet, you know, this would be another way as well. It's great for hackathons. Yeah. Any other questions? That's the repo. Oh, yeah. The repo is... Yeah, this is the repo here. Yeah. You can just go to snapcast.js.org. Yeah. Welcome for contributors. Yeah. Yeah. Anyone like, you know, you still use Firebase and you want to go check this out. There's many things that are not really implemented, you know, completely. So, you know, feel free to contribute. Yeah. Yeah. We are not packaging this up. There's an MPM package. Yeah. It's not an MPM package yet. So, yeah, you have to fork this, but we'll get there someday. Okay. Thank you. Thank you.


Today I'm going to show you how to give your photos that cool faded look. What's up nerds? Today I want to show you how to get that really cool faded look. Now I know all of you have seen this look before. It's all over Instagram. It's all over Flickr and 500 pixels and it's something that a lot of photographers use in their photography nowadays. And I've been asked a couple of times if I could show some people how to do that. And so I want to take a moment today to show you a few ways or a few things to consider when giving your photos that faded look inside of Lightroom. So we're going to jump in here and play around with the picture real quick. Now before I go ahead and do that, here's the deal. This is a look that's probably not for everybody. Everyone has different tastes and different styles and I totally get that. I also like to think of photography as recipes. It's like cooking. You might like lasagna and other people might not like lasagna. And so it's really a matter of taste. The same way it is for eating food. It's the same way for creativity.  So this is a little subjective. It's going to work for some people and it's not going to work for some people. So just kind of keep that in mind. But I just want to show you how to do it.  So let's jump into the develop module and show you a couple of things. So the first thing, probably the easiest thing to do is to head into the basic panel. Typically, if you reduce contrast moving your slider to the left or into to the negative as you reduce the contrast down, you'll actually give the photo a much softer look. So reducing contrast is one way that you can give your photo a faded look. Another way that you could think about giving your image this faded look is to reduce the blacks. If we head on over to the black slider and we move our slider to the negative to the left, the blacks are going to get darker. So unlike contrast, we want to move it in the opposite direction. We want to move our blacks to the plus, making them brighter, which is moving them to the right. And sometimes by moving the blacks up, you'll start to get a softer look. So what I would do is in conjunction with moving my blacks up, I would then go in and then move my contrast down. And another thing that you could do is even reduce the clarity just a little bit. That will also soften the picture. Now you want to be really careful with clarity because clarity will actually make the picture look muddy and yucky if you go too far with it. So just a little bit, but between these three sliders alone, contrast, blacks and clarity, we go from this as our before image to this as our after image. So when you kind of mix these three together, you start to get that faded look. I'm going to go ahead and reset this back to the beginning and I'm going to show you another way. This is probably the more common way that people will give their photos the faded look. And it's by using the tone curve adjustment. So if we go under our tone curve, I've not talked a lot about the tone curve in this channel yet, but I plan to do some tutorials on the tone curve because I think it's a really powerful and underutilized tool for a lot of beginners.  This is just another example of that. So now all you're going to do for the faded look is on this tone curve, we have this diagonal line going at a 45 degree angle. And what you want to do is try and click, not click, but drag the lower left bottom point or the corner of this line. And you just want to drag it up. Now you can see that faded look happening here, but I want to just tell you something that happens to a lot of people.  It'll sort of get stuck and instead it'll do some like weird thing like this where the curve is actually bending. So a little trick that I have found to make it easier for you to actually fade this the way you want is grab the point and drag it to the right and then start to move it up. So don't try and just drag the point from corner straight up because sometimes it'll give you some problems. If it works for you, fantastic. If it doesn't pull it to the right and then start to drag it up. You'll get that faded look you want and then you can drag the pen back over to the left hand side. And so now I can easily move this line up and down until I get just the right faded look that I want.  If I'm going to leave a link in the description below or you can look at the card right here in the top, either one will send you to where these free presets are. You can download them, load them into your catalog and play with them. But if I show you what they look like and just go on to my presets and go over to these faded free ones. I've got one that works really well. If you have people in your picture like I do here, if I go ahead and click on it, it gives you this really nice faded look. Or you can go with the black and white faded, which will give this a really cool kind of vintage vibe. Now if you are someone who is a Patreon supporter, we've also loaded some additional faded presets on our Patreon page. Some of them or two in particular that I really like is this cool faded, which if you have a photo that's really warm and you want it to look a little bit colder or a little bit bluer, this one's really cool. And then we also have a warmer, browner faded look for you as well. But there's four or five other presets in this pack. I think there's a total of six here on our Patreon page and then two free ones that I'm just going to give you if you head on over to this link here. So enjoy those, play with them. It's also important to know the way presets will look good on some photos but not on others. So if you try these presets on one photo and it doesn't look good, it's not the preset. It's the photo. Try a different photo and see if that preset looks better on that image. Eventually as you scroll through different images, you'll find the one where this preset is just magic on it. So don't give up on them. They're really cool. As you can see here, I love them. I use them all the time, but it's got to be the right photo. And that's not true of just my presets. That's true of anyone's presets out there on the market. So hopefully you enjoyed this tutorial, found it helpful or useful or fun. And hopefully you'll download these free presets and use them on your pictures. Use the hashtag PNFL on your Instagram account if you're using these presets. I'd love to see what you guys are coming up with. It's always fun to check out other artists' work and see what you guys are doing. That's part of the community that we're trying to build here. So that's all I've got for you today. Thank you so much for watching. Have a great weekend, everybody.