Re: [sage-devel] Review of tickets #17909, #17943, #18043
Hi again Ping: Can someone review #17909 (and/or #17943)? #18043 was reviewed and applied/closed (thanks Travis). Best Jonas On 02.11.2015 15:40, Jonas Jermann wrote: Hi all I already sent this to sage-nt but didn't get a response, so I try again: Can someone maybe have a look at one of the tickets above (in particular #17909)? They are for modular forms for Hecke triangle groups. In particular this includes (classical) modular forms for SL2(Z) and for the Theta subgroup (see the readme for more information). I no longer work in academics (I'm a software developer now) but the code might be useful for others (e.g. in the classical cases) and in my opinion it would be a pity if the functionality got lost in the ticket graveyard... I didn't expect a fast review but the tickets are there since quite a while already... :-) #17909: Rankin Cohen brackets (also for quasi forms) and more decomposition methods for quasi forms #17943: Depends on #17909 (but I could make it separate I guess). Here I tried to make some experimental code (conversions from numerical coefficients to exact forms) more robust and fixed some bugs #18043: I tried my best to add support for HyperbolicPlane(), it could certainly be improved by someone familiar with the HyperbolicPlane code... So if someone has time or is interested, it's appreciated. :-) Best Jonas PS I would be interested in generalizing the implementation to Jacobi forms if someone has the time to help me with the algebraic structure. PPS Using appropriate subspaces it's quite easy to find some differential equations satisfied by the forms (e.g. E2). For instance I found: n=4 E2.derivative(4) == -3/2*E2^2*E2.derivative(2) + 5/2*E2*E2.derivative(3) + 9/4*E2*E2.derivative()^2 -3*E2.derivative()*E2.derivative(2) n=5 (non-arithmetic) E2^3*E2.derivative(2) == E2^2*E2.derivative(3) + 3/2 * E2^2*E2.derivative()^2 + 4*E2*E2.derivative()*E2.derivative(2) -20/3 * E2.derivative()*E2.derivative(3) -22/3*E2.derivative()^3 + 40/9*E2.derivative(2)^2 Maybe that's of interest to someone... -- 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, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: [sage-support] Sage 6.9 no longer loads packages from /home/me/.local/lib/python2.7/site-packages
On Fri, Nov 20, 2015 at 12:44 PM, Mark Bell wrote: > I've just upgraded to Sage 6.9 from 6.8. I have a large number of packages > that I've installed by using: > python setup.py install --user > so they have been placed in /home/me/.local/lib/python2.7/site-packages/... > > Previously Sage would automatically search this location looking for > packages and so I could do "import mypackage" and everything would work > fine. It now appears that Sage is no longer searching this path > automatically and so attempting to import these packages results in a > "ImportError: No module named mypackage". Is this a bug or was no longer > loading packages from ~/.local/ a deliberate change? It appears that this > has been previously listed as a feature of both Sage and Python, see > http://sage-devel.narkive.com/kld2G6DI/sage-python-packages-and-local and > https://www.python.org/dev/peps/pep-0370/ > This was caused by trac 14243, which -- in retrospect -- I *strongly* disagree with being included in Sage (http://trac.sagemath.org/ticket/14243). In SageMathCloud, I manually revert that ticket so that users have a better experience: https://github.com/sagemathinc/smc-sage/commit/7c9cfd095463091bcf41e1c6ea6e8eebfb61f00c I've made http://trac.sagemath.org/ticket/19612 to revert 14243. - William > -- > 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-supp...@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- 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, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] error compiling sage (atlas failed to build)
Hi all,
As suggested by the output in my console I email this list since I failed
to build sage from source.
I am running debian-sid on a Hp-laptop p 6100 dual core,
linux kernel : 4.2.0-1-amd64 #1 SMP Debian 4.2.6-1 (2015-11-10)
The package that failed to build is atlas-3.10.2
In the attached log I am not sure what is relevant or not I just noticed :
the warning "the use of `tmpnam' is dangerous, better use `mkstemp'
" a good amount of times ...
the error : File .../enums.py", line 201, in make_check_enums
check_enums(output.decode('ascii'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 44:
ordinal not in range(128)
Cheers,
Laurent
--
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, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
atlas-3.10.2.log
Description: Binary data
[sage-devel] error compiling sage (atlas failed to build)
Hi all,
As suggested by the output in my console I email this list since I failed
to build sage from source.
I am running debian-sid on a Hp-laptop p 6100 dual core,
linux kernel : 4.2.0-1-amd64 #1 SMP Debian 4.2.6-1 (2015-11-10)
The package that failed to build is atlas-3.10.2
In the attached log I am not sure what is relevant or not I just noticed :
the warning "the use of `tmpnam' is dangerous, better use `mkstemp'
" a good amount of times ...
the error : File .../enums.py", line 201, in make_check_enums
check_enums(output.decode('ascii'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 44:
ordinal not in range(128)
Cheers,
Laurent
--
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, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
atlas-3.10.2.log
Description: Binary data
Re: [sage-devel] Re: Continuous Integration through a French 'Research Service'
Sorry, travelling right now. Whats IMHO preventing us from better testing is container support, right now the testsuite fails inside docker. Using containers, the patchbot could snapshot clean builds and test on top of that. And automatically test third-party packages. More machines for the buildbot would also be good, e.g. older osx and centos/fedora. On Saturday, November 21, 2015 at 3:29:51 AM UTC-5, Nathann Cohen wrote: > > > http://build.sagedev.org/release/waterfall > > I'm not saying that you are not being very helpful, but we could do > with full sentences and explanations. > > Your web page is very pretty, and indeed tells us more about what > machines are being used to run the tests. Is there anything that > prevent us from a fully automatic integration of trac tickets ? If so, > what and should we change it ? > > Also, do we have all the machines we need or are there some platforms > that you would like to test Sage on to which we don't have access at > the moment ? > > Nathann > -- 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, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Continuous Integration through a French 'Research Service'
On Saturday, 21 November 2015 08:29:51 UTC, Nathann Cohen wrote: > > > http://build.sagedev.org/release/waterfall > > I'm not saying that you are not being very helpful, but we could do > with full sentences and explanations. > > Your web page is very pretty, and indeed tells us more about what > machines are being used to run the tests. Is there anything that > prevent us from a fully automatic integration of trac tickets ? If so, > what and should we change it ? > > Also, do we have all the machines we need or are there some platforms > that you would like to test Sage on to which we don't have access at > the moment ? as can be seen from that picture, we certainly need more different OSX machines, and ARM Linux machines. -- 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, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Continuous Integration through a French 'Research Service'
> http://build.sagedev.org/release/waterfall I'm not saying that you are not being very helpful, but we could do with full sentences and explanations. Your web page is very pretty, and indeed tells us more about what machines are being used to run the tests. Is there anything that prevent us from a fully automatic integration of trac tickets ? If so, what and should we change it ? Also, do we have all the machines we need or are there some platforms that you would like to test Sage on to which we don't have access at the moment ? Nathann -- 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, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
