[QUOTE=wombatman;452363]I readily admit I have no idea what it should be and am going with YAFU's choices. If anybody can suggest some good rules of thumb, I'm all ears.:smile:[/QUOTE]

No worries - this composite is beyond what Yafu's original design parameters from years ago. The polynomial is what it is, but the sieving parameters often need a bit of tweaking.

11040:i10009 on 14e
 

Job entitled "11040:i10009" is next in the 14e queue. Is this name going to cause problems with Windows machines as discussed [url=http://www.mersenneforum.org/showthread.php?t=20024&page=80]earlier in posts 870-872 of this thread[/url]?

Another OPN from the [URL=http://www.lirmm.fr/~ochem/opn/t500.txt]t500[/URL] file.

17189128703^23-1 (C198) SNFS-246

[QUOTE=swellman;452443]Job entitled "11040:i10009" is next in the 14e queue. Is this name going to cause problems with Windows machines as discussed [URL="http://www.mersenneforum.org/showthread.php?t=20024&page=80"]earlier in posts 870-872 of this thread[/URL]?[/QUOTE]

Poly named correctly as C160_11040_10009.

[QUOTE=unconnected;452461]Poly named correctly as C160_11040_10009.[/QUOTE]

Ok I'll shut up now :-).

[QUOTE=unconnected;452461][QUOTE=swellman;452443]Job entitled "11040:i10009" is next in the 14e queue. Is this name going to cause problems with Windows machines as discussed [url=http://www.mersenneforum.org/showthread.php?t=20024&page=80]earlier in posts 870-872 of this thread[/url]?[/QUOTE]

Poly named correctly as C160_11040_10009.[/QUOTE]

Yeah, there's a distinction between the "Name" which functions as a unique ID for numbers in the queue (and is also used for the naming of work files), and "Display name" which is what actually shows up on the status page (in the column labeled "Name" of course).

It's the ID which can't have any questionable characters, since it's used for file names. As Dmitry said, the ID for this particular number, which is what appears when the server hands out work, is C160_11040_10009, so it should be fine.

[QUOTE=RichD;452458]Another OPN from the [URL=http://www.lirmm.fr/~ochem/opn/t500.txt]t500[/URL] file.

17189128703^23-1 (C198) SNFS-246[/QUOTE]

This one sieves really badly and pretty much just needs to be a 15e job.

Which means we're out of new 14e candidates and sieving the last one in the queue. Does anybody have any good ones?

I was afraid of that. How about the following from the same file?

1727870509^23-1 (C196) SNFS-222

[QUOTE=jyb;452543]This one sieves really badly and pretty much just needs to be a 15e job.

Which means we're out of new 14e candidates and sieving the last one in the queue. Does anybody have any good ones?[/QUOTE]
I've C162 from aliquot sequence 842592, running poly select for it now.

13*2^792-1:
[code]# 13*2^792-1 difficulty: 240
n: 66550801146937079103992492175872914857940591301476171283380617092315776829518809046492004774878541988107461118430923903657718756354189489215744823922285881259537614063082698043500928020281
m: 5444517870735015415413993718908291383296
type: snfs
skew: 1.53
c6: 13
c0: -1
rlim: 110000000
alim: 110000000
lpbr: 32
lpba: 32
mfbr: 64
mfba: 64
rlambda: 2.7
alambda: 2.7[/code]
ECM'ed to 2.4t50. With 32LP, target 340-350M rels; I'd like to do LA when ready.

Poly for C162 from aliquot sequence 842592.

[CODE]n: 868347356005122985615018760925237076252576211185291927037972365629369515625168105175451670164964539413087823848439528991318405466048138600755392043193731720352681
skew: 6434585.17
c0: -1286035186241687506780441717878407121546
c1: -1750691765895045653927709391211289
c2: -222403686364331708431746696
c3: 64178599865917602326
c4: -1846268782180
c5: 387600
Y0: -18623527690680223075484694980779
Y1: 244728030520968961
rlim: 60000000
alim: 60000000
lpbr: 30
lpba: 30
mfbr: 60
mfba: 60
rlambda: 2.6
alambda: 2.6
lss: 0[/CODE]