-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Geometor Explorer #60
Comments
Hi Phi, thanks! I love Geometor, beautiful work. I'm in the middle of launching another project but I'd love to have a chat... If you want to send me some contact details via my Contact page ( http://www.davidedc.com/contact/ ) we could try to arrange a call or something. (P.S. The Root 3 B link doesn't seem to work at the moment) |
Thank you. I feel that I am just uncovering the beauty that is already there. These constructions are just the beginning of what I have been researching. There is so much more to demonstrate. I think it will amaze everyone. It is amazing me - that is why I am pretty much dedicating my life to this pursuit. I will send a separate email with contact info. I think an initial conversation would be great. All the best.
PS - I forgot to push the Root-3-b yesterday. It is there now. http://i-am-phi.net/geometor-explorer/root3-b.html |
sorry - getting used to github. |
I apologize if my terminology is not correct - I am fairly new to this vocabulary :) Line 12 is derived from points 39 & 44 (two highlighted points on circle 11 below) - which would make it parallel to Line 4. But the values are causing Line 12 and the related intersection points to occur in the wrong places. (But it does appear the y-intercept is in the correct place.) Line 4 has point 39:
point 44:
here is the rundown on Line 12
in SVG-utils.js, I started creating some check/validation functions This is very much a prototype. And I am kind of guessing on how to use Algebrite. But it all works up until the point values start getting a little complex. I have a near term goal to modularize the code and separate the algebra from the rest of the construction logic. I will try to document what I am actually doing in deriving the equations and points. |
from a high-level perspective, Algebrite should really aim at giving you always "correct" line-line and line-circle intercept(s). we'd need to see the actual steps used... from which of the two equations you isolate the first variable ("root" should always let you do that for degrees one and two so it should always work), how you substitute the obtained expression in the second equation, and then again how you "root" the second equation (to find either the x or the y of the intercepts). Then I guess you substitute back to obtain the other variable (again Algebrite should be fixed to always work there), then to plot the values you want numerical values out of the symbolical ones, and "float" should be fixed to always give you those (and I've dealt with bugs in "float" before, so your points might be somewhere but it could be "float"'s fault that they are not where they should be). So Algebrite should be fixed to always cover those steps. It's another issue altogether whether the symbolic expressions that one gets for these points are in "good enough" shape that you can then still find phi from those expressions (or ratios of distances between these points, etc.)... this could be more complex to tackle especially if along the way there are "unwieldy" surds in the denominators and nested surds... we'd need to see what ends up in those expressions... |
Closing this to clean up my issues. (If only it were that easy) Hope you are doing well. |
Greetings Davide -
First, I want to thank you for Algebrite. It is brilliant.
Second, I want to introduce you to a project I am developing which is leveraging Algebrite called the GEOMETOR Explorer - a browser-based graphics and animation engine for exploring classical constructive geometry and documenting instances of Golden Sections with algebraic proofs.
It's all on Github right here: https://github.com/i-am-phi/geometor-explorer
A fairly descriptive readme is developing in the project so I won't reproduce that here.
I am hoping to gain your interest at whatever level you desire. I see from your website that you are an artist as well as an engineer. I am an architect - not a mathematician - but also a solution developer. I think we would have some very interesting conversations.
Algebrite is working incredibly well - but it seems that some values are not simplifying correctly when the constructions get more complex. I have an additional file in the project - Root 3 B - where the last line (12) is getting munged from the points.
I am using ALgebrite to create line and circle equations from the points, then subtracting/substituting these equations from each other to determine the intersection points. Your insight on how to best approach this scenario would be tremendous.
I am preparing to host this on Geometor.com along with a tremendous amount of content I have been developing over the years.
I hope to hear from you.
The text was updated successfully, but these errors were encountered: