Re: [sage-support] fails to get graph_editor() to work

[Jean-Florent Raymond]

Hello,

I recently started developing a replacement to graph_editor for the
jupyter notebook, using ipywidgets and ipycanvas.
You can find it at the following address :
https://gitlab.limos.fr/jfraymon/phitigra

This is still work in progress but the basic editor (adding removing
vertices and edges, displaying the graph, etc.) works.
One feature that this editor will have is that changes made to the graph
outside of the editor will be automatically updated in the editor. This
will for instance allow to display step by step the computation done by
a function (for teaching, or debugging, or ...).

Any feedback is welcome.

Jean-Florent.

Le 29/08/2020 à 08:27, pong a écrit :
> I see. Is there a substitute for graph_editor()? It's fairly convenient.
> 
> On Thursday, August 27, 2020 at 8:48:32 AM UTC-7 dim...@gmail.com wrote:
> 
>> On Thu, Aug 27, 2020 at 4:45 PM pong  wrote:
>>
>>>
>>> Running sagemath 9.1 from a jupyter notebook
>>>
>>> When calling graph_editor() got the following error message.
>>> How can I make the module 'sagenb' works again?
>>>
>>
>> sagenb does not work with Python 3. You'd need Sage 9.1 (or earlier) built 
>> with Python2 in order to be able to use sagenb.
>>
>> And sagenb will be definitely gone in 9.2, which won't support Python 2.
>>
>> HTH
>> Dima
>>
>>>
>>> [image: ge.png]
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "sage-support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to sage-support...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-support/772c9f8f-e27f-4485-8add-ca97d51290bbn%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
> 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/b3eeea4c-5474-d294-1544-b2b89f872044%40uca.fr.

Re: [sage-support] Possible bug in PARI handling...

[Dima Pasechnik]

I guess it would be Singular, not Pari.

On Fri, 28 Aug 2020, 22:11 Emmanuel Charpentier, <
emanuel.charpent...@gmail.com> wrote:

> Inspiration is this ask.sagemath question
> .
> Roughly, the original question was a discrepancy between the *numerical*
> results obtained by Sage and by Matlab when solving a set of three
> equations with three unknowns.
>
> I wanted to compare the numerical results with those obtained by
> rearranging the original equations into rational fractions and solving
> their numerators (while watching out for null denominators). My code so far
> is in the attached SolutionExacte.sage.
>
> What succeeds :
>
>- Rearranging the equations in rational fractions
>- creating the relevant polynomial ring
>- creating the ideal J representing the set of solutions
>- checking that its dimension is 0
>
> What fails is enumerating the solutions : S=J.variety(QQbar) hasn’t
> returned for more than eight hours (!). When throwing the towel (*i. e.
> interrupting), I got the following message in a message box of the Jupyter
> notebook :
>
> /usr/local/sage-9/local/lib/python3.7/site-packages/sage/rings/qqbar.py:2078: 
> RuntimeWarning: cypari2 leaked 2081168 bytes on the PARI stack df = factor(d)
>
> Questions :
>
>1. Is that a known bug ?
>2. Is that possibly a *new* bug ?
>3. If so, how to file the most informative ticket ?
>4. Are you aware of possible workarounds ?
>
> HTH,
> ​
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-support+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-support/ab9e3015-f0cf-43a8-84b3-5c9c7c12d1bao%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAAWYfq0s_Zxoc2Pib6TRSqrtTHR0RJFRiTFfsyYd9r4yXnm2%3Dg%40mail.gmail.com.

Re: [sage-support] fails to get graph_editor() to work

[pong]

Thanks you. I clone the project but confused what to do next. In the 
README, it saids

Change to the root directory and run:
$ sage -pip install --upgrade --no-index -v .

which root directory are we talking about? the phitigra directory?
Also should it be sage -pip install phitigra --upgrade -no-index -v?

In any case, I couldn't get it install so I must be doing something wrong. 
Please help.

On Saturday, August 29, 2020 at 2:11:12 AM UTC-7 Jean-Florent Raymond wrote:

> Hello,
>
> I recently started developing a replacement to graph_editor for the
> jupyter notebook, using ipywidgets and ipycanvas.
> You can find it at the following address :
> https://gitlab.limos.fr/jfraymon/phitigra
>
> This is still work in progress but the basic editor (adding removing
> vertices and edges, displaying the graph, etc.) works.
> One feature that this editor will have is that changes made to the graph
> outside of the editor will be automatically updated in the editor. This
> will for instance allow to display step by step the computation done by
> a function (for teaching, or debugging, or ...).
>
> Any feedback is welcome.
>
> Jean-Florent.
>
> Le 29/08/2020 à 08:27, pong a écrit :
> > I see. Is there a substitute for graph_editor()? It's fairly convenient.
> > 
> > On Thursday, August 27, 2020 at 8:48:32 AM UTC-7 dim...@gmail.com wrote:
> > 
> >> On Thu, Aug 27, 2020 at 4:45 PM pong  wrote:
> >>
> >>>
> >>> Running sagemath 9.1 from a jupyter notebook
> >>>
> >>> When calling graph_editor() got the following error message.
> >>> How can I make the module 'sagenb' works again?
> >>>
> >>
> >> sagenb does not work with Python 3. You'd need Sage 9.1 (or earlier) 
> built 
> >> with Python2 in order to be able to use sagenb.
> >>
> >> And sagenb will be definitely gone in 9.2, which won't support Python 2.
> >>
> >> HTH
> >> Dima
> >>
> >>>
> >>> [image: ge.png]
> >>>
> >>> -- 
> >>> You received this message because you are subscribed to the Google 
> Groups 
> >>> "sage-support" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send 
> an 
> >>> email to sage-support...@googlegroups.com.
> >>> To view this discussion on the web visit 
> >>> 
> https://groups.google.com/d/msgid/sage-support/772c9f8f-e27f-4485-8add-ca97d51290bbn%40googlegroups.com
>  
> >>> <
> https://groups.google.com/d/msgid/sage-support/772c9f8f-e27f-4485-8add-ca97d51290bbn%40googlegroups.com?utm_medium=email&utm_source=footer
> >
> >>> .
> >>>
> >>
> > 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/8f70e0c4-4f69-4824-a1c1-85b35a4dccc0n%40googlegroups.com.

[sage-support] gp in Sage

[Surendran Karippadath]

Hi,

 I evaluated the j-invariant in Pari/gp In SageMathCell
? \p 50
? ellj(sqrt(163.0)*I)
%1 = 68925893036109279891085639286944512.0163739

Furthermore the Cube-root of the j-invariant I obtained
? (ellj(sqrt(163.0)*I))^(1/3)
%2 = 410009702400.00077461269365317226812447191214259043

Is it possible to check in Sage with High Precision if the values are
Integers.

Thanking you in advance

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAGp5ChV21gzwieMCGvywDMxETh3ZUOuOpHaSGUbPNhNHvbVOpg%40mail.gmail.com.