Giovanni and there's Giovanni in the middle who took over from Alex and Tanmaji and Chris who also helped with the project. And this picture is indeed still taken at the University of Tübingen and I think I was announced as my affiliation being in Tübingen but I have moved to Dundee in Scotland since then and some of them have come with me. Okay, so histone modifications, that's the first part, that's what we are talking about firstly and just a short reminder again. So you have your DNA and the DNA is wrapped around these histone proteins forming these beads on a string like structure and then these, if you are looking into detail in each of these histones, they are actually complex made up of several proteins and these proteins have tails. So the proteins are called H2A and H2B, H4 and H3 and then they have amino acid tails that you can see here and some of these residues can be modified. So for example H3K4, that's the lysine at position 4, can be matulated or acetylated and you see the different chemical modifications that are possible here and this is kind of the nomenclature that I've been using already yesterday. So I've been talking about H3K4 tree matulation or you could think about H2A 190 ubiquitination or something and as you can see there's a whole circus of different modifications at different positions and this is kind of creating this whole landscape of epigenomic patterns. So here's another few of the same thing. So you have the DNA which is wrapped around the histone protein and then you have the different histone modifications that are all potentially present at a given nucleosome and of course you have to measure that across the whole of this very long string and then you get the information in a genome specific way. So the imputation challenge was to fill in missing data. So of course it is very data intensive epigenomics and that is because for once you have a lot of histone modifications that you can measure. They are shown here on the x-axis and as I said in contrast to the genome the epigenome is really different between cell types and tissues. So even for a given individual you would have to measure it across different tissues and so for some of the reference epigenomes and roadmap projects you can see that even there there's a lot of data missing. So the blue squares are measured data and the white square is missing and what we want to do here is we want to fill in the data for each of these squares and importantly also in this case for the reference epigenome these tissues are not stemming from the same individual or tissue culture. They are measured in different labs and they are not related in the sense that they are all derived from the same individual. So it's a reference epigenome which is a mix from data from different labs which are not related in a sense that they share the same underlying genome. And so the ENCODE consortium was calling so the ENCODE consortium is really an international collaboration which is funded by the National Human Genome Research Institute. It's trying to find a comprehensive parts list of all functional elements in the human genome including regulatory elements that control cells and circumstances in which a gene is active. And a major activity of this consortium is to generate new datasets that would enable the characterization of various types of biochemical activities. So however of course performing these assays is still somewhat expensive and there are some technical challenges such that some tissue types or cell types are not as easily accessible and this really prevents its completion. Therefore they have called out a challenge where an international challenge which was mainly led from Stanford, Manoles Kelles and Bill Noble in Washington and they provided us with training datasets. So this is the same kind of matrix that you have seen before. In this case you have the histone modification the y-axis and the cell types on the x-axis and these are the blue dots are provided during the training phase of the challenge then in the second phase we got the validation datasets and eventually we had to test they actually generated new datasets for the prediction for the final prediction and that's where we had to and that's where they validated where they assessed the different competitors. As you can see the sampling of the test training and test set is potentially not ideal so it's not really randomly sampled these testing sets. So initially as I said the challenge closed somewhere in August I think September 2019 and we had not done prediction before, imputation before but we had a prototype which we called IMP and you can see that it performed among the best methods in this international competition and then we went on from there and improved further this tool. So but let's think about first why imputation is possible in the first place and what are the assumptions that we can make. So of course the assumption is that there are partial correlations between different datasets and that is of course because the individual histone modifications are not independent of each other so we have discussed readers and writers yesterday and we have discussed that the writers are very often very big complexes that also contain reader domains or reader proteins and therefore they read and write at the same time and also I have said a number of times that for example H3K4 treatment relation of course at the start of genes so that means clearly that they recognize signals on the DNA so for example the start of genes or the or enhancer motives and these are of course the same these DNA signatures are of course the same across cell types and therefore to some extent these histone modifications would be correlated across cell types. So and this is kind of the setting as I've explained before so we have different cell types one one and two and we have different histone modifications one and two and then we want to infer the histone modification in another cell type. So there were some tools already out there so the pioneers was really Jason Ernst and Manolis Kellis I would say and they published a work in 2015 which they called From Impute and it's still very widely used I would say and it's based on an ensemble of regression trees so you would have your different histone modifications here you have your target mark here and you build and in this case you have different cell types and then you make built regression trees for your target mark and you do the same for your target cell and then you combine it as an ensemble of regression trees. The big disadvantage of this tool is however that for each new target cell type assay combination From Impute requires the training of a new ensemble of regression trees. So every time you have a new tissue and a new histone modification and you have new training data available or new data sets available other historic other marks available you would have to retrain so that's a huge bottleneck. So an alternative approach was suggested in 2018 and then again in 2020 by Timothy Durham and Jacob Schreiber and they considered the whole problem as a tensor factorization problem. So in this case you would have so this is exactly kind of this data matrix that you have seen before but you have of course the genomic axis here as well so you have here a genomic position genomic axis you have an assay so the different histone modifications along this axis and then the different cell types and if you are if you can learn the factors for the differ assay cell type and the genomic position you can then during prediction very simply input the coordinate into this tensor and by combining the learned factors in a clever way you can make a prediction and what you can see here for example is that they are providing three different levels of that they are using genomic factors for different scales so for different bin size so this is a very small bin size and then increasingly larger bin size so it's a massive model and but it worked fairly well and avocado had a little bit of a it had a neural network to combine the different factors in other ways it was very similar to predicted and it worked quite well and it was had the good advantage that it would generalize very well to new unseen combinations of assay and cell types the drawback however is it had to learn factors for every genomic position and of course this is massive because as I've told you before you had a three billion the human genome has three billion letters so this this factor is is really very long so we came up with it is where we used a combination kind of out of well we changed that to some extent so in this case the so this is our model and I'm going through through it in detail in a second so the primary primarily what we are doing is sorry we are also using slices through the genome and we are we are looking at each of these slices independently and the assumption is that there's a lot of redundancy across the genome so if you are looking at a promoter region then this should be captured in the data that you have for this position and it would look to some extent similar to other gen promoter region in the genome so we are getting rid of this of the huge number of parameters that you need for the genomic axis and you could also imagine this as looking through a film a movie and where you have certain pixels missing and you want to complete the missing pixels and you do that actually one frame at a time and the reason why we do it one frame at a time and don't learn across the genome is that given one assay you really get measurements for the whole of the genome that is if you're not having that assay you're also missing the whole of the all other assays all other genomic bins so if you are in a in a in a if you want to predict this square across the whole genome this square is missing so learning across the genome is not really helpful in that sense so we are we are we are it's like looking at a movie where your screen is broken in one corner and so and it's always the same pixels that are missing and we are trying to complete it by looking at the remaining pixels that are available for training and testing okay so the way we do it we separate we first look at the we use a signal embedder so we use first for a given cell type we are taking the data from all the assays at a given genomic position we are combining that with a global cell type embedding and and try to embed this signal with the signal embedder to capture the information of these genomic bin and combine it with the with the global cell type embedder and then we are using self attention blocks so this is coming coming from from natural language processing basically a transformer a kind of architecture where we are now looking at all the other cell types and we are trying to identify which of the other cell types for this slice is really most informative to understand to make a prediction of this of this cell type so we get we create contextualized cell type embeddings with this self attention program right so so with that we can really capture the interactions between different cell types in the model and we do a similar approach across the assays so we are taking all the data for one assay we are taking the the data across all the cell types in one slice we are combining that with a global global assay embedding to learn these embeddings and we again use this self attention model for contextualized assay embedding that really also looks at the other assays at the same time and then we really combine these two fuses in a multi-layer perceptron to make a prediction of this square that is missing exactly here so with that we have kind of what this allows us is to build a model that is has a large that is orders of magnitude smaller than the previous models so instead of billions of parameters we only only have six million parameters and it also generalizes really well to unseen assay cell type combinations with outreach training so we completely got rid of the genomic embeddings so the model doesn't scale with the genome size so for the human genome that's very good news and it turns out that the architectures also very suitable for domain adaptation in order to to apply it also to new data sets so if we are looking at some performance matrices and the generalization efficiency so this this strategy we can really use different blocks of of different random sets of the genome for training so as as performance matrix we use area under precision recall for enrichment for peaks and on the x-axis here I'm showing the number of training bins for genome write prediction and the blue dots are is edi's and edi's is so so higher the higher this area under precision we call the better and you and the x-axis is also in log scale so and this purple dot is the competitor which is chrome impute and no it's actually I'm sorry this is avocado and for avocado because we need to have the genomic factors we can we actually have to do the training on the whole genome so we can't do the same thing that we did that we are just using parts of the genome for training but we have to have seen the genome the whole of the genome for training to make predictions there so it really uses all of the the genome for predictions but if we are only using four orders of magnitude less training data we are already getting a better performance and as you can see it's increasing this more training data as it should so we are also looking at mean square error so basically how similar is our training our predict predicted signal from the measured signal and here the smaller the better you see again this quite significantly less training data we get really good results and also if you look at genome white correlation we do really well so that was quite nice so to look but so now we are looking at some specific results on our predictions so this is a small part of the genome very small part so you have base pairs on the x-axis and it's part of a chromosome I think it's chromosome 11 and you see the observed measurement in blue and our imputed one in red on top and then there are so-called peak finders called the one that's used by the encode pipeline by the official encode pipeline is called max 3 and they really call the regions which are enriched above the background and you can see that they overlap quite well between when you do that on the observed signal versus the imputed signal and also these signals look fairly similar so it does look like edise imputed tracks can quite accurately capture the measured signal so again here are some of the performances so there's mean squared error globally and genome white correlation edise is doing better than its competitors and this is across a large number of different tracks and historical modifications so that's why you get these these bar pilots so it does look like edise is doing a quite good job however the problem here is really that it is really difficult to assess the quality of the prediction and the reason for that is that we are actually not interested so much in recapitulating the precise signal across the whole genome rather what we want to do is we want to find very subtle differences between for example tissues so in this case so here's a needle in the haystack and this is of course a painting of franco and if you were able to very precisely recapture this painting predict this painting but you would not paint the needle in this case overall you seem to be doing a good job but you're missing what we are looking for in biology and the problem is that we don't even know precisely where the needles are what a needle looks like so really we want to assess our predictions mainly on the needles and not the vest of the haystack so we are not interested to very accurately paint the haystack we really want to find the differences between cell types for example do we achieve that so what would tissue specific differences look like so here's for example a peak a signal again xx is the genome which is the same in two different cell types so you have a cell type which is called e025 and a cell type which is called e52 and the measured signal is the solid line in blue and red and you see that these look fairly similar the blue and the red but and when we look at the imputed data it's the dashed lines and they recapture this this shape quite well and they look very similar for the two different tissues if we look however at a peak which is different between the two different cell types so again e025 and e52 you see the solid lines are quite so the the signal is only present in one cell type and not the other and we have captured that really well as well so we we can see that the the two cells are correlated they are related at some in some areas and in others they vary and we are able to predict very well the areas where they are similar and also where they are different and we have tried to quantify that to some extent where we have used the Wasserstein distance as a metric to to see how similar the shape of these peaks are and you can see that this peak so the red triangle you can find it here so in this case you have the Wasserstein distance between the observed marks in the two different tissues and it's a large difference because large matrix because this is a cell type specific peak and also when we looked at the imputed difference it's also a large peak so again we are doing quite well in identifying the differences and also the similarities and that was reassuring so what is I have I'm not talking I see I missed I took out the slides here so when you talk about so I have been working with with biologists and experimentalists for quite a long time and as a bioinformatician really what we have been trying to tell them is that they have to do replicas so it's not enough to just do the measurements once but you have to do it at least three times in every cell type and then you have to do statistical testing between predictions to see what so is this is are these difference these more subtle differences maybe here for example and they relate you to the differences in cell types or is it just is it just noise or random random differences is that just the variance of the of the signal itself so for the imputations this is not not being done so we basically just pull the replicas and make a prediction of the mean signal and that I think is also a bit of a drawback and we were trying to estimate the divergence and then create replicas based on imputed means and then do a statistical testing on these on the different peaks as well and that worked very well as well but in in general the imputation field is is looking at mean signals rather than and then trying to identify differences between tissues without doing proper statistical testing and I think that's still a bit of a drawback and potentially something that needs to be investigated a little bit more so the next thing that we were trying to do was we were thinking is it possible to do that actually in an individual specific way can we use our tool to predict across individuals so in this case we would actually we make a small question because we're moving to a different semi-project right um yeah are there any questions in the room or in the virtual room about transformers and the imputation challenge in general so I have to say that for the very specific technical questions I will eventually refer you to to my my students who did this very sophisticated um uh implementation but I'm very happy to answer um questions um are there references that you can share about these uh yet is there a bio archive yes so this is this the paper is from bio archive and um and it's it's it's submitted and sent out after major revisions so it's a bio archive um paper um at the moment there's also and I after this bit I will talk a little bit more about the competition as well and this the competition paper is also a bio archive paper and I can add it to the to the slides the the references okay thank you any questions that have matured in these minutes okay carry on okay so the next um project that we were so following up from these kind of reference epigenomics um we were thinking it would be really cool if you could make personalized epigenomic imputation and as I've said before um the the reason here is really that um um epigenomic um patterns seem to be changing very very early on uh for example during tumor rechenesis so they seem to be an early diagnostic marker um they are also markers for for uh new new developmental disorders and new degenerative changes and also for aging quite relevant so however um a lot of tissues are actually not easily accessible so it was easily accessible as blood for example but but you might want to know something about your liver tissue so would it be possible eventually excuse me would it be possible eventually if we had some tissues in a in a target individual and we have the relationship between these tissues learn on a different individual to make predictions on a missing tissue for certain epigenomic marks I'm sorry and um very very recently a very good dataset came out um and was added actually to the to the encode dataset and this is data it's the same data matrix that you have seen before with the different histone modifications on the x-axis and different cell types on the y-axis and in addition to that we have now four individuals so these little circles indicate that for this um assay and this tissue we have four data from four different individuals and the individuals are two of them are females and two are two of them are males and they have different ages as well and um so in this case we we chose a small subset of these datasets and we just tried to predict um first um we tried to predict across individuals and um so here we first had to kind of understand the data again very much so this is um a dataset for one tissue type and one histone modification so it's tissue 106 and the assay is H3K4 tree mutilation again and in the different rows you see the different individuals and what what you can see is that globally these um these signals look very very similar um so it it is actually um so and the imputation and the observation is also very very similar and that's not surprising because they are actually very very well conserved so um just to give you an idea i'm sorry i don't know why that's building up but just to give you an idea again what we were trying to do is so for this for this peak um we and for this individual so in this case this is the real of the individual um this is the data matrix um that we had so we have these different tissues and we have these different um assays and we have in this case we are using all the data available and we are trying to predict um this um pixel the value for this individual pixel and we do that for each of the individuals um and um when we are looking at the imputed epigenomes um they look so so the top row is the observed data and the bottom row is the imputed one so again in this in this setting it's a leaf one out setting so we used all the pixels to predict one pixel and then we just um mutated um the around the the the pixels um but we are doing a pretty good job predicting this peak um but it's also a fairly similar fairly easy um um signal because it's shared across all the individuals this is a much more uh difficult um setting so it's a different um uh tissue also it's required for tree mutilation and in this case it's only one of the individuals who has the peak and the other stone half it and um okay that's a bit silly I'm sorry why this is I don't think went wrong went wrong here and if we are looking if we are taking this individual this row the individual again and we are now looking across the different tissues in that individual it looks like that so it's a peak which revise a little bit not only between individuals but also between tissues and so it's becoming really difficult to predict um so the matrix looks like that in this case so the question would be is this a peak there or not um it is there and our predictions for for this peak are also relatively good um as compared to the observed data okay I hope this this makes sense um is there is the strategy clear here not entirely to me so you're not treating uh so the the obvious thing will be to treat different individuals as if they were just different tissues right but you want to somewhat retain the fact that you might have more tissues from the same individual is that no we are we are first we have all the data available for one one individual and um then for the target individual we have missing data and so we want to um and the missing data um in this case we're starting out by just removing one one single pixel in the target individual and we want to predict whether this this this um the value for this um assay tissue combination in the target individual so we have the full matrix for another individual this one um and we are then doing transfer learning um to um infer missing data on another individual um given the data that the other data that we have for that individual so the e things are different types of tissues right but these are the cell types so the tissues right um so the assumption here would be that we are having missing data for one tissue in one um assay so it's a fairly similar so we have a lot of data available so in the next step what we did we are using uh we we wouldn't have any data from one tissue for the target individual uh and we would try to predict the whole row um for uh for a new individual and that turns out to be quite hard and we are not doing very well on that so um yeah we still have to work on that but this is the first step where we are actually trying um one individual um where we have learned the relationships between the different tissues in a different individual and in the target individual we try to infer missing data and we are particularly interested in differences between the individuals as well uh and there was some please repeat from the virtual room but it's not clear what exactly is it clear now after this explanation Tasnim well okay let's assume you cleared it up good okay um oh there's a question from the room okay uh microphone is being carried to the questioner uh just one question about the individuals like are they like for random healthy individuals or like are they differentiated by some specific illness or they are so you can't take these um samples from living individuals so they are deceased um so uh post mortem um but still the question remains whether they were you know healthy dead people or deceased dead people right well they are not um that's that they were considered to be um relatively healthy all right okay thank you um but they weren't um yeah they were considered to be healthy um yeah uh good okay so I guess what you are seeing here is this this is a slice through one bit of the genome just one these these images are slice is just one slice through one position on the genome and you see the differences between the individuals so you have two males and two females here um again you have different tissues and different assays and what you want to do is so this this female looks quite distinct from this male for example and you want to capture these differences between the individuals okay and we and in the imputation you see that we are doing that fairly well also it's a hard problem okay so and the idea is so why should that work in the first place so um if we don't have so I think if our if the underlying reason for a changed epigenomic peak could be on the DNA sequence itself so if you have a mutation on the DNA sequence then that would be individual specific and it would and if it's a germline variant you would see that in all the tissues and it would affect potentially more than one assay and therefore you should be able to infer these differences in the in across the assays also it could be that you had a systemic response for example to pain so a certain gene might be switched on because you have you are repeatedly exposed to severe pain um this is remembered in your epigenome but not in a tissue specific way but in a in a systemic way and then it is possible that you could kind of predict that um it it um manifests manifests itself in a certain way in a certain tissue based on the other tissues that you're seeing and then you could potentially make predictions on on what what does these changed epigenomic states in that tissue might cause so that's kind of the the motivation for us that we are trying to um to predict these individual changes in um in the individuals but it's also again it's really difficult to understand how to how should we validate our predictions and um so and and also how do we compare it to baseline methods for example because you have seen before in the h3k for rematulation setting um a lot of the peaks look very very similar across individuals and you see that here so if we are looking at one male and one tissue and we look all the the peaks that are that we find there for this assay we see that um most of these peaks are shared across all four individuals and all tissues um so this could be because h3k for rematulation is really very often founded promoters the promoters of genes are very important so they are they are shared across individuals they are also shared across tissues and that's um so h3k for rematulation is easy to predict in a sense because it's there's not much variation between individuals but then you have something like h3k9 rematulation and in this case you have um most of the the enrichments are only found in one individual and only in a subset of the tissues and um then it is getting really difficult um to to predict them so um yeah so the next thing that we are doing is we we try to um so this is kind of the uh shared and unique epigenomic patterns and as a baseline we compared our methods to to a very simple um way of of making predictions which is just ever-riching and in this case we are ever-riching um for a given assay across all the individuals saying that okay this this is um um so if we are just ever-riching using the average of all individuals how does the signal look then and the other baseline method would be um we are using the other measured three individuals and take the average of that to make a prediction for a given cell type um assay combination so that's the track average and um and in in our case so the edi's left out um leaf on out um uh scenario is we are learning about we are learning we are using all the available data for that given individual except for the one that we are trying to predict and in the next step a step we were trying to do it um without any data from that given tissue but that's increasingly hard so in the case of the track average of course it is very easy to predict these guys um in this case which are shared across individuals um so you're you're just taking because they are they are shared so you would do quite well with these um these peaks um if you are looking at the average across um individual average across individuals it's these guys which will be easy to predict okay and then if you're looking at the performance measures um that are looking at all enriched regions on the genome um so um H3K4 tree mutilation the averaging already will do quite well um and that's kind of based on the on the way the data is is is shared between individuals and tissues um okay and you can see that um here we are looking at the area under precision recall curve and um the blue uh line as edyes um and we have the the average um averages work quite well for some of the methods and for others it doesn't work quite as well so we make a little bit of progress but to be honest it's it it is a really hard problem um to predict so the ideal target would be for a patient to come into the clinic you take a blood sample um you measure you you take the assays for all these different epigenomic marks and then you make a prediction across many different um tissues that you can't um sample and then um use that for for diagnostic purposes and I think we are quite far away from that but that's that's our motivation that's where we want to go okay can I can I actually ask a question so I mean these numbers are much much lower than the UPR sees that we were seeing before right exactly and the reason is because you're focusing on individual specific enrichment yes okay so you've taken a subset of the you're looking at the hard cases basically and yes exactly okay so we are subsampling the peaks and only looking at peaks which are not shared um uh across individuals I see okay right thanks okay um but in the meantime while we were working on the individuals we were also so the competition was um the competition organizers were also looking at um at the provided the amputed data sets uh and they came up with um uh this ranking um the first ranking that we got was in June 2020 um what is and we were um there we had the third rank there um again the problem here is that um they also had as a baseline um they used averages so this is going back to understanding epigenomic patterns in the reference epigenome and even if you are going in the reference reference epigenome if you are using the average um for given assay across all the cell types um according to their matrices the average did remarkably well as compared to all this very sophisticated um uh partly deep learning uh tools which was quite um frustrating to be honest and I think it was also for the organizers quite frustrating um then they revalidated um the um the whole um data set and went and came up with a different ranking in June 2020 uh in this case um the average performed much worse we are still doing very well relatively well up here um and in the meantime in June 2021 they had a third ranking in which case average was doing intermediate well and we did um uh much worse so the problem here is that the assessment of the data set is is really really difficult and we could talk a lot about you know different types of models and improving the transformer model and and all and so on but the real problem is that we do not understand yet how to assess the data and um and that's a really really big problem I think also in the interpretation of of these histone modification marks we don't understand what is a good mark what what is the needle in the haystack and I think if you are doing machine learning in the context of biology this is the take home message that I would like to give you that it really depends on um identifying the needle in the haystack and getting the matrix for your validation correct and uh that brings us to the next project which is trying to understand what these signals um actually what they actually mean and if we can do something potentially um in the preprocessing slightly better in order to um to to get some of the confounders out of the measured data sets in the first place in order to be better able to to to interpret the the measured data sets and I think here I'm taking a break um for for more questions yeah so one of the things that I noticed was that avocado was consistently the worst no matter how you really renormalize the data right and this was the method that was started to be you know the the best thing by being noble and the organizers at the beginning right yes yes that's actually true and so so how I mean that's that was quite a high impact well at least you know it was well published in a good journal and so on how did they manage since it is consistently worse than average whatever you do uh was that yeah I I suppose that the that the competition is is flawed to some extent in the way the data was um collected and the test data was collected um and but I think it's a it's a very it's potentially we are in a in a similar process than what happened for you know protein structure prediction this kind of took I think 20 years or longer um to actually um get the right assessment scores and to understand how to um how the competition should actually be around so this is the first time um this implementation challenge or the second I think there was one before a slightly different one um so I think it's it's still uh early in understanding how a competition like that should be um designed and I mean to some extent it was created such that you would improve improve upon avocado which was the state of the art at the beginning of the competition what is really worrying that just ever reaching across the samples is creating such a good a result and I think part of the problem is that training and test data were performed at different times in different labs so you have massive confounders and massive batch effects and um the tracks the the tracks in the test um set um the um sharing these confounders but the confounders were different from the training set so if you're just ever reaching across um the tracks from the test set you can more so so you're you're more easily um making a right prediction so so yeah somehow almost predicting the the the technical differences there's a question in the chat uh what explain rank here please so I guess what what are the metrics really if you could expand a little bit more oh um so as we have a large number of different tracks to predict and then large number of different um um so a large number of different matrices like mean squared area over the whole genome area under precision recall curve for the max cold peaks area under rock um background correlation um foreground correlation foreground being within the peak so if you're predicting the the the peak height correctly and so on and they have um they have computed all these different matrices for all the different tracks and then they have combined created a combined rank um for each of the predictions so again that was some of the matrices were highly redundant so um genome-wide um correlation is very much redundant with um background correlation because the majority of the of the of the genome would be background uh for many of the peaks um so so I think um the way they have constructed the ranking is problematic the way they have constructed the training and tested is problematic but it's also um yeah so so I think it's it's not very clear at the moment because we do not know what the needle in the haystack is so how do you validate the two pictures of the haystack if really what matters is the needle but you do not know what the needle is or there are several needles in that haystack and the question is do you identify all these needles um and do you identify needles that are different between different tissues or different individuals if that makes sense so the validation uh is really difficult the questions from the room I mean I would actually have another question uh on these needles I mean suppose you were getting a method that performed you know amazingly well you know drove your average score almost to zero how do you know you've actually found the needle and and what is it then exactly that's exactly the question that that would kind of invalidate the whole prediction purely prediction based uh well I mean the problem is is is bigger than just the imputation and the prediction because you have um so if you have a data set in generated in one lab and you have the same data set generated in another lab and you are trying to identify the needles in these two data sets they are they will be different sets of needles um and quite significantly different sets of needles and so because the the technical biases are quite significantly different and so how do you cope with the variation in the measurement itself how do you disentangle the true hidden signal from this signal that you actually measure I think it's it's not just about imputations it's also about the technique the measurement um how do you eat and so how do you say that this is a particular this this experiment worked and this experiment did not work or how do you say this experiment worked better um than another one okay if I see no further questions either from the actual room or the virtual room let's let's go to your multi multi-stone chip analysis okay yeah and so what I um so so so with that we started to think a little bit more about um how these signals are generated in the first place and um what do you see here is is um there is a bind version so every dot so the every every um every little um diagram here every little a little graph here is is one histone modification um and in there the dots are bins on the genome and um now we are looking at the coverage for that this this height of the signal and we are also looking comparing that with a control sample and um okay I am and it looks like so a background control that in many cases for many signals um so for example h3k4 tree modulation there's really a very high correlation between the background the control and the actual signal that you're interested in so um if you're not looking for this mark but just looking at the background you get a similar high um um uh signal um then if you are actually interested in this signal and that's of course problematic and so let's look at the experiment and how these signals are and actually generated so um the chip sec uh so this is called chromatin immunopress chromatin immunopresentation followed by sequencing and the protocol is as follows um so you have the dna in plaque here and you have i'm showing five different nucleosomes in a row and um three of them are having the mark that you are interested in shown in a as a red ball and then what you do is you do sonication so you're trying to break this very long dna string into smaller bits you do fragmentation such that these bits can be easily sequenced um and and and then you can identify certain locations on the genome the problem with the fragmentation is that the fragmentation is not not random because there could be um you know the the bits which are actually wrapped around the histones are not easily breakable um so the most break points happen between his tones and if you have a very densely packaged package chromatin then it's very difficult to break it up and you would get longer um longer bits of the dna in this region and shorter bits in this region okay um and then you do the chip part which is immunoprecipitation so you take a specific antibody that recognizes um uh your histone modification of interest and um you then remove the actual protein um so in this case um so you remove the protein and um i'm sorry so you're using the antibody of course um to to to filter out um um the dna which is bound to your nuclear to your histone with the modification um and you are only interested eventually in sequencing the bits of the dna which have the modification and which are pulled out um with the with the antibody um so these bits um uh so this bit is particularly highly um uh pulled out but um you also have a step where you do size selection um because you can't um sequence fragments which are too long very well and so this bit would actually not be sequenced very well and this bit would not be sequenced very well either because it doesn't carry the the the mark um so you are ending up with reeds which are then mapped to the genome where you have a very high peak here but lower peaks here um because this is just too densely parked for fragmentation and lower bits here so instead of um identifying these two regions you are potentially only able to reach to to identify this region um this modification and also um you can't this the regional resolution it is much smaller here because this this is not this nucleosome is not independent of the other two which actually carry the mark while this doesn't um so to some extent um you can correct for these problems by using um uh by removing the step of the chip step um where you are just using the fragmentation and the size selection and then you map everything and with that you have kind of a controller background sample that does not enrich for your modification of interest but it just it can tell you something about which areas of um the DNA are actually kind of measurable which are kind of this is would be like the the bright side of the moon and this would be the dark side of the moon so here it's much more difficult to measure in the first place and here it's it's more easy to measure make measurements and that's your control sample so your control sample at any given tenomic bin is really determined by the accessibility of your chromatin but also by the mapability so in some in some cases the DNA is very repetitive and then you cannot easily identify the specific the specific the specific locus where read is coming from but this is also determined by the DNA sequence itself so you have accessibility and mapability which determine your control samples and for the treatment samples you have the same problem you have accessibility and mapability that determine your mark and you have also the specificity of your of your antibody so if your antibody is not very specific you would also pull down fragments that do not have the desired mark so you would pull down noise other unspecific reads so you here you have an addition of the unspecific noise and your signal and both of them are depending the signal that you're seeing is both of them are depending on accessibility and mapability and so the idea that we are having here is first that we can use decodenia we use actually first try to separate in our treatment sample the signal specific part from the unspecific part and then to remove the accessibility and mapability which is a multiplicative factor and in order to separate the unspecific from the specific parts we are using non-negative matrix factorization where for example we have two signals so this is our background our control samples it's also sometimes called in biology input sample and this this is our histone modification that we are interested the first one that we are interested here and by using non-negative matrix factorization we can find an unspecific part which is shared between the control sample and the treatment sample and we can remove this unspecific part from our observed signal and if we are using a different histone modification there's a different signal we would still assume that the unspecific part is also shared and we can remove that one there as well so if you're looking at the origin so this is now a heat map with the original data so this is the control measurement this is the first histone modification and the second histone modification and after the non-negative matrix factorization we can what you can see here is that we are removing quite a lot of the unspecific noise and we are packing that into the unspecific track and we also have the mixing factors so saying that in the first case of the unspecific read in the control read we know that this is a mixture of only the the unspecific it should be only unspecific tracks so that's why we have this this here and in the case of the other two histone modifications we know that there should be some unspecific components and some specific ones and we start we have a much cleaner way of looking at the signal itself and removing the unspecific reads from from that signal and in the next step what we are doing is we are using a tool to remove the multiplicative confounder does that make sense so far just to clarify completely so these indices are h and also a and m are matrices of course right um so this is the treatment sample so i have to say i'm this is the first time i'm presenting that so we are still working on the notation so if you're looking at a given genomic bin for a given histone modification h and a given replica so in this case so you can see that here are different replicas for the same histone for the input and so we have two replicas both for the control sample for the histone modification one and histone modification two and um and they should be shared so um the idea is that most of the time the control samples are actually not very deeply sequenced so we have a lot of missing information here but because the antibodies are never 100 specific and in fact they are very in some cases they are actually not very specific at all the assumption is that they all carry quite a lot of signal from unspecific signal so we are learning the blue curve jointly across all epigenome all histone modifications and then removing that right so that's that's kind of the novel thing in this approach because usually what happens you are just taking um one replica at a time and correct dividing by the input by the control sample rather than learning the unspecific tracks and a and m would be different for average genomic bin excuse me a and m would be different for average genomic bin yeah so m is the mapability which really depends on the dna sequence for this genomic bin how likely can you find the right spot on the genome and a is the accessibility which depends on how the how the dna is kind of packaged in that specific cell type which determines the fragmentation process and the size selection process okay okay so and a and m is shared between control sample and the treatment sample but you also have the in the treatment sample you have added you have the signal here as well and the k is basically in this case the mixing factor so how much signal is there relative to to the unspecific read so that's kind of the specificity so now what we have done we have really we got rid of this bit um the unspecific bit and now we are trying to um so what we are interested is the true signal sh so with the non-negative matrix factorization we got rid of the unspecific reads but this is still confounded by m and m which is very strongly depending on on the position so even after we have removed the blue line from these two tracks you can see that in this area for example it's really really difficult to get any signal whatsoever so if we do get signal here then we want to actually boost it while in this region it's actually quite easy to get signal because even if you are not using an antibody you you get more signal than you would expect so we would kind of want to rescale this peak relative relative to this peak because we already know that here it's it's so difficult to make the measurement and for that we are using um so we want to kind of correct it by removing this multiplicative factor and we are using a technique um from causal inference which is called half zippling regression and the idea is that what is hidden are this the true signal s1 and s2 so these are two different histone modifications and also a times m the confounder and what we are measuring is just x y1 and y2 and by writing down this causal model we can actually remove the effect of am from y and and infer what the true signal should look like and so we are doing that by so this is the red signal now with the blue signal removed but we still know that this is kind of the signal from the noise and by applying the half zippling regression we can boost this we can we learn that this peak should actually be um having a bigger weight than this peak because here it's much more difficult to actually make um to make the to make the measurement in the first place um so um if you we start with this kind of measurement which is very much depending on your specific instrument for sonication for example and the antibody you're using the specific specificity of the antibody so whenever you're using this measuring that signal in one lab and then you're going to another experiment it will look very different and we are trying to correct for that um in order to get the true hidden signal for this history the true hidden um his tone modification enrichment um this this kind of signal and I think if you're using that for the prediction then also in in edice later on it will be more predictable um and more and we'll be able to to make better predictions as well um okay and that's another peak um which is corrected and um so I've shown you this this plot before um so you have the control um um samples here and I've what I've shown you is that there's a high correlation between the background uh and and there are different his tone modifications that we are measuring and we are correcting for that um with this half zippling regression in the non-negative matrix factorization and and so we are getting we are removing this effect which is really a confounder of the different that that the different locations on the genome have different more or less easily measurable and so this this correlation is completely removed in the bottom plots um we also tried um uh we did a couple of um simulations first so in this case we created a peak and a dataset um and this is the true peak um this is our control sample um this is the sample um that this that's the um his tone modification and um when we use max that's the usual preprocessing um um for for this tool um you would identify these two peaks but after using decoden we identify only this peak um which is the true peak that we have put in and this one is is is almost reduced so that's just an here's another example this is the troop in the true peak this is the signal after um decoden this is the simulated chips example if you're using the chips example and you are applying max the usual tool to it this is the signal and you see you would get an additional peak in this area where you also have a high control regions um and again um uh it looks quite good for us now this is a real dataset um with which we have corrected um from the encode dataset um the top is a control dataset so the background control um then then this one is um hvk for tree matulation and this is hvk 27 matulation and what you can see is that here's a big peak only in hvk for tree matulation and this is after nmf and this is after the half zippling regression and you can see um that the peak the shape of the peak is not very much affected um while here's a region where you have a high signal also in the control sample and also in hvk for 27 matulation and um this peak is basically removed after um already nmf but then again after the half zippling regression and the same holds for the hvk for tree matulation signal um so we are we are we are conserving the big peak here which is specific to hvk for tree matulation but we are removing peaks um here that is probably a due to a confounding factor um and we have quite a lot of more examples um where we are where we really can see that the what we are doing makes sense and we are trying to validate that in in different ways now but again that is difficult too because we still don't know for sure um what the needle is in the haystack and um and really what we want to do here is we want to identify the needles in the haystack okay any questions i do have another question so if you actually use multiple tissues here you may also be able to estimate because the mapability is the same across tissues presumably yes but the accessibility no so you might actually be able to estimate tissue specific accessibility directly from gypsy and you could completely compare that with say attack or something like that right exactly yeah we are thinking about a way to do that as well so it's not entirely clear so i'm i was i was talking to some of the biologists and they weren't sure about that i mean i'm i'm calling it accessibility for lack of a better word i think it's kind of um telling you about something about the pre-kits of the dna and uh how densely it is packed because if it's very densely packed you would get longer fragments um so um but attack sec again um is quite a different technique with different biases it would it will be interesting to see how that um how that um compares but i do think that um that um the access so the unspecific track um in a tissue specific um context would be value in its own rights any more questions from the room or the virtual room because you know you still have three minutes so okay i think i leave the last i i think i leave the last um i i i think i this took a little bit longer than i had expected i just um went slower and tried to explain it um i hope it was understandable and i didn't lose everyone anymore last call for questions before lunch well if not uh let's thank uh gabriele um and uh i'll i'll stop the recording right antonio i started a few minutes late fortunately someone reminded me


