[sage-support] Re: Sage on Mac OS X 10.11

[FG R]

OK guys

so to be more specific, I had my problem when i wanted to make an install 
with downloading the .app.dmg file

i deleted that install, and reinstalled with the .dmg file only
i do get a terminal opened when double clicking on the sage icon, i typed 
in notebook() and Sage DOES open in Chrome, its working fine 

so, problem solved to me doing the installation without the app.dmg file. I 
leave it to the devs to figure out why this install works and not the other 
one...

Thanks very much for your help

Le mercredi 7 octobre 2015 00:33:16 UTC+9, Tom Judson a écrit :
>
> Has anyone been able to get Sage running on El Capitan?  The app for Sage 
> 6.8 doesn’t work.  I downloaded sage-6.9.rc2 and tried to build everything 
> from the source code.  After installing the latest version of Xcode and 
> MacPorts, I was able to get the build underway.  However, everything 
> crashed when I tried to run Sage.  I tried to start over, but I get the 
> same error as if I had never installed the new version of MacPorts. 
>
> Tom Judson 
>
>
> = 
> Thomas W. Judson, Associate Professor 
> Department of Mathematics and Statistics 
> Stephen F. Austin State University 
> P.O. Box 13040-3040 SFA Station 
> Nacogdoches, TX  75962 
>
> OFFICE: 316 Math 
> TEL: (936) 468-1704 
> EMAIL: juds...@sfasu.edu  
>
>
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Installation problem for Sage 7.1 on MacOS X 10.11.3 El Capitan

[FG R]

OK guys

so to be more specific, I had my problem when i wanted to make an install 
with downloading the .app.dmg file

i deleted that install, and reinstalled with the .dmg file only
i do get a terminal opened when double clicking on the sage icon, i typed 
in notebook() and Sage DOES open in Chrome, its working fine 

so, problem solved to me doing the installation without the app.dmg file. I 
leave it to the devs to figure out why this install works and not the other 
one...

Thanks very much for your help

Le samedi 2 avril 2016 11:16:08 UTC+9, FG R a écrit :
>
> hi volker
>
> i'm a total noob in MacOS i bought my first Mac days ago. i was running 
> Windows prior to that (and managed to install SAGE for Windows)
>
> i open the terminal but 
>  /path/to/SageMath.app/Contents/Resources/sage/sage doesn't work
>
> maybe you want me to specify the exact path instead of "path/to"
>
> i don't see in which dir sagemath is installed. maybe its in a hidden 
> directory ?
>
> thanks for your help
>
> Le samedi 2 avril 2016 05:57:18 UTC+9, Volker Braun a écrit :
>>
>> What happens if you try to run it by hand? In a terminal: 
>> /path/to/SageMath.app/Contents/Resources/sage/sage
>>
>>
>>
>> On Friday, April 1, 2016 at 7:31:28 PM UTC+2, FG R wrote:
>>>
>>> I’ve installed SAGE on my brand new iMac Retina running on OS X El 
>>> Capitan 10.11.3
>>> after downloading the file 
>>>
>>> sage-7.2.beta0-OSX_10.11.4-x86_64.app.dmg from a mirror site in Japan
>>>
>>> the installation seems to be ok
>>>
>>> however when double click on the Sage application, a new folder in the 
>>> Chrome browser opens up
>>> saying 
>>> The Sage server is currently starting. Please wait...
>>> after a while (around 1minute) I get an error message
>>>
>>> Sage Server failed to start
>>> Please check the log for clues and have that information handy when 
>>> asking for help
>>>
>>> does it come from the Firewall perhaps ? i have AVAST Mac Security 2015 
>>> installed 
>>>
>>> the log is 
>>> Checking install location
>>> Checking existence of SageNB directory
>>> Starting Notebook in Terminal
>>> Checking install location
>>> Checking existence of SageNB directory
>>> Starting Notebook in Terminal
>>> Checking install location
>>> Checking existence of SageNB directory
>>> Starting Notebook in Terminal
>>>
>>> thanks for your hel
>>>
>>  
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Installation problem for Sage 7.1 on MacOS X 10.11.3 El Capitan

[FG R]

