Hello,
Trying to use inversions for elements of Weyl groups, I found that it
exists, but does not work, and is badly documented and tested. In which
patch is this located ?
Frederic
sage: W=WeylGroup(['A',3])
sage: w=W.from_reduced_word([1,2,1])
sage: w.inversions()
AttributeError:
Here is a correct version. I am not currently able to post patches (still
working with 4.7.1 here..)
def inversions(self):
EXAMPLES::
sage: W = WeylGroup(['A',3])
sage: w = W.from_reduced_word([1,2,1])
sage: w.inversions()
[(0, 1, -1, 0, 0, 0), (1,
On Fri, Mar 23, 2012 at 03:37:11AM -0700, Frédéric Chapoton wrote:
Here is a correct version. I am not currently able to post patches (still
working with 4.7.1 here..)
I extracted the method from Mike's patch, and put it in
weyl_group_inversions-fc.patch. I wrote it as:
return [
*
* *
* Tbilisi Mathematical Journal
*
* Special Issue *
* Symbolic computation
It is easy to get the inversion set directly from any reduced word of the
Weyl group element.
If w = s_{i_l} ... s_{i_2} s_{i_1}
then the set of positive roots alpha such that w alpha is negative, is
\alpha_{i_1}, s_{i_1} \alpha_{i_2}, s_{i_1} s_{i_2} \alpha_{i_3},...
This produces right
I can do it.
Can I sneak in a few other things while I'm at it?
1. I want to have a version of bruhat_lower_covers
and bruhat_upper_covers which returns pairs
(weyl_group_element, coroot) where the coroot
tells you which reflection you used.
2. A method that, given a (co)root,
returns the
Nicolas,
1. I want to have a version of bruhat_lower_covers
and bruhat_upper_covers which returns pairs
(weyl_group_element, coroot) where the coroot
tells you which reflection you used.
Ok; then the output would probably be a dictionary
{root: group_element}
Why is this preferable
Just a remark.
The list of inversions, in my view, should preferably be a list of
reflections (which does not need the existence of roots and makes sense for
abstract Coxeter groups).
That is, for w=s_1...s_n, the list of right inversions is the list
s_n, s_n s_{n-1} s_n, ... ,
Andrew Ohana and I have created http://trac.sagemath.org/experimental/ as a
place to experiment with Trac Plugins (and eventually using a git
repository). Changes to tickets, attachments, etc can be made to either
the experimental or the normal trac server: they share the same database
and
On 3/23/12 2:40 AM, David Roe wrote:
So check out a new plugin that's enabled on experimental:
http://trac-hacks.org/wiki/DuplicateTicketSearchPlugin, which does a
search on existing tickets for duplicates when you type in the summary
for a new ticket you're creating. If people like it, we can
On 3/23/12 2:40 AM, David Roe wrote:
Andrew Ohana and I have created http://trac.sagemath.org/experimental/
I just tried creating a ticket and got this error:
ProgrammingError: column code_comment_relation does not exist LINE 1:
...ROM ticket_custom WHERE ticket = 12733 AND name =
Yeah, we're messing with Code Comments. Did you get that failure on
experimental, or on sage_trac?
David
On Fri, Mar 23, 2012 at 00:52, Jason Grout jason-s...@creativetrax.comwrote:
On 3/23/12 2:40 AM, David Roe wrote:
Andrew Ohana and I have created
On 3/23/12 4:01 AM, David Roe wrote:
Yeah, we're messing with Code Comments. Did you get that failure on
experimental, or on sage_trac?
Experimental. Apparently the issue was still created, though, as it
shows up.
Jason
--
To post to this group, send an email to
hopefully we fixed this, the plugin we were working with was written for svn
On Fri, Mar 23, 2012 at 01:01, David Roe r...@math.harvard.edu wrote:
Yeah, we're messing with Code Comments. Did you get that failure on
experimental, or on sage_trac?
David
On Fri, Mar 23, 2012 at 00:52, Jason
Cool. Things should be working now: you should be able to create a ticket
on experimental without getting the error.
David
On Fri, Mar 23, 2012 at 01:10, Jason Grout jason-s...@creativetrax.comwrote:
On 3/23/12 4:01 AM, David Roe wrote:
Yeah, we're messing with Code Comments. Did you get
Thanks a lot for your attention. I have tried to follow your suggestion but
again there are problems.
1. The result of ls -ld /dev/shm/ is:
drwxrwxrwt 2 root root 40 2012-03-23 16:57 /dev/shm/
2. I ran the python script (as ordinary user, not superuser) you suggested;
the response was:
On Mar 23, 1:06 am, rjf fate...@gmail.com wrote:
I assume the idea is to use selecting from menus/palettes, since that
is the
alternative to keyboard input in Mathematica.
I know of no evidence that this makes it easier (or faster) to input
long and
complicated expressions. Do you?
On 23 Mrz., 12:37, AD adphy2...@gmail.com wrote:
1. The result of ls -ld /dev/shm/ is:
drwxrwxrwt 2 root root 40 2012-03-23 16:57 /dev/shm/
That's strange, as the error message in your first post suggests it
wasn't writable (by ordinary users).
What does
$ mount | grep shm
give?
In case
Hello,
Stefane Fermigier pointed me to:
http://forge.scilab.org/index.php/p/sciscipy/page/Tutorial/
Anyone interested in building a Sage interface to Scilab based on
that? Basically all that would be needed is to make a (trivial) spkg
of sciscipy, and maybe wrap a bit the interface
On Thu, Mar 22, 2012 at 11:40:33PM -0700, David Roe wrote:
If you have suggestions for plugins to enable, suggest theme here. I've
scanned through http://trac-hacks.org/ for useful looking plugins and
listed them at http://wiki.sagemath.org/review2/Projects.
I have been dreaming for
Thanks for your detailed answer. However my problem is not yet solved. I
noticed that by using the command
sudo mount -v -o remount,rw /dev/shm
I got the desired result (so that response of mount | grep shm is tmpfs
on /dev/shm type tmpfs (rw)); unfortunately this modification goes away on
Le vendredi 23 mars, AD a écrit:
Thanks for your detailed answer. However my problem is not yet
solved. I noticed that by using the command
sudo mount -v -o remount,rw /dev/shm
I got the desired result (so that response of mount | grep shm is
tmpfs on /dev/shm type tmpfs (rw));
I have posted this question in ubuntu forum also and waiting for reply.
AD
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at
On 23 Mrz., 16:16, AD adphy2...@gmail.com wrote:
RuntimeError: Unable to start gap because the command 'gap -r -b -p -T -o
3900m /home/anupam/sage-4.8/data//extcode/gap/sage.g' failed.
This is one of the errors you get if the PExpect interfaces don't
work, i.e., /dev/pts is not (or improperly)
On 23 Mrz., 17:22, leif not.rea...@online.de wrote:
On 23 Mrz., 16:16, AD adphy2...@gmail.com wrote:
RuntimeError: Unable to start gap because the command 'gap -r -b -p -T -o
3900m /home/anupam/sage-4.8/data//extcode/gap/sage.g' failed.
This is one of the errors you get if the PExpect
Currently Sage ships only single-threaded Atlas libraries.
(i.e. no ptcblas and ptf77blas)
What is the reason behind this?
Over at sage-support there was a question about installing in Sage
a Python package that uses these libraries.
Thanks,
Dima
--
To post to this group, send an email to
On Friday, March 23, 2012, Dima Pasechnik dimp...@gmail.com wrote:
Currently Sage ships only single-threaded Atlas libraries.
(i.e. no ptcblas and ptf77blas)
What is the reason behind this?
Nobody got around to it. Seriously, that is the only reason. Back at sage
days 9, mabshoff and Clement
I tried to answer to the post of the arm port, but i am not sure why i
can't.
I am considering buying an asus eeepad transformer prime. So i would
like to compile sage on it. What are the changes that need to be done
to the source code to do it?. Is there somewhere a tarball with the
code
On 23 Mrz., 19:08, Dima Pasechnik dimp...@gmail.com wrote:
Currently Sage ships only single-threaded Atlas libraries.
(i.e. no ptcblas and ptf77blas)
I actually thought our ATLAS libs /were/ multithreaded, i.e. ATLAS did
automatically build multithreaded libs if POSIX threads are available.
Le vendredi 23 mars, mmarco a écrit:
I am considering buying an asus eeepad transformer prime. So i would
like to compile sage on it. What are the changes that need to be done
to the source code to do it?. Is there somewhere a tarball with the
code already adapted?
Does that run android or
On 2012-03-23, mmarco mma...@unizar.es wrote:
I tried to answer to the post of the arm port, but i am not sure why i
can't.
I am considering buying an asus eeepad transformer prime. So i would
like to compile sage on it. What are the changes that need to be done
to the source code to do it?.
Le vendredi 23 mars, Dima Pasechnik a écrit:
On 2012-03-23, mmarco mma...@unizar.es wrote:
I tried to answer to the post of the arm port, but i am not sure
why i can't.
I am considering buying an asus eeepad transformer prime. So i would
like to compile sage on it. What are the changes
Le vendredi 23 mars, Julien Puydt a écrit:
from the top of my head, you'll mostly need a newer flint (1.5.2)
Here is the trac ticket about the flint package:
http://trac.sagemath.org/sage_trac/ticket/10328
Snark on #sagemath
--
To post to this group, send an email to
So I'm trying to upgrade my beta7 to beta9. It didn't work and I'm
not sure how to interpret what happened:
~/sage-dev/devel/sage-main Starx$ ../../sage -upgrade
http://boxen.math.washington.edu/home/release/sage-5.0.beta9/sage-5.0.beta9/usg=AFQjCNFNueKjqvL-1BX7yv9vvQV1fbl3HQ
[1] 1793
Le jeudi 22 mars, Julien Puydt a écrit:
Le jeudi 22 mars, William Stein a écrit:
On Wed, Mar 21, 2012 at 7:34 PM, Julien Puydt
julien.pu...@laposte.net wrote:
Hi,
yesterday I noticed that there are many places in sage's sources
(I only checked in the sage spkg) where inclusions
On Friday, March 23, 2012 2:04:32 PM UTC-7, Starx wrote:
So I'm trying to upgrade my beta7 to beta9.
Upgrading from one beta release to another is not supported, so this is not
likely to work. (If you are curious about why, then search through
sage-devel for other threads on upgrading.)
On 23 Mrz., 22:04, Starx jst...@gmail.com wrote:
So I'm trying to upgrade my beta7 to beta9. It didn't work and I'm
not sure how to interpret what happened:
~/sage-dev/devel/sage-main Starx$ ../../sage
-upgradehttp://boxen.math.washington.edu/home/release/sage-5.0.beta9/sage-5.0...
[1]
On 23 Mrz., 22:25, leif not.rea...@online.de wrote:
Upgrading *from* devel releases to later releases (stable or devel,
doesn't matter) is currently consciously broken.
Cf. some recent thread here on basing releases on the previous *devel*
release.
See
Does that run android or a complete distribution?
It does run android, but i have read that it is possible to install
ubuntu in a chroot environment.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
On Friday, March 23, 2012 2:07:21 PM UTC-7, Snark wrote:
Le jeudi 22 mars, Julien Puydt a écrit:
Le jeudi 22 mars, William Stein a écrit:
On Wed, Mar 21, 2012 at 7:34 PM, Julien Puydt wrote:
Hi,
yesterday I noticed that there are many places in sage's sources
(I only
Le vendredi 23 mars, John H Palmieri a écrit:
I'm far from being a cython expert, but take a look at the log file
for the Sage library (SAGE_ROOT/spkg/logs/sage-...): there will be a
line (like yours):
python `which cython` --cplus --old-style-globals
--disable-function-redefinition
On 23 Mrz., 22:30, John H Palmieri jhpalmier...@gmail.com wrote:
On Friday, March 23, 2012 2:07:21 PM UTC-7, Snark wrote:
Le jeudi 22 mars, Julien Puydt a écrit:
Le jeudi 22 mars, William Stein a écrit:
On Wed, Mar 21, 2012 at 7:34 PM, Julien Puydt wrote:
Hi,
yesterday I
P.S.: What makes *me* wonder since years btw. is the bizarre python
`which cython` ... :-)
-leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group
On 2012-03-23 22:58, leif wrote:
P.S.: What makes *me* wonder since years btw. is the bizarre python
`which cython` ... :-)
Simply cython should work I guess...
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
On 23 Mrz., 23:18, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2012-03-23 22:58, leif wrote: P.S.: What makes *me* wonder since years
btw. is the bizarre python
`which cython` ... :-)
Simply cython should work I guess...
Yes, but this is too obvious. I must be missing something.
On 24 Mrz., 00:25, leif not.rea...@online.de wrote:
On 23 Mrz., 23:18, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2012-03-23 22:58, leif wrote: P.S.: What makes *me* wonder since years
btw. is the bizarre python
`which cython` ... :-)
Simply cython should work I guess...
Yes,
On Friday, March 23, 2012 4:39:02 PM UTC-7, leif wrote:
On 24 Mrz., 00:25, leif not.rea...@online.de wrote:
On 23 Mrz., 23:18, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2012-03-23 22:58, leif wrote: P.S.: What makes *me* wonder since
years btw. is the bizarre python
Is there a report that lists tickets needing work that I *attached a
patch to*?
These are now reports 84 and 85 (sorted by time and component respectively).
David
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Hello sage-devel,
(I sent this from my email a couple of hours ago but it hasn't appeared
on the list yet. I am trying again from within Google Groups.
Apologies if it ends up being a duplicate post.)
Schemes and their points are not yet properly embedded in the category
framework. One of
Elements are supposed to inherit from their category's element_class, but
this requirement is waived for elements that are implemented in Cython.
See the following snippet from
sage.structure.element.Element._test_category (line 495 of element.pyx):
# Tests that self inherits methods from
On 2012-03-23, Julien Puydt julien.pu...@laposte.net wrote:
Le vendredi 23 mars, Julien Puydt a écrit:
from the top of my head, you'll mostly need a newer flint (1.5.2)
Here is the trac ticket about the flint package:
http://trac.sagemath.org/sage_trac/ticket/10328
Please review it! It needs
On Saturday, March 24, 2012 5:04:32 AM UTC+8, Starx wrote:
So I'm trying to upgrade my beta7 to beta9. It didn't work and I'm
not sure how to interpret what happened:
~/sage-dev/devel/sage-main Starx$ ../../sage -upgrade
On Saturday, March 24, 2012 1:45:01 PM UTC+8, P Purkayastha wrote:
On Saturday, March 24, 2012 5:04:32 AM UTC+8, Starx wrote:
So I'm trying to upgrade my beta7 to beta9. It didn't work and I'm
not sure how to interpret what happened:
~/sage-dev/devel/sage-main Starx$ ../../sage
53 matches
Mail list logo