Hello, in this video we're going to create a geo package with all the data layers and styles and the project. Let's start with using the package layers tool from the processing toolbox. With the tool we can package vector layers into a new geo package. So I choose here the layers that I want to package. So I just want the catchment boundary and the channels. And by default the box is checked to save the styles into the geo package, which I also want. Choose an output name for the geo package file. And click run. If I refresh the browser panel I can find here our new geo package with the two layers in it. Now let's add some more layers that we want to keep. I'm going to add the DEM subset tiff layer. In order to do so simply drag the layer to the geo package. It says that the import was successful. Note that for rusters the styles are not imported and we see it there. The three layers but they need to be added to the project because they're not automatically added. So I select the three layers and drag it to the map canvas. Remove the non geo package layers and only keep the geo package layers that we want to keep. I'm renaming the DEM to not get confused because it got another name and I'm duplicating it called duplicate hillshade because the DEM does not have the style I'm going to copy the style from the original file from the geo tiff and paste it here. I can do the same for the hillshade. Now I remove everything that I don't need anymore and only keep the geo package layers that I've styled. You can check if these are your geo package layer by hovering your mouse over the files. I can also save the project to the geo package.  Click OK. Now everything is in one geo package. In this video you've learned to package all your layers into one geo package including the styles and the project.


Good morning Like take a moment introduce Take a moment to talk a little bit about a conda as a the conda Corporation and also as well as the a star open-source project a little bit about me. My name is mark McLean I am co-founder and CTO of a conda previously served on the open-stack technical committee as well as former neutron PTL So when we start thinking about the conda and you know the backing a star open-source project We really start talking about the neutron operational challenges in terms of you know, how do we manage multiple services whether it's routing load balancing firewall You know, are we using SDN? Are we using multiple different L2 backends? You know, it's very hard to change them Additionally, you know, how do we handle multi-vendor deployments over time and you know And so what happens, you know when we started this project is we were all working You know, we're working at a hosting provider and working in public cloud And so day two operations were very important for us a lot of solutions You'll see are very easy to stand up on day one But in day two it would become very difficult to operate and so that was the motivational challenge for creating A conda and one of the other things we wanted to do is kind of capture Transformation we've been seeing over the last 20 years as you know the over-the-top Network services have been provided, you know It started in the 90s with voice over IP rolled through with video and public cloud hybrid cloud And so now capturing that and providing different services over the top So within that we birthed the Astara project and really key Three key things to that were you know to be hyperscalable You know provide a control plane that can support a large number of endpoints whether it's public cloud or whether it's containerized services Also to provide the overtop network services we focused on layer three through seven I'll kind of touch on that in a minute why we didn't go all the way down to layer two And then additionally we want to maintain those open-source API is that you expect to find an open stack Mainly we want to you know enable Users to continue using the existing tooling they have not have to write special one-off Scripts or one-off management or monitoring, you know make it very easy to use And so at the heart of the conda solution is the Astara orchestrator It kind of has the affectionate nickname the rug Mainly from the line of the movie the Big Lebowski for the rug really pulls and ties the room together So I think we've kind of all seen this slide in terms of what reference neutron looks like you have a you know If fleet of microservice agents they talk via message queue to the neutron server in the database Operationally it can be a bit challenging you have a lot of agents running you have a lot of agents speaking different protocols The protocols evolved over different over different times. They're not always the same payloads can be vastly different And so with neutron we simplified a little bit the L2 agent still there because we wanted to remain layer 2 agnostic and to provide layer 3 And above and so a star Communicates directly with the neutron server a star itself as a plug-in into neutron So you have the standard neutron API, but behind that you have a star managing layer 3 An alternate way of looking at it if you think about the neutron reference architecture You you know you have your hypervisors you have your network nodes in this case We've got one up there Typically the network nodes can become points of saturation points of failure points of congestion and with a star it's a little bit different So if we're archers if we're orchestrating The network functions within the deployment we can actually run them So in this case we're we're we're showing it as being run as service VM So if you notice they're actually spread throughout the deployment the one benefit to that is that if you have a failure of your network function the impact to Tenets is actually going to be mitigated a little bit because it's going to be localized and so it The impact is a lot less When we start in a star itself a star supports routing as a service load balancing as a service And so a couple of benefits you will find say over the stock neutron is a star supports dynamic routing both OSPF and BGP More recent releases of open stack, you know have added support for BGP speaker But we've been supporting BGP almost all the way back since Folsom It was designed from the ground up for IPv6 and as a matter of fact traditionally if you were to install Starra, you know the management plane is almost always v6 It can run on IPv4, but we decided to be more forward-looking and we wanted to be layer 2 agnostic There's a number of layer 2 technologies whether your your virtual switch is based on OBS You're or Linux bridge running on the host or you could be running say hierarchal port binding with some of the top-of-rack switching that's available and So being layer 2 agnostic enables you to have Different data center deployments you can keep them all consistent You can also over time as you roll out new deployments You can actually change your hardware mix without having to worry about you know, oh no now I've got to have a different layer 3 solution Another way of looking at this with the star with this with the architecture is on the left-hand side You'll see the orange boxes for Nova neutron And a star those are all run with the control plane the important thing about a star itself is a star is an orchestrator so No elements of a star actually run within the data path So if you're looking on the right-hand side, you'll see that you know, there's the physical network There's you'll see OBS or Linux bridge or some proprietary Solution which is managing layer 2 a star has a little bit of a shim Which really all that does is talks to the interface layer for layer 2 in most cases It's actually a no op the standard open stack API's and then advanced services for routing low-balancing firewall VPN and so You know The real benefit of the plug-able architecture for a star is that you know, we can support new services easily So in the metaka release, we were able to rapidly add VPN as a service and One of the other features we enabled is actually kind of what we've nicknamed bring your own network function So one of the challenges with a lot of open stack deployments is once the infrastructure set up You're locked into the particular solution you have for low-balancing locked in particular solution out for routing But what if tenants need a different? Provider for that what they need a different appliance and so with that An operator could easily enable to bring your own function. So a tenant could actually say hey, I have my own, you know Routing router that I want to run and so you can upload that into the cloud via glance and then a star I can orchestrate that for you Similarly is it orchestrates routing everywhere else And within that it's all driver-based. So currently within the open source tree. We have it support for ha proxy We have support for engine x both flavors regular engine x and engine x plus We're supporting the VPN as a service API That's via neutron and then we provide route even provide support for routing You know where those images are based on Linux BSD. You could have something like Cisco CSR It's very easy to plug these things in and that the plug ability is really key because you know today We have those network functions available But what if you want to add a new network function a star because of the way the orchestrator is written? It's very easy to write, you know and provide a little small driver that then will work that then teaches the orchestrator how to manage that resource You know It's all it's all there. It's all open APIs. It's all you know integrated very well in with neutron nova glance and sender Another one the interesting features about the control plane about a star is a star was since we designed it for the public cloud use case It was designed to both scale up and out So one of the more interesting things with a star is that from an operation standpoint? We start talking about day two operations is you have the ability to you know scale up You can add more threads as you have more network functions Running or if you know Optionally with VNF so you can with a star process. It's multi-process on a single host so you can add more processes Or one the newer features that we've added recently You know started working on the Liberty release and rolled out in Mitaka is actually with the stars You can actually stand up different a star instances on different nodes They're both multi-process and multi-threaded so you have the ability to scale both up and out and if you notice The set of VNFs that are managed is automatically repartitioned as you add Orchestrators so if I were to add a third one it would get partitioned again And so as a set of orchestrators expands and contracts a star is handling this for you There's actually no active involvement as An operator other than just configuring the service turning it on all the orchestrators talk with with each other And then partition the set of VNFs amongst themselves similarly if I were to contract that set it will repartition the set So within the Mitaka release I kind of touched on a little bit earlier to bring your own network function We think that's very powerful. We think that's it enables operators to provide some really interesting services To their end users Active active appliances is similar to the HA function HA routing pair that you would find in reference neutron. It's VRP support the VPN as a service and Then further refinements to instance pooling. So one of the challenges. I think anytime you're providing Services via VMs, there's always a little bit of time it takes between when you spin up a VM and when you When it's usable and so what we're able to do with instance pooling is keep a set of hot spares. So in the background the Astara orchestrator the Astara orchestrator is Constantly checking and the health of a particular network function if the network function degrades it can you know Spend down that instance grab a new one out of the pool and immediately configure it And your only loss, you know is going to be the time it takes to configure it If you're running active active you the tenant is likely not to see any impact at all So, you know as far as what a condo, you know when you take the open source of star You pair that with a condo the company and the service and sport, you know What we found over time is that it's it's a star in a condo significantly faster. Oops You know, it's 90% You know as far as setting things up This it scales significantly more and the cost is significantly cheaper over say some of the other solutions on the market so with that My PowerPoint keeps the one jump to the demo so we will So what I've got up here So what I've got up here if you look on The right-hand side what you'll see is you'll see I'm just kind of tailing the orchestrator logs What it does it gives you a good idea of just kind of the motion in the flow of what the orchestrator is doing in the background Kind of a little bit of telemetry and so what I've done here Standard vanilla open stack install with Astara enabled so if I go in and look at The network topology. It's kind of easy. We've got you know, we have one router. We have one network. We have one VM If I go in and you know Create a new network Got to make sure I give it and so in the background what you'll see is you'll see a star working You'll see you'll see the log files kind of scroll if I go click on the router and I add an interface to it And add the other network to it You'll see a star is watching these changes watching telemetry coming out of neutron. It's going through and proactively configuring The routing instance also adding attaching the network. So now if I go in and launch a new instance Can attach it to my new network. I just created And then So it's still that's still building and so from there you'll notice that the motion that a star is constantly watching It's constantly monitoring For the VM to be created And so that's kind of how it works is it from a user standpoint You're not necessarily noticing anything different from the operation standpoint you can go in And if we take a look underneath the hood, you'll see that the instances available So now I'm viewing more from an admin perspective You'll see it. There's there's no star service appliance running in this case because it's running my laptop I'm just running one. I'm not running in ha configuration You'll see it the management network is IPv6. It has the private network public And so from routing as a service, that's kind of how we provide it for testing purposes There's we kind of created like a little simple Linux box Image for doing routing now one of the other interesting things is let me switch over to this deployment is so let's say I've got two deployments here. I have this one here, which is very simple again network topology with VPN support I can go in and then I have another cloud deployment Maybe they're two different clouds in different regions or they're in different offices or data centers They're all connected in with each other and so if I go in and So I can open them up and so like if I click here, you'll see That you know, this is 157.2 And if I click here, you know, this is 150 This is 155.3 and so via the VPN that I've set up I'm able to go in and so if I open a console Yeah, I can go in and VPN across but what's interesting as well is because of the way the orchestrator works Underneath the hood as an operator if I ever wanted to go in and poke around at what's going on underneath You know, I can get access to So I can get access to that so if I take a look you'll see here that like You'll see it's it's configured strong swan IPsec VPN. It's doing a key exchange These are connecting via the link we have within our lab that kind of replicates a wider network As well as like if I wanted to go through and provision it it's just to kind of show you how I set it all up This is you know created policies created the service groups endpoints What's interesting about this is that you can actually use this feature and then you can use it to say bridge and open Stackcloud into say Google compute VPC or Amazon of us VPC as well the reason you can do that say with a star that you may not be able to do that say with You know the default reference implementation as a star supports PGP underneath the hood and so that you can actually create the IPsec peering and then you can and then additionally create the PGP peering session so you can exchange routes and get full connectivity so With that just kind of to wrap up again, you know a star was designed for hyperscale Scalability provides control plane, you know for clouds with a lot of endpoints whether it's containers or whether it's VMs The use case is very similar when you have lots of use endpoints. It's over-the-top network services today We have routing we have low balancing we have VPN Within the upcoming cycles we're talking about adding support for additional network functions The nice thing is you don't have to have wait for us. You can write a plug-in and a star can suddenly become aware of a new Service and network function and it's all open-source API's A condit a condit selfless company provides services and support We're happy to talk to you about how we can customize and work and provide plugins Thank you very much


