Hi! I almost accomplished to port my group cohomology spkg to T2.
As a side note: It was necessary to rename two functions in the underlying C code, since on T2 (but nowhere else) apparently these functions got confused with functions of the same name from pari. This also turned out to be a problem for #1396. The remaining problem concerns the random generator of GAP. It behaves differently on T2 than on any other machine that I have access to. On my desktop computer, on sage.math and on bsd.math (the latter both in 64 and 32 bit mode), I get: gap> Reset(GlobalMersenneTwister);; List([1..10],i->Random(1,100000)); [ 85758, 234, 18408, 12676, 2507, 38166, 24692, 15013, 4755, 94043 ] On T2, I get: gap> Reset(GlobalMersenneTwister);; List([1..10],i->Random(1,100000)); [ 96343, 43659, 75071, 1314, 40740, 69892, 10586, 31272, 96336, 26794 ] It seems that due to this problem, my package may compute a different (though isomorphic) ring presentation for a cohomology ring on different machines. But in some tests, I create elements with certain properties, and for that purpose I need a computationally unique ring presentation, not only for testing the result but for setting up the example. So, even marking some test as random would not help. What do you think is the best way to cope with that problem? Is there a painless way to duplicate some doctests and tell the test script that one version is for Solaris and the other is for everything else? Best regards, Simon -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
