On Wednesday, 10 May 2017 22:25:13 UTC+10, Paul Leopardi wrote:
>
> I have just completed the first draft of a paper, "Classifying bent
> functions by their Cayley graphs".
>
Eric,
Chromium Version 63.0.3239.132 (Official Build) Built on Ubuntu ,
running on Ubuntu 17.10 (64-bit) does not display the any labels or
numbers on the bounding box. Firefox 58.0 works fine.
I tried grabbing the latest three-min.js from threejs.org to see if that
helped. No luck.
I don't
Le vendredi 26 janvier 2018 21:19:22 UTC+1, Andy Howell a écrit :
>
> Eric,
>
> I tried with threejs. I could not get the labels to show with either sage
> 8.0 or sage 8.2beta3.
>
The labels are here, but they are not placed along the blue arrows of the S
object: they are located on other
Eric,
I tried with threejs. I could not get the labels to show with either
sage 8.0 or sage 8.2beta3. One interesting thing I did find through. I
plotted a sphere, with the opacity=0.2.
S = sphere(center=(0,0,0),size=2,opacity=0.2)
show(S, viewer='threejs',axes=True, axes_labels=['a','b','c'])
Hi,
Le mardi 23 janvier 2018 21:58:35 UTC+1, Andy Howell a écrit :
>
> I was trying to plot a 3d object and was not sure which axes were which
> in the plot.
>
Just for this purpose (i.e. finding which axes are which), note that you
can use the threejs viewer, which automatically labels the
will be fixed in https://trac.sagemath.org/ticket/24597
On Friday, January 26, 2018 at 3:59:28 PM UTC, Erik Bray wrote:
>
> On Fri, Jan 26, 2018 at 11:51 AM, Dima Pasechnik > wrote:
> > It appears that libpython is not correctly linked to the python3
> executable:
> > ...
Good catch, yes, this fixes the weirdness on python2!
On Friday, January 26, 2018 at 3:59:28 PM UTC, Erik Bray wrote:
>
> On Fri, Jan 26, 2018 at 11:51 AM, Dima Pasechnik > wrote:
> > It appears that libpython is not correctly linked to the python3
> executable:
> > ...
>
On Fri, Jan 26, 2018 at 11:51 AM, Dima Pasechnik wrote:
> It appears that libpython is not correctly linked to the python3 executable:
> ...
>
> make[2]: Leaving directory
> '/var/export/home/dima/Sage/sagetrac-mirror/local/var/tmp/sage/build/python3-3.6.1.p1/src'
> Testing
On 2018-01-26 12:10, Dima Pasechnik wrote:
PS. We now have access
Who is "we"?
I'm certainly willing to have a look if "I" have access.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving
Thanks. I've fixed this.
On Friday, January 26, 2018 at 12:29:46 PM UTC, Mark Bell wrote:
>
> I think there is a minor typo in the *To get an account* instructions at
> https://trac.sagemath.org/. It says that:
>
> the default username is the first letter of the surname followed by the
>> name
I think there is a minor typo in the *To get an account* instructions at
https://trac.sagemath.org/. It says that:
the default username is the first letter of the surname followed by the
> name (i.e. mjohnson for Mike Johnson or tlei for Tan Lei).
Should this not say:
the default username is
On Friday, January 26, 2018 at 10:51:18 AM UTC, Dima Pasechnik wrote:
>
> It appears that libpython is not correctly linked to the python3
> executable:
> ...
>
> make[2]: Leaving directory
> '/var/export/home/dima/Sage/sagetrac-mirror/local/var/tmp/sage/build/python3-3.6.1.p1/src'
> Testing
It appears that libpython is not correctly linked to the python3 executable:
...
make[2]: Leaving directory
'/var/export/home/dima/Sage/sagetrac-mirror/local/var/tmp/sage/build/python3-3.6.1.p1/src'
Testing importing of various modules...
ld.so.1: python: fatal: libpython3.6m.so.1.0: open
the MPFR problem is "resolved" here - well, it's at least clear how to fix
it.
https://github.com/wbhart/mpir/issues/242
On Tuesday, January 23, 2018 at 4:59:29 PM UTC, Maria MacCallum wrote:
>
> Spotted this error after posting!
>
> See attached new config logs from the gmp attempt and the mpfr
14 matches
Mail list logo