Boom. What's up, money geeks? Mr. V here. Welcome to another video. So in this one, we are going to talk about Ticket Symbol, RIV, and Rivian auto models. Again, this is an IPO that we covered here on the channel and I told you guys what I was gonna be looking at this IPO when it came out and this has been some updates so I wanna make sure that we are on top of this. Before we get started, guys, if you're new to the channel, we talk about how to earn money, how to save money, how to invest and build wealth. So that's something that interests you. Go ahead and hit that subscribe button and the notification bell so you don't miss out on new content. So when it comes to Rivian auto models, again, this is one that we've talked about here on the channel. This IPO I think is gonna make some noise on Wall Street because they keep moving the price up and up and up. So I know this is gonna come out out of the gate hot. So if you guys remember, no, again, the company Amazon invested in this company massively. So be aware of that.  So CNBC was reporting that they have updated their perspectives and changed their initial offering price from $62 like we talked about last time from $72 and between $72 and $74. So if you see this thing went from $57 to $62 and then now they've moved it to $72 and $74. So it just, I mean, just keep driving the valuation of this company way, way up. So if you go take a look at the perspectives, you can see now, this is the amendment right here showing $74. So I anticipate that when this thing came out of the gate, it's not just gonna be $74. Look at this thing to get somewhere to $95 or even a hundred right out of the gate because this is what people on Wall Street are gonna be paying, they're big banks. They're gonna be paying this amount. But me and you retail investors, by the time this thing hit main street, it's gonna be $100 or $110 before we can even touch it. So personally, my game plan is I would day trade it if I can and then wait for a pullback before getting because if you buy that tip, remember what happened to Coinbase, you buy at the tip when it pulls back, you're gonna be holding a massive back and I don't wanna hold it in the back. So I'm gonna day trade it, take some profit, but then wait for that entry point. So that's the object I wanted to give you guys. So if you are still debating, if you wanted to get into this, I'm gonna do a separate video. I think the IPO, very few places are offering the IPO. So I'm gonna try to find where you can buy this particular IPO, do a separate video on that one.  Amazon is a huge investor in this particular company. Amazon has what we call the DSP program where they have a lot of veins that go out and deliver their customer's products. So if anything, if Amazon invested huge in this and Amazon is driving to go green, then why would they not wanna use this company to build those vans? So that is my, my trend of thought here is that the way things are gonna play out, but no, but that's how I do the math and try to figure out why I think this company is gonna succeed. Because if Amazon turned out to be their only customers, they're still pretty good because Amazon is pretty much everywhere.  You see they drive those Amazon Prime delivery vans all over the place. Imagine that they stop using Ford or Dodge and start using Rivian for that. So that is a potential catalyst. And then they're also trying to carve out a niche for themselves for outdoor trucks. So not just your average truck, but if you are like an outdoor person, then this truck is for you. So that's another thing that you have to keep an eye on. So again, I'm gonna keep you guys posted. So right now they are projected to go public Wednesday, November 10. Usually you don't give you any timeline when that's gonna happen. So I try to make sure that I open the ticket symbol and have it on my screen and just keep watching it until it starts to trade. For the most part, as retail traders, you don't have any options but just to wait. So they give you the date, but no specific time. So that's something that I want to keep an eye on. So if you're looking to know exactly when that's something to do. And again guys, if you're new here, we talk about how to earn money, how to save money, how to invest and build wealth. So that's something that interests you. Go ahead and hit that subscribe button and your notification bell so you don't miss out on new content. Also, if you're looking to get help with investing, Weibo has their promotion where if you sign up and deposit five dollars, you get free crypto and some free stocks, links in the description and as always guys, do you do diligence, don't be a greedy savage. Stay motivated.


This video is part of a series and you should check out the description of this video for the full playlist. But today we're going to quickly look at a few ways to check out the information on the memory on your system. First option, which is readily available, is free. If you just type free and hit enter, you get some information there on your RAM. Another option would be to cat out PROC MEM info and that will give you some more information on your current memory status. Other options to quickly get a look at are two tools that may not be installed by default but are readily available. The first one is TOP, which not only shows you what processes are running but up here will show you how much memory you have, total, free, used, and same with your swap. Now, TOP is nice and simple but there's also H-TOP. H-TOP is very much like TOP but a little bit nicer looking.  So it's a little bit nicer. Again, TOP and H-TOP are readily available but not necessarily installed by default on your system. On most systems you should be able to type free to see it. That's pretty much standard as well as cat forward slash proc mem info, just cutting out that file showing what's going on there. So those are four very simple, very quick tools to see, get a quick visual of how much memory is available and being used on your system. As always, I appreciate you watching. I ask that you think about becoming a supporter over, patreon.com forward slash metalx1000. There should be a link in the description. Check out my website, filmsbychrist.com. That's Chris with the K. There should be a link in the description to that as well. If you can't support financially, even though just a dollar a month is much appreciated. If you can't do that, be sure to like, subscribe, share and comment on this video. I thanks you for watching and as always, I hope that you have a great day. A bonus note because I forgot to say this. I mentioned the free command which shows you but you can see that's a little hard to read. Free dash M, it will tell you in megabytes the RAM you have. If you say dash G, it will tell you in gigabytes. If you do it in dash dash terabytes, it will tell you in terabytes, which is bigger than I have, but you can also just simply use the H which will make it human readable. So if your reading is in megabytes, gigabytes or terabytes, it will automatically convert that. So free dash H is a great command to remember. So a little bonus there. Thanks for watching and hope that you have a great day.