hi volker

i'm a total noob in MacOS i bought my first Mac days ago. i was running 
Windows prior to that (and managed to install SAGE for Windows)

i open the terminal but  /path/to/SageMath.app/Contents/Resources/sage/sage 
doesn't work

maybe you want me to specify the exact path instead of "path/to"

i don't see in which dir sagemath is installed. maybe its in a hidden 
directory ?

thanks for your help

Le samedi 2 avril 2016 05:57:18 UTC+9, Volker Braun a écrit :
>
> What happens if you try to run it by hand? In a terminal: 
> /path/to/SageMath.app/Contents/Resources/sage/sage
>
>
>
> On Friday, April 1, 2016 at 7:31:28 PM UTC+2, FG R wrote:
>>
>> I’ve installed SAGE on my brand new iMac Retina running on OS X El 
>> Capitan 10.11.3
>> after downloading the file 
>>
>> sage-7.2.beta0-OSX_10.11.4-x86_64.app.dmg from a mirror site in Japan
>>
>> the installation seems to be ok
>>
>> however when double click on the Sage application, a new folder in the 
>> Chrome browser opens up
>> saying 
>> The Sage server is currently starting. Please wait...
>> after a while (around 1minute) I get an error message
>>
>> Sage Server failed to start
>> Please check the log for clues and have that information handy when 
>> asking for help
>>
>> does it come from the Firewall perhaps ? i have AVAST Mac Security 2015 
>> installed 
>>
>> the log is 
>> Checking install location
>> Checking existence of SageNB directory
>> Starting Notebook in Terminal
>> Checking install location
>> Checking existence of SageNB directory
>> Starting Notebook in Terminal
>> Checking install location
>> Checking existence of SageNB directory
>> Starting Notebook in Terminal
>>
>> thanks for your hel
>>
>  

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage on Mac OS X 10.11

[Ivan Andrus]

The log says says "Starting Notebook in Terminal" which means that it should 
have opened up Terminal.app so that you can type in a password.  Did you 
perhaps not notice it?  Try again and if Terminal.app doesn’t start up, you can 
try starting sage in a terminal as Dima suggests (Terminal Session > Sage).  Or 
you can try opening Terminal.app yourself and running (from the appropriate 
directory):

sage --notebook=sagenb

-Ivan

> On Apr 1, 2016, at 3:57 PM, Dima Pasechnik  wrote:
> 
> Can you start Sage in a terminal? (it is somewhere in the menus of the app)
> 
> perhaps it's the antivirus that causes your problem - they are known to break 
> things, in general
> 
> 
> On Friday, April 1, 2016 at 6:31:28 PM UTC+1, FG R wrote:
> I have also the same problem on MacOS X 10.11.3 El Capitan
> 
> I’ve installed SAGE on my brand new iMac Retina running on OS X El Capitan 
> 10.11.3
> after downloading the file 
> 
> sage-7.2.beta0-OSX_10.11.4-x86_64.app.dmg from a mirror site in Japan
> 
> the installation seems to be ok
> 
> however when double click on the Sage application, a new folder in the Chrome 
> browser opens up
> saying 
> The Sage server is currently starting. Please wait...
> 
> after a while (around 1minute) I get an error message
> 
> Sage Server failed to start
> Please check the log for clues and have that information handy when asking 
> for help
> 
> does it come from the Firewall perhaps ? i have AVAST Mac Security 2015 
> installed 
> 
> the log is 
> Checking install location
> Checking existence of SageNB directory
> Starting Notebook in Terminal
> Checking install location
> Checking existence of SageNB directory
> Starting Notebook in Terminal
> Checking install location
> Checking existence of SageNB directory
> Starting Notebook in Terminal
> 
> thanks for your help
> 
> Le mercredi 7 octobre 2015 00:33:16 UTC+9, Tom Judson a écrit :
> Has anyone been able to get Sage running on El Capitan?  The app for Sage 6.8 
> doesn’t work.  I downloaded sage-6.9.rc2 and tried to build everything from 
> the source code.  After installing the latest version of Xcode and MacPorts, 
> I was able to get the build underway.  However, everything crashed when I 
> tried to run Sage.  I tried to start over, but I get the same error as if I 
> had never installed the new version of MacPorts. 
> 
> Tom Judson 
> 
> 
> = 
> Thomas W. Judson, Associate Professor 
> Department of Mathematics and Statistics 
> Stephen F. Austin State University 
> P.O. Box 13040-3040 SFA Station 
> Nacogdoches, TX  75962 
> 
> OFFICE: 316 Math 
> TEL: (936) 468-1704 
> EMAIL: juds...@sfasu.edu <> 
> 
> 
> 
> 
> 
> -- 
> 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 post to this group, send email to sage-support@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/sage-support 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage on Mac OS X 10.11

