Design #1159
Add global enum "verify/DontVerify"
Description
should we have a global enum for "verify/DontVerify"?
this could be a pervasive feature in cocoalib.
Related issues
History
#1 Updated by Anna Maria Bigatti about 6 years ago
- Target version set to CoCoALib-1.0
John says it might be better to have a "reliability flag", which takes "0" as "certain".
I am thinking of the function MinPolyModular
, so with 0 it would verify the answer, otherwise it would apply the desired level of checking to the rational reconstruction of the coefficients.
#2 Updated by John Abbott about 6 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
- a "boolean" interface is easy to understand (and simple to use)
- a more sophisticated interface would need to be well documented to be useful (e.g. NTL uses a boolean interface for probabilistic determinant)
- it would be nice to have a "universal scheme" for CoCoALib (e.g. a parameter to be used by all fns which offer an optional "fast heuristic" mode)
It may be possible to have a sophisticated interface which can also be used as if it were a boolean one: I am thinking about the method I used for specifying the GMPAllocator
when creating the GlobalManager
. The user can see it as just a flag, or can specify a parameter along with the flag.
#3 Updated by John Abbott about 6 years ago
- Related to Design #950: factor and SmoothFactor for integers --> FactorINT, FactorINT_TrialDiv, FactorINT_PollardRho added
#4 Updated by John Abbott almost 6 years ago
- Related to Feature #1167: New class VerificationLevel added
#5 Updated by John Abbott almost 6 years ago
- Assignee set to John Abbott
- Target version changed from CoCoALib-1.0 to CoCoALib-0.99600
Close this issue and refer to #1167?
#6 Updated by John Abbott almost 6 years ago
- Status changed from In Progress to Closed
- % Done changed from 10 to 100
- Estimated time set to 1.10 h
This issue has been subsumed by #1167. Closing!