#9623 closed enhancement (fixed)
interacts for high school level education
Reported by: | schilly | Owned by: | itolkov, jason |
---|---|---|---|
Priority: | major | Milestone: | sage-4.7.1 |
Component: | interact | Keywords: | |
Cc: | kcrisman, mhampton, robert.marik, rbeezer, jthurber | Merged in: | sage-4.7.1.alpha0 |
Authors: | Lauri Ruotsalainen, Harald Schilly, Robert Mařík, Marshall Hampton | Reviewers: | Jason Grout, Karl-Dieter Crisman, John Thurber, Marshall Hampton |
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description (last modified by )
Include the interacts listed here in $SAGE/devel/sage-main/sage/interacts/...
Apply:
Attachments (10)
Change History (62)
comment:1 Changed 12 years ago by
- Status changed from new to needs_work
comment:2 Changed 12 years ago by
- Cc kcrisman added
comment:3 Changed 12 years ago by
comment:4 Changed 12 years ago by
the "from the wiki" patch is meant to be applied on top of the "high school" patch to keep things separate for now.
Changed 12 years ago by
Changed 12 years ago by
comment:5 Changed 12 years ago by
- Status changed from needs_work to needs_review
- Summary changed from interacts for high school level to interacts for high school level education
I know that practice_differentiating_polynomials
is buggy and that a few more comments in the generated output of each example to explain what it is all about won't hurt, but I call it finished for now and I will not add more examples. Maybe a reviewer finds the bug or donates some additional words?
Changed 12 years ago by
comment:6 Changed 12 years ago by
I've added a short introduction and a pointer to these interacts in the reference manual. 9623-interact-examples.patch
combines both patches and the other ones can be removed.
comment:7 Changed 12 years ago by
- Cc mhampton added
comment:8 Changed 12 years ago by
- Cc robert.marik added
comment:9 follow-up: ↓ 10 Changed 12 years ago by
Thanks for nice patch, I'll look at it. First ideas: practice_differentiating_polynomials does not work as expected, so I think that it could be removed.
I think that it is better to enter limits from keyboard for trapezoidal and Simpson integration rather than input from slider. I also think that it is better to use html.table in Newton method and it is worth to include option which puts computation fot trapezoidal and Simposon integration in a table. Also newton_method and secant method should have similar input forms (presicion is negative power of ten in one of the interacts and positive in the other).
In the integrals, dx should be TeX-ed as \mathrm{d}x
I am collecting these ideas and include then in a reviewer patch which comes (hope) in few days.
comment:10 in reply to: ↑ 9 ; follow-up: ↓ 11 Changed 12 years ago by
Replying to robert.marik:
practice_differentiating_polynomials does not work as expected
I know, it's something odd about the state transitions and I just did not have enough patience ...
I think that it is better to enter limits from keyboard for trapezoidal and Simpson integration rather than input from slider.
Ok, well, I like the range slider better. It's a matter of taste but the reason for that is that I tried to make it as intuitive as possible and that includes using mouse handles than having to type in numbers.
I'm fine with your other comments.
comment:11 in reply to: ↑ 10 Changed 12 years ago by
Replying to schilly:
Ok, well, I like the range slider better.
On the other hand, with sliders you cannot integrate from 0 to 1. I changed the interacts for trapezoidal and simpson rule and they accept both input from slider and keyboard. I hope, this is intuitive enough.
I tested all interacts and give a positive review (removed practice_differentiating_polynomials which does not work as expected)
Added interact for bisection, since it is close to secant method and newton method.
Added interact for definition of Riemann integral, which is close to trapezoidal rule and Simpson formula, removed.
Fixed one deprecation warning. Added titles to (most) of the interacts. Added tables for computation related to Simpson and trapezoidal rule.
Positive review for 9623-interact-examples.patch! Thank you for the patch. I wonder if the layout parameter in interact can be used also with library_interact.
I included reviewer patch in 9623-interact-examples2.patch. Could you or someone else review my changes?
comment:12 Changed 12 years ago by
Btw: The interact for riemann integral is a part of work which has been supported by the grant 131/2010 of the FRVŠ
Known problem for trapezoidal and simpson integration: bad rendering of the computation if we integrate negative function: minus sign follows dot or plus sign.
comment:13 Changed 12 years ago by
Some comments:
- several typos and nicer latex symbols---see patch
interacts.library.cube_hemisphere()
-- the cube corners do not touch the hemisphere, so I'm confused what the picture is supposed to be.interacts.library.coin()
-- Again, I'm confused about what the picture should be. The code looks like it is plotting[(i,k/i) for i in num_points random numbers]
. I'm not sure what the y-axis is supposed to represent, given that there is no documentation.function_tool
-- you can have a button selected in each row, which looks really weird. This is a problem with interacts, and should be another ticket.
comment:14 Changed 12 years ago by
Try again:
Some comments:
- several typos and nicer latex symbols---see patch
interacts.library.cube_hemisphere()
-- the cube corners do not touch the hemisphere, as the docs indicate that they should
interacts.library.coin()
-- Again, I'm confused about what the picture should be. The code looks like it is plotting[(i,k/i) for i in num_points random numbers]
. I'm not sure what the y-axis is supposed to represent, given that there is no documentation. I think the fix is to add documentation
- (for another ticket)
function_tool
-- you can have a button selected in each row, which looks really weird. This is a problem with interacts, and should be another ticket.
comment:15 Changed 12 years ago by
Robert's changes look good. Can someone comment on points 2 and 3 in my list above?
comment:16 Changed 11 years ago by
- Cc rbeezer added
- Reviewers set to Jason Grout
Rather than let this bit-rot I would like to see it go in soon. There are endless tweaks and improvements that can be made to these but it would be nice to have this much included.
I removed the init.py and replaced it with an all.py that avoids importing everything in the library.py file, which leaves the autocompletion options of interacts much less cluttered.
comment:17 follow-up: ↓ 19 Changed 11 years ago by
Adding the original author! It only seems fair, even if she didn't commit a patch.
Also, did we ever get the issue about how these are doctested figured out?
Finally, there is at least one place where I see the word 'intergral' :) Though I wouldn't hold up positive review for that, since I am not formally reviewing (yet).
comment:18 Changed 11 years ago by
Karl, I did fix that spelling mistake. I'll continue to improve these until this is reviewed (but I would be happy if that was very soon!).
comment:19 in reply to: ↑ 17 Changed 11 years ago by
Agreed on the quick reviewing need. I wish I weren't looking at these things just for five minutes each time, but I haven't had a stretch of time for proper reviewing yet.
Also, did we ever get the issue about how these are doctested figured out?
I can't remember where this was, and searching for it online proves to be a nightmare of unrelated hits. I'm going to email Jason about this.
comment:20 follow-up: ↓ 23 Changed 11 years ago by
No, I don't think we ever had any conclusion about doctesting them.
comment:21 Changed 11 years ago by
- Cc jthurber added
- Milestone changed from sage-4.6.2 to sage-4.6.1
I've done a modest review, applying the patch, running tests on the sage/interacts, and looking at a few of the interacts in the notebook. So far, all is good.
Unless someone is doing it sooner, I'll run --testall --long tonight.
comment:22 Changed 11 years ago by
- Milestone changed from sage-4.6.1 to sage-4.6.2
comment:23 in reply to: ↑ 20 Changed 11 years ago by
Replying to jason:
No, I don't think we ever had any conclusion about doctesting them.
Okay, then I would say a prerequisite for positive review is opening a ticket for figuring out what to do about that. Do you (or anyone else) have any objections to incorporating this nonetheless? I think it's far more useful than whatever bitrot may occur in the interacts themselves over time, to be honest, and at least provides a nice place to put them all.
comment:24 Changed 11 years ago by
I've done the standard testing against the new release of 4.6.1, and all pass, but I'm inclined to step back and leave the status change to those of you who have been more involved with this one. I joined in because Marshall brought it up at bugdays, but some of you may have more vested in it.
Perhaps new tickets should be opened to address Jason's points about cube.hemisphere() and coin(). The hemisphere picture is disconcerting, adding documentation to coin() would be easy.
comment:25 Changed 11 years ago by
I'm fine with getting this in and opening up other tickets to address the small number of points I raised.
comment:26 follow-up: ↓ 27 Changed 11 years ago by
Actually, maybe the best thing to do is put the hemisphere and coin interacts on another ticket, and let everything else go in. That would be better than contributing interacts that clearly need work.
comment:27 in reply to: ↑ 26 Changed 11 years ago by
Replying to jason:
Actually, maybe the best thing to do is put the hemisphere and coin interacts on another ticket, and let everything else go in. That would be better than contributing interacts that clearly need work.
Okay, if someone else doesn't, I'll try to take care of that tonight. We certainly want the interacts in the library to be top-notch.
comment:28 follow-up: ↓ 29 Changed 11 years ago by
Getting rid of the hemisphere and coin interacts sounds good to me. I like the coin one, thought it was totally self-explanatory, but clearly I'm in the minority.
comment:29 in reply to: ↑ 28 Changed 11 years ago by
Replying to mhampton:
Getting rid of the hemisphere and coin interacts sounds good to me. I like the coin one, thought it was totally self-explanatory, but clearly I'm in the minority.
I agree in that I can think of only one interpretation for the y-axis. Explaining what it must be could be a good exercise when using it.
comment:30 follow-ups: ↓ 51 ↓ 52 Changed 11 years ago by
- Reviewers changed from Jason Grout to Jason Grout, Karl-Dieter Crisman, John Thurber
I am really glad I looked at these. In general, they are really nice, and ready for prime time - and SO much easier to use than sifting through the wiki!
But oh my goodness... SO many minor things that still had to be taken care of. I apologize for not creating a new diff - I had already started making the changes quite a bit when I realized I should have just made a reviewer patch. I tried to make the commit message maximally informative, though. There is already too much stuff on here to try to avoid the patch bomb; in retrospect, we should have added these a little more incrementally so as to avoid this situation.
So, very unfortunately, I must still ask for review on this. There are too many changes. BUT I feel like many of them are ones which would have impacted the professionalism pretty significantly. Read on.
Things I fixed:
- We needed to import
fast_callable
for the Julia set one, for whatever reason.
- I removed the hemisphere, tried to improve the wording of the coin as well as I could - it's a nice example, in fact.
- Many formatting things, $, ticks in doc, confusing wording, bad parenthesis in label of difference quotient, etc.
- Fixed bad thing in function tool where deprecation warning appeared because of
f(x*a)
-type stuff in the code.
- The two formulas on the Simpson one were on top of each other in Safari (not FF). Since the author used the equals sign incorrectly in any case, I added some words to clarify it was an approximation, and that fixed it. I think Safari may not like math without words between math (see below for another possible example). Same on trapezoid.
- In fact, the entire "Area" line in the trigonometry one was gone on Safari, probably because of
\text
, which I removed. Also note the triangle was calledA
, notABC
as it should have been.
PS - I love the fact you can sage -b while the notebook is still running. This would have been impossible otherwise.
Things I did not fix:
- Really annoying thing where using these seems to reset my worksheet every so often - I mean it just stops and returns me to the top. This could be because I had the worksheet open in FF and Safari at the same time. (?)
- Annoying thing that I could not access the documentation for an interact in the notebook once I had already viewed that particular interact. This might be a general interact bug.
- I could not easily figure out how to get this in the reference manual; I think I have to create a new directory and a .rst file that will somehow autogenerate, but I don't know how to do this (though I'm sure it's easy). The original patch of Harald's did not work for me.
- Polar prime spiral consistently complains about failing to evaluate the function at various points. I had no idea how to fix this, since there are so many functions I couldn't easily identify which one wasn't evaluating, though perhaps it's one of the parametric plots (makes most sense).
- Trig properties angle and circle and text ALL fail to format properly in Safari (not FF).
- The unit circle one should somehow have formatted
pi
, but I still don't know how to do that.
- Julia set thing doesn't zoom when you zoom, unless you zoom a lot. Instead it just cuts off the picture for the zoom area. Maybe it needs a simultaneous plot point uppage? Incidentally, this one could REALLY use an 'update' button.
- Julia and Mandelbrot ones look kind of sad compared to easy-to-download apps available nowadays, even at max plot points. I suppose this is the limit of what we can do with an interact of this kind.
- Some of these definitely need a teacher to interpret for someone who is brand new to things. That's not a bug, but worth pointing out, especially if there is a way to get these in the reference manual. For instance, the trig on a triangle one is a little weird, because you're putting points on a unit circle labeled by degree. Okay, but then there are still tick marks labeled on the axes! So we're sending a mixed - and weird - message with that. Not a game-stopper, but still somewhat rough.
- Quad. Eq. one stacks a little too close in the formatting even in the opening gambit.
- Some of the graphers need more flexible ranges. I'm not sure how to do this conceptually, though, since we have to hardcode something in with the interacts, and too big a range will make it too hard to zoom. I guess my point is these are not universal.
- Trapezoid and simpson didn't always immediately respond to the 'from keyboard' change. Maybe you have to click that first, before doing any keyboard changes, or it doesn't like it?
- To me, trig isn't calculus, but I'm not arguing that it can show up there, so I left that one in both calculus and geometry.
So tickets that should be opened after someone (please! unless I missed something) gives this positive review:
- Fixing the problem with buttons in multiple rows Jason mentioned.
- Putting the hemisphere plot back in, if we want to.
- Polar prime spiral plot point issue.
- Figure out how to get this in the manual
- Figuring out how to truly doctest them. For instance, there could at least be a search for deprecation warnings, or even random input typed... but at least more than just checking that an html block is formed.
comment:31 Changed 11 years ago by
Buildbot may apply only trac_9623-rebase-v3.patch if it so chooses.
comment:32 Changed 11 years ago by
- Description modified (diff)
Still applies to 4.6.2.alpha4. I'm tempted to give it positive review myself to avoid bitrot; if I wouldn't have had to rebase a fair amount, I would have just made a reviewer patch, but that was hard for me to do.
comment:33 follow-up: ↓ 34 Changed 11 years ago by
This still applies OK to sage-4.7.alpha2. My inclination is to let this in, with all its faults, and incrementally improve through more tickets. From that standpoint, not showing up in the reference manual might be a good thing in the short term.
comment:34 in reply to: ↑ 33 Changed 11 years ago by
Replying to mhampton:
This still applies OK to sage-4.7.alpha2. My inclination is to let this in, with all its faults, and incrementally improve through more tickets. From that standpoint, not showing up in the reference manual might be a good thing in the short term.
I just needed someone to review my changes - I agree totally! I just had to make the most needed changes, and there were enough that I didn't feel comfortable giving positive review.
So if you think it's fine, do positive review! Please feel free to open all these followup tickets too :)
comment:35 Changed 11 years ago by
- Status changed from needs_review to positive_review
OK. Lets do it then.
comment:36 Changed 11 years ago by
- Reviewers changed from Jason Grout, Karl-Dieter Crisman, John Thurber to Jason Grout, Karl-Dieter Crisman, John Thurber, Marshall Hampton
comment:37 Changed 11 years ago by
- Description modified (diff)
comment:38 Changed 11 years ago by
- Description modified (diff)
- Status changed from positive_review to needs_work
comment:39 Changed 11 years ago by
- Status changed from needs_work to needs_review
comment:40 follow-up: ↓ 41 Changed 11 years ago by
- Status changed from needs_review to needs_work
<rant>
This is an example of the kind of not-really-necessary thing that really delays tickets. When it was written, it was 2010!
</rant>
But now that you did it, I will have to say 'needs work'. Although Harald put it in writing, since Lauri Ruotsalainen is the one who came up with many of these in her thesis, it seems inappropriate to not put her in the author listing at the top where you added Harald. So at least something like based on work by ...
should be added there.
comment:41 in reply to: ↑ 40 Changed 11 years ago by
Replying to kcrisman:
This is an example of the kind of not-really-necessary thing that really delays tickets. When it was written, it was 2010!
Note that changing the year was only a trivial change, I made the headers compliant with the developers manual http://sagemath.org/doc/developer/conventions.html#headings-of-sage-library-code-files
comment:42 Changed 11 years ago by
- Milestone changed from sage-4.7 to sage-4.7.1
Anyone wants to fix this????
comment:43 Changed 11 years ago by
Yes, but it's just tedious enough (for me, because I'm very non-automated and still am a novice with queues) that it isn't as high a priority. Is there any way you can just merge the previous material and move the copyright patch, with the request to add Ruotsalainen, on another ticket? I feel like that would be much more productive, and actually rather easier for me (or someone else) to fix easily.
comment:44 Changed 11 years ago by
- Status changed from needs_work to needs_review
I updated the copyright patch to reflect the contributions of Lauri Ruotsalainen. I can change it if someone objects.
comment:45 Changed 11 years ago by
- Description modified (diff)
- Status changed from needs_review to positive_review
This seems reasonable enough; Harald did do the actual turning into a Sage file. Thanks, Marshall.
I assume that is positive review of Jeroen's changes, and I don't think such a trivial change (in terms of code) that Marshall just made needs other review. They aren't in the reference manual yet, so nothing needed there. Passes tests. Positive review!
comment:46 Changed 11 years ago by
- Merged in set to sage-4.7.1.alpha0
- Resolution set to fixed
- Status changed from positive_review to closed
comment:47 Changed 11 years ago by
A question for anyone who contributed to this ticket: the file library_cython.pyx
has this code in it:
cpdef cellular(rule, int N): ''' Cythonized helper function for the callular_automata fractal. Yields a matrix showing the evolution of a Wolfram's cellular automaton. Based on work by Pablo Angulo. http://wiki.sagemath.org/interact/misc#CellularAutomata INPUT: - `rule` -- determines how a cell's value is updated, depending on its neighbors - `N` -- number of iterations TESTS:: sage: from sage.interacts.library_cython import cellular sage: rule = [1, 0, 1, 0, 0, 1, 1, 0] sage: N = 3 sage: print cellular(rule, 3) '''
Note that the output from the last line of the doctest is missing. Since the docstring is enclosed in triple single quotes instead of triple double quotes, doctesting skipped this altogether. At #8708, there is a patch which will now run doctests within triple single quotes, in which case this file has one failure.
So the question is: what is the output supposed to be? When I run this command, I get
sage: print cellular(rule, 3) [[0 0 0 1 0 0 0] [0 0 0 1 0 0 0] [0 1 0 1 0 1 0]]
Is this right? I don't know what the mathematics here is trying to do, so I really have no idea...
comment:48 Changed 11 years ago by
There's also a typo - "callular" isn't an adjective I'm familiar with in Wolfram's work :) And N
is not actually used in the rule.
See this MathWorld site for the descriptions. The rule is given by binary, so this rule is 2+4+32+128=166
. It looks like there is in fact an error; I'm having a lot of trouble getting the rules to do what they should with things like rules 1 or 2.
Here's the problem:
for k in range(N-j, N+j+1):
instead of
for k in range(0,2*N):
as on the wiki. Someone thought they'd be smart and only update the cells that "need" updating... but that totally screws it up, as ALL cells might need updating if e.g. the rule has the final binary digit = 1.
I'm opening a ticket for this. Thanks a lot for catching this, John.
Finished porting most of the examples to the sage library. There are some remaining issues:
practice_differentiating_polynomials
- mixups with the states happentrigonometric_properties_triangle
andspecial_points
- drawing the items doesn't always work as it should.If there is somebody who sees the bug, please correct it ;)
Apart from that, they are now conveniently accessible via
interacts.calculus.[TAB]
,interacts.geometry.[TAB]
andinteracts.statistics.[TAB]
. Maybe I implement some additional ones from the wiki, too... (and it probably doesn't hurt to add a h2 header and some introduction text to each example)