If you get a message like this:
Warning (get_approx): Field not known to required precision. Can apply workaround: 23028, Infinity except (0->20694, 1->20694, 2->20694)
Note: you can suppress future warnings with ExactpAdics_SetWarningAction("get_approx", "Ignore")
then the code has run into a bug which, as far as I can tell, is due to an issue with Magma's arbitrary-precision p-adic fields. It can be worked around, but potentially with some performace penalty, which is why it is only a warning. As the message says, you can use ExactpAdics_SetWarningAction to suppress this message.
If you get a message like this:
then the code has run into a bug which, as far as I can tell, is due to an issue with Magma's arbitrary-precision p-adic fields. It can be worked around, but potentially with some performace penalty, which is why it is only a warning. As the message says, you can use
ExactpAdics_SetWarningActionto suppress this message.