Zeruxe
With "flat disks" I suppose you mean the temporomandibular joints, those are like small cushions inside your jaw joint, just where your lower jaw meets your skull, you have one on each side.
It sits between the lower jawbone and the skull bone so they don't rub against each other, it sort of slides along the jaw when you open your mouth.
A real one isn't a flat blue plate of course, it's a pale rubbery pad that curves over the top of the jaw bone like a little cap.
I suppose I could of done a better visual demonstration and I will look into improving it when time allows it, thank you for pointing it out.
Base gemotery was derived from BodyParts3D, where the meshes were optimized.
Nerves and vesseles mostly follow data from Z-Anatomy
Internal tooth anatomy was modeled inside the actual tooth rather than coming from one complete premade GLTF
Three.js loads and renders those GLBs and handles interactions,materials,camera controls etc.
Hope this makes sense, if you want to know more there are proper sources of assets on the repo :)
But it is too much if that makes sense, it's hard to fit in so much stuff in one little web app, so it ends up just being a cool visualizer but not so good educating tool.
The base anatomy comes from BodyParts3D, an open anatomical dataset from DBCLS which is openly licensed under CC BY-SA 2.1 Japan.
The tooth internals were modeled to fit the actual teeth so it’s a mix of open anatomical data, processing, and additional modeling.
The 3D models you see are rendered in a javascript framework called three.js, an awesome framework if I may say.
Thank you again for the kind words!
The FDI numbering system can be confusing at first and I see how you could have mistaken it.
More than anything though, I do appreciate the change of tone, and I hope all these lurkers hating on AI were like you.
For what it's worth, I probably could have been less aggressive in my response too, the coffee explanation was funny.
Thank you for actually taking the time to look through the project properly.
I just don't understand the point of view where - "a clanker made it therefore it's trash", it's always the same people they lurk on reddit aswell.
Even in the case of putting something together manually, you are competing against people using AI and you will never match their production level or speed.
I mean the people who hold the highest priority say in this are the dentists/dental students, and so far all the feedback from those have been nothing but positive?
If you found somewhere in the UI that says 38, point it out and I’ll fix it. That is useful feedback.
The rest is just a long rant based on the assumption that using AI means I neither understand nor review what I build. You know nothing about my education, my engineering background, or how this project was developed.
Sounds like an old grump that is falling behind to AI.
AI helped with implementation. It did not do the research, architecture, product decisions, debugging, validation or review for me.
You can dislike AI assisted development. Saying I "built nothing" is just lazy.
Just to clarify the 3 days part though, that is the implementation period currently visible in the GitHub history. The research, planning and architecture work started roughly 2 weeks before that.
But I agree with the broader point. The useful part is whether the tool actually helps someone understand the anatomy better, and that is what I care most about improving now.
Thanks for the feedback about the bug I will look into that.
Also thanks for the suggestion and the compliment :)
I spent roughly 2 weeks researching the domain, figuring out the structure of the tool, planning the architecture and deciding how the different anatomical layers and interactions should work before the repo history you are looking at began.