Good morning everyone after a week of without political science 303. I know you've missed this class very much Therefore you have an in-class assignment. I know how much you missed writing papers for this class So you have an in-class assignment on Thursday at 1 p.m. So that we write it down in about 25 minutes Okay on Thursday 1 p.m. You you must have received an email Through stars airs if you haven't done so you have to see either me or somebody else For this the in-class assignment will be on Brexit okay, why Brexit happened? According to one political scientist Who teaches on? Refugee issues might migration issues and globalization and especially globalization of labor and migration, so Please watch the TED talk. It's going to be a TED talk as Announced it's less than 20 minutes. I think it was about 17 minutes or so I found it very, you know amusing to watch it was It flows it's a nice talk by a colleague from the UK and I we will be asking you one question out of it Which is more of a discussion question rather than okay. Tell me What year did Brexit or what day Brexit happened or what day? The referendum on the Brexit Happened okay, so so rather than an information question think about a discussion Question or discussion topics okay for this Assignment you're entitled to bring you're allowed to bring one page With your handwritten notes not in pencil But in colored pen okay or in colored pencil Whatever you want, but it shouldn't look like a photocopy like a Xerox copy. I want you to Note down your ideas your own ideas therefore, I won't Allow any plagiarism either from a text or from a friend of yours Okay, no copying so so please follow the instructions you will be handing in the a4 paper or paper with your With your in-class assignment Before I continue with this you will be writing in total two assignments. I will be giving three assignments You're entitled your you can write only two of these You can't write a third So pick and choose the fight You want to pursue? In each of these in-class assignments, it'll be something similar to this a Video or an article or an article and a video on a current issue that Reaches or that is at the top of the political agenda of these Case countries, okay, so in total you you're required to write two You should be able to pick two out of three But the this is the upside to it the downside to it is that There will be no makeup for an in-class assignment so if you miss if you don't take the first and And miss the second you will be losing five points According to our contract, which is the syllabus, okay? So so please make sure that you either take it or you don't fall sick Okay, so that you come to class and write the assignment now any questions on anything on the assignment or or Britain Any questions about Britain which we have completed last week around this time? We didn't have class on Friday Because of the jumul yet by gamma the republican day or republic day. I'm sorry So My plan today is to discuss. It's to start my discussion on France Okay, so And in about two weeks Will write a midterm So the midterm will be comprised of questions in Or on Britain and France compared so two major cases But think of these at the back of your minds, but there won't be any direct question coming out of those pieces that that you have That you've already written a quiz on the results of the quiz will be announced before Next class on Friday. So we're still going over them And and here is France if there are no questions No questions All right We'll do exactly the same thing for France in comparison to Britain Remember we first talked about The British history in this or the British history or state tradition in historical perspective So we'll do French state in historical perspective or history of political history of France how the French Republics came into being in the 21st or 20th century and then where we are in terms of You know Politics and power in the 21st century then political economy of economic and social policies economic development social development Followed by governance and policymaking where we'll look at the executive and its relationship with the other organs of state and And also the French model of Statehood, you know, what's the administrative system like in France fourth? We'll talk about representation and participation and finally we'll We'll discuss some current challenges and then we'll be writing our midterm. Okay, so Whenever you we I talk about or you think about France think of it in comparative terms With what we've discussed for Britain Okay, so so you should you should keep that in mind all right a little bit to start what does France look like you know where France is on the map and We have 22 plus five regions In France that make up France Five of these are overseas regions Corsica, which is off the coast, but Guadeloupe French Guyana Martinique and reunion are the are the other areas other regions of France We have 96 to 100 I Mean 96 departments Plus five overseas departments around 100 101 Overseas departments departments think of departments as Provinces or small-scale provinces Compare that to to Turkey if you if you will France is in the Temperate climate or enjoys a temperate climate as you can see it has its coastal It has coasts on the Mediterranean and also on the Atlantic Right across is the is the is Britain as an island. We've got the channel the tunnel and Which which which connects? Britain to to France of very large quite large one of the largest areas in Europe one of the you know largest countries in Europe Populated quite densely about 63. I'm sorry. It used to be 63 now. It's 66 million So we have 66 million inhabitants in France It is very much fertile. So it is very amenable to agriculture Also because of the temperate climate it enjoys and The French state as we shall be talking about is a unitary state. It's a highly centralized Unitary state so unlike Britain we have yes a unitary state But this is a more centralized form of unitary states Okay, very hierarchical the the center is very much powerful in comparison to isn't tight in comparison to what we've seen in France Population-wise it is widely it is heavily populated But in comparison to To Britain which is about 60 million Which is around the same But when you compare that to to Germany, which is around 80 81 million it is less densely populated Let me now turn to after this quick introduction some history things start with the fifth century the breakup of the Roman Empire for 75 Right for about five centuries. France can France remains to be part of what's called the Holy Roman Empire The principalities Kingdoms and all that And then it it comes under the domination of Merovingian and Carolingian dynasties Charlemagne by about the 8th century or 800s becomes the king So France Charlemagne Charlemagne France Then Capetian monarchs dominate France In the 14th century it was almost Being dominated by France are dominated by Britain But then defeats Britain in what's called a hundred years war. So by about Istanbul was conquered the war ends 1453 Then something Important happens. We have all throughout 16th century. These are basically highlights in French history or milestones in French history All throughout 16th century we have religious conflict War of what's sometimes referred to as the war of religions Protestants the newly born stream within Christianity and Catholics come in conflict for almost a hundred years all throughout the 16th century Then we have Henry the fourth Through the addictive not Providing toleration or religious liberal liberties to the French Ugueno's or sometimes refer sometimes pronounced as ugueno's So so French Protestants Are being given religious tolerations. So that's about the end of 16th very early 17th century Okay, so that's that's important then France rivals England in Its claims to North America up north French territories in Quebec Which I mean part of Canada is called sometimes in history. It was called Nouvelle France new France so Quebec was the area there and Down south we have Louisiana which which came under French influence. So so French the French and the British the English then Really rival one another are competing for those territories in North America They want to colonize those places. They want to keep their colonies to themselves and they fight over those colonies Overseas, okay, so colonial wars with Britain but overseas As you can see there's so much competition between Britain and France in the 17th century 18th century but then France was defeated in seven years war in 1750s 1760s But about this time Let me go back to 16th century another milestone in in French history, which we Talked about very briefly when I was talking about the absolutist regime remember We've got the Ancien regime which crystallizes in the 17th century. So early 1600s yes throughout the 1500s there were there was some Century pedal tendencies some centralization Emerging in France in the French lands back then but with this 17th century we have The Bourbon regime Controlling much of contemporary France and builds What's called, you know the absolutist state Absolutist states are characterized by strong bureaucracies and That they were territorial remember we talked about this in much more detail these bureaucracies were of two kinds tax collection and Very good military bureaucracies so Louis the 14 says let us say more The state it's me So he says okay. I am the absolute ruler here. It's a certain type of Early modern state that comes to the historical scene and It really lays the groundwork for what's called the modern state, okay? and by about the mid 17th until about the mid 18th year 18th centuries We have frequent war and stagnant economy so France comes under war It's there's there's this frequent war with with her neighbors And also its economy stagnating so and and And compare that to Britain When did industrialization in Britain start in Britain first industrialization 18th century So by about mid 18th century industrialization starts in Britain, but we have stagnant economic activity here in France So France did not industrialize When Britain industrialized it became a follower It became because of its stagnant economy because economic activity was low in terms of levels it remained In in some sense underdeveloped or undeveloped or in a way backwards Okay in comparison to her arch rival Britain Stagnant economy the regime pressures pressures peasants even more with taxes and From one standpoint, we've got the French Revolution. We'll talk about this in more detail But what's important here is that? Absolute a state so a certain type of state reigning France or dominating France the Bourbon dynasty It's a monarchy. We've got the king with absolute powers coming to power and frequent warfare stagnant economy then we end up with the French Revolution. What does the French Revolution look like? in this Juncture critical juncture we have The monarchy and the ancien regime being toppled Okay, Parisian crowds Rain or they they they run into the French State-controlled prison in Bastille, which is in central Paris. They raid Storming into Bastille and they freed the prisoners So the prisoners of the ancien regime have been freed so we have a new new regime That is in the making This was a revolution Quite a big social Change political change with all kinds of ramifications cultural ramifications, but also social religious Political as well as economic it was a nationalist or national Revolution in the sense that people Were given the right to choose or people thought that they were given the right to choose Which nation they wish to belong? and and by this The monarchy the Bourbon monarchy the ancien regime was undone So so it was in that respect a national or nationalist revolution. It was abolished But later state institutions as we shall be seeing state institutions were reinforced that was the irony of the French Revolution, but it was also an international Revolution which inspired all of Europe and also elsewhere so the ideas of or the ideals of The three ideals of the French Revolution which inspired not only societies Peoples in Europe, but also elsewhere. What were these three ideals which represents which represent the flag the French flag? Liberty liberty equality and fraternity brotherhood Liberty is the blue equality is the white and brotherhood is The blood okay is the red so so these ideals have influenced Not only societies right next to France, but also elsewhere You've you've we've all Read about the decline of the Ottomans for example in our in our history textbooks It was in a way a liberal Revolution because it brought with it Individual liberties the idea of or the motto of liberty so the idea the ideal of liberalism or Individual liberty, but also secularism the idea of secularism. Okay, it's it's We had the entire 16th century one century of bloodshed in the name of religion Catholicism versus Protestantism Okay Therefore the the French the new system the new regime after the revolution meant Excuse me, so so let's forget about the past. Let's start a new new future and Let it be this time secularism by secularism the French mean Laicite the idea of what's the difference between laicite and secular way of life? Laicite and secular way of life secular way of life Yes, you may be religious, but you I mean you you you put your your religious ideas ideals on the side and you lead a life So you'd I mean you'd your your your life It's not dictated by the precepts and the principles of religion This is for individuals or societies, but if you want to describe a state a secular you you generally refer to it with the With the separate it's a specific term called laicite so so when it's when we talk about Statehood when we talk about states secular states we we refer to the French word Laicite the ideal after the 16th century the entire 16th century with the French Revolution the with the you know liberal revolution we refer to it as the You know laicite secularism in that respect it was a democratic revolution in the sense that from Those years onwards. We have all citizens All citizens are being on an equal footing or all citizens should enjoy equal Rights qualitative as well as quantitative rights all all different kinds of rights So so this was in a way as a a revolution which brought with it all kinds of changes transformation ruptures not continuities like or as opposed to what we've seen in Britain remember the glorious revolution we don't talk about all this kind of stuff. Yes, you know religious Did the question of religion had been resolved? But but this was a massive rupture with history whereas in Britain We had some kind of incremental change or incremental progress, but here we have the old order being undone abolished a New system was put into place and then we will have we will see that new systems will also be being put in place later on Immediate aftermath of the French Revolution. We had a reign of terror The revolutionary regime was brutally intolerant and they were so hostile toward women that the All those ideas about the revolution the fraternity Egalité liberty were really betrayed then French destabilizes once again All these instabilities Come and go Let me highlight those Sequences one by one So the French wished to call Every regime every stable like regime a Republic okay What happened was with the French Revolution the idea of a Republic as a Regime emerged. What's what does Republic mean? Republic I Don't mean Plato's the Republic, but what do we mean in in political science? What do we mean? when we say Republic It's a form of government Yes, we've got citizens instead of subjects. Okay. Yes, but what's important here is that Compare not necessarily compare that to the Ancien regime Not necessarily generally Not necessarily but generally yes, but what's important here Contrast that to the monarchy in Monarchies we have rulers with Blood ties so it's hereditary in Republics, it's a form of government in which we do not have hereditary Institutions or hereditary power. Okay, so rulers They don't they don't follow a dynasty okay, they change over time all right so the ideal of Republicanism or Republic here is that there was a rupture between The Ancien regime which was a monarchy centralized monarchy versus Republics okay, so whenever we talk about monarchy's we don't talk about Republics So in that respect is Britain a nation-state Somebody said nation when I asked Republic is Britain a nation-state It is a nation-state. Yes. Oh, you said now. I'm sorry is Britain a democracy Yes, is Britain a Republic? Okay, is that clear do we understand the difference between Republic and monarchy and and these categories of democracy nation or nation-state or nationalism and and Republic anyway, so first Republic immediately after the great the French the great revolution Napoleon Bonaparte who was an army general installs a coup and Declare himself as emperor 1802 He declares himself as the first emperor. Okay, so he installs an empire But then in about 15 years he was defeated by the English So again French British rivalry and the monarchy is restored meaning that the first Republic ends Okay, so first Republic ends because monarchy is restored restored Second Republic About 30 years later There was an uprising against the ruling monarchy in between these these republics that there was a revolution and There was a republic for three years Okay, so a new regime comes to power Louis Napoleon who happens to be Napoleon Bonaparte's nephew and his heir Says I'm the the emperor. I'm the king but later on Franco-Prussian war and The revolutionary people producing the Paris commune civil war 1870s weaker government democracy for a year. So again everything goes down the drain For after three years and then it's aftermath we go back to some kind of monarchy and instability Third Republic after the Paris commune 1871 This becomes more durable in which which lasts about 40 another 30 about 70 years Okay, we see the emergence of a parliamentary system. So we have a parliament with a weak executive because the The founding fathers are thinking These were strong executives Let's now change it to Weak executive and the strong parliament, okay but This system also Ends up with the Nazi invasion Nazi occupation 1939 1940 so So the Third Republic Gets undone when we look at the period between the early 19th century and the pre-war periods pre-World War two period we see an oscillation between Strong parliament weak executive or weak parliament strong executive Republic versus Monarchy so monarchy and some kind of radical democracy those democratic ideals Whether it it would fly But when we look at this we see Frequent regime change So regime the French mean in this period for about more than a hundred years We have frequent turnover in terms of Not so lasting regimes right first Republic monarchy second Republic upheaval third Republic upheaval well war and Then there will come the fourth Republic. So up until the fourth Republic and the World War two we have French system French state being Really imbalanced and also very I mean the French system as as in very highly unstable system. Okay, so Political instability could Characterizes all this this almost a century and a half the enduring questions linger state autonomy so Remember that this comes from a French a French style absolutist state So the the French way of organizing your state Autonomy from society state autonomy from others insulated state or insulated policy making from its societal sectors versus democratic participation of of Internal groups which was which emerged especially after the French Revolution. So the pendulum swings between not only monarchy and Radical democracy, but also state autonomy versus democratic participation and State autonomy democratic participation state autonomy democratic participation. So so it's it's a back and forth movement all the time highly unstable secularism 16th century War of religion or religions But the French ideal of secularism had not been settled. Yes, it is there in the French Revolution It is an ideal But still an unresolved question at the back of the French psyche in terms of its citizens Political conflict continues Instability continues In the meantime So when we look at I mean we talked about the fact that Britain industrialized by about the mid 18th century, you know Light industries late 18th century head industries. We have all throughout this period up until World War two almost Slow industrialization slow growth. We have a large peasantry We have Limited natural resources Except for some coal which is neighboring France Alsace-Lorraine underdeveloped entrepreneurial spirit that was also unlike Their neighbors right across the tunnel or right across the English Channel Slow population growth, that's also important and high protection through tariffs protecting French industries against its competitors through high tariff walls, okay, so which meant that efficiency of the Manufacturing sector, which was limited anyway was low Productivity was also low because it wasn't in competition and Also the French ideal of Civilizing mission What they call the mission civilization civilizing mission. It was also very important by this The French meant its white man's burden Like the British its white man's burden to expand to to expand French ideals Republican ideals Economic growth economic progress to elsewhere so bring about change elsewhere But this was used more of more or less as a pretext For finding markets as well as natural resources Just like in the case of Britain to a certain extent So Then comes war We have a new regime installed throughout the war it's more or less a puppet regime it Enters into an armistice with Hitler the French state Which divides France into two in the north we have direct German control in the south We have an independent or quasi independent or independent looking or seemingly independent puppet regime in Vichy, which is a central city in France So so it controls some parts of France, but the northern parts are controlled by the Nazis, please Ha Oh, I don't know that we should look into that it may have been the case But would Vichy regime include Southern part of it may be true. It may be true. I don't know that but it's it's it's worth looking it up So so France is divided into two the north is under the Nazis the Vichy government in time throughout the war years was fiercely opposed by Different segments in society especially by communists by Socialists and by progressive Catholics so So there was much reaction to The German occupation up north But there was also much reaction to the puppet regime in Vichy the French state government in Vichy and Dugol general Dugol Sees his power he gains control over all those that rally against the Vichy regime and Says okay, I propose a new regime with strong leadership and citizens vote for this for this regime and They say no, we don't want that so general Dugol retires immediately but immediately after we see the emergence of an Opposite type of regime where we've got a strong parliament and the weak executive. This is exactly what The goal insisted against he said I want a regime because we had so much instability I want a regime of strong executive weak parliament, but it was defeated in the polls by citizens and we see the emergence of a force Republic with a strong parliament and the weak executive and Proportional representation so so as you can see not winner takes all system, but a more proportional system more democratic system In its ideal form, but which but this brought all kinds of instabilities with it The in the in the in the ensuing elections There was economic development Yes But the French were involved in Vietnam in the 50s 60s they withdrew from Vietnam and they also Wanted to crush an anti-colonial Rebellion in Algeria, but they the French state the government could not do that and then there emerged general goal out of retirement and says hey Let me change things once again and he emerges As prime minister and installs a new regime, which is called the fifth republic so He and his associates draft a new constitution Which gives much stronger role to the executive and much weaker role to the parliament so as You can see strong parliament strong legislature weak Executive now turning upside down strong executive weak legislature So so that's how the fifth republic comes into being What's important here is that we see again Again in the 20th century the swinging of the pendulum from strong executive weaker legislature to strong legislature weaker executive back to strong Executive and weaker legislation Okay, so and that's where we are and and many observers think or see that this is going to endure I mean this this last version limited parliamentary power weaker Legislature and stronger executive will last For some time some more time that this is more in tune with the French Administrative system or administrative psyche any questions Now that we are with the fifth republic Any questions until now so what I want you to remember here is that we've got We've got the pendulum swinging back and forth between radical democracy and monarchy Radical democracy monarchy, okay, so one republic after another but With this disruptions in between okay, either instability or outright war or outright puppet regime like the Vichy regime so first republic Second republic third republic fourth republic fifty eight 1958 fifth republic Okay, so that's that's where we are in terms of How France enters into the 20th century? I mean post-World War two period Some regime was installed but but this was untenable this was unsustainable then a System which was quite in opposition or quite opposite to The fourth republic emerges, okay, I think it's time to take a break