[Dima Pasechnik]

Can you start Sage in a terminal? (it is somewhere in the menus of the app)

perhaps it's the antivirus that causes your problem - they are known to 
break things, in general


On Friday, April 1, 2016 at 6:31:28 PM UTC+1, FG R wrote:
>
> I have also the same problem on MacOS X 10.11.3 El Capitan
>
> I’ve installed SAGE on my brand new iMac Retina running on OS X El Capitan 
> 10.11.3
> after downloading the file 
>
> sage-7.2.beta0-OSX_10.11.4-x86_64.app.dmg from a mirror site in Japan
>
> the installation seems to be ok
>
> however when double click on the Sage application, a new folder in the 
> Chrome browser opens up
> saying 
> The Sage server is currently starting. Please wait...
> after a while (around 1minute) I get an error message
>
> Sage Server failed to start
> Please check the log for clues and have that information handy when asking 
> for help
>
> does it come from the Firewall perhaps ? i have AVAST Mac Security 2015 
> installed 
>
> the log is 
> Checking install location
> Checking existence of SageNB directory
> Starting Notebook in Terminal
> Checking install location
> Checking existence of SageNB directory
> Starting Notebook in Terminal
> Checking install location
> Checking existence of SageNB directory
> Starting Notebook in Terminal
>
> thanks for your help
>
> Le mercredi 7 octobre 2015 00:33:16 UTC+9, Tom Judson a écrit :
>>
>> Has anyone been able to get Sage running on El Capitan?  The app for Sage 
>> 6.8 doesn’t work.  I downloaded sage-6.9.rc2 and tried to build everything 
>> from the source code.  After installing the latest version of Xcode and 
>> MacPorts, I was able to get the build underway.  However, everything 
>> crashed when I tried to run Sage.  I tried to start over, but I get the 
>> same error as if I had never installed the new version of MacPorts. 
>>
>> Tom Judson 
>>
>>
>> = 
>> Thomas W. Judson, Associate Professor 
>> Department of Mathematics and Statistics 
>> Stephen F. Austin State University 
>> P.O. Box 13040-3040 SFA Station 
>> Nacogdoches, TX  75962 
>>
>> OFFICE: 316 Math 
>> TEL: (936) 468-1704 
>> EMAIL: juds...@sfasu.edu 
>>
>>
>>
>>
>>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Installation problem for Sage 7.1 on MacOS X 10.11.3 El Capitan

[Volker Braun]

What happens if you try to run it by hand? In a terminal: 
/path/to/SageMath.app/Contents/Resources/sage/sage



On Friday, April 1, 2016 at 7:31:28 PM UTC+2, FG R wrote:
>
> I’ve installed SAGE on my brand new iMac Retina running on OS X El Capitan 
> 10.11.3
> after downloading the file 
>
> sage-7.2.beta0-OSX_10.11.4-x86_64.app.dmg from a mirror site in Japan
>
> the installation seems to be ok
>
> however when double click on the Sage application, a new folder in the 
> Chrome browser opens up
> saying 
> The Sage server is currently starting. Please wait...
> after a while (around 1minute) I get an error message
>
> Sage Server failed to start
> Please check the log for clues and have that information handy when asking 
> for help
>
> does it come from the Firewall perhaps ? i have AVAST Mac Security 2015 
> installed 
>
> the log is 
> Checking install location
> Checking existence of SageNB directory
> Starting Notebook in Terminal
> Checking install location
> Checking existence of SageNB directory
> Starting Notebook in Terminal
> Checking install location
> Checking existence of SageNB directory
> Starting Notebook in Terminal
>
> thanks for your help
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Need handholding about Sage Git good practices.

