[X] No -- do not adopt the code of conduct stated below
Bruno
2014-11-24 2:26 GMT+01:00 Robert Dodier :
> On 2014-11-23, William Stein wrote:
>
> > [X] No -- do not adopt the code of conduct stated below
>
> best
>
> Robert Dodier
>
> --
> You received this message because you are subscribed to
> For example:
>
> - what is our commitment to free software ?
> - should we collaborate (fund, advertise,...) with closed proprietary
> software ?
> - how do we take decisions (equality, transparency, collaboration, taking
> care of minorities,...) ?
> - are there some reserved territories wit
On 2014-11-23, William Stein wrote:
> [X] No -- do not adopt the code of conduct stated below
best
Robert Dodier
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
t
Volker Braun wrote:
>
> How about making arb a standard package, we should probably think about
> that sooner or later anyways.
>
+1
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from
icc is a pretty garbage C++ compiler, unless you are doing exactly the type
of linear algebra operations that they optimise to death (on Intel
processors at least :) for benchmarketing.
On 23 November 2014 at 21:53, Thierry Dumont
wrote:
> Le 23/11/2014 20:53, Jeroen Demeyer a écrit :
>
>> On 20
Le 23/11/2014 20:53, Jeroen Demeyer a écrit :
On 2014-11-23 19:05, Thierry Dumont wrote:
Vtune shows, for example, that a call to std::copy is
not as fast as a for loop, which is turned by the compiler in a memcopy
(probably std::copy is not!).
If that's the case, get a better C++ compiler.
h
On 23 November 2014 at 20:41, Thierry Dumont
wrote:
> But what about the quick sort? is it sure that the implementation cannot
> degenerate? it is well known all the efficiency can be lost if the "key"
> used for partition is not chosen as it should be... What about replacing
> the quick sort by
Le samedi 22 novembre 2014 15:39:40 UTC+1, Nathann Cohen a écrit :
>
>
> > I got other examples, eg trying using graphs, and discovering than
> building
> > a 100x100 grid was surprisingly time consuming: I am afraid that it
> denotes
> > basic flaws in the definition of graphs in Sage.
>
> Don't
I'm seeing this behavior in sage 6.4, just built from git:
$ ./sage
┌┐
│ Sage Version 6.4, Release Date: 2014-11-14 │
│ Type "notebook()" for the browser-based notebook interface.│
│ Type "help()" f
On 2014-11-23 19:05, Thierry Dumont wrote:
Vtune shows, for example, that a call to std::copy is
not as fast as a for loop, which is turned by the compiler in a memcopy
(probably std::copy is not!).
If that's the case, get a better C++ compiler.
--
You received this message because you are subs
Le 23/11/2014 19:09, Nathann Cohen a écrit :
Hello !
What about likwid https://code.google.com/p/likwid ? It is free. Did
somebody used it to measure cython code performances?
Never tried vtune, nor likwid.
What is the size of what you are sorting ? If it is small enough to fit in
the cache
[X ] Yes -- adopt the code of conduct stated below (*)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this gr
> [X] Yes -- adopt the code of conduct stated below (*)
>
> [ ] No -- do not adopt the code of conduct stated below
>
~Ben
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send
Le 23/11/2014 19:07, Francesco Biscani a écrit :
On 23 November 2014 at 18:07, Volker Braun mailto:vbraun.n...@gmail.com>> wrote:
C++ std::sort will be able to inline the comparator.
Just look at the assembly code:-)
+1
std::sort() will do exactly what you describe, only in a type-safe
On 11/23/14 8:52 AM, John Cremona wrote:
> On 23 November 2014 at 11:26, Viviane Pons wrote:
>>
>>
>>>
>>> You ask about the value of a non-enforced code. I think it's valuable
>>> to have something to point to, both for setting expectations for new
>>> contributors and a reminder for long-timers
There's a sort.h library you should be able to include that will have quick
sort + many others, and will allow the compiler to properly inline
functions. https://github.com/swenson/sort (disclaimer: I wrote it). I get
about a 10x speed improvement over qsort just for the ability to inline
functions
> [X ] Yes -- adopt the code of conduct stated below (*)
>
Luca
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To p
On 23 November 2014 at 19:05, Thierry Dumont
wrote:
>
> Is gprof enough powerful with modern architectures on such programs? from
> my point of view, no.
> There are non free, commercial, tools like vtune which can do fantastic
> measurement job. Vtune shows, for example, that a call to std::copy
Hello !
> What about likwid https://code.google.com/p/likwid ? It is free. Did
> somebody used it to measure cython code performances?
Never tried vtune, nor likwid.
> What is the size of what you are sorting ? If it is small enough to fit in
> the caches, and better in the L1 cache, you can pos
On 23 November 2014 at 18:07, Volker Braun wrote:
>
> C++ std::sort will be able to inline the comparator.
>
+1
std::sort() will do exactly what you describe, only in a type-safe and
compiler-checked automatic way.
--
You received this message because you are subscribed to the Google Groups
"
Le 23/11/2014 18:07, Volker Braun a écrit :
Did you profile your code on the C-level? e.g. using gprof? As a rule of
thumb, guesses about where the bottleneck is are wrong :-) Its entirely
conceivable that branch prediction and speculative execution solve this
already for you.
Is gprof enough
Yo !
> Did you profile your code on the C-level? e.g. using gprof? As a rule of
> thumb, guesses about where the bottleneck is are wrong :-) Its entirely
> conceivable that branch prediction and speculative execution solve this
> already for you.
Yeees daddy :-P
I did that like a grown man w
Did you profile your code on the C-level? e.g. using gprof? As a rule of
thumb, guesses about where the bottleneck is are wrong :-) Its entirely
conceivable that branch prediction and speculative execution solve this
already for you.
C++ std::sort will be able to inline the comparator.
Link-t
[ X] Yes -- adopt the code of conduct
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email t
On 23 November 2014 at 11:26, Viviane Pons wrote:
>
>
>>
>> You ask about the value of a non-enforced code. I think it's valuable
>> to have something to point to, both for setting expectations for new
>> contributors and a reminder for long-timers when things get heated. It
>> allows one to succi
On Sun, Nov 23, 2014 at 8:33 AM, Nathann Cohen wrote:
> Hello everybody,
>
> I wrote a bruteforce Cython code recently (#17309) which spends most of its
> time on calls to qsort.
>
> This is normal, sorting is sort of the most expensive thing I do, but to
> call qsort you need to provide a compari
Hello everybody,
I wrote a bruteforce Cython code recently (#17309) which spends most of its
time on calls to qsort.
This is normal, sorting is sort of the most expensive thing I do, but to
call qsort you need to provide a comparison function. Now, as qsort is
compiled in a library, the compariso
[X] Yes -- adopt the code of conduct stated below (*)
On Sun, Nov 23, 2014 at 7:38 AM, John Foster wrote:
>
> On 11/22/2014 06:47 PM, William Stein wrote:
>
>>
>> [X] Yes -- adopt the code of conduct stated below (*)
>>
>> [ ] No -- do not adopt the code of conduct stated below
>>
>>
>>
> --
> J
On 11/22/2014 06:47 PM, William Stein wrote:
[X] Yes -- adopt the code of conduct stated below (*)
[ ] No -- do not adopt the code of conduct stated below
--
JOhn Foster
SAGE USER
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscr
[X ] Yes -- adopt the code of conduct stated below (*)
On Sun, Nov 23, 2014 at 3:38 PM, Nathann Cohen
wrote:
> [X] No -- do not adopt the code of conduct stated below
>>
>
> Nathann
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsu
>
> [X] No -- do not adopt the code of conduct stated below
>
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
Hi,
[X] No -- do not adopt the code of conduct stated below
I don't think that's really necessary. The usual netiquette covers
everything already!
Snark on #sagemath
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this gro
On Sunday, November 23, 2014 11:36:02 AM UTC, Jeroen Demeyer wrote:
>
> 1) Keep preparse() in Sage as it is.
> 2) Use IPython, which calls preparse(), to keep track of the relation
> between unpreparsed and preparsed source code.
> 3) Don't try to change the raw traceback (as returned by the Pyt
[X ] Yes -- adopt the code of conduct stated below (*)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this gr
On 2014-11-23 12:11, Volker Braun wrote:
Whoever puts stuff last in the line cache wins, obviously. IPython
obviously puts the current input there just before executing.
OK, for the first time in this thread I think I actually understand your
argument. Am I right that you're arguing:
1) Keep
> You ask about the value of a non-enforced code. I think it's valuable
> to have something to point to, both for setting expectations for new
> contributors and a reminder for long-timers when things get heated. It
> allows one to succinctly re-direct trolls rather than feed them. It
> gives furth
[X] Yes -- adopt the code of conduct stated below (*)
> Code of Conduct
> ---
>
> The Sage community is comprised of an international mixture of
> mathematicians, computer scientists, engineers, researchers, teachers,
> amateurs, and others with varied backgrounds. This diversity is o
On 23 November 2014 at 11:13, Volker Braun wrote:
> How about making arb a standard package, we should probably think about that
> sooner or later anyways.
+1
>
>
> On Sunday, November 23, 2014 6:51:09 AM UTC, Clemens Heuberger wrote:
>>
>> In #17194, (rather minimal) bindings for the optional pa
How about making arb a standard package, we should probably think about
that sooner or later anyways.
On Sunday, November 23, 2014 6:51:09 AM UTC, Clemens Heuberger wrote:
>
> In #17194, (rather minimal) bindings for the optional package Arb are
> provided.
>
> The module sage.rings.real_arb i
On Sunday, November 23, 2014 10:53:44 AM UTC, Jeroen Demeyer wrote:
>
> > Also, the commandline interface would then have to override IPython's
> > use of the linecache.
> I don't see why. You can have two libraries (Sage and IPython) both
> using the Python linecache library, why is that a prob
[X ] Yes -- adopt the code of conduct stated below (*)
On Sunday, November 23, 2014 1:48:16 AM UTC+1, William wrote:
>
> Hello Sage Developers,
>
> This is a simple majority vote for the original proposed code of
> conduct. I will close voting on Monday at midnight PST. (If the vote
> is an
On 2014-11-23 07:51, Clemens Heuberger wrote:
What's the recommended way to handle this?
Unfortunately, I don't think there is a way to handle that.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receivin
On 2014-11-22 22:53, Volker Braun wrote:
IPython is, at its core, a library to apply transformations to
sources
No, sage.misc.preparser.preparse() applies transformations, IPython just
calls that function.
and evaluate them
A one-liner in Python, no need for IPython here.
with easy-to-read
[X] Yes -- adopt the code of conduct stated below
Am Sonntag, 23. November 2014 01:48:16 UTC+1 schrieb William:
>
> Hello Sage Developers,
>
> This is a simple majority vote for the original proposed code of
> conduct. I will close voting on Monday at midnight PST. (If the vote
> is an exact
>
> [X ] Yes -- adopt the code of conduct stated below (*)
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to th
I think Robert makes a very important pint here which I would like to
highlight (as I must confess that I have stopped reading all of every
post in this thread...):
On 23 November 2014 at 06:59, Robert Bradshaw
wrote:
>
> You ask about the value of a non-enforced code. I think it's valuable
> to
[X] No -- do not adopt the code of conduct stated below
Regards,
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post
47 matches
Mail list logo