All right, welcome to August 19th, Microsoft Developer Sync. So here we are. So we've just had quite an extensive discussion about some matters that are not of interest to the public, but we're going to carry on with the rest of it now. I'd like to give a quick hardware update to kick it off with some good news. Well, it's not really good news. It's just the expected news that we've kicked off the second rev of the hardware board to resolve the issues we found on the first go round. Hopefully, we'll get those back this week. And they should come up in pretty short order. Pretty much everything was solved except for being able to program the XMOS chip on the last one. And that was just because there were some problems with the way the pads were implemented. So we'll get that sorted on this round. And we'll keep you apprised of what's going on there. Other than that, we've been digging into the precise wake word tagging process and the schema for that. We've had some extensive discussions offline today about that process. So that's a topic that we could get into here. I think it concerns basically all of us. And is there anything else that we should talk about, any other agenda items for today? Oh, I know. We put off a discussion of the tickets yesterday, didn't we? That's your ticket? Yes, there it is. Yeah. You haven't talked to the tickets. OK. And there's also the track status stuff, if anyone has opinions about that. But probably easiest is just to go check that out in the PRs of my profile. Sorry, I didn't quite catch what you were referring to there. Sorry, there's also the GUI track status. The GUI track? That I've mentioned very briefly at the start. Right. So just a proposed, well, an update to the existing track status. It's an internet, you know. Anyway, I think go have a look at the PR. Let's not talk about it here. OK, OK. All right. Then let's do something boring for a little bit and talk about the tickets. Chris, there, are you in a position to help us walk through that? I still don't have a good handle on how this GUI works. Thumbs up on the video if you like JIRA. I used to love JIRA, but that was a long time ago. Now, if you had a voice interface and I could just say, hey, JIRA, show me all the open sprints. Wouldn't that be awesome? Yeah. So if anyone's listening and wants to create a microp skill for navigating JIRA, please get in touch. There's a compliment one in the way. Oh, nice. OK, so Chris, are you intended to be muted? No. So is this, if we're talking, we just want to talk about who's doing what this week or do we want to really go through all projects like we had done before? And looking at this from a project's perspective or from a person's perspective? Let's go by a person. OK, see if this works. Project as project roll over under for tickets for that? Well, we actually had a sprint for the prototypes that we've closed out, I think. I started a sprint for support, but there's really not, well, let's see, there was something that came through yesterday that guess handled. But yeah, there's really not an active one. We could start the support sprint. Yeah, I mean, what would be the overall arching project? Would we have a separate project just for project roll over? Or would we have a, would it be under business development with a sub-project of roll over? Well, yeah, so there's, the way it's set up right now is basically in each, you can have separate projects. So there's like a hardware board that everything feeds into the backlog of the Microsoft Sprint. So you could have a, you should actually have a business dev board. You can put all the project roll over stuff within and then, you know, we might have the, like the specific sprints of building the prototypes that pulls from that, tickets from that board. So yeah, if you wanna populate project roll over tickets in the dev board, they should still feed into the Microsoft Sprint. Okay, so I'll start with me. It's really, I'm working on the precise sample upload stuff, I'm gonna have some changes. I had a bunch of stuff in review, but I'm gonna have some changes to that code once we get the schema worked out. So I'll have to go back in there a little bit. I had moved on to the script that moves the data from one place to the next, but I'll have to pause work on that once we get the schema happy. I'll go back, rework things that has to be reworked and then move on from there. This is really my, what I've been working on this week and have been working on is getting this spread away. Ken, where is your, I think part of the problem with using this all sprints and clicking on people is if you're not actually assigned to things, if the assignments are right, that's not gonna work, but that's the point of being able to click on faces up here, if everything's assigned right and everything's assigned, you should show up. Well, what's the project doing? It looks like, for example, all my tickets are in precise, P-R-E-C. That shouldn't matter because all the issues from all of our other projects should be linked into here.  Yeah, I'm putting my sprints. Well, all I know is right now in progress under precise project, if you search for me, you should see that there's four tickets in progress, 71, 72, 74, and 75, P-R-E-C-Dash. Yeah, this is the problem that I've been having with you. Yeah, I mean, basically- You're here in Buc-Fixes, right? Which sprinter are you in? It's a good question, I don't know. Where I was put, all I know is I've got tickets. They're P-R-E-C-Dash, the way I find them as I search for the items. Well, really the easiest way is go to P-R-E-C-Dash 60. You want to see what you and I are both working on. That's in the backlog. All right, so yeah, if you go bring that up, you'll see all the tickets sub-categorized. See right there? Yeah. First piece, and I'm working on that third piece. It's gonna meet and settle. But if you click on that, you should see, yeah. And then there's my in-progresses, my guns and all that good stuff. Okay, all of these should probably be in the, well, I don't know if this all isn't really part of the precise upload sprint, but if this is all stuff you're doing, you should probably have a sprint defined for the things you are doing to precise. Because right now, it looks like you're working out. I don't know how you guys do it. Usually, a sprint is a sprint, and then there's a collection of work that's done during that sprint, which could be a variety of tickets on a variety of projects. I've never really assigned sprints to. We do it a little differently here, really a sprint for us is a kind of like a project, the collection of tickets that we do, and we kind of group them together. And then once we're working on that group of tickets, we set the sprint to active. Yes, so if you're using sprints as projects, what are you using projects for? Just a way of partitioning the tickets, you know, by subject. Actual JIRA projects are applications, precise as a project. Minecraft Core is a project, Selene is a project. But then you take the backlog of all those projects and you group those tickets into projects, probably the wrong word, in this regard, but you group them into sprints, a group of tickets that you wanna do kind of out together in an average to, in my case, get the precise uploads done. Yeah, well, it's okay anyway, that's how you find my stuff. Okay, we should probably create a sprint for what you're doing. Yeah, I mean, if this is too complicated, given the small size of our team, we don't really need to have more sprints than we have team members. Maybe it does make sense to just do like a rolling two week sprint like we had before. I prefer to keep things organized by projects because it helps us to see how much we have done until we've accomplished a specific unit of work, right? Like if you've got 12 items that need to be done before we can roll out the new version of precise, then it's nice to see what those 12 items are, irrespective of what work, Gez is doing on the 20-08 release or Chris Bear is doing on Selene, if it's unrelated. So that's why I like to group in things. For that, so if we go into the Minecraft Sprint here, you can go in the backlog, if you look at the epics, you can see the stat, how many issues there are and the status of them. Right. So if we use epics, right? And instead of use them, epics to track the progress of a project rather than the sprints themselves, then we could do both. We could have the sprints do. It is what we're doing in the next week or two weeks and have these epics to track how much work needs to be done to get whatever subdivision of tickets we want to do for projects. Sure. Okay.  We certainly have a lot of work to do. Yeah. But you can also like this, you can drag these. So like this is what I'm working on now and one of the more important ones, you can put the one you're working on here at the top. So you're not scrolling down to find them all the time. But yeah, so if we want to do that, after today, we can reorganize things a little bit here. Right. So we can have a whole bunch of sprints to find here and a lot of them might even have started yet. Right. I don't know, maybe we should just be using, well, we can't just use epics without sprints, right? Because you can't just look at all the issues in an epic without, or you should be able to without. You can, it's not the best interface. Yeah. And epic is typically defined as a project that's not, it's going to span multiple sprints. Right, right. My concern is just, yeah, okay. Well, I mean, then the only sensible thing to do is to define sprints as a unit of time, right? A week or two weeks or whatever. Yeah. And which would be fine for, you know, keeping track of how quickly we're doing things. But again, you know, I'm not sure how useful that is given the small size of the team, or maybe it's super useful given the small size of the team.  That's the same thing as just having a backlog though. Right. It's just dragging things from the backlog to the in progress column. Yeah. And then you use, you can still use epics and other categorizing things to categorize the tickets and then, you know, what we're doing. Okay. Well, I don't have a specific problem I'm trying to solve right now. So I guess we don't have to spend too much time on it. As long as we can get to what people are working on pretty easily, that's really all I care about right now. Yeah, I actually have on my bookmarks menu the ticket PREC-60, because that has the three major sub-tickets and then those sub-tickets kind of have their items. And traditionally that might be a epic and then projects and then tasks, but. Yeah. I don't want to introduce a lot of management overhead in terms of managing the tickets because there's only three of us. That's why I said just go to PREC-60, simplest way to get there. Okay. All right, so having had all of that meta discussion, did we actually talk about your tickets at all? No. Okay, let's do that. We just said that 71, 72, 74, and 75 are in progress. Gotcha. Okay, so you've got four things in progress. Let's just take a quick look at the summary of what they are here. Sure. Okay, so determine trigger and response. There's one of them. Yeah. And this is, yeah. So this is basically, at some point in time, we've accumulated enough files to trigger a new model build process to kick off. And so this speaks to that. Right, well, not necessarily just files, it could be new tags or things like that. Well, for right now, the trigger is strictly new files. We can certainly refine that. This is part of a larger process, obviously. Okay. And then go to the next one, 72, Chris. Yeah. Yeah. Here is kind of, add new data to existing data sets. Okay, so yeah, yeah. So this is basically speaking to the fact that when the new data schema is done, I'll take the existing code that I've built or that I'm finishing up and I'll change the SQL to go to the new schema versus the old schema. Okay. Yeah, we've got a streamline in this process. Yeah. Sometimes I just use the URL and change the number. Yeah, right. Roll down to the bottom, let me see the latest on this. Yeah. So this is, what is this balancing of some sort? What's the title of this ticket? It is. Yeah. So this is speaking to the fact that as I've been iterating through this balancing, I've learned some stuff, which is that you want to limit the user contributions as late in the process as possible because you never know how much data you're gonna lose during the classification phases.  And it also speaks to the concept that when we said, well, we'll limit samples to 10 per account where I'm basically at is 10 per account per bucket, if that makes sense. So if an account had 10 high wake words and 10 low wake words and 10 high not wake words and 10 low not wake words, I've expanded it to include it from that perspective. Otherwise, when I was combining the data sets up higher and whatnot, I was ending up with like two or 3000 usable samples at the end of the balancing. And where I'm at right now is I'm at about 10 or 12,000. And I actually added a step in the process to bring in some raw external data to balance out our weakness, which is female not wake words or high pitched not wake words. And not wake word should never be a limiting factor for our data set size, right? I can say, okay, don't have enough high pitched wake words or low pitched wake words, that could be a limit, but not wake words. I should be able to get that information or get extra data. So that's what I did. I'm actually in that process now where I'm bringing data in from the wild, converting it to our format, which is 16 hertz or 16 kilohertz and 256 bits, blah, blah, and so I basically download them from some different places that are given them up free. I convert them and I add them at the very last step right before the balancing occurs to the index file as additional rows. And so I noticed that I was 2,000 short on high pitched not wake words. So by adding these additional 2,000, I will acquire 8,000 additional centers that make sense. So that was absolutely necessary at this stage because we have such a small data set size. And so that's what this kind of speaks to is I've been iterating through that process, running through it, finding out what I end up with, determining how I can get the maximum number of balanced data samples out of what we have and hopefully that'll serve us moving forward. Okay, and then one more, Chris. Just go up and change the URL. What was that? Oh, you can click there, I guess, sure. Should be 75, right? Mm-hmm. Oh, this just speaks to the fact that once I get this training data set with the latest data assembled, I will build some new models using it and see how they perform. Okay. Anything limiting your progress right now? Nothing. Nothing. All right, full steam ahead. Yes, sir. Infinite speed. Okay. Okay. Infinite velocity. Yeah. It's the same as velocity zero. Well, I guess if we're going forward, sure. All right. So, I guess, let's take a look at Jess's plate here. Yeah, so mostly focused on 20.08 at the moment, which is all the things in the review. There's a few others that have switched over to Chris's allocated Chris review, but okay, it's been really helpful in reviewing things as well. So, I think everything, all the PRs that are pushed has passed all their tests and have been reviewed for memory. The remaining pieces that I think are really important for 20.08 is the inf module has been fully deprecated and we pulled that out for a few places but I think there's like three places where it still is used. So, switching that over to import lib and the lingua franca community have been doing a huge amount of work, particularly chance encounter on some pretty big changes there. So, we're trying to get that in for this major release as well because there's breaking changes in there. The, I think the last sticky point was that if you called a particular, if you normalize an utterance and then called extract date time or extract duration in Italian, then a couple of those test fails. So, I'm spending today looking much more deeply into lingua franca to see where that's up to. But, I mean, our only officially supported language is English and so I feel like if there are a very like half a dozen tests in Italian that are failing, then I'm inclined to push ahead and just mark them as expected fail and merge it and fix it in 2008. But, yeah, if other people have opinions on that then. Yeah, it's an interesting issue. Is there nobody developing in Italian that can help fix those before we? They haven't been around recently and like in a very recent future, and we're just, we're at a pretty tight deadline as well. And it's specifically related to seconds. Like, essentially the normalized function, I think, converts it into seconds in the sort of ordinal, two and a second, as opposed to the fact that it could be either a time unit or an ordinal number. Yeah, so potentially we'll be able to fix it. And, but, you know, just in terms of if we can't, because we don't speak Italian, then maybe we push it and encourage a bug fix, you know, for 20.8.1. Right. Okay, so we're talking about this is for 20.8. Or for the 20.0.2, the last 20.2, at least. No, it's the last 20.2 really just gone out. So this is for 20.0.8. Yeah, to have that, because the changes to lingua franca, they pretty structurally change how lingua franca is structured. So it's a, and there's potentially breaking changes particularly for other languages if people are using it in core. Gotcha. Okay, well then I'm fine with you pushing it with those few tests failing. I'd be hesitant to mark them as expected fail because, well, do we have a path forward for recognizing when it's, you know, notifying people which tests are failing at, or effectively just not being run, right? If they're expected to fail, it will not run them unless they start working and we get a notification that, hey, this test that we thought failed now works, right? I don't remember what the resolution on that was. I don't think we have that yet as far as expected fail starting to pass. I don't think that's been built. Okay. Yeah, I mean, I kind of use it as a, you know, someone saying, how can I help? I'm like, well, if you search our repos for expected fail or for a skip test, then, you know, that's a pretty sure sign that something needs some love. Mm-hmm. Very well. Okay. All right, fair enough. All right. Yeah, but we'll see. Maybe we might be able to sort it out, you know. Okay. Anything else? Yeah, I mean, the other stuff, they're like updating the docs for the open data set and that sort of thing. I was trying to put on a back burner for the minute until we get 208 out. And I'm catching up with, okay, later today to go through the sort of major release process and just make sure I've fully understood all of that. Cause, yeah, okay, it was always in control of that in the past. And, yeah. Okay, great. Christopher. Did you already go through and you muted? Yeah, I was first. Oh, you were? Yeah. Okay. We can do Derek though. Sure, let's do Derek. Okay, so, yeah, for the Mark II Dev Kit project, I had been back looking at some things today in terms of thinking about, well, it's kind of reprioritizing some of the stuff to a certain degree. So we're talking about getting ready for the first draft kind of 3D printed design that, you know, kind of was the look of the production product. But I've created a few of these laser cut enclosures to, you know, get it into a form factor that, you know, the same location for what will eventually be the production design and utilize an acoustic chamber that is essentially the same volume and, you know, same porting and sealed and all that good stuff. So what I'm thinking, the thing we need to do though is test that in comparison to be off the shelf design. So we have, or correct me if you guys think I'm wrong in this way thinking, we don't really have any metrics to try and, you know, strive for in terms of performance here, mainly because we haven't sought to optimize the off the shelf design because we kind of had the limited ability to do so. So in terms of saying, you know, what is the ability for us to barge in, what's the decibel level that the speaker is playing at that we can barge in? And what is the decibel level that the user can speak to Mycroft and activate the wake word? You know, we did a little bit of testing with some interns about a year ago, you know, doing like simulated whisper select 40 decibels at like three feet, six feet, 12 feet, that kind of stuff. Does it activate the wake word? You know, does it not, et cetera. But what we're really doing then was benchmarking existing products with benchmarking Amazon benchmarking Google. We don't really have any data on the off the shelf design, you know, how it performs. So I'm thinking, you know, for us to make a decision on the, you know, the SK201 whether it's successful or not, we need to have some of these things thought of, like we need to say, can we do, before we, I think before we get to the point of, I mean, I can do some work in parallel like getting ready for a production kind of equivalent design, but if we have no way of telling that we're passing some kind of performance parameters, I think it's a bit of a carbon foil horse to get too far along on that. So we need to have some way of saying, okay, this is gonna get there, this is promising. Because we are switching, you know, the XMOS chip from what the off the shelf design. So, you guys think, you know, that's on the right track of thinking. So I was kind of reshuffling the priority there instead of me kind of moving forward with getting, you know, a more detailed plastic design. I'm kind of sitting down there to write some metrics to try and... Yeah, I think that's a good idea. We should search the backlog for tickets of this nature because I think I went through and put a whole bunch of tickets in around this. Okay. Quite a while back. So that might be a good starting place for those metrics. Okay, yeah, I can, yeah, I'll dig through the backlogs and see where I can find and move those to kind of active.  So that's a, you know, last couple of days for this demo that Josh, I requested, I do for a digital customer. And I think those were actually ended up in print 12. I got some devices done. So now I do have devices so I can do some of these things. I can use the benchmark test. So that's kind of where I'm thinking that I should be spending my time. And then I also have, you know, so I have there in review, I've got built-in device for Kent. So one of these devices I do want to get to Kent because he doesn't have one. So I've got two that I've built over the last two days. And then one I want to keep so that I can do this benchmarking. Yeah, so I think that's, you know, that's gonna keep me busy for the foreseeable future. I did take a look at some of the user stories that you're working on, Michael, for the precise tagging. And particularly number two, I think is the part that I would be involved in or be able to contribute in terms of helping on the UI of the user-facing tagger. So I'm not sure if that's, if we need to get rolling on that pretty quickly or if that's still a ways out. Well, I think the more user stories we can get now, the better off we'll be because it's affecting the architecture of the system.  And it turns out there's a, you know, when you look at it from different angles, there's different requirements. And it wasn't, you know, it's not obvious from looking at it from just one angle what the right answer is. So, you know, even when I was going through and adding in some just stuff off the top of my head like, oh wait, yeah, we need to have some way of dealing with putting in beginning and end boundaries on samples to know where, you know, to delineate where the actual wake word occurs inside the sample, especially if there's more than one utterance of that wake word, right? Stuff like that. So, yeah, the more examples that we can give them, I think, the better. Yeah, particularly one thing I was thinking about, I think I threw it on a comment for the ticket that they've gotten kind of lost in the whole precise organization stuff. But the idea of moving, we're basically saying, you know, is this, hey, mycrofters, it's not, hey, mycrofter in the past. And now we're talking about possibly tagging multiple things. So my concern there is we might want to test that because there could be kind of a fatigue for the tagger, the user, if they've got this. Yeah, the GUI, the presentation to the user should be completely independent of the database. And so, yes, in terms of how we present it to the user, I think that we'll probably need some experimentation there, and certainly some design there. But yeah, I mean, it could be that we have, you pick one attribute and it's swipe left or right for true or false. And you just do that on like a, you know, one sample a second or whatever, just as fast as you can. Or it could be listen to a sample with a waveform on the screen and enter the beginning and time points for when the wake word stops and starts and then tag as many attributes as you can that match that, you know, like it's English and it's, it is a wake word and it has a funny accent and whatever. So there's different ways of doing it. And then we may have multiple tools for tagging. So all those stories should be in there and in terms of what you might want to try. And then we can, you know, the database side of things should be sort of diagnostic with respect to that or should accommodate them. But I don't, I specifically made the note of I don't want the GUI to be represented in the database because I think they're, you know, they're different, like they're different issues. Cool. Okay. Well, that's good. So yeah, we can experiment with the best way because I just have a feeling like, you have used like a multiple choice thing or like, you know, check boxes that might just be too much. I do like the idea of like, let's, let's get it to you. You know, hot dog, not hot dog. Well, you guys were just speaking to, I'd like to call the syntax of the problem. Sure. And then there's Mantix, which is, and I don't know how to deal with this other than to just say it. So if you're saying, hey, you know, while you're tagging this, tell us if this is a male or a female voice. I think you're going to get further with that. And if you say, tell us whether you think this is a high or low pitched voice, because I think the latter is a more subjective value, not how you're going to deal with that. That's just something I want to throw out there. Yeah. Yeah, I think that's a good thing. You know, this, the idea of that specific tagging problem, I think does, we should maybe talk to some people and see what we think the best, the best way we should phrase that. But yeah, I think you're right. You know, you don't want to be ambiguous or confusing to the user is like, you want to be able to, but I think we also just, we want to keep in mind, we want to be representative of as many different people as possible. So. Right. And also, but you know, and it's about serving the utility of the, of the recognizer, right? Maybe classifying things as male or female isn't important to us because we don't really care if we just, you know, we don't, we don't care if a particular user is male or female, we just care that we can recognize them when they say, hey, Microsoft or whatever the wake word is, right? And so getting the right classifications in order to accomplish that is what's important to us. You know, the reason high and low pitch, I think makes sense for now at least is because it doesn't matter whether it's a high pitch male voice or a low pitch female voice or whatever, right?  But, so the fact that you're female doesn't matter at all in that particular case, or it's not relevant to improving the wake word performance, I guess I should say. Yeah. More generic concept, right? Let's take age group. So I think I listened to a sample. I think it's a child. Somebody else listens to it and they think it's a high pitch speaker. All I'm speaking to is how do you deal with that concept? Well, again, I don't think it's relevant unless it impacts the performance of the wake word, right? If it's a high pitch, you know, child versus a child with a raspy voice versus, you know, an older person, like it doesn't really matter as far in the sense that, you know, whichever of those things are important to the wake word classifier or the recognizer in terms of, you know, making it perform better, right?   So, you know, I don't know if he'd show up in the normal classification for a kid's voice. How are we getting out there? I feel like the biggest tension for me is like, you know, we're asking people to tag their perception of an audio sample. We're not asking people to tell us what the speaker, how, you know, who the speaker is kind of a thing. And so I think just in terms of how we frame it in the UI, I think that's going to be important because then it'll be like, you know, you can't be wrong about what is your perception of this voice? And which is kind of analogous to what we want, which is like, how do we think that a machine learning algorithm is going to perceive this voice? Yeah. I mean, that, yeah, that thing we all say is, if you ask people, is this, is this, is this saying, hey, Minecraft, that yes or no is a lot less ambiguous than some of the other classifications we're going to try. That's all I'm getting. In fact, those other classifications can be ambiguous. The question is knowing that, how do we deal with it? Is it something we care about or not? That's awesome. Yeah.   So, but it was a lot, there's a lot to, but that, but I guess where we're at right now, we're still at the user stories. You haven't, you know, kind of got that far. Do you want, Michael, do you want people contributing to this, this document, the user stories document? Actually, sure. I'd love to see the community contribute to this. Well, I was just thinking like anybody on the team, but yeah, maybe we could throw it out to the community too. Well, sure, the team, obviously, I think that the team should have input, but I think it would be interesting to hear from the community as well. Okay, cool. All right, well, I'll try and get in there and throw some extra stories on if I can think of any. We do want to move quickly on this though, because, you know, Chris is, it's kind of, it's on the critical path for us to do the next step in the tagging system. Yeah, well, I think next week, I should start carving out some time then to like start mocking up some of the UI for it. So, I'll get that on the sprint for next week. Okay. And well, we'll just check it out. And well, we'll just have to hope that it can, the system we choose can accommodate it or it can be easily changed if we come up with any changes, because I think, you know, Chris, correct me if I'm wrong, Chris, but I think we're kind of hoping to get this resolved today or tomorrow. Is that, you're muted, so I can't hear what you're saying. The schema itself, yes.  From our discussions this morning. So, yeah, I really can't do a whole lot more of the work that's assigned to me until the schema's ironed out. Well, anything I'd start on UI-wise, is it's gonna be super, like, I mean, not talking like the graphics are important or anything, just talk, you know, getting the basics, wireframes, you know, very simple stuff. Yeah, I don't think that's relevant to what Chris is doing. Well, I'm having stories as fine too, because then I could use those stories to build behave tests, for example, you know, make sure that, you know, those things work when somebody uses the tagger, you know, that kind of thing.  And, you know, I don't think so far, all of the user stories in there, I think the current version of the schema will support, just from looking at them more quickly. But, it's really not gonna hurt to have all these things we expect the system to do, sitting in there. Okay. All right, cool. Well, I'll try and get into some contribution there. So, I think that's it for me then. So, yeah. All right. Well, unless there's any final things that people like to discuss, I think we should call it there. And we'll be back together on Friday. Sounds good. Yeah. All right. Well, thanks very much. Talk to you on Friday.