[Volker Braun]

The cleaner solution is to add on top of your previous commits (all based 
on 7.1rc0), this will make the history more understandable.

But, really, merging in the latest beta is not that bad either. The only 
downside is one extra log message, not that much of a deal. The code on the 
ticket is really all commits that are not yet merged, so an unnecessary 
merge doesn't add anything. If you play around with git you can have it 
display just the changes with respect to the latest beta.  



On Friday, April 1, 2016 at 9:31:05 PM UTC+2, Emmanuel Charpentier wrote:
>
> Dear list,
>
> three weeks ago, I opened Trac#20190 
>  to upgrade R to 3.2.4. This 
> worked fine for me, but stumbled on a problem in another Sage installation 
> (different system libraries). At the time I had no time to explore it.
>
> This turned out to be an upstream bug 
> , which 
> has been resolved, and I now prepare to merge this in. In the interim, Sage 
> has progressed from 7.1rc0 to 7.2beta2. I followed suit in my local 
> "develop" branch.
>
> In order to check that my fix works with current Sage, I merged my local 
> patch branch with the current develop (works fine). Fine, but now, my patch 
> contains about 890 (IIRC) commits already in 7.2beta2. Not Fun...
>
> Furthermore, the Developer's Guide advises against that :
> "A special case of merging is merging in the master branch. This 
> brings your local branch up to date with the newest Sage version. The above 
> warning against unnecessary merges still applies, though. Try to do all of 
> your development with the Sage version that you originally started with. 
> The only reason for merging in the master branch is if you need a new 
> feature or if your branch conflicts."
>
> Well, given the current pace (frantic, that is) of Sage upgrades, You'd 
> better stay up to date.
>
> Should I
>
>- revert to by original patch against 7.1rc0, update it and push this 
>to Trac for review ? Or
>- push by jumbo patch ?
>
> Your advice is expected,
>
> --
> Emmanuel Charpentier
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Need handholding about Sage Git good practices.

[Jeroen Demeyer]

On 2016-04-01 21:31, Emmanuel Charpentier wrote:

Fine, but now, my
patch contains about 890 (IIRC) commits already in 7.2beta2.


What's your definition of "contains" here? Your branch (I guess that's 
what you meant with "patch") "contains" all commits made in the past in 
Sage. I don't see what's so special about the 890 most recent ones.


--
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Need handholding about Sage Git good practices.

[Daniel Krenn]

On 2016-04-01 21:31, Emmanuel Charpentier wrote:
>   * revert to by original patch against 7.1rc0, update it and push this
> to Trac for review ? Or
>   * push by jumbo patch ?

If the merge of 7.2.beta2 into your 7.1.rc0+whatever works without a
conflict, then there is no need to do this merge. If there is a
conflict, then you should merge 7.2.beta2 into your 7.1.rc0+whatever.
(Just to point this out: you should merge it in the way said and not the
other way round)

But, I have to admit, maybe I do not understand your problem completely
(because merging in 7.2.beta2 if not needed is possible as well; I do
not see why you call it jumbo patch).

Daniel

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] How to take out a matrix as common factors

[Oscar Alberto Castillo Felisola]

Dear community,

I'd like to show to my students how to obtain the structure functions of a 
Lie group, say SU(3). Therefore, I create a basis for the Lie algebra, 
normalized via the trace of the squares. Then, I defined a commutator 
function, and start calculating the algebra... However, I'd like to 
separate the matrix generator from the coefficient (structure constant 
element).

How (if possible) can I take out a matrix factor from the result of the 
commutator?

Cheers!

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Need handholding about Sage Git good practices.

[Emmanuel Charpentier]

Dear list,

three weeks ago, I opened Trac#20190  
to upgrade R to 3.2.4. This worked fine for me, but stumbled on a problem 
in another Sage installation (different system libraries). At the time I 
had no time to explore it.

This turned out to be an upstream bug 
, which has 
been resolved, and I now prepare to merge this in. In the interim, Sage has 
progressed from 7.1rc0 to 7.2beta2. I followed suit in my local "develop" 
branch.

