Changes between Initial Version and Version 7 of Ticket #16964


Ignore:
Timestamp:
Dec 13, 2014, 10:20:12 PM (8 years ago)
Author:
Jeroen Demeyer
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16964

    • Property Priority changed from major to critical
    • Property Milestone changed from sage-6.4 to sage-6.5
    • Property Component changed from algebraic geometry to number fields
    • Property Summary changed from MPolynomialIdeal_singular_repr.variety: sage.libs.pari.gen.PariError: not enough precomputed primes to Speed up comparisons in QQbar
  • Ticket #16964 – Description

    initial v7  
    3737}}}
    3838
    39 This is extremely annoying, since apparently the result of the computation was available at that point, and it was only sorting the result which failed. Neither the unsorted result nor the triangular decomposition had been cached, throwing away 8 hours worth of computation. So I suggest
    40 
    41 1. wrap that sorting into a try-except block to return the result unsorted if there is any problem sorting things.
    42 2. perhaps provide a switch to disable sorting up front, since repeated exactification might cost time.
    43 3. Try to work out why exactly the comparison fails here, and avoid this error in the first place.
    44 
    45 The system of equations in this exact form was written by someone else, so I'll have to either reproduce this with my own (equivalent) system or request permission to post that code. In any case, it's rather lengthy.
    46 
    47 I'll also try to run the code on a modified sage which simply disables the sort in order to get my hands on the bare QQbar descriptions behind the failed computation.
     39This is extremely annoying, since apparently the result of the computation was available at that point, and it was only sorting the result which failed.