Nikos,
> It seems that when the vertices are labelled 0,..., n-1 then the
> translation is simply 0 <-> n, and the rest is fixed. At least
> this is the case with all examples I've seen. Can I assume that
> this will allways be the case?
This is what happens. At first, the graph calls its rela
Jaap Spies writes:
>
> Download the patch ( be sure it is the original!) to $SAGEROOT
> start ./sage
> and do
> sage: hg_sage.patch('trac_5017-graph_aut_gp_trans.patch')
> cntrl-d
> and do a ./sage -br
>
Thanks a lot. I did as you said and now the problem is solved.
Also, thanks a lot to Robert
Nikos Apostolakis wrote:
> Jaap Spies writes:
>
>> Nikos Apostolakis wrote:
>>> It seems that when the vertices are labelled 0,..., n-1 then the
>>> translation is simply 0 <-> n, and the rest is fixed. At least
>>> this is the case with all examples I've seen. Can I assume that
>>> this wil
Jaap Spies writes:
> Nikos Apostolakis wrote:
>>
>> It seems that when the vertices are labelled 0,..., n-1 then the
>> translation is simply 0 <-> n, and the rest is fixed. At least
>> this is the case with all examples I've seen. Can I assume that
>> this will allways be the case?
>>
>
>
Jaap Spies wrote:
> William Stein wrote:
>> On Sun, Jan 18, 2009 at 3:53 AM, Jaap Spies wrote:
>>> Nikos Apostolakis wrote:
The "translation=True" flag does not work after upgrading to sage 3.2.3
I am not sure when this behaviour was introduced. In version 2.10.2 it
works fine, un
Nikos Apostolakis wrote:
> Jaap Spies writes:
>
>> Nikos Apostolakis wrote:
>>> The "translation=True" flag does not work after upgrading to sage 3.2.3
>>> I am not sure when this behaviour was introduced. In version 2.10.2 it
>>> works fine, unfortunately I don't have a more recent old sage to
Jaap Spies writes:
> Nikos Apostolakis wrote:
>> The "translation=True" flag does not work after upgrading to sage 3.2.3
>> I am not sure when this behaviour was introduced. In version 2.10.2 it
>> works fine, unfortunately I don't have a more recent old sage to check.
>>
>> sage: foo = Grap
mabshoff wrote:
>
>
> On Jan 18, 10:08 am, Jaap Spies wrote:
>> William Stein wrote:
>>> On Sun, Jan 18, 2009 at 3:53 AM, Jaap Spies wrote:
>
>
>
>>> Jaap -- great work tracking down when this broke. Could you open
>>> a trac ticket? Thanks!
>> I'm sorry I couln't be more precise. For som
On Jan 18, 10:08 am, Jaap Spies wrote:
> William Stein wrote:
> > On Sun, Jan 18, 2009 at 3:53 AM, Jaap Spies wrote:
> > Jaap -- great work tracking down when this broke. Could you open
> > a trac ticket? Thanks!
>
> I'm sorry I couln't be more precise. For some reason my sage-3.1.3 and
William Stein wrote:
> On Sun, Jan 18, 2009 at 3:53 AM, Jaap Spies wrote:
>> Nikos Apostolakis wrote:
>>> The "translation=True" flag does not work after upgrading to sage 3.2.3
>>> I am not sure when this behaviour was introduced. In version 2.10.2 it
>>> works fine, unfortunately I don't have
On Sun, Jan 18, 2009 at 3:53 AM, Jaap Spies wrote:
>
> Nikos Apostolakis wrote:
>> The "translation=True" flag does not work after upgrading to sage 3.2.3
>> I am not sure when this behaviour was introduced. In version 2.10.2 it
>> works fine, unfortunately I don't have a more recent old sage to
Nikos Apostolakis wrote:
> The "translation=True" flag does not work after upgrading to sage 3.2.3
> I am not sure when this behaviour was introduced. In version 2.10.2 it
> works fine, unfortunately I don't have a more recent old sage to check.
>
> sage: foo = Graph()
> sage: foo.add_edges(
12 matches
Mail list logo
