Hi Sage-Combinat,
I get an attribute error when ploting a poset. I already created a
ticket for it :
http://trac.sagemath.org/sage_trac/ticket/12351
I know I should ask first but is this a duplicate ticket or known bug?
Cheers,
Sébastien
sage: m = WordMorphism('a-abb,b-ba')
sage: w =
Salut!
This spring, I am going to stay in Quebec : redaction of the thesis...
Note that we organize a Sage (Combinat) Days in May 7th - 11th 2012 in
Montreal. The official announcement will be made soon.
Sébastien
--
You received this message because you are subscribed to the Google Groups
Meanwhile, do you know a oneliner (simpler than the one above) that
draw 3d graphics object with aspect ratio 1, i.e. where cube looks
like cube?
BTW, I know this works :
sage: G = cube((10,5,3)) + cube((-7,-3,0))
sage: G.show(aspect_ratio=1)
but the problem is that this returns None and
This is now #11383.
I thought there was a category for beginners but could not find it.
http://trac.sagemath.org/sage_trac/ticket/11383
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Is this desired?
sage: Color('red') == Color('red')
False
Sébastien
--
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
I'm thinking about something like :ticket:`3412` or :trac:`2132`.
Any preferences or objections ?
I prefer trac. I don't know why.
Sébastien
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
1) When submitting a patch, make sure there is reasonable *commit
message* (use hg qrefresh -e to set the message).
or
hg qrefresh -m #: Commit message
to do it from the command line. I think if one does
hg qrefresh -e #: Commit message
it erases the patch and replaces it by the
That's not the trend I'd highlight in the code. Looks to me like
we're overdue for a surge in doctest coverage. Can we get up to 95%
in the next 3 releases?
Maybe we could fix an objective for each release instead of just
having the objective of 90% for sage-5.0. Is gaining 1% per release
Not to mention this may just be caused by a dilution of the undocumented
code. New code -- always documented -- is being added, so the undocumented
code disappear in proportion. Not in volume :-)
Right :
sage: (1 - 0.844) * 26816
4183.296
sage: (1 - 0.848) * 27200
4134.400
PS : Can somebody indicate me how to stop the y-axis at 100 without
losing the title ?
Can you post your code?
http://www.thales.math.uqam.ca/~labbes/Experimentations/coverage_evolution.py
One thought is that we really ought to use the matplotlib title
functionality. From the graph, it
Hi,
I'm going to still wait a few days before starting, so feel free to
pile on if you would like to add to the discussion.
At Sage Days 28, I gave a talk about how to contribute to Sage. The
philosophy I choose to present was to create one personnal branch
using queues for managing many
Hi Emil,
Well, here is how I interpret it. You tested the file sage/misc/
citation.pyx and one of the examples inside of that file failed.
Comparing what was expected and what you got, I think that there no
whitespace error : the results are really different.
Maybe the term whitespace error
Agreed - probably there is a way to link this tohttp://wiki.sagemath.org/Talks
I just added a link to it.
I'd also say that it would be good to show in thetalkhow to make an
alias for hg, which is assumed in thetalk(or that one has it
installed globally). Some developers will just have
Salut Pablo,
I dont know if it can help but this week I found this makefile which
helped me to understand how to call sphinx with which options :
devel/sage-main/doc/en/tutorial/Makefile
Sébastien
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this
Hi sage-devel,
I am more an more using .rst files for myself and I am thinking of
implementing new scripts that I think would be usefull. Below I
describe what are those commands. I still don't know exaclty how to
code them, so if you have any ideas, suggestions I'm interested.
==
Hi sage-devel,
I am actually reviewing ticket #8431 [1] and I have a problem with
building the documentation. I obtain the following error message :
/Users/slabbe/Applications/sage-4.5.3/devel/sage/doc/en/reference/
combinat/index.rst:4: (WARNING/2) toctree references unknown document
u'sage
Hi sage-devel,
According to http://wiki.sagemath.org/Workshops the upcoming Sage
workshops are :
* Sage Days 25 -- Mumbai, India (August 9-12, 2010); funded by India
* Sage Days 26 -- Kaiserslautern, Germany (August 27-31, 2010); funded
by Germany
But according to
Yes. The main intent of what I'm suggesting is that people who are
contributing a *lot* of code, but not doing any reviewing, will be
very, very strongly encouraged to do more reviewing.
If this is the main intent, then I would suggest something different
than a system that may lead to
Yes. The main intent of what I'm suggesting is that people who are
contributing a *lot* of code, but not doing any reviewing, will be
very, very strongly encouraged to do more reviewing.
If this is the main intent, then I would suggest something different
than a system that may lead to
Hi,
Im guessing the code to make the B[word: ] string
may have been in a python file that corresponded to one of the
Categories above but couldnt find it
The 'word: ' part comes from sage/combinat/words :
sage: Word(range(10))
word: 0123456789
sage: Word(lambda n:n)
word:
Hi,
Im guessing the code to make the B[word: ] string
may have been in a python file that corresponded to one of the
Categories above but couldnt find it
The 'word: ' part comes from sage/combinat/words :
sage: Word(range(10))
word: 0123456789
sage: Word(lambda n:n)
word:
Hi sage-devel,
If I want to draw a 3d point of size 100 in Sage, I do :
sage: point((2,3,4), size=100)
but for a 2d point, the argument is not the same :
sage: point((2,3), pointsize=100)
In the ticket #8599 (which needs review), I propose to change
``pointsize`` for ``size`` because I think
No objection. But you need to provide deprecation warnings before
removing any long used things in Sage.
For now, I use the rename_keyword(pointsize='size') so that both
works. I replaced every occurence of pointsize for size in the doc so
that people should forget soon about pointsize. Maybe a
Félicitations Minh!
I am grateful for all the work you did.
Sébastien Labbé
--
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
Félicitations Minh!
I am grateful for all the work you did.
Sébastien Labbé
--
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
That sounds exiting, are there also plans to implement discrete
fractals? (combinat.WordMorphisms and word-paths and things like
that?)
http://www.sagemath.org/doc/reference/sage/combinat/words/paths.html
http://alexis.monnerot-dumaine.neuf.fr/articles/fibonacci%20fractal.pdf
I just
That sounds exiting, are there also plans to implement discrete
fractals? (combinat.WordMorphisms and word-paths and things like
that?)
http://www.sagemath.org/doc/reference/sage/combinat/words/paths.html
http://alexis.monnerot-dumaine.neuf.fr/articles/fibonacci%20fractal.pdf
I just
to
http://sage.math.washington.edu/home/slabbe/days20/
Done. I uploaded the four sage worksheets + the one pdf.
Sébastien
--
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
Hi Sage-devel,
I am currently experiencing some problems when comparing elements of a
QuadraticField. See below.
sage: Q.sqrt3 = QuadraticField(3)
sage: 0 sqrt3
False
sage: RR(sqrt3)
1.73205080756888
The operator and do not correspond :
sage: sqrt3 Q.zero()
True
sage: Q.zero() sqrt3 #not
Hello sage-devel,
Just to make you know that I created a new page [1] on the sage wiki
to include animations (like .gif) made using sage. Indeed, the page
[2] was getting huge and was containing a mix of pictures and
animations. Then I moved four animations from [2] to [1] and added
link to
Is the following the intended behaviour?
sage: type(15.mod(4))
type 'sage.rings.integer.Integer'
sage: type(mod(15, 4).lift())
type 'sage.rings.integer.Integer'
sage: 15.mod(4) == 7
False
sage: mod(15, 4).lift() == 7
False
Sorry, I should have said what was the intended
This is the final alpha release of Sage 4.3.3. The next release would
be an rc0. The development version of Sage is now in feature freeze.
Does that mean only ticket solving a defect will be merged into sage
until sage-4.4.1?
The Sage days 20 are beginning on Monday. I think there will be a
I hope 4.3.3 can be out... tomorrow.
How about a Sage 4.3.3.final with #8295 released Sunday Pacific time?
Then one could produce Sage 4.3.4 incorporating changes from Sage Days
20.
+1
I will work twice as much this week to make more patches to be merged
in sage-4.3.4 !!!
Sébastien
--
Can you try sage -t -verbose?
Great. It worked. It was a syntax error in a doctest : a line ...:
after a one-liner while.
Thanks to both of you for the quick answer.
Sébastien
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an
I answered on the sage-combinat list just after the forward of Nicolas
Thiéry, so I am pasting my answer here on sage-devel.
Sébastien
2010/1/3 Sébastien Labbé sla...@gmail.com:
Hi Victor Miller,
I would like the following enhancements of graph drawing:
1) The ability to add an optional
-4.3$ make
[...]
making dataentry.d from dataentry.c
making devX11.d from devX11.c
making rotated.d from rotated.c
making rbitmap.d from rbitmap.c
make[6]: quittant le répertoire « /home/slabbe/sage-4.3/spkg/build/
r-2.9.2/src/src/modules/X11 »
make[6]: entrant dans le répertoire « /home/slabbe
Dear sage-devel,
Is there a reason why str are wrapped in \texttt for the latex output?
sage: latex('abcde')
\texttt{abcde}
Moreover, underscores are changed to \_ :
sage: latex('t_i=4^i')
\texttt{t\_i=4^i}
Personally, I don't like it and I wrote a patch that makes latex
behave like identity
I strongly disagree. For any object foo in Sage, latex(foo) is
supposed to produce a version of foo that is suitable for typesetting
within a mathematics environment. For a string, the right thing to
do is use texttt.
Ok, I understand. So maybe you have a different and better solution
for
Hi Florent,
One thing that I dislike in the current doc rendering is that the method are
reordered in alphabetical order.
I remember I read this question in sage-devel last summer and I just
found the link :
Hi,
To me, a year is FAR too short. Mathematica makes a major release about once
every two years, and a semi-major one every 6-12 months. There are plenty of
people using older versions of that. If Sage wants to make a viable
alternative
to Mathematica, it needs to keep deprecated
Well, the sage-devel google group editor broke the wrapping of my
lines, so that all my examples are incomprehensible... Sorry. To see
what I mean, type
sage: Partition??
sage: Partition?
sage: sage.graphs.graph?
in a 80-character wide terminal.
Sébastien
Hi,
On Oct 27, 12:37 am, John H Palmieri jhpalmier...@gmail.com wrote:
Trac ticket #6820 (http://trac.sagemath.org/sage_trac/ticket/6820)
makes the following change:
sage: help()
no longer runs the interactive Python help utility.
+1, but I personally would like help(MODULE) to still
Hi,
I hope people will
testhttp://uw.sagenb.org/! Please try it. Report any bugs at all
that you find.
I tested the %timeit option. It works when a space is added after
%timeit, but works like %time when no space is added :
---
%time
t = 9+0
Hi Dan,
Thanks for reporting these. Both of those things, I think, should work.
I will check on them and see if I can fix them. If possible, it would be
helpful if actual .tex files that showed those errors could be posted
somewhere or sent to me.
Dan
I just uploaded a new version of the
Hi,
My feeling is that adding the sentence
WARNING - DO NOT TRUST ANY RESULTS FROM THIS BUILD OF SAGE
to a prerelease but not for a stable Sage version evokes that we can
trust all the results from the stable one. But I'm sure there is still
one bug to be fixed even in a stable Sage version.
* I try to do some search in the sage-devel group from its own web page, but
it apparently finds only the very recent messages. For example, searching
Siena doesn't show me the message Franco wrote about the talk he gave in
University of Siena : Your search - Siena - did not match any
Bonjour Jaap,
This is now http://trac.sagemath.org/sage_trac/ticket/6593.
I will post a patch soon.
Seb
On Jul 22, 5:37 am, Jaap Spies j.sp...@hccnet.nl wrote:
John Cremona wrote:
Fresh builds of 4.1.1.alpha0:
64-bit linux:
The following tests failed:
sage -t
Hi,
This weekend I was introducing Sage to a friend. To illustrate Jmol, I
showed him some 3d Cayley graphs of some finite groups :
{{{
sage: S = SymmetricGroup(4)
sage: S.cayley_graph()
Digraph on 24 vertices
}}}
Then, he asked me to show the Cayley graph of some groups he often
works with :
Hi,
I just built sage-3.4.rc0 without problem this morning on Ubuntu 8.10.
I have 3 failed tests (the first one was already written above) :
$ uname -a
Linux slabbe-laptop 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC
2009 i686 GNU/Linux
File /home/slabbe/sage-3.4.rc0/devel/sage/doc/en
Hi!
I would like to know if the following is a bug or if I have to work
with it.
It is related to this conversation :
Finding a duplicated vector in a list of vectors
http://groups.google.com/group/sage-support/browse_thread/thread/714bd13c9b36f683#
Thank you,
Sébastien Labbé
*
Zdrazvitie Pavel,
Long-term goal is to work towards a general and consistent library of
formal language constructs, such as automata, grammars and so forth.
Recent merge of Words seems to be of support.
We are thinking of many new functionalities to add in the Words
library. Some of them are
51 matches
Mail list logo