{5} Assigned, Active Tickets by Owner (Full Description) (3 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

dreyer (1 match)

Ticket Summary Component Milestone Type Created
Description
#435 Extension polybori.lib dontKnow 3-1-5 and higher proposed feature Jul 4, 2012

Maximilian Kammermeier and Susanne Scherer just finished polybori.lib for wrapping PolyBoRi via pyobjdect.), see attached. Now, PolyBoRi can be used in a very Singular-ish way: 

  LIB "polybori.lib";

  ring r0=2,x(1..4),lp;
  poly f1=x(1)^2+2*x(2)*(x(3))-x(4)^3;
  poly f2=x(1)^2-x(3)*x(1);
  poly f3=x(2)+5-2*x(1);
  poly f4=x(1)*x(2)-x(3);
  ideal I=f1,f2,f3,f4;

  bideal bI = I;          // Convert to PolyBoRi data structues and add x(i)^2-x(i)
  bideal bRes = std(bI);  // actually calls PolyBoRi 

  ideal I2 = ideal(bRes); // convert back ...
  std(bRes[1..2]);        // ... or continue within PolyBoRi

This is the first shoot, so any comments are welcome!

Note: In addition to pyobject.so it needs the most recent development version of Singular as well as PolyBoRi installed in the search path of python or Singular.

hannes (1 match)

Ticket Summary Component Milestone Type Created
Description
#483 omalloc alignment wrong on 32-bit SPARC omalloc 3-2-0 and higher bug Apr 9, 2013

When building Singular on the following system (relevant is the 32-bit SPARC processor) 

$ uname -a
SunOS mark 5.10 Generic_127111-01 sun4u sparc SUNW,Sun-Blade-2500

accesses to 64-bit integers must be aligned to 8 bytes, otherwise Singular crashes with a Bus Error signal. However, omalloc/configure fails to detect this problem. gdb session (Singular running within Sage): 

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1 (LWP 1)]
0xf9f743ac in add_to_basis_ideal_quotient (h=0x4f170dc, c=0x4f16b38, ip=0x0) at tgb.cc:1518
1518      c->weighted_lengths[i] = pQuality (h, c, c->lengths[i]);
(gdb) list
1513      }
1514      else
1515        pNorm (h);
1516      pNormalize (h);
1517
1518      c->weighted_lengths[i] = pQuality (h, c, c->lengths[i]);
1519      c->gcd_of_terms[i] = got;
1520    #ifdef HAVE_BOOST
1521      c->states.push_back (dynamic_bitset <> (i));
1522
(gdb) print c->weighted_lengths
$5 = (wlen_type *) 0x4f4659c

Here, wlen_type is a 64-bit integer at a non-8-byte aligned address.

Configuring with --with-align=8 fixes the issue. This should probably be handled in omalloc/configure. I am unable to provide a patch since I don't understand what the various alignment options (8 vs. strict vs. sloppy) mean and this doesn't seem to be documented.

Oleksandr (1 match)

Ticket Summary Component Milestone Type Created
Description
#717 resolution inconsistencies dontKnow 4-1-0 and higher bug Mar 20, 2015

Here is an example, in which minres minimizes the resolution correctly if not printed beforehand, but does not minimize the resolution if printed beforehand. 

ring r = (0,w),(Y(1..4),z),(c,dp(4),dp(1));
ideal H = Y(4)-3*z^2+24*z-39, 3*Y(3)+(-w)*Y(4), z^2-8*z+13;
qring q = std(H);
ideal inI = Y(1),(w^2)*Y(4);
minres(res(inI,0));
resolution resInI = res(inI,0); // q^1 <- q^2 <- q^1 
minres(resInI); // minimizes correctly to q^1 <- q^1

ring r = (0,w),(Y(1..4),z),(c,dp(4),dp(1));
ideal H = Y(4)-3*z^2+24*z-39, 3*Y(3)+(-w)*Y(4), z^2-8*z+13;
qring q = std(H);
ideal inI = Y(1),(w^2)*Y(4);
minres(res(inI,0));
resolution resInI = res(inI,0); // q^1 <- q^2 <- q^1 
resInI;
minres(resInI); // remains q^1 <- q^2 <- q^1
Note: See TracReports for help on using and creating reports.