On Wednesday, August 23, 2017 at 12:51:54 PM UTC-5, Jori Mäntysalo wrote: > > On Wed, 23 Aug 2017, Travis Scrimshaw wrote: > > > Thank you for doing this. Do you want to add this as a file into the > > $SAGE_SRC/sage/tests? How long does it take to run these tests on your > > system? > > It seems to already be more than a second per lattice. > > This kind of randomized stress testing can not be added to any normal > release cycle. I do not know if our current framework has any good place > for this. >
Since they are around 1 second, you could add the test code to our tests folder with one to a few "generic" examples marked with "# long time". That way anyone who wants to run more stress testing can easily do so (as opposed to, e.g., posting the code on your homepage). This could also be used as a function to run timing benchmarks on Sage as well. > > Is there more places for this kind of testing? Personally I have run some > tests for QQ-polynomial factoring and found several bugs in Singular (they > have been corrected). For matrices we know that product of eigenvalues > equals to determinant etc, product of invertible matrices is invertible > etc. What else could be done? > > I've come across something that is possibly ZZ-polynomial bug in Singular, but I ended up working around it by converting to the SymbolicRing. I'm not sure if I would be able to recover it, much less isolate what precisely the problem was as I was doing stuff in the ZZ['q'].fraction_field(). Although for these types of bugs, individual doctests added in the corresponding code (merged once the corresponding Singular upgrade was done). Ralf regularly does this with Pynac. Further tests that would be good are symbolic and calculus related. There are a fair body of tests, but maybe some more specific integrals or expression simplifications to do both regression and speed testing would be useful. However, I think Ralf and other people who care and work more in the symbolics might have a better thought or opinion on this. For those things with matrices, these are more like unitests, and so I think it would be good to add to the TestSuite methods by adding methods named _test_*. Thus, something like _test_eigenvalues would test that the sum is the trace and the product is the determinant, etc. Best, Travis -- 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.
