Okay, thanks, Fernando. And we are sensitive. And so um, so this meeting, I think we are going to make a working meeting that will try to discuss the timing protocol for epic supplements. And it's many it has been circulated for the last half year, I hope that we make progress in the in the very recent time, so that we could formulate or we can condense this idea into consensus, consensus and making to the defense documenter for the data acquisition system. And so can be useful for both the premier design review and also also also in the coming TDR and sinfully sense to William Cooper, who put a lot of work on designing the innovation in some of the specifications on the timing protocol, which we'll discuss today, as well as carrying out to the actual text of the of the proposal hardware, close energy of service, close hardware, so William Wilkie presentation today. Meanwhile, earlier this week, we also had a StreamReader, the working group meeting that found the offline point of view about how invasion, offline possession coupled timeframe data, I think it's also closely related to our working group, and instance where as a data source, as well as it relates to to Williams talk. So I think that, let's try to so let's do a one slide summary from Tuesday's meeting, before I handed the microphone to William. And so let me quickly stop here. And so, so it's a coming from Tuesday's Oh, I screaming it out wasn't good meeting here is a link agenda. And meeting minutes is also posted, including everybody's contribution as well as the consensus. And I think the consensus, the consensus, and we'll be reflecting, at least in this meeting, what opening things that timeframe would look like, and how we process them, and could also contribute to us. So from from the beginning, that's where I have been crossing at 98.5 megahertz. And it's fun stream to stream without coming to be aware as if taking clock trigger after 98.5 megahertz and those and the record every event, you know crop trigger, right. So that's effectively how it's logically working to working to recover data. And we just do a CBO to aggressive suppression so that data can feed into the data contracts, and only about 5% colletion were actually clearly being passed imposing well actually contains a colletion data, and that well interacted with a dictator provides strikes and showers as well as most crossing wells does contain noise in the background, they are also going to produce a detailed interaction. And the farm to detect farm raid outerwear can be packaged as a hit particular defects or interactions into his as well as time slices in some which will be building to some subsystem for examples. SVG will have two to 10 microsecond time slices spilled into the Stroop window. And then from data validation, well further package them into timeframes and Adwaita. I think consensus it's about a two megahertz out two kiloHertz also in the room, that states as the data will be passed along to the offline for analysis. And discussion found that Tuesday meeting was that so from offline point of view, we actually have a preference now to align the timeframe lens, which is a lens of how a packet of data in the timeframe with respect to EIC beam rotation. That is because for example, when we go so time, pattern recognition, you know, timeframe, there could be a bias instance that at which crossing data, we start to pattern recognition and the witch crossing and, and the price is very small, but there's a prevalence is not allowed to align that buys potential bias waves or any bi EIC speeds date, which are related to the being rotation, which is about 12 microseconds for the whole beam to rotate the whole rounds. And in that case, a small loss efficiency at that level is not a problem. But we really do not want to introduce and extinguish the bias instance that wants to control the freedom of Paola assymetry, merriments sysmac Asante to below 10 to minus four, and we definitely want to about any correlation that could induce a systematical city in that case. So that's an offline Palmview. I'm sure that will be also discussed today from our side, which is read our point of view. Then the next part is even and keen. So, since we are basically marrying every every promising events and whether there is collusion or not, and as a basic primary event team in the author discussion prefer to be sick to look for both 64 Beta being collision clock, which basically 98.5 megahertz clock, and I believe later on the RSA Barbie have distributed us throughout the readout system. And so, you will be our exclusive event kings instance that you will be able to differentiate the average of the beam process. And the secondary team will be a tuple of run timeframe counter and also the beam calculating timeframe, which should also give our team a way to associate it with a particular remke rater for human consequences. Both for human use, and the Reconstruction were also generates a human encounter, like for example, my Helpouts collision events from a particular selection. Were also touch a tagging of human country. So, let me go to timecode on timecode, please, so feel free to raise hands and join the discussion at any time. Please,