> It's easy to go overboard with holding the user by the hand. We can assume
> that when things get _too_ slow for a user, he or she will start looking for
> a speedup, which they might find inside SageMath, or elsewhere. We give them
> the tools, we give them the documentation; how they use that
On Thu, Nov 19, 2015 at 10:34 AM, Stefan wrote:
> On Wednesday, November 18, 2015 at 2:12:43 PM UTC-6, Nathann Cohen wrote:
>>
>> Hello Jori,
>>
>> We should of course state such things as clearly as possible in the
>> doc, that's an mandatory step.
>>
>> In some cases,
Hello Jori,
We should of course state such things as clearly as possible in the
doc, that's an mandatory step.
In some cases, however, the users call functions without knowing
(subfunction of other things), or just won't look at the doc, or just
won't even profile the code (not everybody knows
Hello everybody,
I wondered if we could have "something" to give our users 'tips' they
might ignore, when they use Sage.
For instance when using graphs:
- installing 'bliss' makes .automorphism_group() run *much* faster
- installing 'igraph' makes flow computations *much* faster
- installing
On Wed, 18 Nov 2015, Nathann Cohen wrote:
In some cases, however, the users call functions without knowing
(subfunction of other things), or just won't look at the doc, or just
won't even profile the code (not everybody knows how) and 'just wait'.
True. But I can see no easy way to do it.
Hey Nathann,
This sounds like you should write a thematic tutorial "Graph
implementations and algorithms" (or whatever title you want).
Best,
Travis
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop
>This sounds like you should write a thematic tutorial "Graph
> implementations and algorithms" (or whatever title you want).
I do not believe that those who would benefit from a tip on an
optional packages would find and read that.
Nathann
--
You received this message because you are