[sage-devel] Re: integration algorithms

Le vendredi 3 mars 2017 23:20:42 UTC+1, rjf a écrit : > > If you were teaching calculus, at what point would you want > your students to take out a smartphone and do integrals? > > At least as soon as they are at level n+1 if integration is teached at level n. At level n, make 2 kinds of exam:

Re: [sage-devel] Hiding answers to non-trivial exercises in thematic tutorials

On Fri, 3 Mar 2017, Thierry wrote: that we should propose a solution or some hints. However, the solution should not be readable at the first look of the page, but still accessible by the user. Did we already have a discussion about this? HTML manual could have for example ALGORITHM-part

[sage-devel] Re: integration algorithms

Calculus classes today do not typically teach the Risch algorithm, in my experience. However, you shouldn't design calculus courses at most places based on experiences with MIT students. I think it is an interesting question about how much time we should spend teaching *how* to compute

[sage-devel] Re: integration algorithms

If you were teaching calculus, at what point would you want your students to take out a smartphone and do integrals? How much time would you allocate to teaching the syntax of the CAS, what to do with error messages, how to download the latest copy, etc.? And what benefit would this be to the

[sage-devel] Re: a 7(!) year old (Singular) overflow issue still holds

I asked in the Singular forum, how to change the exponent size for Singular: https://www.singular.uni-kl.de/forum/viewtopic.php?f=10=2576 Is it transparent for overflow detection? > I don't understand the question. My question is, does overflow detection work correcly with different exponent

Re: [sage-devel] Re: The end of our current R saga ? Reviews needed.

On 2017-03-03 15:27, Emmanuel Charpentier wrote: This set of tickets is up for review again since about two weeks. in Trac#21770 , Jeroen Demeyer is of the opinion of keeping curl (and probably pcre, but he doesn't say that) as optional packages "for a

Re: [sage-devel] Re: The end of our current R saga ? Reviews needed.

The time should be NOW, unless review exhibits some snags... -- Emmanuel Charpentier Le 3 mars 2017 17:04, "Jeroen Demeyer" a écrit : > On 2017-03-03 15:27, Emmanuel Charpentier wrote: > >> This set of tickets is up for review again since about two weeks. in >>

Re: [sage-devel] Re: How to provide answers to non-trivial exercises in thematic tutorials ?

Hi, On Fri, Mar 03, 2017 at 06:42:43AM -0800, Emmanuel Charpentier wrote: > Dear Thierry, > > If I understand you correctly, you'd like to see Sage documentation acting > a bit like courseware ? No, i just want to be able to propose exercises with hints or solutions in thematic tutorials. >

Re: [sage-devel] "replacement" optional packages

On Wed, Mar 1, 2017 at 8:52 AM, Jeroen Demeyer wrote: > I have been thinking about this too. My personal conclusion was that the > "type" enumeration (standard, optional, experimental, pip, script) is simply > too restricted and that we need additional metadata with more

[sage-devel] Re: Hiding answers to non-trivial exercises in thematic tutorials

Dear Thierry, If I understand you correctly, you'd like to see Sage documentation acting a bit like courseware ? If so, I think that this is a bit peripheral to Sage *Documentation* needs, where our primary goal should be to *enhance* information availability, not hinder it. However, it

[sage-devel] Re: The end of our current R saga ? Reviews needed.

This set of tickets is up for review again since about two weeks. in Trac#21770 , Jeroen Demeyer is of the opinion of keeping curl (and probably pcre, but he doesn't say that) as optional packages "for a while". This woulkd delay our already exceeding

[sage-devel] Hiding answers to non-trivial exercises in thematic tutorials

Hi, currently thematic tutorials are made of examples and straightforward application exercises. I would like to propose non-trivial exercises, so that we should propose a solution or some hints. However, the solution should not be readable at the first look of the page, but still accessible by