Re: [sage-devel] Re: cannot post comments on trac #19984
On Monday, 1 February 2016 20:43:40 UTC, Volker Braun wrote: > > Something broke already before you pressed submit, the next-to-last > preview already timed out Still looks more like a network issue, > perhaps a wonky UW firewall? > you appear to be right; I was able to leave http://trac.sagemath.org/ticket/19984?replyto=22#comment:24 using geom as socks_v5 proxy (see e.g. https://calomel.org/firefox_ssh_proxy.html on how to set it up) And a no web-proxy attempt still hangs. What can we do about it? Complain to UW, via William? Move over to other hosting? (ODK grant surely can get us a good enough GCE or other host...) Dima > > On Monday, February 1, 2016 at 5:49:54 PM UTC+1, Dima Pasechnik wrote: >> >> is it just skrew clock somewhere upstream that causes this? > > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: cannot post comments on trac #19984
Something broke already before you pressed submit, the next-to-last preview already timed out Still looks more like a network issue, perhaps a wonky UW firewall? On Monday, February 1, 2016 at 5:49:54 PM UTC+1, Dima Pasechnik wrote: > > is it just skrew clock somewhere upstream that causes this? -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: interrupt.pyx on PyPi?
On Monday, February 1, 2016 at 10:40:42 AM UTC+1, Martin Albrecht wrote: > > but perhaps turning Sage into a bunch of smaller Python libraries is > something which can be accomplished step-by-step. > The first order of business should then be to modularize the doctest framework, otherwise you end up with a bunch of packages that have no working testsuite. Which nobody in their right mind would want to base their work on. Also, namespace packages (i.e. multiple packages sharing sage.*) are easier in Python >= 3.3 thanks to PEP420. Splitting of non-mathematical tools would be definitely an advantage since they would be useful in other projects. And some fairly isolated interfaces with third-party programs could be factored out, too. But I don't think there is much value in splitting up most of the core functionality; If the doctests can't be run independently then modules are irreducible. And there aren't many doctests that you can run without libgmp or libsingular, for example. Also, the semver coolaid doesn't really work if there is nobody running e2e tests. Which really is admitting defeat, if I can't develop packages independently then they are not independent. At least in npm one can work around broken semver by installing specific versions in parallel, but pip does not support that. On the plus side, one can still install install pip packages without pages of warnings about unsupported/abandoned versions -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] interrupt.pyx on PyPi?
Hi Jeroen, Jeroen Demeyer writes: > On 2016-02-01 10:40, 'Martin R. Albrecht' via sage-devel wrote: >> In particular, I am *very* interested in turning Sage’s interrupt >> handling into something that can be easily installed from PyPI. For >> those who don’t know what Sage’s interrupt handling does: it allows that >> you can press Ctrl-C to interrupt long running C code and that crashes >> in a library do not necessarily crash your Python shell. > > First of all, do you assume that the code you want to interrupt is > Cython? Or do you want something which could work more generally? Cython-only is enough for me. > I guess it could be separated from Sage. It might be a good project for > some Sage Days workshop. +1, I don’t think I’ll attend any anytime soon. Let’s see if I can find some time to work on this in the mean time. I’ll wait a bit more if there are objects here and then open a ticket, where we can move technical discussions. > One non-trivial thing is that the Sage interrupt framework also refers > directly to PARI. So this would need to be abstracted. Ah, I forgot about removing that one for my hack. Good point. > And of course it will only work on POSIX systems. I guess we could provide some noop for non-POSIX systems? Cheers, Martin -- _pgp: https://keybase.io/martinralbrecht _www: https://martinralbrecht.wordpress.com _jab: martinralbre...@jabber.ccc.de _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
Re: [sage-devel] Re: Sage GSOC 2016
How about adding support for machine learning algorithms in sage ? Hello developers, I am just pitching in a very rough and amateur thought for the idea of upcoming GSoC, and we can refine it further due to your inputs. Sage can have a support for a variety of Machine Learning algorithms. We can wrap around python's scikit-learn library, it has been great since a past few months. Plus a whole new domain would be a huge addition to the things which Sage can provide. A good amount of Object Oriented Programming in Python is required for that. I am not sure much yet, as I am a newbie, but I say if the veterans of Sage in this mailing list have a look at this idea, I can take it up myself for this year's GSoC. On Wednesday, January 20, 2016 at 10:19:30 PM UTC+5:30, Harald Schilly wrote: > > > > On Tuesday, January 19, 2016 at 4:15:43 PM UTC+1, Johan S. R. Nielsen > wrote: >> >> How does it work with Sage's application to GSoC and what are the >> relevant deadlines? > > > Hi, the program is explained on the GSoC website, and the timeline is here: > https://developers.google.com/open-source/gsoc/timeline?hl=en > > The start/midterm/end times are given by that timetable. > > If you have an idea, please add it to SageMath's wiki page, for the year > 2016. > > -- harald > > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] interrupt.pyx on PyPi?
On 2016-02-01 10:40, 'Martin R. Albrecht' via sage-devel wrote: In particular, I am *very* interested in turning Sage’s interrupt handling into something that can be easily installed from PyPI. For those who don’t know what Sage’s interrupt handling does: it allows that you can press Ctrl-C to interrupt long running C code and that crashes in a library do not necessarily crash your Python shell. First of all, do you assume that the code you want to interrupt is Cython? Or do you want something which could work more generally? I guess it could be separated from Sage. It might be a good project for some Sage Days workshop. One non-trivial thing is that the Sage interrupt framework also refers directly to PARI. So this would need to be abstracted. And of course it will only work on POSIX systems. Jeroen. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: cannot post comments on trac #19984
is it just skrew clock somewhere upstream that causes this? -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Can anyone provide access to recent Intel or AMD machines?
Are Intel(R) Xeon(R) CPU @ 2.30GHz interesting for you? (That's what one gets on SMC. We have some SMC licenses here bought for ODK) No idea if one could get something better there, but you could ask William. Dima On Monday, 1 February 2016 11:43:05 UTC, Bill Hart wrote: > > Hi all, > > today Alex Best started in Kaiserslautern on this OpenDreamKit project. > He's working on support in MPIR for the latest Intel and AMD processors. > However, we have very little access to anything later than about 2010. > > Does anyone have more recent Intel and AMD machines (linux servers) that > they could provide log in access to? We'd be doing timings of all the basic > MPIR functions and eventually superoptimising the assembly language > functions. > > In general, one can expect up to a 2x speedup for each different > microarchitecture (code from previous arches is rarely anywhere near > optimal for more recent ones). E.g. we just tried some code which is > roughly optimal for bobcat on a piledriver and it was two times slower than > the old K10 code we have! > > If you can help, please contact me off list. > > Bill. > > P.S: We are aware of the GCC farm, but almost everything there we have > access to elsewhere. > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Can anyone provide access to recent Intel or AMD machines?
On Mon, Feb 1, 2016 at 7:32 AM, Dima Pasechnik wrote: > Are Intel(R) Xeon(R) CPU @ 2.30GHz interesting for you? > (That's what one gets on SMC. We have some SMC licenses here bought for ODK) > No idea if one could get something better there, but you could ask William. It's a Virtual Machine, so may or may not be useful for their tuning. The main plus is that it is a Haswell architecture, which is pretty new: $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 63 model name : Intel(R) Xeon(R) CPU @ 2.30GHz stepping: 0 microcode : 0x1 cpu MHz : 2299.968 cache size : 46080 KB physical id : 0 siblings: 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_t sc nopl xtopology eagerfpu pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm fsgsbase bmi1 avx2 sme p bmi2 xsaveopt bugs: bogomips: 4599.93 clflush size: 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: > Dima > > > On Monday, 1 February 2016 11:43:05 UTC, Bill Hart wrote: >> >> Hi all, >> >> today Alex Best started in Kaiserslautern on this OpenDreamKit project. >> He's working on support in MPIR for the latest Intel and AMD processors. >> However, we have very little access to anything later than about 2010. >> >> Does anyone have more recent Intel and AMD machines (linux servers) that >> they could provide log in access to? We'd be doing timings of all the basic >> MPIR functions and eventually superoptimising the assembly language >> functions. >> >> In general, one can expect up to a 2x speedup for each different >> microarchitecture (code from previous arches is rarely anywhere near optimal >> for more recent ones). E.g. we just tried some code which is roughly optimal >> for bobcat on a piledriver and it was two times slower than the old K10 code >> we have! >> >> If you can help, please contact me off list. >> >> Bill. >> >> P.S: We are aware of the GCC farm, but almost everything there we have >> access to elsewhere. > > -- > 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 https://groups.google.com/group/sage-devel. > 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: cannot post comments on trac #19984
can somebody make a packet trace, eg. using wireshark? On Monday, February 1, 2016 at 2:28:50 PM UTC+1, Daniel Krenn wrote: > > On 2016-02-01 12:28, Volker Braun wrote: > > You should be able to post even if the preview hangs... possibly > > requires to press send again. Did you try that? > > When I had the same problem, I've tried, but it did not work. > > Daniel > > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: cannot post comments on trac #19984
On 2016-02-01 12:28, Volker Braun wrote: > You should be able to post even if the preview hangs... possibly > requires to press send again. Did you try that? When I had the same problem, I've tried, but it did not work. Daniel -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Can anyone provide access to recent Intel or AMD machines?
Hi Bill, we got 16 cores (w/o HT) of Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz here. If that helps, let me know off list and I can grant Alex access. Cheers, Martin 'Bill Hart' via sage-devel writes: > Hi all, > > today Alex Best started in Kaiserslautern on this OpenDreamKit project. > He's working on support in MPIR for the latest Intel and AMD processors. > However, we have very little access to anything later than about 2010. > > Does anyone have more recent Intel and AMD machines (linux servers) that > they could provide log in access to? We'd be doing timings of all the basic > MPIR functions and eventually superoptimising the assembly language > functions. > > In general, one can expect up to a 2x speedup for each different > microarchitecture (code from previous arches is rarely anywhere near > optimal for more recent ones). E.g. we just tried some code which is > roughly optimal for bobcat on a piledriver and it was two times slower than > the old K10 code we have! > > If you can help, please contact me off list. > > Bill. > > P.S: We are aware of the GCC farm, but almost everything there we have > access to elsewhere. -- _pgp: https://keybase.io/martinralbrecht _www: https://martinralbrecht.wordpress.com _jab: martinralbre...@jabber.ccc.de _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
[sage-devel] Can anyone provide access to recent Intel or AMD machines?
Hi all, today Alex Best started in Kaiserslautern on this OpenDreamKit project. He's working on support in MPIR for the latest Intel and AMD processors. However, we have very little access to anything later than about 2010. Does anyone have more recent Intel and AMD machines (linux servers) that they could provide log in access to? We'd be doing timings of all the basic MPIR functions and eventually superoptimising the assembly language functions. In general, one can expect up to a 2x speedup for each different microarchitecture (code from previous arches is rarely anywhere near optimal for more recent ones). E.g. we just tried some code which is roughly optimal for bobcat on a piledriver and it was two times slower than the old K10 code we have! If you can help, please contact me off list. Bill. P.S: We are aware of the GCC farm, but almost everything there we have access to elsewhere. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: cannot post comments on trac #19984
You should be able to post even if the preview hangs... possibly requires to press send again. Did you try that? On Monday, February 1, 2016 at 11:22:01 AM UTC+1, Dima Pasechnik wrote: > > On Monday, 1 February 2016 00:28:31 UTC, Volker Braun wrote: >> >> I've increased the mod_reqtimeout limits, if we are hitting a timeout on >> the trac side then it must be that. Though it could very well be a timeout >> on the network in front of trac... >> >> still the same sh*t. It hangs on the automatic previewing. Is it possible > to shut it off (perhaps have a setting to shut it off)? > Otherwise, someone would have to develop a fix for 'git trac' to post > comments... > > >> On Sunday, January 31, 2016 at 9:38:53 PM UTC+1, Dima Pasechnik wrote: >>> >>> I can comment just fine on some tickets, and just cannot on some others. >>> It really does not look like a networking error, but rather some trac >>> trouble... >>> >>> On Sunday, 31 January 2016 15:59:06 UTC, Daniel Krenn wrote: On 2016-01-31 14:19, Daniel Krenn wrote: > On 2016-01-31 14:07, Dima Pasechnik wrote: >> On Sunday, 31 January 2016 12:23:59 UTC, Volker Braun wrote: >> >> There is a request data read error in the log, this seems to be a >> networking error and not the fault of the trac server. I tried and >> could comment on the ticket just fine.urther > > No problem at the moment with #10519. Now, some troubles. I split it into two comments and it worked. (but it's annoying...) Daniel >>> -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: cannot post comments on trac #19984
On Monday, 1 February 2016 00:28:31 UTC, Volker Braun wrote: > > I've increased the mod_reqtimeout limits, if we are hitting a timeout on > the trac side then it must be that. Though it could very well be a timeout > on the network in front of trac... > > still the same sh*t. It hangs on the automatic previewing. Is it possible to shut it off (perhaps have a setting to shut it off)? Otherwise, someone would have to develop a fix for 'git trac' to post comments... > On Sunday, January 31, 2016 at 9:38:53 PM UTC+1, Dima Pasechnik wrote: >> >> I can comment just fine on some tickets, and just cannot on some others. >> It really does not look like a networking error, but rather some trac >> trouble... >> >> On Sunday, 31 January 2016 15:59:06 UTC, Daniel Krenn wrote: >>> >>> On 2016-01-31 14:19, Daniel Krenn wrote: >>> > On 2016-01-31 14:07, Dima Pasechnik wrote: >>> >> On Sunday, 31 January 2016 12:23:59 UTC, Volker Braun wrote: >>> >> >>> >> There is a request data read error in the log, this seems to be a >>> >> networking error and not the fault of the trac server. I tried >>> and >>> >> could comment on the ticket just fine.urther >>> > >>> > No problem at the moment with #10519. >>> >>> Now, some troubles. I split it into two comments and it worked. (but >>> it's annoying...) >>> >>> Daniel >>> >> -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] interrupt.pyx on PyPi?
Hi all, In a thread over at [sage-support] William wrote: > I've suggested numerous times that we should massively refactor the > sage library to be a bunch of smaller Python libraries, develop them > say on github (?), use Pypi and pip. If people would realize how > important it is that we revamp how Sage development is done in a much > less monolithic way, and better using existing tools, then I would be > happy and enjoy watching as people do the revamp (e.g., like happened > with switching from Mercurial to Git, which I didn't do much on, but > definitely supported). I don’t mean to restart a general strategy/development discussion here, but perhaps turning Sage into a bunch of smaller Python libraries is something which can be accomplished step-by-step. In particular, I am *very* interested in turning Sage’s interrupt handling into something that can be easily installed from PyPI. For those who don’t know what Sage’s interrupt handling does: it allows that you can press Ctrl-C to interrupt long running C code and that crashes in a library do not necessarily crash your Python shell. It is a difference between night and day to interface with external C/C++ code >From Python without and with it. Having this code available outside of Sage enables, for example, to turn some of our C/C++ library interfaces into stand-alone libraries[^1], like I’ve done with our fplll interface at https://github.com/malb/fpylll Sage’s interrupt handling lives at https://github.com/sagemath/sage/tree/master/src/sage/ext/interrupt I think the technical challenges are manageable. I’m using a copy of it separately in https://github.com/malb/fpylll/tree/master/src/fpylll/interrupt without issues. Making this code independent would mean one big patch to the library, though, where we replace all include 'sage/ext/interrupt.pxi' with an appropriate new line depending on where we’d install the file. My question is: am I overlooking some technical challenge or another reason why making this code independent could be a problem? I’m happy to put some work into this, in case you’re wondering. Cheers, Martin [^1]: Okay, there’s also the small issue of how to do type conversion Sage ←→ library in a nice modular yet fast way, but one step at a time. -- _pgp: https://keybase.io/martinralbrecht _www: https://martinralbrecht.wordpress.com _jab: martinralbre...@jabber.ccc.de _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. signature.asc Description: PGP signature
