 So, we have those couple of apps that we still need to get up and running. One of them is this Spectrogram EEG, using the same file, which is called Spectrogram. It just has that index html, let's start an info text, it's mentioning a labio, to get rid of labio. So, we have this description. Okay, we have this info, do we need to keep that? Maybe, maybe not. And we can get rid of it for now. Yeah, we won't have the play button. Right, let's keep the description to minimum. And what else do we need to do? First of all, we could just take, not this one, but the last working app, SpectroMD noise. Yeah, we can copy this one. We have the data, we need the data, and play its app. Close all for sec. All right, info text. Okay, so instead of this, let's run this quickly, just to see it's running okay. Okay, so that's what we have in development. And essentially what we want to do is replace the frequency spectrum by this spectrogram. Frequencies, spectrum, these frequencies, spectrogram. That's right, we have this HHR script and html, and the actual Python application, co-pilot. Yes, we want to replace, we should be doing it. It was actually called frequency spectrum, it's that second shot. It's actually called some sort of container. It's the second container. Up here anymore, can I change or replace frequency spectrum with a frequency spectrogram? You might have an option for it, but in the Python code, report more stuff, really have scipy signal, don't we? It creates spectrogram, but it's not an audio file. It is not specific to our app. I provide a course for it to facilitate it too. Yeah, that's the correct file. It's not an audio file. So we want a function here, using the same file. This is the one function to display g-spectrogram. Okay, now it's more specific. Do I need to plot show? No, I don't need to show anything in here. I want to show it in the html. It has to be an image to display the spectrum in the web page to be converted into the image. Yeah, how about plotly? We're already using plotly. Not sure if copilot is actually reading the files. It's giving me some sort of generic stuff. So what I want to do is have an option to turn this spectrum into a spectrogram and try to use github copilot for it. We have a mixed success, and spectrogram plot controls a output container. Yeah, we can pop it in. Yeah, spectrogram plot a plots wrapper. Now in JavaScript code to generate and display the spectrum, it will depend on the specifics of your github. I don't want it to write JSON file. So yeah, now it's getting more of the context. So actually, I had to tell it to explain the files before it started giving something more relevant. Let's go to see if you have a function, get the github. I'm pretty sure we have it. No, we do not. We have a function called get. I'll just read the code. Do you have access to the code in open devs? I get it. How it works sometimes. Okay, how do I share it? How do I share open devs with you? I want to finish with me by copying and pasting into our conversation. So how's it different from just using change of data? What's the point of copy pasting? Yeah, I should be just able to do stuff in here. Get data. If I do generate a spectrogram since thinking has two options, there should be a get, what's returning 400 just in case of error. What? We're already doing this. It's not being accessed. Yeah, I can just get it in here. So it's returned. Do we want to replace it or return both of them? I think we're run out of time. We'll continue in a bit. See you soon.