In order to check that my fix works with current Sage, I merged my local 
patch branch with the current develop (works fine). Fine, but now, my patch 
contains about 890 (IIRC) commits already in 7.2beta2. Not Fun...

Furthermore, the Developer's Guide advises against that :
"A special case of merging is merging in the master branch. This brings 
your local branch up to date with the newest Sage version. The above 
warning against unnecessary merges still applies, though. Try to do all of 
your development with the Sage version that you originally started with. 
The only reason for merging in the master branch is if you need a new 
feature or if your branch conflicts."

Well, given the current pace (frantic, that is) of Sage upgrades, You'd 
better stay up to date.

Should I

   - revert to by original patch against 7.1rc0, update it and push this to 
   Trac for review ? Or
   - push by jumbo patch ?

Your advice is expected,

--
Emmanuel Charpentier

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Format of partial derivatives within sagemanifolds

[Oscar Alberto Castillo Felisola]

Dear community,

I'm using SAGE with SageManifolds to calculate Lie derivatives. First, I 
would like to congratulate all the team of developers, because day to day 
sagemanifolds get more useful. Next, the "problem".

I'm trying to find the most general rank two tensor compatible with O(3) 
symmetry. Here some code:

# The manifold
M = Manifold(4, 'M')

# The patch
X. = M.chart(r't r:(0,+oo) th:(0,pi):\theta ph:(0,2*pi):\phi')

# Killing vectors
Lx = M.vector_field('Lx')
Lx[:] = ( 0, 0, -cos(ph), cot(th)*sin(ph) )
Ly = M.vector_field('Ly')
Ly[:] = ( 0, 0, sin(ph), cot(th)*cos(ph) )
Lz = M.vector_field('Lz')
Lz[:] = ( 0, 0, 0, 1)

# The general tensor
T = M.tensor_field( 0, 2, 'T' )
for i in xrange(4):
for j in xrange(4):
T[i,j] = function("T%s%s" % (i,j))(t, r, th, ph)

# One of the Lie derivatives
LxT = T.lie_der(Lx)
LxT.display_comp() 

Then, the "problem" is that the PDE displayed show partial derivatives with 
respect to `th` or `ph` instead of using the LaTeX symbols as defined on 
the patch.

Is there a way to correct this behaviour?

Cheers.

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Installation problem for Sage 7.1 on MacOS X 10.11.3 El Capitan

[FG R]

I’ve installed SAGE on my brand new iMac Retina running on OS X El Capitan 
10.11.3
after downloading the file 

sage-7.2.beta0-OSX_10.11.4-x86_64.app.dmg from a mirror site in Japan

the installation seems to be ok

however when double click on the Sage application, a new folder in the 
Chrome browser opens up
saying 
The Sage server is currently starting. Please wait...
after a while (around 1minute) I get an error message

Sage Server failed to start
Please check the log for clues and have that information handy when asking 
for help

does it come from the Firewall perhaps ? i have AVAST Mac Security 2015 
installed 

the log is 
Checking install location
Checking existence of SageNB directory
Starting Notebook in Terminal
Checking install location
Checking existence of SageNB directory
Starting Notebook in Terminal
Checking install location
Checking existence of SageNB directory
Starting Notebook in Terminal

thanks for your help

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Sage on Mac OS X 10.11

[FG R]

I have also the same problem on MacOS X 10.11.3 El Capitan

I’ve installed SAGE on my brand new iMac Retina running on OS X El Capitan 
10.11.3
after downloading the file 

sage-7.2.beta0-OSX_10.11.4-x86_64.app.dmg from a mirror site in Japan

the installation seems to be ok

however when double click on the Sage application, a new folder in the 
Chrome browser opens up
saying 
The Sage server is currently starting. Please wait...
after a while (around 1minute) I get an error message

Sage Server failed to start
Please check the log for clues and have that information handy when asking 
for help

does it come from the Firewall perhaps ? i have AVAST Mac Security 2015 
installed 