Hi everyone, welcome to today's tutorial on chloroplast genome assembly. This is a tutorial in the Galaxy training network and we'll be following it today. So what we're going to look at is how we can assemble a chloroplast genome, and to do that we'll assemble a genome from long reads. Then we'll polish that assembly with short reads. Then we'll annotate the assembly and look at the annotation. And then finally we're going to take a subset of the reads and map them back to the assembly and see how they look. So let's have a look at the chloroplast itself. So the chloroplast is a photosynthetic organelle found in plants and algae. And here are some, they're the little green circles within those larger cells. And you can see this under a microscope. And it's thought that these chloroplasts were originally a type of photosynthetic bacteria that was ingested by another cell. So, and now it has become the chloroplasts within the plant cell. And a similar thing is thought to have happened with the mitochondria. So because these chloroplasts were originally bacteria as thought, the genome of the chloroplasts now is similar somewhat to bacterial genomes. It's usually circular, but it's much more than typical bacterial genomes. So in plants a chloroplast genome might be about 160,000 base pairs. And they're usually in these four parts. There's a large single copy region, a small single copy region. And then these two areas which are the same or very similar and in different orientations. And they're called the inverted repeats. So there might be lots of chloroplasts within a plant cell. So there might be lots of these chloroplasts genomes. Then the plant will have typically a very large nuclear genome. And there might also be a lot of mitochondrial genomes in the mitochondria. So just to get this idea of these relative proportions of those three genomes within the plant cell, the large nuclear genome, the several medium sized mitochondrial genomes, and then many quite small chloroplasts genomes. That's an oversimplification, but I just wanted to get this idea of there being these multiple genomes. And today we're going to look purely at the chloroplast genome. So today we'll do genome assembly. So this is the process where we piece together lots of smaller DNA fragments and join them into longer pieces, hopefully representing the original chromosome or chromosomes from which those reads came. So in this tutorial today, we're using long reads from Oxford Nanopore sequencing and short reads from Illumina sequencing. And the dataset we're using, it's a real dataset from a sweet potato sequencing project, but I've cut the data down into a much smaller subset so that it's easier to use in this tutorial setting. So the chromosome that we're assembling today will be about 160,000 base pairs long. And that's obviously going to be an easier thing for us to do and to try and assemble a nuclear genome, which are very much larger. Let's start with looking at uploading the data. So what I'm going to do is keep the tutorial information open in one tab and then a Galaxy window opening another tab. So here is my Galaxy window and here's the tutorial information. So this tutorial should work on all the major galaxies. It should work on Galaxy main, Galaxy Europe and Galaxy Australia. Okay, so to start with, let's open up Galaxy login or register first if you haven't used Galaxy before. And then we will name this history and now we'll get our data files in. So we're going to import those from a repository on Zenodo. So here in this tutorial lists where they are and we can actually just copy those links with the copy button. Then back in Galaxy we'll go to get data, paste fetch data. Paste in those links, then start and then close. And we'll see those files start loading here. They're in progress now all of its column and when they've loaded they'll turn green. So the data we're loading here is one set of Nanopore reads in fast Q format and one set of Illumina reads also in fast Q format. They may take a few minutes to load depending on how busy Galaxy is. Let's have a look at our files now that they're in a history. We can do this with the icon next to the file. Just have a look at what's in that file just to check it's how we expect it to be. So this is our Illumina fast Q reads. We can see that this looks as we would expect. We have the read header. Then we have the read itself. So the DNA sequence. Then we have just a blank line and then we have this line of quality scores, which is encoded by symbols and letters. So that looks correct. We've got lots of reads there. Let's have a look at our Nanopore reads. And again, that looks correct. We've got read headers. We've got the read sequences. Then a space and then the read quality scores to reach of those positions. And then the next read starts and so on. So that looks correct. One thing that we'll do here is have a quick look at the Nanopore read quality. So that's the second section here in the tutorial. And we're going to do that with a tool called Nanoplosh. So I'm going to type that tool in into the toolbar. And we found that here. And all we really need to do here is to give it the correct file name. So make sure we're giving it the Nanopore file because that's the one we want to look at here. And click, click execute. And that job has now loaded in Galaxy. So there are five output files that are going to be produced from that Nanoplot tool. And the tool is now running. So there are lots of things you can do with this step where we're looking at read quality. There are various other tools you can use. And then you can look at your Nanopore reads, your Lumina reads or whatever data you have. So that tool is finished. So let's look at just one of the outputs today. We'll look at the HTML report with the eye icon. So we won't go through this in a lot of detail because there are other tutorials available in the Galaxy train network that go into a lot more detail about quality control. So I wanted to give you a brief overview today of how we might use one tool at this step. So Nanoplot has looked at those Nanopore reads and it's calculated a lot of statistics and made some plots. We can get some general information here. We can see the mean read length is almost 7000 base pairs. That's quite good. We can see the histogram of read lengths and so on. So for us, that's a fairly good read length that we are using in this assembly process today. But if you were doing a particular type of assembly or had some other requirement, you may need different characteristics of your read set. And so this quality control step is where you can look at read length or read quality or whatever it is you need to know to make sure it's adequate for your analysis. So we've just had a brief look there, mainly at the read lengths in this case. But again, there are these other tools that we can use. For example, we can use FastQC for the Illumina reads. And we can also use a nice tool called FastQE, which will give you your quality scores represented as emoji. So that's a fun way to have a quick look at the quality of your reads. Now let's assemble our reads. We're going to assemble the long reads, so the Nanopore reads. And to do that, we'll use a tool called Fly. So I'll type that again into the tool panel. Click on Fly. And just collapse that side panel there so I can see a bit better. We want to give it these Nanopore reads as input. We'll give it an estimated genome size, 160,000 base pairs. And we will quick execute. And now Fly is running. You can see it's making five output files. So Fly may take some time to run. It may take five minutes or 15 minutes, perhaps, if there's a very big Q in Galaxy. So I'm going to pause this recording now while I wait for Fly to finish. So Fly has now finished assembling those reads. We've got five output files. I've clicked here on the icon for the log file. And we'll zoom to the end here where just a little bit. We can see that the total length of the assembly is almost 160,000 base pairs, which is what we would expect. And there's two fragments. So let's have a look at the assembly graph with the bandage tool. So in the tool panel, we're going to search for bandage. We will skip the bandage info part today. We'll just go to bandage image. We want to give it the graphical fragment assembly file. We won't look at the node length labels today. And we'll click execute. And I'm just going to collapse this side panel again so we have a bit more room. And then that's finished. So let's click on the eye icon. Let's zoom out a little bit so we can see that assembly. So this looks like we'd expect. We have a large part and then sort of a collapsed part here and then a smaller part here. So this seems to reflect what we would expect. This is probably the large single copy region of the chloroplastinone. This is probably the small single copy region. And then this is probably the collapsed inverted repeat region. And there's a bit more discussion about that in this question and solution section in the tutorial, which you can look at by clicking on the plus next to the solution. So this was just one tool we've run here today, run fly. But you can repeat this with different versions of fly. Sometimes the newer versions will assemble these reads just into a single circular chromosome. So some of the changes in that new version can affect the assembly. But you can also try different assembly tools such as canoe or unicycle. Now let's polish that assembly. So because we have a set of short reads, we can use those to correct some of the errors that might be now long read assembly. Because the long reads typically have a higher error rate than the shorter aluminum reads. So let's do that now. Let's zoom back in a bit to make our galaxy bigger. So first of all, we need to take our set of aluminum reads and we need to map them to this nanopore assembly. So let's look for the tool BWAM. And will you select a reference genome from your history or use a built-in index? We're using a genome in our history. So it's one we've already made. And which shall we use? We'll use the fly assembly. So that's the consensus sequence here. Leave that as auto. These are single-end reads. And then we need to give it the correct set of reads. So this is the alumina fast queue reads. Those other settings are correct. And then we will execute that style. Okay, so that's given us an output which is a BAM file. I'm going to rename this file just so it's easier to see what we've done. So let's call this alumina BAM. So I did that with the pencil icon here in the history panel. So we're going to use that BAM file now in the tool pile on. So let's search for the tool pile on. So again, we're using a genome from history. We're using our fly assembly here. We need to give it the alumina BAM, which it's already found. We will create a changes file. Yes, there. And then we can click execute. So we've got two output files here. We've got the actual corrected assembly. This is the faster file. And we can look at it with the icon. But we've also got this file, a changes file that we wanted to have a look at. This actually shows us all the changes or the polishes that pile on has made to the assembly using information from the short reads. So that can be quite a useful thing to see. So we've polished our assembly with the short reads. Let's get some statistics on that polished assembly and compare it to the unpolished assembly. So we'll do that with a tool called faster statistics. So I'll search for that again here. So first let's run it on our original fly assembly. Execute that. And let's run it as well on this pile on polished assembly. Okay, so for our original assembly, we can see the length of our assembly was 158,857 base pairs, which is about what we thought. But with the changes made by polishing, we now have a much bigger assembly. It's moved up to more than 172,000. So really roughly four or five thousand changes have been made in that polishing step. So with pile on, you might want to do several rounds of pile on polishing. So each time you'll polish the new or the latest assembly. And there are other polishing tools as well. So you can explore all of that in Galaxy and some of them have a different effect on the polishing step. Now we will annotate the assembly. So that's putting information onto that polished assembly about the genomic features that are on there. So there isn't yet a tool available in Galaxy specifically for chloroplast genome annotation. Instead today we'll use an approximation. So we'll use a tool called Prokka, which is designed for bacterial genomes. So it's not going to be perfect for the chloroplast genome, but just as an example to show you of how we would do the annotation step, we're going to use Prokka today. But I have put some information here in the tutorial about how you might want to use a more specific tool for chloroplast genomes. There's a web based tool called GE Seek, which is quite good. That's what you might want to do if you were doing this in a real life situation with the chloroplast genome. But today we'll just use Prokka. So let's type that in here. And we want to give it the polished assembly. So that was this faster from the pile on step. And we'll leave all the settings as they are and click execute. So Prokka makes a lot of output files and you can explore those by clicking on the icon once that tool has run. Today we'll probably just look at the text file output just for a very quick and brief overview of the annotations. And after that we'll view those annotations in a genome browser called Jbrows. Okay, so Prokka has finished. Let's click on the text file. And we can see it's found lots of coding sequences, some ribosomal RNAs and some transfer RNAs. So that's just a very brief example of how we might do an annotation. And let's view it now using Jbrows. So type in Jbrows. So we're using a genome from our history. We're going to use our polished assembly, which is from the pile on step. We will use the bacterial genetic code. So now we're setting up a track group. Click insert track group. Insert annotation track. And then it asks what type of track do we want? And here we want a GFS track because that's our annotation file that we're going to look at. And it's found the GFS file here, which is from Prokka. And then we will set that to run. So Jbrows has finished. Let's have a look at the output. So I'm going to click on the I icon here. I will collapse both the side panels this time. So we have a little bit more room. Make sure our tracks are ticked. So we're looking at a track, which is the reference sequence. And then we're also looking at this Prokka annotations track. So let's zoom in a bit here to get an idea. So if we zoomed in all the way, we would get right to the nucleotide level. In fact, we'll make that a little bit easier to see. Let's only show the forward strand and let's not show the translation this time. So this is our reference sequence. And then zooming out again. Various parts of that have been annotated with features. So some of them will be hypothetical proteins. Some of them will have names. And you can click on those names to learn more about those annotations. So we did this today with Prokka. As I said, you can also do this with other tools, such as GSEC. So now we're going to view our sequencing reads mapped against our assembly just so we can get a bit of an idea about how those reads look. So we could use the original set of sequencing reads, but instead I've cut those data sets down even further just so it's a bit easier to visualize here. So again, we need another set of finals from Zanodo. We can copy the link from the tutorial. We can go to the get data box, paste fetch data, paste in those links, click start and close. And those files are now loading here at the top of our history. So what we need to do is to make two BAM files. We need to align the alumina reads to the assembly, and then we need to align the nanopore reads to the assembly. So we can start setting up that tool to run, even though these files are still loading. So we'll do it the same way we did when we were looking at our polishing step when we match the reads to the assembly. So we want to look for BWAMM. And first of all, we're using a genome from History. We will use our pylon polished assembly. We'll use single reads, alumina reads, and this is the alumina tiny fast cue set. So select that there and execute. And we can repeat that job with the nanopore reads. And one way you can repeat jobs in Galaxy is to click on the rerun button underneath an output file. And so we can repeat this job for the nanopore tiny reset. Make sure you tell it to use nanopore mode, and now that job's running. So we'll rename these output files, so it's a bit easier to see what we've done. This was the alumina mapping. And then this is the nanopore mapping. So nanopore tiny. Okay, so we have these two new BAM files, and we want to look at them in a genome browser. So again, we're going to use Jbrows. We're using a genome from our History. It's the pylon polished genome. In search track group, annotation track. So last time when we did this with the annotations, we used a GFS file here. You can see in track time. But this time we're using the BAM file track type. So click here for BAM. Let's look at our nanopore BAM file here. And let's insert another track. Again, a BAM track. Let's make this the alumina match rates here. And we'll set this to run. And we'll pause here while that runs. Okay, so that's finished running now, and we can view that output. Again, I'm going to collapse these side panels here. So we have a little bit more room. Make sure everything's ticked here. And let's zoom all the way in again. We'll zoom all the way into the reference sequence level. Again, make this a little bit easier to see. Just show the forward strand, and don't show us the translations. So this is our genome along the top. Zoom out again. And we can see the sets of match reads. So you can probably tell by looking, but the set at the top, these are our shorter alumina reads, and the set at the bottom are our longer nanopore reads. So I just think this is a nice way to get an overview of how the reads are different. We can see that there are lots more potential errors here in these longer nanopore reads with all these little colors representing differences from that reference sequence. And there are far fewer differences here in the alumina reads. So we can zoom out and just get an idea of how those reads look against the genome. And this is one way you can check your finished assemblies because if there are large areas where no reads are mapping, or there are twice as many reads mapping, or other variations like that, you can start to see whether there may be a mis-assembly part in your assembly, so something that is perhaps incorrect, or where there is perhaps a repeat region. So if there is twice the read depth in some areas, perhaps it's a repeat region in the genome. So in the real genome, it might be two areas, but your reads have all been matched in one single area. So it's a way you can start to explore the correctness and some of the features of your sample genome. So there's a nice tutorial in the Galaxy Training Network where you can learn more about J-Browns, and that's linked here in the tutorial. So one of the things that you can do next is to repeat the steps we did in this tutorial on a different dataset. So I found a dataset from a Eucalyptus sequencing project and I've cut that down in size a bit, so it's more easily used in the tutorial. There's a link to that here in the tutorial and you can upload those files to Galaxy. And then you can run either the same tools that we ran here with the sweet potato data, or you can use some different tools as well and learn more about what the tools do and what the results would be. So in conclusion, what we did today, we assembled the chloroplast genome with the long reads. We polished it with the short reads. We looked at the assembly graph and had a bit of a think about the structure of the genome. We annotated the genome and had a look at that in a genome browser. And finally, we took these wall reads and we matched them back to the assembly and started to get an idea about how those reads differ and how we could use those to investigate the correctness of the assembly or some of those other features like repeat regions. So that's the end of the tutorial today. Thank you very much for coming into this tutorial. We hope you found it useful. We'd encourage you to fill in this feedback form at the end of this tutorial if you can. That's really useful information for us. And don't forget, there are lots of other really useful tutorials available in the Galaxy training network. Thanks very much.


