On Wednesday, 26 March 2014 17:52:13 UTC-6, Ralf Hemmecke wrote:
>
> I have not personally used it (so I might be wrong), but I somehow feel
> that git-rerere might be of some help. As I understand, you basically
> want to see exactly what your merge resolution was.
>
> http://git-scm.com/blog/2
On Wednesday, 26 March 2014 17:49:18 UTC-6, Volker Braun wrote:
>
> At the end of the day only the combined diff matters, this is what is
> getting applied to the source tree. But of course there are a lot of tools
> to go log spelunking if you want to tease out who did what. You want the
> outp
I have not personally used it (so I might be wrong), but I somehow feel
that git-rerere might be of some help. As I understand, you basically
want to see exactly what your merge resolution was.
http://git-scm.com/blog/2010/03/08/rerere.html
Ralf
On 03/27/2014 12:31 AM, Andrey Novoseltsev wrote:
At the end of the day only the combined diff matters, this is what is
getting applied to the source tree. But of course there are a lot of tools
to go log spelunking if you want to tease out who did what. You want the
output of
git log -p --cc
and not the output of
git log -p -c
As always,
Hello,
I have just merged current "develop" into a branch abandoned half a year
ago (http://trac.sagemath.org/ticket/15240). I think I've resolved
conflicts correctly, but once everything is committed - how can I review
what exactly have I done during the merge? I.e. how can see just the hunks
You compute powers but *not* of the matrix itself ! You just compute
iteration of a single vector. Here is a rough implementation of what
you should do
sage: A = matrix([[1,2,3],[1,1,1],[1,0,1]])
sage: s = 0.
sage: v = random_vector(RDF,3)
sage: v /= v.norm()
sage: for i in xrange(100):
:
IIRC, the bottleneck to computing the spectra of large graphs is in
the construction of the adjacency matrix. I don't know why.
On Wed, Mar 26, 2014 at 3:28 PM, Paul Mercat wrote:
> Le mercredi 26 mars 2014 22:56:46 UTC+1, Dima Pasechnik a écrit :
>>
>> On 2014-03-26, Paul Mercat wrote:
>> >
>>
Le mercredi 26 mars 2014 22:56:46 UTC+1, Dima Pasechnik a écrit :
>
> On 2014-03-26, Paul Mercat > wrote:
> >
> >
> > Le mercredi 26 mars 2014 20:48:32 UTC+1, Dima Pasechnik a écrit :
> >>
> >> On 2014-03-26, Paul Mercat > wrote:
> >> > I need to compute charpoly of big sparse matrices obtain
On 2014-03-26, Paul Mercat wrote:
>
>
> Le mercredi 26 mars 2014 20:48:32 UTC+1, Dima Pasechnik a écrit :
>>
>> On 2014-03-26, Paul Mercat > wrote:
>> > I need to compute charpoly of big sparse matrices obtained in sage, but
>> > there is no efficient algorithm in sage for the moment.
>> > So I
On 2014-03-26, Julien Puydt wrote:
>
>
> Le 26/03/2014 12:28, Bill Hart a écrit :
>> Hi all,
>>
>> We still don't have any tuning code on ARM or Atom for MPIR. Note MPIR will
>> run extremely slowly without new tuning values due to recent changes.
>>
>> Please let us know on the mpir-devel list if
Le mercredi 26 mars 2014 20:48:32 UTC+1, Dima Pasechnik a écrit :
>
> On 2014-03-26, Paul Mercat > wrote:
> > I need to compute charpoly of big sparse matrices obtained in sage, but
> > there is no efficient algorithm in sage for the moment.
> > So I would like to implement it and add it to sa
On 2014-03-26, Daniel Krenn wrote:
> Am 2014-03-26 15:28, schrieb Volker Braun:
>> I'm aware that git hardcodes paths in its templates. IMHO we shouldn't
>> allow moving the directory around except in binary packages. And the
>> latter doesn't need git or the dev scripts, so it should not be inclu
On 2014-03-26, Paul Mercat wrote:
> I need to compute charpoly of big sparse matrices obtained in sage, but
> there is no efficient algorithm in sage for the moment.
> So I would like to implement it and add it to sage.
> I think it already exists in gp or in linbox, but I was not able to use it
I had to reinstall Xcode after moving to Mavericks, but after that I
compiled sage without problems.
I recommend to upgrade to Mavericks from Lion.
Paul
Le vendredi 21 mars 2014 05:51:56 UTC+1, Andrew a écrit :
>
> As far as I can see sage is compiling and running on mavericks. From those
> who
Le 26/03/2014 12:28, Bill Hart a écrit :
Hi all,
We still don't have any tuning code on ARM or Atom for MPIR. Note MPIR will
run extremely slowly without new tuning values due to recent changes.
Please let us know on the mpir-devel list if you are willing to help.
As far as we know, there ar
On 26 March 2014 17:15, Volker Braun wrote:
> There is this: http://sagemath.org/doc/developer/manual_git.html
Indeed, and that has what is needed, with only these issues: (1)
people don't find it; it does not look like what you need to start
doing anything at all, partly because (2) the title o
Not everything is in there !!!
* nothing about the develop branch
* nothing about the subtle difference between "sage -b" and "make"
2014-03-26 18:15 UTC+01:00, Volker Braun :
> There is this: http://sagemath.org/doc/developer/manual_git.html
>
> --
> You received this message because you are s
There is this: http://sagemath.org/doc/developer/manual_git.html
--
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 t
Hi,
> [...]
>
> It would be very great if the documentation could outline the basic steps
> required to get the latest (or suggested) version up and running. That
> could include pointers at how to build sage from source, together with the
> URL of the git repository and the command needed to clon
Hi!
Reading the dev guide at http://sagemath.org/doc/developer/, I find that
I'm missing a relevant piece of information: how to obtain the sources and
start using all these commands in the first place.
For most packages, I use a binary installation (compiled from source since
I'm on Gentoo, b
Am 2014-03-26 15:28, schrieb Volker Braun:
> I'm aware that git hardcodes paths in its templates. IMHO we shouldn't
> allow moving the directory around except in binary packages. And the
> latter doesn't need git or the dev scripts, so it should not be included
> in binary packages. But if you want
> So you never looked closely at sage -advanced ? 8-P
Or I forgot since ?... :-P
I just tried this -sync-build, and... It still crashes T_T
Thanks !
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and st
On Wednesday, March 26, 2014 4:31:38 PM UTC+1, Nathann Cohen wrote:
>
> Never head of syncbuild btw O_O
>
>>
>>
>
So you never looked closely at sage -advanced ? 8-P
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this gro
Sorrry
It was the option -sync-build
2014-03-26 16:31 UTC+01:00, Nathann Cohen :
> ~$ sage -syncbuild
> sage-run received unknown option: -syncbuild
> usage: sage [options]
> Try 'sage -h' for more information.
>
> Never head of syncbuild btw O_O
>
> Nathann
>
> On Wednesday, Marc
Hi,
I was wondering whether there is some way of replotting a graph in the
notebook.
I would like to do something like the following:
for ii in range(0,10):
gg=bar_chart([-3,5,-6,ii], rgbcolor=(1,0,0))
gg.show()
sleep(1)
gg.show(False)
Obviously, the command gg.show(False) does
I need to compute charpoly of big sparse matrices obtained in sage, but
there is no efficient algorithm in sage for the moment.
So I would like to implement it and add it to sage.
I think it already exists in gp or in linbox, but I was not able to use it
in sage.
Maybe sage has no proper way to c
Is new:
$ git log build/pkgs/dateutil
commit 5e9bffe79134dc328643e4eff36710b8d5637e93
Author: John H. Palmieri
Date: Fri Dec 20 11:12:11 2013 -0800
Trac #14993: update matplotlib to version 1.3.1
This version of matplotlib has new dependencies, so create new
packages for dateu
~$ sage -syncbuild
sage-run received unknown option: -syncbuild
usage: sage [options]
Try 'sage -h' for more information.
Never head of syncbuild btw O_O
Nathann
On Wednesday, March 26, 2014 2:00:12 PM UTC+1, vdelecroix wrote:
>
> Did you try "sage -syncbuild" ?
>
> You might have some garbage
Is dateutils new? Otherwise why would I have noeen affected by this before?
John
On 26 March 2014 14:40, Volker Braun wrote:
> Fix for the missing dependency is at http://trac.sagemath.org/ticket/16015
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-
Thanks Volker, that is most appreciated!
Bill.
On 26 March 2014 15:32, Volker Braun wrote:
> This is the arm box that I posted about earlier, the second attempt at
> tuning worked:
>
> vbraun@node3eth0:~$ cat /proc/cpuinfo
> Processor : ARMv7 Processor rev 0 (v7l)
> processor : 0
> BogoMIPS :
Can you make the dateutil log also world-readable?
--
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,
Fix for the missing dependency is at http://trac.sagemath.org/ticket/16015
--
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
This is the arm box that I posted about earlier, the second attempt at
tuning worked:
vbraun@node3eth0:~$ cat /proc/cpuinfo
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 2786.91
processor : 1
BogoMIPS : 2793.47
processor : 2
BogoMIPS : 2793.47
processor : 3
BogoMIPS : 2793.
On 26 March 2014 14:24, Volker Braun wrote:
> On Wednesday, March 26, 2014 1:11:13 PM UTC, John Cremona wrote:
>>
>> OK, thanks. I did "make distclean" and then "make" again, which
>> resulted in one failure, not matplotlib but dateutils.
>
>
> It would be interesting to get the log for that if y
I'm aware that git hardcodes paths in its templates. IMHO we shouldn't
allow moving the directory around except in binary packages. And the latter
doesn't need git or the dev scripts, so it should not be included in binary
packages. But if you want to fix it feel free to work on it.
On Wednesd
On Wednesday, March 26, 2014 1:11:13 PM UTC, John Cremona wrote:
>
> OK, thanks. I did "make distclean" and then "make" again, which
> resulted in one failure, not matplotlib but dateutils.
It would be interesting to get the log for that if you still have it.
The rest is normal, sometimes you
I think this is at heart an IPython-related bug, not something
Sage-specific.
I can't reproduce this at the moment -- natch -- but I've had exactly this
symptom from time to time when using ?? to look at source when using
IPython outside of Sage. One afternoon it was driving me crazy but I was
to
On 26 March 2014 12:39, Peter Bruin wrote:
> Hello John,
>
> The matplotlib problem is #16002.
OK, thanks. I did "make distclean" and then "make" again, which
resulted in one failure, not matplotlib but dateutils. I thne did
"make" again expecting it to do almost nothing but it did start doing
Did you try "sage -syncbuild" ?
You might have some garbage from previous Sage compilation.
2014-03-26 10:36 UTC+01:00, Daniel Krenn :
> Am 2014-03-26 10:14, schrieb Nathann Cohen:
>> When I type "Graph??" in Sage then "q" I get a crash. I tried on two
>> computers. Am I just cursed or is there
Hello John,
The matplotlib problem is #16002.
Peter
Op woensdag 26 maart 2014 11:44:28 UTC schreef John Cremona:
>
> Just when I thought that I had got the hang of git-based development,
> sincething fails which makes me realise that I have no idea what is
> happening...
>
> After upgrading
On Wednesday, 26 March 2014 19:35:17 UTC+11, Nathann Cohen wrote:
>
> > As mentioned in this thread, this already exists.
> > Use "# known bug" which is equivalent to "# optional - bug"
> > and which can be tested using
> > ./sage -t --optional=sage,bug [...]
>
> Yes, but if nobody explicitly
Can someone, at least, reproduce those failed doctests??
Daniel
Am 2014-03-18 18:19, schrieb Daniel Krenn:
> I've compiled sage in /local/data/krenn/sage-dev/sage-6.1.1 and then
> moved it to another directory. I am getting the following when testing
> sage:
>
> File "src/sage/dev/test/config.py
Just when I thought that I had got the hang of git-based development,
sincething fails which makes me realise that I have no idea what is
happening...
After upgrading to beta5 using the usual (for me) git pull trac
develop, I type make and it fails as follows. The first two of these
are optional
Hi all,
We still don't have any tuning code on ARM or Atom for MPIR. Note MPIR will
run extremely slowly without new tuning values due to recent changes.
Please let us know on the mpir-devel list if you are willing to help.
As far as we know, there are three things that can go wrong with tuning
Am 2014-03-26 10:14, schrieb Nathann Cohen:
> When I type "Graph??" in Sage then "q" I get a crash. I tried on two
> computers. Am I just cursed or is there a more interesting reason to
> that ? O_o
No crash on my Sage (6.1.1 on Debian Wheezy; compiled from source).
Daniel
--
You received this
On 26 March 2014 09:14, Nathann Cohen wrote:
> Hell everybody !
>
> When I type "Graph??" in Sage then "q" I get a crash. I tried on two
> computers. Am I just cursed or is there a more interesting reason to
> that ? O_o
It works ok for me with 6.1.1 and 6.2.beta5 on ubuntu 12.04 .
John
Hell everybody !
When I type "Graph??" in Sage then "q" I get a crash. I tried on two
computers. Am I just cursed or is there a more interesting reason to
that ? O_o
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
> As mentioned in this thread, this already exists.
> Use "# known bug" which is equivalent to "# optional - bug"
> and which can be tested using
> ./sage -t --optional=sage,bug [...]
Yes, but if nobody explicitly wants too see it, it becomes rather useless...
I will use stopgaps, then But I
On 2014-03-25 21:39, Nathann Cohen wrote:
Well. For instance keeping broken doctests in Sage would be nice I
think. You would see the bug each time you do a "sage -t" somewhere.
But that can confuse newcomers too...
Indeed. An important invariant of Sage releases is that all
(non-optional) doct
49 matches
Mail list logo
