Project Med

Fixed few issues (minor)

I fixed and tested a bunch of stuff until I asked Claude to fix one sizing issue, but instead it changed everything, which was a huge issue but I fixed it. Then the graphs (especially the mini ones) were super squashed so that had to be fixed too. The README is finally done because I added screenshots and acknowledgements. The UI looks great despite some issues.

Currently I finished the website overall but testing it has been a headache because it is not running and the screen is white… I tried to resolve this with Claude, Github Copilot, and EVEN Chatgpt but none of them could really figure out whats going on so I think it is because of my browsing system so I will need to figure something out. I also worked on my README and completed it ALMOST.

I built a good enough logo using Canva for my product and I also tested the product and found out that there was a LOT of errors and I am going to fix it now in upcoming recordings so STAY TUNED. Plus I added stimulated data for testing.

Claude also helped me a lot and so did Github Copilot: CSS Variables — I set up –primary and other custom variables at the top of the file so I can change one color in one place and have it update everywhere. No more hunting through 50 random lines.100vh — For the activation screen, I used min-height: 100vh so it always fills the full screen height. vh just means “viewport height,” so 100vh = the whole screen.em and rem — When I used em, it scales based on the parent’s font size (like 1em = same size, 1.5em = 1.5× bigger). rem is more predictable because it always uses the root font size instead of the parent.inline-block — I used inline-block for elements that needed to sit next to each other but still have proper width and height. It’s basically the middle ground between inline and block.Flexbox — I used flexbox to lay things out cleanly in rows or columns, like the stat cards and the nav tabs. Way easier than messing with floats.CSS classes for show/hide — Instead of writing display: none in JavaScript everywhere, I just toggled a .hidden class. CSS handles the hiding, JS just switches the class.Activation screen background color — I can change the activation screen’s background by setting background-color on #activation-screen or .overlay in the CSS. I can make it any color or even a gradient. THERE was a lot of errors when I was typing but that was fixed. A big thing is that I also used OneCompilor tool which helped me compile my code and test it before showing it to claude which approved or disapproved it and then I carried on from there.

You have covered topics such as the concept of the IIFE and how it must be enclosed, the distinction between null and 0, what exactly linearSlope, stdDev, classifyTrend and analyzeEntries do, and how Groq API relates to your application through the web browser via your API key. You spotted and corrected some bugs, including the issue with duplicate IDs, typographical error such as entried vs entries, and the discrepancy between escapeHtml and escapeHTML. You came up with your own designs of < 35 || > 42 for flagging temperatures and 40-180 for heart rate, as well as AI safety rules. Not bad for one session! I was a bit confused in a bunch of aspect but that’s fine because Claude and Github Copilot helped a lot and really changed my way of coding and it also taught me stuff like Standard Deviation and moreee.

I am working on the Html and JS part of my project and my goal is basically to make a medical device with hardware to help people with ai insights but currently I am doing the coding and trying to put stimulated data and more.