Hi Anne,
Is this related to k-shapes that we discussed a couple of years
ago at a conference in Montreal?
Yes ! How did you guess ?
The problem with allowing zeroes is that there may be several correct
answers:
for example with row=[0,0] and col=[0,0] the skew partitions:
Hi Florent,
the patch 8429 depends on many patches merged in 4.3.4.alpha1 already
(for instance 8418). Did you applied those first?
Maybe I should not guard by 4_3_4 the patches which 8429 depends on
Sébastien
2010/3/6 Florent Hivert florent.hiv...@univ-rouen.fr:
Dear Sébastien,
consider also the code in
sage: Permutation([6,2,3,1,7,5,4]).robinson_schensted()
which performs insertions (and more). Mike Hansen added it, it bisects
per row, and is thus be much faster for large partitions.
in any case there should really be a function called T.bump()!
paul
On Sat, Mar 6,
On Sat, Mar 6, 2010 at 5:32 PM, Paul-Olivier Dehaye
pauloliv...@gmail.comwrote:
consider also the code in
sage: Permutation([6,2,3,1,7,5,4]).robinson_schensted()
which performs insertions (and more). Mike Hansen added it, it bisects
per row, and is thus be much faster for large partitions.
On Sat, Mar 6, 2010 at 6:35 PM, Anne Schilling a...@math.ucdavis.eduwrote:
There's a generalization by Knuth (check Robinson-Schensted-Knuth
algorithm ) that uses insertion for non-permutations and bijectively maps
arbitrary matrices -- two-row arrays -- pairs of semistandard
tableau
On Sat, Mar 6, 2010 at 9:26 PM, bump b...@match.stanford.edu wrote:
On Mar 6, 3:52 pm, Pedro Sanchez pdsanc...@gmail.com wrote:
consider also the code in
There should actually be two versions of this. This version (as Anne
said)
relates nxn matrices with nonnegative integer values to
On Mar 5, 2010, at 6:33 PM, Minh Nguyen wrote:
Hi Dima,
On Sat, Mar 6, 2010 at 1:27 PM, Dima Pasechnik dimp...@gmail.com
wrote:
if it's PARI-dependent, it makes sense to upgrade PARI to the latest
version.
Perhaps upgrading Pari could be a goal for Sage 5.0?
It is:
I've heard that sage 3.4 was going to be something of an LTS, a
stable release. If so, it would be brilliant to include this one
with ubuntu, and then not produce another ubuntu package before the
next LTS. The custom with such repositories, even more so with debian,
is certainly not to get the
On Mar 5, 2010, at 12:23 AM, Simon King wrote:
Hi Robert!
On Mar 5, 12:42 am, Robert Bradshaw rober...@math.washington.edu
wrote:
[...]
As soon as anything is done with the object, it
does a *real* import, replaces itself in G with the real thing, and
since the reference from G is gone, the
On Mar 5, 2010, at 5:04 PM, Dr. David Kirkby wrote:
I just got a doc test failure on Solaris.
File /export/home/drkirkby/32/sage-4.3.4.alpha0/devel/sage/sage/
plot/colors.py, line 660:
sage: gold / pi + yellow * e
Expected:
RGB color (0.51829585732141792, 0.49333037605210095, 0.0)
The maintainers logic is clear they don't want to duplicate stuff. I can
appreciate that. I suggest we approach them, saying we understand this, and
that
in general it would be silly to include everything. If we then produce a long
list of packages which have needed to be patched, then it is
On Mar 6, 7:27 am, Dr. David Kirkby david.kir...@onetel.net wrote:
Kasper Peeters wrote:
Has anyone considered emailing the official maintainer
Tim Abbott tabb...@mit.edu
and ask him whether he would be interested in handing over
maintainership to someone with more time to bring the
On Mar 5, 2010, at 7:56 PM, Dr. David Kirkby wrote:
Nick Alexander wrote:
David is trying to argue that the goals for Sage-5.0 should be
* Official Solaris 10 support (all tests pass)
TARGET DATE: Sometime in March?
*instead* of the following:
* 90% doctest coverage score (=write about
Pat LeSmithe wrote:
As Jason said, the docstrings do indicate what model (simple, for now)
we're using to transform colors. We mention in several places in
colors.py docstrings that we reduce R, G, and B components modulo one.
But we could be more explicit.
Anyway, we could make it possible to
2010/3/6 Robert Bradshaw rober...@math.washington.edu:
On Mar 5, 2010, at 6:33 PM, Minh Nguyen wrote:
Hi Dima,
On Sat, Mar 6, 2010 at 1:27 PM, Dima Pasechnik dimp...@gmail.com wrote:
if it's PARI-dependent, it makes sense to upgrade PARI to the latest
version.
Perhaps upgrading Pari
Em 6 de março de 2010 13:29, Paulo César Pereira de Andrade
paulo.cesar.pereira.de.andr...@gmail.com escreveu:
2010/3/6 Robert Bradshaw rober...@math.washington.edu:
On Mar 5, 2010, at 6:33 PM, Minh Nguyen wrote:
Hi Dima,
On Sat, Mar 6, 2010 at 1:27 PM, Dima Pasechnik dimp...@gmail.com
On Mar 6, 2:57 am, Minh Nguyen nguyenmi...@gmail.com wrote:
Hi Uli
On Sat, Mar 6, 2010 at 5:33 AM, kuli strangequ...@gmx.at wrote:
SNIP
Secondly, I want to ask you, if it would make sense (I think it makes)
to develop a computational logic module for sage math. I'm thinking of
tools
On Mar 6, 1:49 am, Robert Bradshaw rober...@math.washington.edu
wrote:
We're talking about adding and scaling colors here--there arguably
isn't a right answer here, though we do want what we do to be good
and consistent, and it is documented what it does.
That is probably true, but
Minh,
I wonder how one can contribute changes/patches to files in sage/doc/
en/constructions
It's also not always clear who wrote what there, and thus seems hard
to discuss possible
improvements with authors.
Thanks,
Dima
On Mar 6, 1:08 am, Minh Nguyen nguyenmi...@gmail.com wrote:
Hi Dan,
On
On Mar 6, 9:59 am, Dima Pasechnik dimp...@gmail.com wrote:
well, this is trickier than you think.
E.g. Python 2.6 has not made it into Debian stable yet.
And installing Python 2.6 on Debian stable using the standard Debian
source package
installation mechanisms does not work.
Python is
It would be great if sage could have widgets like the ones wolphram
alpha has:
http://www.wolframalpha.com/downloads.html
I particularly like the one in:
http://phisycsandgnulinux.site11.com/
(I take this chance to invite you to my new website, if you know spanish...)
thank you!
Oscar
--
Hi,
Thanks everybody for all the discussion of sage-5.0 goals. I've made
a new sage-5.0 milestone
http://trac.sagemath.org/sage_trac/milestone/sage-5.0
and I've made a list of our goals. I set the release goal date at
June 1, 2010, which gives us a full 3 months to meet the given goals.
Running the doctests on Solaris against 4.3.4.alpha0 I see this:
Expected:
Interact color selector labeled None, with default RGB color (0.5, 0.0,
1.0), widget 'colorpicker', and visible input box
Got:
Interact color selector labeled None, with default RGB color
(0.50196078431372548,
On 4 bře, 18:03, Florent Hivert florent.hiv...@univ-rouen.fr wrote:
Hi there,
Disclaimer: I'm not a debian user and my intend is not to launch a flame nor
to disregard the hard work that has been done to have a sage debian package.
Hi all,
I have three machines on Debian (notebook,
On Mar 6, 3:37 pm, ma...@mendelu.cz ma...@mendelu.cz wrote:
I think, it does not have too much sense to have Debian package. It
would be better to put compiled Debian binaries to sagemath.org
download page.
Cheers,
Robert Marik
I agree that compiling sage is not too difficult, and I
Robert Bradshaw wrote:
I think you're making a mountain out of a molehill here--it's fairly
obvious in both the code and documentation that we're looking at RGB
triples here. The last couple of bits are off, but they clearly don't
matter (until we have 150-bit color output, though one would
On 03/05/2010 11:16 PM, Pat LeSmithe wrote:
As Jason said, the docstrings do indicate what model (simple, for now)
we're using to transform colors. We mention in several places in
colors.py docstrings that we reduce R, G, and B components modulo one.
But we could be more explicit.
Anyway, we
I made a boo-boo and opened two tickets on the same topic.
#8461 can be closed as a duplicate of #8462. I know one would generally close
the later ticket, but I've already put a patch on the second ticket, showing the
results etc. It would seem more sensible to close #8461.
Since #8408 has
On Fri, Feb 26, 2010 at 10:46:15PM +0100, Florent hivert wrote:
Quick question: many types have methods one_element() and
zero_element() which are used a lot. For example, ZZ.one() and
ZZ.zero() are aliases for ZZ.one_element() and ZZ.zero_element(). Is
your intention to deprecate
Hello,
Another vote here for getting an old and/or broken version *out* of
Debian unstable/experimental. Seems kind of ridiculous to have a
version that old in what is commonly viewed as the 'cutting edge'
branch.
Just tossing out ideas here... if its too much of a PITA to keep sage
meshed with
On Sat, Mar 6, 2010 at 3:51 PM, memilanuk memila...@gmail.com wrote:
Hello,
Another vote here for getting an old and/or broken version *out* of
Debian unstable/experimental. Seems kind of ridiculous to have a
version that old in what is commonly viewed as the 'cutting edge'
branch.
Just
William Stein wrote:
Hi,
Thanks everybody for all the discussion of sage-5.0 goals. I've made
a new sage-5.0 milestone
http://trac.sagemath.org/sage_trac/milestone/sage-5.0
and I've made a list of our goals. I set the release goal date at
June 1, 2010, which gives us a full 3 months
On Sat, Mar 6, 2010 at 4:06 PM, Dr. David Kirkby
david.kir...@onetel.net wrote:
William Stein wrote:
Hi,
Thanks everybody for all the discussion of sage-5.0 goals. I've made
a new sage-5.0 milestone
http://trac.sagemath.org/sage_trac/milestone/sage-5.0
and I've made a list of our
I thought there was going to be a 4.4 stabilisation release, but if I create a
new trac ticket, I'm given the milestone options are 4.3.4 and 4.5 - there is no
4.4 choice.
IMHO, it would be good if the stabilisation release did go ahead, and *only*
bug-fixes were permitted. i.e. no new code
I recently stumbled over a bug in the pexpect module shipped with
Sage. It turns out that specifying the full path to a command doesn't
work; you get an UnboundLocalError exception. I've created a ticket
with an example:
http://trac.sagemath.org/sage_trac/ticket/8471
The question is, do we
On Mar 6, 2010, at 6:57 PM, Franco Saliola wrote:
I recently stumbled over a bug in the pexpect module shipped with
Sage. It turns out that specifying the full path to a command doesn't
work; you get an UnboundLocalError exception. I've created a ticket
with an example:
On Mar 6, 2010, at 4:50 PM, Dr. David Kirkby wrote:
I thought there was going to be a 4.4 stabilisation release, but if
I create a new trac ticket, I'm given the milestone options are
4.3.4 and 4.5 - there is no 4.4 choice.
IMHO, it would be good if the stabilisation release did go ahead,
On Mar 6, 2010, at 4:06 PM, Dr. David Kirkby wrote:
William Stein wrote:
Hi,
Thanks everybody for all the discussion of sage-5.0 goals. I've
made
a new sage-5.0 milestone
http://trac.sagemath.org/sage_trac/milestone/sage-5.0
and I've made a list of our goals. I set the release goal
On Mar 6, 2010, at 3:51 PM, memilanuk wrote:
Hello,
Another vote here for getting an old and/or broken version *out* of
Debian unstable/experimental. Seems kind of ridiculous to have a
version that old in what is commonly viewed as the 'cutting edge'
branch.
Just tossing out ideas here... if
On Mar 6, 7:58 pm, Robert Bradshaw rober...@math.washington.edu
wrote:
On Mar 6, 2010, at 4:06 PM, Dr. David Kirkby wrote:
[snip]
A 30-second skim through the list gives me the impression that there
are probably 3 or 4 issues total that are causing all of these
failures. Of course I
On Sat, Mar 6, 2010 at 7:40 PM, Robert Bradshaw
rober...@math.washington.edu wrote:
On Mar 6, 2010, at 6:57 PM, Franco Saliola wrote:
I recently stumbled over a bug in the pexpect module shipped with
Sage. It turns out that specifying the full path to a command doesn't
work; you get an
On Mar 6, 2010, at 9:22 PM, William Stein wrote:
On Sat, Mar 6, 2010 at 7:40 PM, Robert Bradshaw
rober...@math.washington.edu wrote:
On Mar 6, 2010, at 6:57 PM, Franco Saliola wrote:
I recently stumbled over a bug in the pexpect module shipped with
Sage. It turns out that specifying the full
On 7 bře, 01:05, William Stein wst...@gmail.com wrote:
It's not clear if it is PITA or not. As far as I can tell, nobody
lifted a finger to work on the Debian/Ubuntu packaging of Sage during
the last 6 months (or more). Nobody is working on it.
Just some ideas. I wonder if the following is
43 matches
Mail list logo