Chris here from IELTS Advantage. So it's the day before your test. How can you make sure that you get the score that you deserve? So in this video, I'm going to talk about four things that are going to lead to you getting the score that you deserve, reaching your potential. No video will be able to genuinely tell you things that will boost your score 24 hours before the test. There are no magic tips and tricks and hacks and shortcuts. They're lying to you. They only want clicks on their YouTube channel. But what is really, really important is you reach your potential. So for example, let's say you were in my class and I said, book the test. You are going to get a band seven.  Your speaking is at a band seven. You're reading. You're listening. But then you go and do the test and you get a six or 6.5. Often that is nothing to do with the test. It is nothing to do with your speaking ability or your writing ability. It's to do with these four things that cause people to get a lower score than they deserve. And the four things are number one, stress can lower your score. Number two, some practical things can lower your score. Number three, physiology. So things like nutrition, your sleep, stress as well is related to that. And then number four, your whole approach to the test, your test technique, your test strategy. So we're going to talk about these four things, these things that you should and shouldn't do the day before your test. Okay. So let's start off with number one, which is stress. Stress can cause you to get a lower score. There's no way around that. And what, when I talk to people about stress related to the test, they think that their IELTS score is who they are as a person. And they're afraid of letting people down that could be a friend or a family member, or it could mean that they don't get to move to this country, don't get their visa, don't get their job. And they build all of this up and they start to feel really guilty about maybe not getting the score that they need. They're afraid of letting other people down and letting themselves down. You are not the IELTS score that you need. You are not a 6.5. You are not a 7. You are not a 7.5.  If you speak to the people who really love you and you speak to them about how you are feeling, if they actually love you, they will totally agree with you that you, yes, you are under stress, you're under pressure, but just go and do your best. They love you. They're not going to judge you if you don't get the score that you need. And then if you think about it, oh, I'm going to miss out on the job of my dreams or I can't move to this country. You can't move to that country today, but that doesn't mean to say that you won't get the score that you need in the future. When people talk about stress, what they really mean is fear. They fear that unknown, they fear that they're not ready. They fear that something's going to come up that they're not ready for. And how you combat that fear is by preparing properly for the test. So when you go into the test tomorrow, there's nothing you can do that is going to boost your score, that is going to improve your score. You are going to get the score that you deserve. And if you get the score that you need, great, but if you don't get the score that you need next time, what you should do, instead of booking the test and putting pressure on yourself to get the score that you need next time at that date, instead flip it completely around and focus on what do I need to do to guarantee that I will get that score. So the students that I work with, we tell them, don't book the test until we tell you you're ready, until we do everything that you need to do in order to get to a band seven. And then when you do the test next time, you have no fear or no stress at all. Once you know if you do this, do this, do this, you're going to get the score that you need. So remove all of that fear, remove all of that stress, don't put any pressure on yourself, think realistically about it, and talk to the people who you think might be let down if you don't get the score that you need. And that will remove all of that stress. The second thing is practical things to think about. You would not believe the number of students who would run into a speaking test, covered in sweat, because they didn't know where the room was, they got stuck in traffic, they didn't know where the building was, and they get there completely flustered, and they don't get the score that they deserve. Because their brain is thinking about 20,000 different things other than how do I give my best performance in the speaking test, the writing test, the listening test, the reading test, whatever. So the day before, figure out how you are going to get there and get there one hour before your test begins. Go into the building, find out where the toilets are, where you can get water, which room you are in, and then you will be completely settled, and you'll be completely focused on what you need to do, rather than, I'm late, which bus is it, which street is it, which room is it, you want to be completely focused on what you are going to do. Our brains are not very good at thinking about lots of different things at the same time. We want you sitting in that chair and able to give your best performance. So the day before, figure out all of those other things, and then you can be totally focused on test day. So the examiners are going to be testing your ability to speak, testing your ability to write, to read, to listen, and as human beings, that is going to be affected by our physiology, by how much sleep we get the night before and the week leading up to the test, by the food that we have in our body, by the stress or hormones, all of those things do affect our score, and students can get very angry about this because maybe they have sent me like five essays, and they're all at a seven or above, and then they go in and do the test and they get a 6.5, and they get really angry, and I say, well, did you sleep well the night before? What did you have for dinner? What did you have for breakfast? How were your stress levels? And they'll say, oh, I only slept three hours because I was so stressed out, and then I didn't eat any breakfast because I was really nervous, and then I couldn't find the room and I was really stressed out. It's like, it's pretty amazing that you got a 6.5. I'm surprised that you got as high of a score as that, considering all of those things. Start the week before to get into a normal sleep pattern. Go to bed at the same time every day, get up at the same time every day, so that you get into a regular sleep pattern. I'm not a sleep doctor, but I'm sure that you understand the things that you need to do that will make a difference between you getting a good night's sleep and not getting a good night's sleep. Do those things. Make sure that you are getting as much sleep as possible before your test date, and whatever you do, do not sit up the night before cramming and looking at YouTube videos about aisles and looking for vocabulary and looking at band 9 essays and all these things. It's impossible for you to improve your aisles performance by doing those things the day before your test. The next thing is nutrition. If your blood sugar is low, if you don't have enough energy, you're not going to be able to perform as well. So make sure that you get a really healthy dinner the night before and a really healthy breakfast. If you're not a breakfast person, try and eat something, you can also bring some drinks and snacks.  It will make a difference. The difference between a 6.5 and a 7, for example, can be a tiny, tiny, tiny thing.  Nutrition, sleep, stress, we've already talked about stress can mean the difference. So give yourself every chance to get the score that you need by following those few rules that I've given you on physiology. The final thing is test strategy and test technique. One thing that I encourage my students to do 24 hours before the test is something called an English warm-up. So think about yourself as an athlete. Imagine you were going and playing a football match. Footballers don't walk onto the pitch and just immediately start playing. They would go through like an hour or half an hour of a warm-up.  You should do the same thing with English. 24 hours before your test, try and listen and read and speak and write in English.  I'm not saying that you should stay up all night watching English movies or listening to English podcasts. Just try and do as many of the things that you would normally do, but do them in English. If you would normally listen to a podcast in your own language, listen to it in English. If you would normally watch the news in your own language or read a newspaper in your own language, read it in English, speak to people in English, write emails in English. You might not be able to do that for work purposes, but try and do as much in English the 24 hours before your test as possible. It is going to make a big, big difference because it's very difficult to, let's say, you are from Vietnam where my wife is and you're totally surrounded by Vietnamese. And then to go in and then, let's say, you're in your speaking test to switch into English immediately, it's quite difficult to do, but if you have been chatting in English for the past 24 hours, it's much easier because you're warmed up. Now, when it comes to 24 hours before your test, there's nothing I can tell you which is going to boost your score, but there are a few things that I can tell you that will stop you getting a lower score than you deserve. You're not going to be able to trick the examiner by using memorized essays and memorized speaking answers or learning lists of vocabulary and fixed phrases and anything that is a trick or a hack or a shortcut, the examiners know what you're doing and they're counterproductive. Instead, in the speaking test and the writing test, focus on what you are being tested on. It's not a memorization test. It's not a how many tricks can you learn test. It's an English test. They're testing whether when you move to an English speaking country, can you operate normally in English when you get there. So in the speaking test, focus on clearly communicating with the examiner. Pretend you're speaking to a friend. So if you're speaking to a friend, you wouldn't show off how many amazing words you know or how many tenses you know how to use. You would just answer the questions and clearly communicate with them in English. Same with writing. Feel as if you are writing to a friend. So if you are writing a letter, what would you write to them? Would you try and show off or would you just clearly communicate with them? Put yourself in the reader's shoes. If you were reading your essay, what would you want to read? Would you want to read something where you're adding in as many different ideas as possible? Or would you just clearly answer the question? And that is going to ensure that you get the best possible mark, not by using tips and tricks and hacks. Even though people on YouTube will try and sell you those things, they simply don't work. Go in and give your best performance. And if you get the score that you need, absolutely amazing. You can forget about this test for the rest of your life. If you don't get the score that you need, then you can feel free to get in touch with me, Chris at islesavantage.com and we will talk you through how to prepare not 24 hours before your test, but months and weeks before your test so that you can be guaranteed to get the score that you need next time. Hopefully you enjoyed that and good luck in your test tomorrow. Bye-bye.


Normally, sailors are the ones hosting a Tiger Cruise. For a group from the USS Antietam, this was their opportunity to be the Tigers. They embarked on board the Japan Maritime Self-Defense Force icebreaker JS Serase for a cruise on Tokyo Bay. Seaman Emily Dachels even had the opportunity to make a friend on board. It was amazing. She happened to be in IT. It was just really cool to relate to somebody who pretty much carries out the same performance and job duties as you do. The sailors and visitors had the opportunity to try out some of Serase's special Antarctic exploration here. We have Japanese ships that will come to our base and they'll be performing their own operations and I wasn't expecting anything to be like this. It was just a great day overall. At the end of the day, it's just one more way that these two navies work together to strengthen their alliance. Reporting from JS Serase, I'm Petty Officer Jacob Allison.