[sage-combinat-devel] Re: How to install (parts of) the combinat queue on many machines?
we now have a public sage notebook with the combinat queue applied running on sage.lacim.uqam.ca. Everything seems to run smoothly, but we are still in the TEST PHASE, so please NO SERIOUS RESEARCH so far, accounts and worksheets MIGHT GET DELETED. no one really answered here; does that mean no one (except us) is interested in having such a notebook, or is it just the summer? I did some more test on Monday and it seems to be stable, we will see how the summer school goes... Christian -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
Re: [sage-combinat-devel] Re: How to install (parts of) the combinat queue on many machines?
Hi Christian, I did try it out and it worked for me (though I did not run heavy calculations since you said not to use it for resarch ;-) ). I think it is a very good idea to have such a notebook server! Anne On 7/20/11 3:06 PM, Christian Stump wrote: we now have a public sage notebook with the combinat queue applied running on sage.lacim.uqam.ca. Everything seems to run smoothly, but we are still in the TEST PHASE, so please NO SERIOUS RESEARCH so far, accounts and worksheets MIGHT GET DELETED. no one really answered here; does that mean no one (except us) is interested in having such a notebook, or is it just the summer? I did some more test on Monday and it seems to be stable, we will see how the summer school goes... Christian -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
[sage-devel] Re: Adding new unit tests
Maybe since we already mark doctest as #optional or #random or #long or something we should add another marker which say's #known bug. Unit tests being slightly different should have a different solution. But some pythonic way of marking unit tests as known bugs would also be usefull. Kind Regards, Maarten Derickx -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Few minutes for a sage minor bug?
Are there good reasons you need to use that specific version of the LLL algorithm? If you just need some result fast (before the deadline) it might be easier to just use one of the other LLL algorithms. The NTL wrapper object has a lot of .LLL methods to chose from. And appart from that you might also want to not use the LLL wrapper directly but just use regular Sage matrices to call the LLL. For example sage: A=MatrixSpace(ZZ,5,5)(range(25)) sage: A.LLL() [ 0 0 0 0 0] [ 0 0 0 0 0] [ 0 0 0 0 0] [ 0 1 2 3 4] [ 5 3 1 -1 -3] Kind Regards, Maarten Derickx -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Adding new unit tests
On Wednesday, July 20, 2011 12:14:09 AM UTC-7, Maarten Derickx wrote: Maybe since we already mark doctest as #optional or #random or #long or something we should add another marker which say's #known bug. Apparently you can already do this, but it's not documented in the developer's guide: in the script sage-doctest, having a test marked # known bug is treated exactly the same as if it's marked # optional. -- John -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Adding new unit tests
On Wed, Jul 20, 2011 at 9:29 AM, John H Palmieri jhpalmier...@gmail.com wrote: On Wednesday, July 20, 2011 12:14:09 AM UTC-7, Maarten Derickx wrote: Maybe since we already mark doctest as #optional or #random or #long or something we should add another marker which say's #known bug. Apparently you can already do this, but it's not documented in the developer's guide: in the script sage-doctest, having a test marked # known bug is treated exactly the same as if it's marked # optional. I think I wrote that long ago. Given that now there are tags for optional, I might prefer # optional - bug That way one could doctest exactly the known bugs in the sage library, if one wanted to for some reason. sage -t --only_optional=bug ... Keep in mind that optional tests are almost never run by anybody, so the main current utility of including them is that readers of documentation see them. William -- John -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -- William Stein Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Adding new unit tests
On Tue, 19 Jul 2011 14:44:10 -0400 Michael Orlitzky mich...@orlitzky.com wrote: 2. Subject to #1, where is the most appropriate place to add the tests? My first guess would be in the TESTS: section of sage/calculus/calculus.py, but there appear to be some standalone tests defined in sage/tests, too. If you are adding tests only for integration, starting a new file sage/symbolic/tests.py might be better. There is a list of open integration tickets here: http://trac.sagemath.org/sage_trac/wiki/symbolics Don't forget to mention the ticket number in the test. Cheers, Burcin -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Adding new unit tests
On 07/20/11 13:26, Burcin Erocal wrote: On Tue, 19 Jul 2011 14:44:10 -0400 Michael Orlitzky mich...@orlitzky.com wrote: 2. Subject to #1, where is the most appropriate place to add the tests? My first guess would be in the TESTS: section of sage/calculus/calculus.py, but there appear to be some standalone tests defined in sage/tests, too. If you are adding tests only for integration, starting a new file sage/symbolic/tests.py might be better. There is a list of open integration tickets here: http://trac.sagemath.org/sage_trac/wiki/symbolics Don't forget to mention the ticket number in the test. This is what I've done so far. I'll figure out how to mark them optional - bug, and post them when I'm done. Thanks. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Adding new unit tests
How about one adds a file with bugs in the name that lists the doctests together with their _wrong_ output and corresponding trac link. That way, we'll find out immediately which tickets are fixed by some upstream spkg update... -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Adding new unit tests
On Wednesday, July 20, 2011 9:36:22 AM UTC-7, William wrote: On Wed, Jul 20, 2011 at 9:29 AM, John H Palmieri jhpalm...@gmail.com wrote: On Wednesday, July 20, 2011 12:14:09 AM UTC-7, Maarten Derickx wrote: Maybe since we already mark doctest as #optional or #random or #long or something we should add another marker which say's #known bug. Apparently you can already do this, but it's not documented in the developer's guide: in the script sage-doctest, having a test marked # known bug is treated exactly the same as if it's marked # optional. I think I wrote that long ago. Given that now there are tags for optional, I might prefer # optional - bug That way one could doctest exactly the known bugs in the sage library, if one wanted to for some reason. sage -t --only_optional=bug ... See http://trac.sagemath.org/sage_trac/ticket/11615. -- John -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] How to make BuildBot know which patches to apply and in which order ?
Hi Sage-devel, How should I say to the BuildBot which patches to apply and in which order ? Following the information available on the buildbot page [1] on the Sage wiki, I am not able to make the BuildBot understand how to apply patches on the ticket #11379 where two of the patches should not be applied. I also saw that a similar problem is affecting #11468. Does the information must be put in a comment instead of in the description? I know Jeroen ask once to write the information about which patches to apply in the description instead of somewhere down in a comment. Is there a convention? Thank you, Sébastien Labbé [1] http://wiki.sagemath.org/buildbot [2] http://trac.sagemath.org/sage_trac/ticket/11379 [3] http://trac.sagemath.org/sage_trac/ticket/11468 -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: How to make BuildBot know which patches to apply and in which order ?
Ok, I just answered my question : the information must be put in a comment, not in the description of the ticket. The release manager already asked to put the information about which patch to apply in which order in the description instead of hidden somewhere in a comment. So, could the Buildbot also read the description? Sébastien -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
