View Single Post
Old 2016-11-19, 23:04   #1
EdH
 
EdH's Avatar
 
"Ed Hall"
Dec 2009
Adirondack Mtns

114168 Posts
Default factmsieve.py Questions

I'm using factmsieve.py in a scripted method with several machines to distribute sieving across them. They use the spairs.add feature to collect all the relations and have them incorporated into the .dat file on each check. The way I am doing this, is probably quite rough, but it is working seemingly (to me) well. (If anyone is interested, I will provide further details later.

For now, my first question is how I can modify factmsieve.py (or, something else) to take smaller steps for its qintsize. Is qstep (or, qintsize) calculated, or from a table? I'm expecting to work with ~120-140 digit composites.

My reason to want to decrease the size, is that with all the extra machines adding relations, I get some real oversieving sometimes. A recent c131 gave me a situation where factmsieve.py checked at ~91.5%, so it assigned the next set of tasks. But, by the time it finished those, enough relations had been added from the other machines to take the count over 150%.

My next question has to do with polynomial pair selection. Is there a method to aggregate polynomials from external source machines, similar to the spairs.add feature for relations gathering?

Alternately, can I just "cat" them to one of the files and would the entire file contents be considered when the best poly is chosen by msieve (or, factmsieve.py)?

Last question for now, if I can describe it correctly, is with my composites around 130 digits +/- 10, do I need to be sure the external (to the main) poly searching machines are deconflicted in their search regions? If so, what is my best method? Is there a program related way to determine where msieve has chosen (via factmsieve.py) to work?

Thanks for all your help...
EdH is offline   Reply With Quote