Opened 5 years ago
Closed 5 years ago
#835 closed bug (fixed)
modStd() yields wrong result
Reported by: | steenpass | Owned by: | somebody |
---|---|---|---|
Priority: | minor | Milestone: | 4-2-0 and higher |
Component: | dontKnow | Version: | 4-1-1 |
Keywords: | modStd | Cc: |
Description
In the following example, the result of modStd() is wrong:
> option(noloadLib); > LIB "modstd.lib"; > ring r = (0,a), (x,y,z), dp; > module m = a*x*gen(1)+prime(2^29)*y*gen(3), y*gen(2), z*gen(3); > std(m); _[1]=z*gen(3) _[2]=y*gen(2) _[3]=(a)*x*gen(1)+536870909*y*gen(3) > modStd(m); // ** Ip is no standard basis // ** Ip is no standard basis // ** Ip is no standard basis _[1]=z*gen(1) _[2]=y*gen(1) _[3]=x*gen(1) >
Also note the warnings which should not be there.
Note: See
TracTickets for help on using
tickets.
fixed with 8ac0543abc53e49f3dfa217c1250d95fa23928fb