-npr stage2_norm messing

firejuggler · 2013-09-03, 01:06

on the C178 i'm working on, the default npr give

Code:

R0: -6163573546672968242255135989697165
R1: 739618031188734043
A0: 629226877951340829676857716785479684410208
A1: 127760965365329647685569066274757276
A2: -374372760578712799259543217578
A3: 4538508589990243715003
A4: 25034222885267304
A5: 506017512
skew 4280944.79, size 1.251e-017, alpha -7.333, combined = 7.834e-014 rroots = 5

if I modify my stage 2 norm between 14e23 and 25e23 it slightly improve, to

Code:

R0: -6163573546595863062503710465714415
R1: 739618031188734043
A0: 898308088167298363834393218755622749665608
A1: 49965972628334682552481864995120696
A2: -371315167867738021006955029328
A3: 15032773832611814483003
A4: 25297984513397304
A5: 506017512
skew 4319301.76, size 1.303e-017, alpha -7.377, combined = 7.974e-014 rroots = 5

Down to 27e23 upto 1e35, it is the same as the 'default'
If I reduce it down to 13e23 , no poly is found above a min score of 7e-014
So can we consider the *sweet pot' of a C178 between 16e23 and 2e24(note : the default stage2 norm is at 2.44e25)?

firejuggler · 2013-09-03, 01:34

ok, nevermind, each poly has to be optimised individually, too bad.

2013-09-03, 01:34	#2
firejuggler Apr 2010 Over the rainbow 2³·5²·13 Posts	ok, nevermind, each poly has to be optimised individually, too bad. Last fiddled with by firejuggler on 2013-09-03 at 02:15