the log is 
Checking install location
Checking existence of SageNB directory
Starting Notebook in Terminal
Checking install location
Checking existence of SageNB directory
Starting Notebook in Terminal
Checking install location
Checking existence of SageNB directory
Starting Notebook in Terminal

thanks for your help

Le mercredi 7 octobre 2015 00:33:16 UTC+9, Tom Judson a écrit :
>
> Has anyone been able to get Sage running on El Capitan?  The app for Sage 
> 6.8 doesn’t work.  I downloaded sage-6.9.rc2 and tried to build everything 
> from the source code.  After installing the latest version of Xcode and 
> MacPorts, I was able to get the build underway.  However, everything 
> crashed when I tried to run Sage.  I tried to start over, but I get the 
> same error as if I had never installed the new version of MacPorts. 
>
> Tom Judson 
>
>
> = 
> Thomas W. Judson, Associate Professor 
> Department of Mathematics and Statistics 
> Stephen F. Austin State University 
> P.O. Box 13040-3040 SFA Station 
> Nacogdoches, TX  75962 
>
> OFFICE: 316 Math 
> TEL: (936) 468-1704 
> EMAIL: juds...@sfasu.edu  
>
>
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Help needed with getting PARI/GP residue fields in Sage finite field form

[Misja]

On the contrary: it is a helpful remark! I hadn't realised this before. At 
least I can check whether I am lucky and the order is of the form Z[X]/(f) 
and proceed very quickly if so :-)

On Saturday, 26 March 2016 14:54:00 UTC, David Loeffler wrote:
>
> Dear Misja,
>
> What I had in mind was something like this. Given some monstrous number 
> field K with enormous discriminant, and some small prime p, you can ask 
> Sage for a p-maximal order and it'll find one reasonably quickly, as you 
> know.
>
> All I was saying is that if the resulting order O is of the form Z[X] / 
> (f), for some polynomial f in Z[X] -- i.e. if "O.ring_generators()" is a 
> list of length 1 -- then you can quickly compute all possible maps O --> 
> Fp-bar by just factoring f modulo p. (Sage really ought to have this coded 
> up already; sadly it doesn't, but it's trivial to implement.) Maybe this 
> isn't a terribly helpful remark; I don't know how likely it is that the 
> orders you work with have this form.
>
> David
>
> On 17 March 2016 at 16:33, Misja > wrote:
>
>> Hi David,
>>
>> Thank you very much for this helpful reply! You're right, of course: my 
>> example was silly. Here's an example with a 104 digit discriminant that my 
>> code just got stuck on (for a bit).
>>
>> x=polygen(QQ);
>> K=NumberField(x^5 + 16255223088*(x^4) - 330681713908949415936*(x^3) - 
>> 5058938091171222191449571328000*(x^2) - 
>> 2907488578277274989701398473183198183424*x + 
>> 76587534178613500902724649685949865805676749520896,'a');
>> fact=K.factor(5);
>> print K.residue_field(fact[0][0]);
>>
>> What I am trying to do is to calculate reductions of modular forms modulo 
>> some prime ideal P. However, the coefficients of such a modular form may 
>> lie in a number field with a 1000 digit discriminant and I want to avoid 
>> trying to factor this if I can, hence my trying to use p-maximal orders.
>>
>> Could you explain a bit more what you mean in the monogenic case? Could 
>> you do something like EquationOrder(K.defining_polynomial(),'alpha'), take 
>> a p-maximal order there and then do what you are suggesting? Although, 
>> actually, I don't know if sage can calculate a p-maximal order of a given 
>> order.
>>
>> Misja
>>
>>
>>
>> On Thursday, 17 March 2016 15:50:59 UTC, David Loeffler wrote:
>>>
>>> There are two reasons why people work with non-maximal orders: because 
>>> they're actually interested in their arithmetic; or (more often) because 
>>> they're working with examples where the discriminant is too large to 
>>> efficiently factor. Which is the case in your problem? In the example you 
>>> give, you're letting PARI choose the order for you, but the discriminant is 
>>> small enough that one can find a maximal order in a few milliseconds anyway 
>>> (and Sage is perfectly happy to work with residue fields of maximal 
>>> orders). 
>>>
>>> If you genuinely don't want to factor the discriminant, but the orders 
>>> you're interested in are "monogenic" (generated by a single element over 
>>> Z), then you can just factor the characteristic polynomial of the generator 
>>> over Fp and that gives you the factorisation, and the reduction maps, 
>>> immediately.
>>>
>>> Can you give an example of a case you'd be interested in where the 
>>> maximal order is really too big to easily find?
>>>
>>> Regards, David
>>>
>>> On 11 March 2016 at 14:42, Misja  wrote:
>>>
 For a number field N I am trying to factor an integral prime p in a 
 p-maximal order Op. In the end I would like a map from the quotient of the 
 p-maximal order Op/P (for P|p) to some finite field in Sage's standard 
 finite field form, but I can't quite figure out how to do it.

 Firstly, Sage doesn't have ideals or residue fields of non-maximal 
 orders implemented, so I am trying to compute the factorisation of p in Op 
 via the PARI/GP interface with sage. I think this can be done, for 
 example, 
 in the following way, in which we compute a 7-maximal order of the number 
 field defined by x^8+x^3-13*x+26 and compute all primes above 7 in this 
 order.

 x=polygen(QQ);

 nf=gp.nfinit([x^8 + x^3 - 13*x + 26,[7]]); #Note the [7] at the end, 
 indicating a 7-maximal order only.
 nf; 

 fact=gp.idealprimedec(nf,7); 
 fact;

 res_field_sizes=[];
 for i in fact:
 res_field_sizes.append(i[1]**i[4]);

 res_field_sizes;

 Now, for each element fact[i] of fact, I would like to compute a 
 homomorphism Op->Op/fact[i]->GF(res_field_sizes[i-1],'gen') - note that 
 we're using a vector in pari/gp and a list in sage hence fact[i] 
 corresponds to res_field_sizes[i-1]. I can't quite get this to work.

 I feel like there are two options:

1. Translate the p-maximal order and prime factorisation back to 
sage. Take a poly quotient or something. Map this to a finite field.
2. Keep on working in pari/gp and use, for example, 
 

Re: [sage-support] Re: Sage Crash Report

[Henri Girard]

Your welcome...
I like very much this tool because it works fine and is well documented :)
I wanted to translate examples but it's too much work, and I guess all 
people using it are knowing english !

Better original language than a bad translation !
Henri

Le 01/04/2016 14:55, Oscar Alberto Castillo Felisola a écrit :
Thank you HG, Your suggestion worked like a charm. I create a new 
branch in my sage installation and tried your suggestion, and it works 
smoothly.


Best wishes!
Oscar.

On Thursday, 31 March 2016 14:56:08 UTC-3, HG wrote:

sagemanifolds compiles well usually... Just follow the install doc
and sm-install.sh :

http://sagemanifolds.obspm.fr/download.html#script_install/sm-install.sh


I prefer than git.

Le 31/03/2016 19:00, Oscar Alberto Castillo Felisola a écrit :

Hi Eric,

I finally compiled the source of sage from github, but I got a
merge conflict when I added the sagemanifolds branch. I'll post
further when I get to the office. Hope you could help me.

Cheers.

On Tuesday, 29 March 2016 15:51:53 UTC-3, Eric Gourgoulhon wrote:

Hi Oscar,

I'm afraid I cannot help much with your specific problem. The
only thing I can tell is that Sage 7.1 + SageManifolds 0.9
works well on Ubuntu, which is based on Debian, but of course
differs from it.

Best regards,

Eric.

Le mardi 29 mars 2016 16:04:20 UTC+2, Oscar Alberto Castillo
Felisola a écrit :

Dear community,

lately, I'm having problems with the installation of
SAGE. I downloaded the version Sage v.7.1 for Debian_8,
and it seems to work... but I installed sagemanifold
v.0.9, and I got the report file attached to this post.

I'm having problems too when compiling the scr code,
because the file `flint*` has a problem.

Any suggestions?

-- 
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 post to this group, send email to sage-s...@googlegroups.com
.
Visit this group at https://groups.google.com/group/sage-support
.
For more options, visit https://groups.google.com/d/optout
.


