search

PCCMathSAC / apex-mbx

Repository for a conversion of APEX Calculus to MathBook XML
2 stars 10 forks source link

First pass at images, fixed glaring errors. #77

Closed CVollet closed 7 years ago

CVollet commented 7 years ago

Did not fix periods inside math. Also, I left a lot of the implicit functions as sets of points. I think that is best. Alex, I left you some todos in terms of graph styling on a closed curve. Not sure if you want to create a style for these so that the arrow heads don't show but that the colors are consistent with the rest of the graphs.

Alex-Jordan commented 7 years ago

If I understand what you mean, then in a situation where no one ever will want arrows, you can go like \addplot+[-] and the - (no arrows) will be applied following the pgfplotscycle parameters and overrule the <->. I'll almost certainly catch these when I get here.

CVollet commented 7 years ago

Yes, exactly. I didn't know that would work. Do you still need the "smooth" when the plot is a set of points? Also, I probably set the sample

too high on some of the parametric plots to make it look smooth. Are you

parameterizing with respect to arc length to avoid that?

On Nov 13, 2016 5:03 PM, "Alex Jordan" notifications@github.com wrote:

If I understand what you mean, then in a situation where no one ever will want arrows, you can go like \addplot+[-] and the - (no arrows) will be applied following the pgfplotscycle parameters and overrule the <->. I'll almost certainly catch these when I get here.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PCCMathSAC/apex-mbx/pull/77#issuecomment-260227076, or mute the thread https://github.com/notifications/unsubscribe-auth/AGBt66Af2-EKRAyQk4Ai55hW2C-AwewRks5q97NRgaJpZM4Kw2zU .

Alex-Jordan commented 7 years ago

I think you would need smooth if you are making a curve by declaring coordinates. I did not put that in the default styles because it puts an extra burden on computation.

For plots that look angular because of samples, I try to use polar coordinates or hyperbolic coordinates first. Both systems are still centered at the origin, so maybe also shift. For example, to plot y=sqrt(x+3), I'd settle on polar coordinates, centered at (-2,0). So x=r*cos(t)-2. And solve for r in the equation r*sin(t)=sqrt(r*cos(t)+3) to get whatever you get, which I'll call r=f(t) here. Then I'd work it through without simplifying anything like:

\addplot+[...] ({x}, {sqrt(x+3)});
\addplot+[...] ({r*cos(t)-2}, {sqrt(r*cos(t)-2+3)});
\addplot+[...] ({f(t)*cos(t)-2}, {sqrt(f(t)*cos(t)-2+3)});

Then you can either change the variable to be t in the options or change the t's back to x's. And you need to replace t with deg(t) inside trig functions.

Would you like me to merge this PR? I can revise any image stuff when I catch up to you. Or you can change things in this PR. Or in another PR. If you want to merge this one, go ahead. I might be away form email a bit today.

Alex-Jordan commented 7 years ago

Oops. I screwed that up. "Solve for r in the equation r(sin(t))=sqrt(r*cos(t)-2+3)."

CVollet commented 7 years ago

Go ahead and merge it and catch anything you find on your pass. I'll look at that PR carefully to see what you end up changing. Maybe do the WebWork as a separate branch?

I think I only kept the smooth part where it was coordinates. I agree that we don't need it globally.

On Mon, Nov 14, 2016 at 8:44 AM, Alex Jordan notifications@github.com wrote:

Oops. I screwed that up. "Solve for r in the equation r(sin(t))=sqrt(r*cos(t)-2+3)."

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PCCMathSAC/apex-mbx/pull/77#issuecomment-260389388, or mute the thread https://github.com/notifications/unsubscribe-auth/AGBt6wDrrWOaHHcO6dwxC0_FwVMlRq0dks5q-JAIgaJpZM4Kw2zU .

Carly Vollet Mathematics Instructor Math Department Co-Chair Math Club Faculty Advisor PCC Cascade, SSB 321 971-722-5564

CVollet commented 7 years ago

I won't make any further edits on this section until you've had a chance to look at it.

On Mon, Nov 14, 2016 at 11:56 AM, Carly Vollet carly.vollet@pcc.edu wrote:

Go ahead and merge it and catch anything you find on your pass. I'll look at that PR carefully to see what you end up changing. Maybe do the WebWork as a separate branch?

I think I only kept the smooth part where it was coordinates. I agree that we don't need it globally.

On Mon, Nov 14, 2016 at 8:44 AM, Alex Jordan notifications@github.com wrote:

Oops. I screwed that up. "Solve for r in the equation r(sin(t))=sqrt(r*cos(t)-2+3)."

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PCCMathSAC/apex-mbx/pull/77#issuecomment-260389388, or mute the thread https://github.com/notifications/unsubscribe-auth/AGBt6wDrrWOaHHcO6dwxC0_FwVMlRq0dks5q-JAIgaJpZM4Kw2zU .

Carly Vollet Mathematics Instructor Math Department Co-Chair Math Club Faculty Advisor PCC Cascade, SSB 321 971-722-5564

Carly Vollet Mathematics Instructor Math Department Co-Chair Math Club Faculty Advisor PCC Cascade, SSB 321 971-722-5564

Alex-Jordan commented 7 years ago

OK. Even if I don't do WeBWorK stuff in a different branch, I'll do it on a separate commit for sure. You can view diffs from individual commits within a PR.