 it's basically selecting a shape of a signal, adding noise to it. And there's a detection algorithm, in this case, a fuzzy logic algorithm that is used to detect the original signal. And obviously they've increased noise. It becomes harder to detect the signal. Currently we are replicating this in Python. This is what the application front panel should look like. I also saved this image and dropdowns as expected. Now we have the actual HTML in the template folder. Some papers that the Chisholm-T plugin, this is playing called Scholar AI Bound time series prediction of driving motion scenarios using. You have to know about that. Interval type 2 fuzzy aggregation approach combining multiple neural networks, clustering prediction time series. It's a lot of robotics time series prediction and anomaly detection of the recurrence spiking. It works. Let's check if this links are legit at all. IE cheeto-torque is a legit website. It's a legit, yeah, it's a conference conference. Great, this is what Google Scholar gave. Yeah, obviously, forecasting financial time series. It's not quite the topic of my YouTube channel. I'm sure this will get a lot of views. Yeah, I'm interested in how they did the comparison between the two, how do they even measure performance? We can do it with past data. Let me just stick into prediction quickly. I have some template for the JavaScript. It's a bunch of errors. So we're already including plotly. Yes, it is a great tool. Thank you. Input graph, Alps graph. It's right, so the two of them. So let me make sure they actually, the noise output should be important. The noise. So the JavaScript should take this noise output and generate a waveform out of it. Should have a basic shape based on the input window. We're still kind of in a template stage. Yes, we are doing a flash application and an index HTML and a method that will be called using a post-HTML request called analyze and it will give you the result. We should have the data actually coming from the backend from Python getting elements from the HTML data output wave signal. Well, what we currently have doesn't work. So we might as well replace it. The error went away. This, by the way, not the EEG. This will be more basic stuff checked. Don't tell me we have 56 errors. This will be like a fake EEG. It's still time series data loading forever. I mean, later we can add the other shapes to it as well. That might be more EEG relevant like a spike. Can have an envelope of a spike or slow wave EEG. And this particular tool is using fuzzy logic to try and detect this signal currently. All right, we have to update this HTML because we actually need the charts in it. We're actually using GitHub co-piles, which might be a GPT-4, okay. No, I meant with the charts. We need the charts visible. We have charts and no. It's the ID output wave input wave. Now the input wave is already there. That's the dropdown menu. We actually need the chart as well. So we do have the input graph and output graph, but we don't see them. We added the input and output graphs and not display anything. How do we fix that? Plotly library is correctly imported. Yeah, Plotly library is loading forever. Don't know why. Check if the data is there. I suspect there's no data. Check noisy signal, update input graph, log noisy signal to console, generate signal is not defined. Never understand this main JS 42, 22, 42, 22. Which one is it? I'm not having that labeled by the linter. That's a template, isn't it? We need to replace this. Yeah, this should be a function. It's all templates so far. The error should go away. Get something wrong with the loading time. Where's the network? Now those errors are actually okay. Yeah, it's loading the Plotly. So we do have the data. Looks like it's overlaid on top of a sinusoid. Yeah, we can add noise. Just create and the output is not doing anything because we don't have that functionality yet. The CDN seem to be loading forever. Well, forever, it's eventually loading, but it's way too long. It's meant to be a mini version of it as well. The other problem is obviously the output. The output shouldn't be a selection. It definitely shouldn't be a drop-down menu. It should be an output, right? So let's change that. I mean, it could be an input only if we are training, but we are not training at the moment. And should we change it? Yes, label for output. Yeah, output data is not updated. Yeah, we need to update for output wave. So in HTML, we have that, okay. And in JavaScript, update output data. It won't work, but okay. Because we don't actually have the output data. We also don't need this constant. So the output should be displayed as text that won't work, would it? Output wave. Okay, we actually need the input waves to work properly. We're generating the functions in Python code or JavaScript. It's a key to generate a JavaScript. I wanna do as much as possible on the front end so my server is not overloaded. And we can add this sign so it's as well. The square bricks, one of the other triangle. Default is still, sign wave, case, left trapezoid. Some work square works and there is no output. Don't have those functions, do we? No, graph is updating. We have the noise, everything. It doesn't work, ends up being a sinusoid and there's no output. The analyze doesn't do anything anymore, does it? Yeah, that's just to mock up generate signal, add noise, analyze signal, calculate detection error, calculate the unknown percentage. That sounds much better, doesn't it? I couldn't shoot, just do it to begin with. I'm not dropping frames anymore in my stream, but JavaScript is loading forever. Put wave is empty. Detection error is always zero. Send unknown is always zero. It's like I want some displayed output wave detection error and unknown percentages for HTML. Check HTML control, output wave. You already have that. Detection, date output in JavaScript function. Do we have this function? It should be better. Makes sense. Having an error in JavaScript. 67. That's where the error is from. Yeah, those are just templates. Let's mark the actual code to calculate unknown percentage. It should be signal, noise signal should be input and output. It should be using fuzzy logic. Okay, write and code should do a fuzzy logic library. Yeah, this is not quite right, it's just an example. That's a good start to install this library. It's not noisy, it's getting 2.5. It's not noisy, it's getting something else. Yeah, we need to change. Yeah, so the one good thing about LabVIEW was not using it anymore. Mainly because of the cost of the license, because it had the toolkit for designing fuzzy logic, some of these embassy functions. Essentially it's taking out the features from the signal. One thing is for sure, output wave would predict, detect input wave, and the values should be the same. It simply returns the input wave. Yes, we do want to perform the fuzzy logic. No, that would not do it. Three issues with the labels should have left them as they were. So it's giving me the sinusoid, I don't know why. Yeah, we need to do the fuzzy rules at the moment, just template. Originally I think it was looking at three sensors, but this example is better because it's actually taking out the features. It's still having some technical issues with the tool itself. It's actually became worse. The output, this output wave should be a text, obviously. You gave a lot of errors. Let's clear this quickly. The length of symmetry versus 100. The problem with this array doesn't have a length in it. It's actually an error. Let's check it and see. It's a 464. Anyway, we'll have to troubleshoot it next time. I'll see you later. Bye.