--
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 post to this group, send email to sage-support@googlegroups.com 
.

Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.


--
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-support] Re: Sage Crash Report

[Oscar Alberto Castillo Felisola]

Thank you HG, Your suggestion worked like a charm. I create a new branch in 
my sage installation and tried your suggestion, and it works smoothly.

Best wishes!
Oscar.

On Thursday, 31 March 2016 14:56:08 UTC-3, HG wrote:
>
> sagemanifolds compiles well usually... Just follow the install doc and 
> sm-install.sh :
>
> http://sagemanifolds.obspm.fr/download.html#script_install/sm-install.sh
>
> I prefer than git.
>
> Le 31/03/2016 19:00, Oscar Alberto Castillo Felisola a écrit :
>
> Hi Eric, 
>
> I finally compiled the source of sage from github, but I got a merge 
> conflict when I added the sagemanifolds branch. I'll post further when I 
> get to the office. Hope you could help me.
>
> Cheers.
>
> On Tuesday, 29 March 2016 15:51:53 UTC-3, Eric Gourgoulhon wrote: 
>>
>> Hi Oscar, 
>>
>> I'm afraid I cannot help much with your specific problem. The only thing 
>> I can tell is that Sage 7.1 + SageManifolds 0.9 works well on Ubuntu, which 
>> is based on Debian, but of course differs from it.
>>
>> Best regards,
>>
>> Eric.
>>
>> Le mardi 29 mars 2016 16:04:20 UTC+2, Oscar Alberto Castillo Felisola a 
>> écrit : 
>>>
>>> Dear community,  
>>>
>>> lately, I'm having problems with the installation of SAGE. I downloaded 
>>> the version Sage v.7.1 for Debian_8, and it seems to work... but I 
>>> installed sagemanifold v.0.9, and I got the report file attached to this 
>>> post.
>>>
>>> I'm having problems too when compiling the scr code, because the file 
>>> `flint*` has a problem.
>>>
>>> Any suggestions?
>>>
>> -- 
> 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 post to this group, send email to sage-s...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Eulers method for non-linear ODEs

[slabbe]

There is a multiplication sign (*) missing:

sage: AA = y*(1-y)-0.2*(1-0.7*cos(2*pi*x))
sage: AA = y(1-y)-0.2*(1-0.7*cos(2*pi*x))
Traceback (most recent call last)
...
TypeError: number of arguments does not match number of variables in parent

Then it works (with a deprecation warning):

sage: eulers_method(AA,0,1,1/2,1)
 xy  h*f(x,y)
.../sage-git/local/lib/python2.7/site-packages/sage/misc/decorators.py:705: 
DeprecationWarning: Substitution using function-call syntax and unnamed 
arguments is deprecated and will be removed from a future release of Sage; 
you can use named arguments instead, like EXPR(x=..., y=...)
See http://trac.sagemath.org/5930 for details.
  return func(*args, **kwds)
 01  -0.0300
   1/20.970   -0.1554500
 10.8145500   0.045529148750

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Re: Eulers method for non-linear ODEs

[Harald Schilly]

On Friday, April 1, 2016 at 9:40:13 AM UTC+2, Jesse Hulse wrote:
>
> eulers_method(y(1-y)-0.2*(1-0.7*cos(2*pi*x)),0,1,1/2,1)
>

I have the feeling ,that your y(1-y) should be y*(1-y)

A variable with parenthesis next to it is a function call, i.e. like y(7) → 
something, whereas you seem to mean multiplication, which is the "*" sign.

-- h 

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Eulers method for non-linear ODEs

[Jesse Hulse]

I have never used sage before, and I'm trying to use it to numerically 
solve non-linear ODEs. The code I found online does not work for my 
non-linear equation x'=x(1-x)-0.2(1-0.2*cos(2pi*t)). 

from sage.calculus.desolvers import eulers_method
x,y = PolynomialRing(QQ,2,"xy").gens()
eulers_method(y(1-y)-0.2*(1-0.7*cos(2*pi*x)),0,1,1/2,1)


The Error I get is:

TypeError: number of arguments does not match number of variables in parent


Any ideas on how to do this correctly?

-- 
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 post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.