Godzilla X Kong has been out for about a week now. I did a review on it. You're free to check that out on the channel Adam Does Movies and subscribe if you haven't. But today I thought I would do a spoiler video on the thing. So let's get to it. As always with these spoiler videos, don't look for any in-depth brilliant discussion or dissection about the thing. I talk about these films like a regular movie goer, like a fan of films, but not necessarily an expert on anything. I mean, I couldn't tell you all the different monsters in the monsters universe. I barely remember the names of these people because they're pretty much disposable and forgettable. There's Def Girl, there's the main chick, there's Trapper, I think his name is. Since I watched this last week, this is not going to be chronological. I can't even imagine I'll remember most of it because these films become so obsolete in my brain after about a week. That's the shelf life. If you asked me anything about Godzilla vs Kong, I'd have a hard time recalling anything outside of a couple shots. I think they fight on an aircraft carrier that can for some reason hold their weight.  I think some of the characters carried over to this one. I don't know if Trapper was in the first movie. He's certainly mentioned in this one a lot. It's Trapper. Hey guys, it's Trapper. I'm Trapper. He's got his Hawaiian shirt and shades. I'm going to be that guy. I'm the wild card of the picture. I think the black dude was in the last one too. Don't recall his name. I do have IMDB up. Bernie Hayes, it says. There's Bernie Hayes. Gia, that's the Def Girl. Eileen Andrews, of course. Eileen, everybody's favorite character from Godzilla V, Kong.  Is that a fighting thing too? Godzilla X, that means versus. Instead of the V, we switch to X. It's hilarious. It's honestly hilarious. We open this film with Kong in Hollow Earth, his new playground. This is inside of regular Earth where Godzilla is just chilling out. Godzilla is just up there hanging out. It's established that these two cannot be by each other because they're both alpha dominant. That can't stand. They'll fight to kill each other for the dominance over the domain that is Earth. So they put Kong underneath and everything's kosher. But he's having a hard time adjusting to the fact that he's by himself. Certainly no other giant apes in the vicinity.  Seriously, Kong is basically John Rambo in this film. He sets up booby traps. He's got like things that fly down and impale creatures. He's digging pitfalls. The guy knows what he's doing.  And Kong looks a lot older. He looks grizzled. Godzilla still has a pretty nice coat on him. But Kong is aged up. He's got gray hair. He looks like Kratos from the new God of War games. I'm liking the look. He's still got his battle axe. He's battle hungry. But he doesn't have much to do and he's depressed. And the humans know this because they're monitoring his vitals at the Monarch station. I had a big problem with Godzilla v Kong because the tone of that film wildly changed from the previous entries in the Monsterverse. It went from semi plausible and serious in Kong to just downright loony tunes in Godzilla v Kong. That shift was so completely radical and so was the technology. They went from driving jeeps and having regular surveillance equipment to suddenly having like futuristic flying machines that could tunnel through earth and in like speed through time and space. It was just nuts. And having that knowledge now going into Godzilla x Kong. It's an easier pill to swallow. I now know that these movies are not serious in the slightest.  And that's alright. I had a lot of fun with this film. I said that much in the review. I actually had a really good time.  I'm excited to watch it again with my family when it comes home to stream. Okay. Kong's depressed. Godzilla meanwhile is chilling up top literally sleeping through most of this movie. Once in a while he wakes up stretches out the scales and kills another giant monster because they've been kind of unearthed or disturbed because of hollow earth and they're popping up once in a while. Godzilla kills them. He also kills thousands, tens of thousands of people every time he just gets up and walks and lumbers around. It's like 20,000 people dead and monarchs like ehhh. Just let him cook. Let Godzilla cook. And then the chef goes back to sleep. Honestly, I think I saw Godzilla as like eight minutes of screen time in this film. He's really underutilized and it's a bit disingenuous to call this Godzilla x Kong. Kong should have the titular spot. It should be Kong x Godzilla in small or Kong featuring Godzilla because this is very much a King Kong movie. And it's really more a Planet of the Apes movie overall and I dig the Planet of the Apes film so this was right up my alley McBeal. He is on hollow earth and he runs into a bunch of bad eggs. These bad gorillas come out of nowhere. He starts fighting them. It gets messy and eventually just chucks one to its death which was awesome.  I tried to be nice.  You're dead. Baby Kong comes along. This little baby ape. Cute as a button. I'm sure they're gonna sell merchandise off of it. You have to. God have that synergy.  I don't trust apes because there's like a slave camp, internment camp down even further into hollow earth. Hollower earth or maybe hollow back earth. We could call it like a Gwen Stefani reference.  Few times I've been around that track but this is where it goes full blown despicable me. Kong gets led to hollow back earth. That's what I'm calling it now. And there's this evil gorilla there. He's introduced to the Scar King who straight up looks like a cartoon villain from one of the Minions movies. He has a bone sash over him. Really elongated weird body physique.  Really not threatening at all, but it's a fun character regardless. I was hoping for more of a Coba type of character from Planet of the Apes. I believe it was the second one. Rise or, no, Dawn. Dawn of the Planet.  It's Dawn of the Planet of the Apes. Anyway, Scar King has himself quite the project going on. They're surrounded by magma and he's got, he's got the apes just, he's like Dr. Evil. He's got the apes arbitrarily moving rocks around. I have no idea what the hell they're doing down there. He's just got a whole crew of guys basically going back and forth doing this back breaking work picking up rocks. What's the end game here? It just doesn't make any sense. But maybe rocks are their currency and he's selling them on the black hollow earth moa. And he's selling, and he's selling these rocks on the hollow back market. I don't, I don't really know what's happening in this film. It doesn't matter. Bottom line is he's bad. Kong's here. He's going to disrupt the process and things seem to be going all right.  But we find out that it's actually controlling another Godzilla creature who's been lying dormant in the rock. The internet tells me its name is Shimu or Shimu. Listen, this is not my bread and butter.  Shimu is what I'm going with. It's basically an ice version of Godzilla that walks on all fours like a little puppy dog thing.  It's not, something's wrong. Something's a bit off with Shimu. Okay, maybe he took the helmet off a little too early at birth and it didn't form right on the skull. I don't know what's going on, but it's a pretty cool creature. Kind of a neat creation. He shoots ice and he's going to shoot ice at Kong who's going to block it, but it's going to go right through that hand up the arm giving him frostbite which is killing him. Yeah, our boy Kong has had a bad day already because earlier that morning he was back up on earth getting the tooth fixed. One of his teeth had become infected. I don't know why old age, who knows what's happening with him and his body, but he goes back up to shore. Monarch's there like, what in the hell is this guy doing? And then an in comes trapper.  That's no problem.  The tooth fixing scene is about 45 seconds long. He gets on the side of the plane, drops down via large comical hook, hooks it in, points up, he zips back up like he's in around a fortnight and they rip that sucker off. He puts the new one in with some device. The whole thing's done lickety split. I could not believe it. A scene like that in any normal movie, any realistic film would have been a 45 minute sequence. How are we going to get this tooth out? How are we going to possibly come up with the technology to remove a giant ape tooth and replace it with some silicone thing? No, it's all ready. They already did it. They had it done in like a cup of coffee. It's just insane. This whole movie is like that. Later on, Trapper has to leave to get the Calvary. He's like, oh, I'll be right back. I have a crazy idea. He runs away. Like 10 minutes later, he's back with a platoon of fighter jets. What? Who is Trapper? Is Trapper real? Yeah, NPC. You can just warp away and come back later. It's bananas, which makes sense because it's an ape movie, so there should be bananas. What else? I'm all over the place. Again, it's really hard to remember heads or tails of this thing, especially with so many heads and so many Kaiju tails going on. Godzilla, when he finds out, when he catches wind, that Kong is back up on shore. His spider sense tingles. The pheromones are all wild. And so he makes a beeline to Kong. Even though Kong goes back to Hollow Earth, it's enough to trigger Godzilla. But it turns out that's not what triggered Godzilla at all. It was actually a call down in Hollow Earth from a tribe of people. They set out a beacon, an SOS saying, help us. Help us, Godzilla. You're our only hope.   He's got to take out another Kaiju and absorb its power, and that makes him turn into Barbie Godzilla. He gets pink. He gets even more badass. And then he's going to go fight in the final battle with Kong. That's going to be the only time he really contributes to the actual storyline. The B plot going on with the humans is that Jia or Jaya, something like that, the deaf girl, she's actually getting that same distress signal from those tribes because they are long lost ancestors or something of hers. The part of the same tribe that lives in Hollow Earth. She's getting that message from them. And it's kind of like Sam Whitwicky and I think Transformers 2, whatever that dumb movie was called, New Moon Rises or Dark Side of the Moon, or Revenge of the Fall. That might have been Revenge of the Fall and it doesn't matter. Sam Whitwicky's getting all those like hieroglyphics and messages. He's writing them all down. That's what she's doing except for she's just scribbling trees or triangles. And they know that she's not crazy. They know that something's reaching out to her and she can communicate with Kong. So it's very likely she's picking up some other form of that language. And it turns out that's exactly what's happening. So she and her adopted mom Eileen, everyone's favorite character Eileen, they're going to head to Monarch and then go to Hollow Earth with a crack squad of people which include an out of shape Monarch soldier, wild card trapper, and token black guy Bernie who's a conspiracy theorist who really doesn't have a lot to offer but he's going with too because we got to fill out the roster somehow. That's the crew. That multi-billion dollar Monarch is entrusting with the well-being of Hollow Earth and you know, not causing the end of Earth as we know it. They're going to go in.  The crew gets into the ship. They take off down the ocean portal thing and they kick on a song. I forgot what the song is right now. It's a badass song, an oldie but a goodie. And right when it gets to the refrain, they cut the freaking thing. Like how do you not know the assignment? That's when this movie was really picking up speed and getting really fun and they cut the music. Now it's a bit of a foreshadow because the song does come back in its glory. They get the refrain out there later but I wanted it now damn it.  Moving past it, once they get to Hollow Earth there's really a lot of investigatory stuff that takes place with the crew. The main Monarch guy, the one Monarch soldier dies almost instantaneously by a plant tree, a pretty cheesy scene. It felt really kind of out of place because it's the only thing that kills anyone or is even a threat in this film. Unlike in the original Kong skull island where there's a ton of weird creatures and stuff just always threatening the humans, Hollow Earth really only had the tree monster that one time and nothing else ever again. You know what, now that I say that I don't think Trapper who I mentioned earlier brought back a platoon of people, he actually got those flying buzzard bird things. That's what he got. Either way it was just hilarious that he was able to do this so fast, get all the way back to his plane, find the creatures flying and then take them with him. This whole movie's nonsense. It's ludicrous and I had a great time with that. Eventually they will find this tribe and they are essentially the characters from Lost Season 4 or 5. They just have a donkey wheel thing that they turn and it moves their entire organization over to a different location. Very, very out there. But I thought this stuff looked pretty cool. CGI palaces. We find out that the thing she was scribbling were those three triangles. It's essentially their homes. And that's what they're going to find Kong.  And so yeah, Kong shows up. He just got the worst hand job ever and now he's going to need a second one from the heroes. Trapper conveniently mentions that Monarch has been working on essentially an Iron Man suit for Kong but they didn't get very far. They did get far enough though with the hand. It's so ridiculous. There's no foreshadow for this even. They just have this. So Trapper's like, give me 5 minutes and I'll go get the hand. He's like beep boop beep beep beep and then the hand flies to them and it lands perfectly on Kong's hand. Steams coming out and Kong goes Everybody's favorite character Eileen goes, I think he likes it. Because Kong is an intelligent creature, he knows he has no shot at 2B1ing this crew. He needs to even out the odds. So he once again has to go back to the surface to get his boy Godzilla. Thankfully there's portals just up in the sky. Portals everywhere. He just picks one pops up somewhere in Egypt I think and that just so happens to be where Godzilla is or at least he was close by because it took about 10 seconds for him to show up. This movie's awesome. They have a fight and I think Kong would have won. He bodied him pretty heavily.  They have a 2V2 showdown. Gravity is going all herky jerky so they're flying around in the air punching each other. Gamma radiation. But it wouldn't be a true Godzilla Kong movie if we didn't have some earthly destruction. So they all power shoot back up through one of those portals and we're on earth again for the third time for Kong. Scar's eating well. He's got that bone chain. He's ripping through buildings smashing stuff and this is again where we finally get to see some scale. Because a lot of this movie takes place at hollow earth with Kong and other apes you don't really get a sense of his size. That's where it really kind of feels like a plan to the apes movie.  He's a big guy but when you just see him the whole time in his earthly realm he doesn't look like much. He just looks like an ape with some cool armor chain thing. But yeah back on earth now they're causing tons of destruction. It's another awesome fight sequence and eventually of course Godzilla and Kong win the day. They pump fists, they brohog and they go their separate ways to my knowledge. I think Godzilla just goes and lays back down in the Colosseum in Rome. He just chills out there. That's his nesting ground and I think Kong goes back home. I really don't know. There is a touchy and little scene with a deaf girl because you know the ongoing plot is not only is she hearing from her own tribe but also that might be where she belongs and that makes fan favorite Eileen very sad scientist. Eileen's like hey I understand if you need to leave me and be with your own people and she turns to her new mom and says hey mom you are my people. I belong where you go I go. I love you and it was a nice little moment. It was very touching. The whole fight really turned a corner when they destroyed that crystal laser pointer and Shimo was no longer controlled by the evil ape. It's able to have a mind of its own again and go oh man where am I? What's happening?  Star King had no shot. He was taken down. Shimo went back to Hollow Earth with Kong.  As of editing the video this morning I realized they made a glaring omission. The only real spoiler to talk about in Godzilla X Kong is the one that I didn't talk about and that's that Mothra returns gloriously resurrected from the dead. I apologize for the crude nature of this interruption but I had to put it out there quickly. Essentially what happens is our favorite scientist Ilana, Elena, Isabella whatever it is I already forgot. She and Deaf Girl realize that they're part of a thing with the tribe. What's the word I'm looking for? A prophecy. I got there eventually. She's part of a prophecy which says in crude images and a little bit of hieroglyphics that this girl is going to be the one that brings back Mothra somehow by just being present touching the side of this protective shield barrier thing and then Mothra's reborn Phoenix rising again from the ashes. What's so funny is during this scientist lady is looking at the pictures and giving us this perfect history lesson of everything that took place based on the most like crude images that she finds. I thought it was hilarious and it goes on for quite a while. She's like and then this happened and then they locked away this and then and then She-Ra or She-Ma the the Ice Dragon comes back. Also by the way that Ice Dragon is female I also believe. I screwed up on that and said he a couple times. I apologize to the Godzilla community. Well what a disaster this has been. Okay I just wanted to point that out. Mothra returns. It flies around for a while. It's the one that connects Godzilla and Kong together. Makes them realize hey they're friends in this situation. They need to work as friends. Come together as one and take out this other threat and then that's what happens. I don't actually know what happens to Mothra at the end. If it just it cooks for a while then goes back into the kitchen later. I'm not sure. I think it's fine. I think it's fine. That's Godzilla X Kong. The new empire. The second movie this month to have empire in the title. The first being Ghostbusters Frozen Empire. Neither of them really contain an empire. If we're really gonna split hairs about it. But this movie also didn't feature a lot of Godzilla. When he was on though he was pretty awesome.  Let me know if you saw what your thoughts are if I really just did a bang of job reenacting and going through this movie.  Like the video please subscribe if you're new here. I post constantly reviews, roasts, rants, live streams. It's a good time. It's 24 seven movies. I also have a brand new second channel Adam does rants. I just fired up. I have one or two videos there as of recording this. Hopefully you join me. I'm just ranting about nonsense. Nothing political or religious. It's all very surface level, fun observational humor. Like not getting a straw in your bag at the drive-through or how disgusting public bathrooms can be. Just kind of things we can all agree with and have fun with. Hopefully I see you there as well. Take care.