Congratulations!
This reminds me that I need to work on my paper interface to the Sage Cell
Server. :)
On Wednesday, June 12, 2013 12:18:21 AM UTC+3, Dox wrote:
Great work! Congratulations!
--
You received this message because you are subscribed to the Google Groups
sage-combinat-devel
'Allo!
On Tuesday, March 26, 2013 1:34:32 PM UTC+3, Volker Braun wrote:
The group action framework is just the implementation, you still haven't
answered the question that this thread was about: Should permutation
actions on nested containers automatically discover one possible action or
are you going to do if
there is more than one possible action. You'll have to either use some
heuristics (take the simpler / less nested action) or raise some exception
telling the user to explicitly disambiguate between them.
On Monday, March 25, 2013 8:33:57 AM UTC+1, tom d wrote:
Hm
oops, here's the code! I keep getting server erros when trying to attach
as a file, so I'm just including the text of the code file below:
class GroupAction(Parent):
def __init__(self, G, S, phi):
#phi a group action G\times S \rightarrow S
self.phi=phi
self.G=G
Hm, wouldn't this just be a direct product of the individual group
actions? It seems to me that we're expecting the permutations to act
according to an 'obvious' group action. Should we also expect 'obvious'
actions of things like a dihedral group when given a 2-dimensional vector?
Probably
.
It should work now.
Ben, please pull from the sage-combinat server before you keep working on
your patch!
Best,
Anne
On 3/15/13 2:51 PM, tom d wrote:
From tonight's attempt to apply the queue in Sage 5.7rc0:
applying trac_4327-root_system_plot_refactor-nt.patch
I think Ticket #12940 is probably ready for review, at long last, if anyone
can find a bit of time to look it over. It's a combinatorial
implementation of the affine Weyl groups of types A,B,C,D and G.
http://trac.sagemath.org/sage_trac/ticket/12940
cheers!
--
You received this message
From tonight's attempt to apply the queue in Sage 5.7rc0:
applying trac_4327-root_system_plot_refactor-nt.patch
patching file sage/combinat/root_system/type_affine.py
Hunk #1 succeeded at 237 with fuzz 2 (offset -54 lines).
applying trac_14143-alcove-path-al.patch
applying
I think longest_element is fine; long_word indicates that there will be a
word returned instead of an element, which is maybe not what we're after
here.
Wiser minds than mine will have more knowledge of how to handle
deprecation, but here's an example from skew_partition.py:
sage:
Ok, thanks for the quick fix!
On Sunday, March 3, 2013 9:43:29 PM UTC+3, Nicolas M. Thiery wrote:
Hi Tom
On Sun, Mar 03, 2013 at 10:27:05AM -0800, tom d wrote:
Yup, just hit this myself, also with a missing plot module? here's
my
crash report:
44
Sorry, I was traveling and missed this.
The file name has been changed to 'affine_permtation.py' as recommended,
which should remove the headaches mentioned.
On Thursday, January 24, 2013 1:14:01 PM UTC+3, Andrew Mathas wrote:
On Thursday, 24 January 2013 20:31:36 UTC+11, Anne Schilling
Thanks! That did the trick. (And I've folded in your fix patch, Anne.)
On Tuesday, January 22, 2013 12:34:20 PM UTC+3, Anne Schilling wrote:
Hi!
In discussion with Christian Stump and Nicolas Thiery, I learned that the
way to fix a problem when sage remembers a wrong link (for example,
There's been a change to the init function for the Iwahori Hecke Algebra
that causes the NilCoxeterAlgebra to fail. I _think_ this is happening in
the affine_iwahori_hecke_algebras.patch; the nilcoxeter algebra is still
working fine with combinat unapplied.
There's an extra parameter
Ok, thanks; I'll just stick to working lower in the queue for now then.
On Saturday, January 19, 2013 3:28:20 PM UTC+3, tom d wrote:
There's been a change to the init function for the Iwahori Hecke Algebra
that causes the NilCoxeterAlgebra to fail. I _think_ this is happening
Hello!
The write-up looks good! I have a bunch of stuff planned for the coming
term incorporating Sage in Kenya and South Africa. Perhaps the line about
Africa could be expanded to something like: 'The open nature of the Sage
and Sage-Combinat projects encourages participation in developing
Hey, all!
Thanks for running this, Nicolas, and providing the detailed report!
For converting people to linux: I'm working with a computer lab in Maseno,
where we've now got linux dual-booting on all of the machines (about 40).
Over the last couple months, we've gained a number of linux
Hey, all;
So the Mombasa algebraic geometry workshop is set for 6-28 July, 2013.
Which is really long! They're interested in having some sage sessions; if
anyone's interested in coming out I can plan to be there for an overlapping
time and co-hosting the Sage sessions. (However, the first
It's looking like there's a good chance that I'll be able to come through!
On Friday, September 28, 2012 11:12:05 AM UTC+3, Nicolas M. Thiéry wrote:
Dear Sage / Sage-Combinat fans,
FPSAC (Formal Power Series and Algebraic Combinatorics) is the main
yearly international conference
Is there a way to (easily) check whether there are updates on the mercurial
server without popping all patches, reapplying, and rebuilding? With the
amount of cython in the queue, it's taking quite a while for sage to
rebuild itself after each check. I just want to check that there are no
:
On Tue, Oct 16, 2012 at 01:31:11AM -0700, tom d wrote:
Is there a way to (easily) check whether there are updates on the
mercurial
server without popping all patches, reapplying, and rebuilding?� With
the
amount of cython in the queue, it's taking quite a while for sage
This is probably a simple question, but here goes.
I'm working on a patch which contains a modification to the setup.py file,
in order to indicate that a new directory exists in Sage. I'm following
the instructions for exporting a patch on the mercurial howto, and it says
to move the patch to
Hey, all;
Christian asked for a way to get a permutation group without running
through the matrix representation. There's an object called the 'Numbers
Game' which essentially constructs the Coxeter Group from a coxeter graph
by tracking application of reflections to the simple roots. This
[x] standard package
(...sang the choir to itself)
On Jun 28, 1:57 pm, Franco Saliola sali...@gmail.com wrote:
On Tue, Jun 28, 2011 at 11:04 AM, Florent Hivert
florent.hiv...@univ-rouen.fr wrote:
Hi,
With Mike and Anne we are about to finalize an interface with lrcalc:
Ok, so long as it's understood, I'm happy to ignore it, too. I was
mainly concerned with making sure that old tests still worked with my
patched code.
On Jun 27, 12:26 am, Nicolas M. Thiery nicolas.thi...@u-psud.fr
wrote:
Hi Anne!
On Sun, Jun 26, 2011 at 07:18:16PM -0700, Anne
.
-tom
On May 15, 12:25 pm, Nicolas M. Thiery nicolas.thi...@u-psud.fr
wrote:
On Sun, May 15, 2011 at 03:29:41AM -0700, tom d wrote:
Yeah, so the failure's definitely happening in the check for version
guards. I added a couple print statements in the update script to try
to figure out
returning false. So the
question is whether the hg_all_guards output above looks sensible, or
whether it's funky somehow (like, say, those leading numerals).
Best,
-tom
On May 12, 9:21 am, Nicolas M. Thiery nicolas.thi...@u-psud.fr
wrote:
On Wed, May 11, 2011 at 11:09:55AM -0700, tom d wrote
Ah, the -v has to go before the update command; sorry.
Here's the (hopefully relevant) excerpt from the verbose update
command...
pre
patch queue now empty
Pulling the new version of the patches from the patch server
(cd .hg/patches ; /mnt/data/sage-4.6.2/sage -hg --config
pre
:/mnt/data/sage-4.6.2/devel/sage-combinat$ sage -hg qselect -s
guards in series file:
1 +4_1_2
2 -4_3_1
3 +4_3_1
1 -4_3_2
2 +4_3_2
2 +4_3_3
1 +4_3_3:
2 +4_3_4
1 -4_4
1 +4_4
2 +4_4_1
1 +4_4_2
1 +4_4_3
1 +4_4_4
2 -4_5
4 +4_5
3 -4_5_2
1 +4_5_2
1 +4_5_3
1
Here's information from 4.6.2. I don't remember whether it was binary
or source-built. The 4.7.1.rc2 that's having troubls was definitely
source-built, though.
Version output:
pre
:/mnt/data/sage-4.6.2$ sage -version
| Sage Version 4.6.2, Release Date: 2011-02-25 |
/pre
Hey, all;
I've been having trouble updating/installing combinat this last week.
I was hoping to (finally) finish up the stembridge patch, but updating
combinat has been uniformly failing. Anne said it was working fine
during Sage Days, so I'm rather confused.
I have two different machine, both
Hmm... Just tried that; the 4.7.rc2 install has no guards applied
(perhaps to be expected). I found this line in both the 4.7.rc2 and
the 4.6.2 output when I tried to update:
pre
patching file sage/categories/examples/posets.py
unable to find 'sage/categories/facade_sets.py' for patching
31 matches
Mail list logo
