 So we have that fuzzy logic tool, can select a waveform type, yeah later we'll try to have a scroller that just scrolls through them and those values change as you scroll, they do change when you adjust the input parameters. So yeah there was a misunderstanding, it was giving an array of extracted features, so essentially for each data point this input waveform will have a value for symmetry and sharpness, which is not correct, we need it for the whole waveform, so now it suggests that we should correct the code. So GPT-4 has a lot of the context, you can load all the code into it and it doesn't forget it, keeps the copilot seems to forget what just happened a couple seconds ago. So what we tried here is when the original GPT generated the code, we also asked to generate prompts for the changes in the last response, let's start the new GPT because it was going places there, it was wrong, so we're now replacing a calculate peak sharpness array and symmetry array into one value. So for example, we already took it from GPT, but just so it has the context, let's quickly do this again, it should essentially produce the same code, calculate waveform symmetry to assess the symmetry, it's dividing the whole waveform into two parts, it's the first half, second half, it makes more sense and left and right. This is a really good absolute value, it's a different calculation, so the original one is calculating mean, arithmetic mean and the second one will be a problem after this, yeah so those, yeah but we should just calculate symmetry, should not be an array, calculate sharpness, remove the waveform from there, okay now it's better, calculate sharpness, getting an error sign will be, yes, as if data is missing or invalid, okay, you probably need to do that, calculate sharpness, and also add the prompt to modify the logic function to use the new whole waveform symmetry and sharpness features, yeah this will give us a wrong output, we'll try it anyway, already have fine peaks, fine drops, I don't know why it's starting to regenerate the whole thing, to update the membership function, it can contribute to this as well, because co-pilot for the reason, trying to update the whole code, I don't know why, added more membership functions, those rules, the membership function, the 0 to 10 should correspond to the range of outputs for symmetry and sharpness, I think that is correct, what is the range of output for symmetry and sharpness calculations, it says it doesn't have access to the specific data or calculations, there's no doubt it should be in the code, it's expecting something more specific, having much like with co-pilot, that's actually suggesting to simplify the code to have only symmetry low and high, sharpness low and high, we have the rule, it's not the complete code obviously, now it's back to three levels, low, medium, high, the membership functions between 0 and 1, they are trapezoid, that's what I have in the code isn't it, yes, okay now just copy pasting from my code, from the earlier code, I have another rule for unknown, but sharpness, it's as if it's forget about the unknown, did I edit later, instead of edit it later, God looks more like it, I like this one, so let's modify the functions step by step, so we're already calculating global features, don't need to pull, actually called, don't have the waveform in the name, it's okay, they do take in the noisy signal, getting this information from this the noisy signal, okay, symmetry, I like what we have so far, but now the membership functions, it's suggesting to low and high, I have three, low, medium, high, let's stick to the low, medium, high, same, those are the membership functions, then you have a degree of membership, it's just sharpness, it's the fuzzy interpolate, interpolate, interpolation, symmetry universe, yeah that looks legit, then we have the fuzzy rules, so we have suggesting to have type A, so square has low symmetry, low sharpness, triangle has low symmetry, high sharpness, yeah there's a problem there, that's because we're not doing the medium stuff, we're sure we would need three levels, but and then this code is not complete because the rule types, a couple of issues, first of all, wouldn't three levels be better than two, so symmetry and sharpness have membership functions of low, medium and high instead of low and high alone, second issue, can you look at the code that provided and update the rule names, there should be rule square, rule triangle and rule trapezoid, a third problem is we need to include an option where the algorithm doesn't know what the waveform is and producing a unknown as an answer, didn't get the known, that's a good idea, okay, dating rule names, yes handling unknown, see using triangular membership functions again, okay the rule square, symmetry high, yeah that's incorrect, you know what happened there, it was producing an SS Python, then all of a sudden that's CSS, what, but it's the continuation, some threshold, instead of threshold, to define a threshold for unknown, we need to return the centroid as well, a couple of issues with it, but yeah, we have trouble integrating triangular membership, we have the rules, okay let's go over the rules again, square, yes symmetry should be high, sharpness low, medium and triangle sharpness high, symmetry low, then switch triangle, we're talking about currently getting a 500 response, okay sharpness high, trapezoid, yeah rule square, what it does, okay fake width, don't need that, that's adding zeros to make the length, to match length of the rays, where's the defuzzify let's do this here, I'll keep it centroid, meant to be, we have single quotes or double quotes, yeah there's still a problem, yeah we need to watch just the JavaScript as well, it's a noisy signal instead of signal isn't it, something I don't get in co-pilot, go JavaScript, how to modify this JavaScript code based on recent changes in the Python server backend, I need to modify the JavaScript to work with this Python code, are you kidding me, this is the Python backend, what, don't understand, okay the shit is hopeless, can you see the above JavaScript code that I provided earlier, based on the changes, the recent changes in Python code, do we need to modify anything in the JavaScript as well, yeah co-pilot is hopeless with code text, yeah this is all the same, the fuzzy data is now called something else, let's do these funny things now, where it's generating another response with how to win, what happened to chgpt, it's producing the code as text outside the Python window and then another window called bash, which doesn't make any sense, saving these super bold letters, yeah something is up, it's going down, let's see out the company again, we'll go down at some stage, so I'll see you next time, bye