mersenneforum.org  

Go Back   mersenneforum.org > Factoring Projects > Msieve

Reply
 
Thread Tools
Old 2016-11-19, 23:04   #1
EdH
 
EdH's Avatar
 
"Ed Hall"
Dec 2009
Adirondack Mtns

5,101 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
Old 2016-11-20, 00:06   #2
Brian Gladman
 
Brian Gladman's Avatar
 
May 2008
Worcester, United Kingdom

72×11 Posts
Default

The values used for quintsize (and hence qstep) are set by the def-par.txt file. The format of lines in this file are described in the file while individual lines set out the parameters used for various size factoring jobs. I believe that you should be able to do what you want by modifying appropriate lines to suit your needs (note however that factmsieve.py changes the values for very large jobs of 160 digits or more).
Brian Gladman is offline   Reply With Quote
Old 2016-11-20, 01:37   #3
EdH
 
EdH's Avatar
 
"Ed Hall"
Dec 2009
Adirondack Mtns

117558 Posts
Default

Quote:
Originally Posted by Brian Gladman View Post
The values used for quintsize (and hence qstep) are set by the def-par.txt file. The format of lines in this file are described in the file while individual lines set out the parameters used for various size factoring jobs. I believe that you should be able to do what you want by modifying appropriate lines to suit your needs (note however that factmsieve.py changes the values for very large jobs of 160 digits or more).
Thank you.

I thought perhaps I had done something a few years ago in that file, but I couldn't see a correlation with any of its lines and a recent run. Now that I know that is the place, I can work out my needs.

I had seen the section of code for 160+ digit composites. I almost altered it before noticing it was for that size and above.

Thanks for all.
EdH is offline   Reply With Quote
Old 2016-11-22, 17:47   #4
EdH
 
EdH's Avatar
 
"Ed Hall"
Dec 2009
Adirondack Mtns

5,101 Posts
Default

Quote:
Originally Posted by Brian Gladman View Post
The values used for quintsize (and hence qstep) are set by the def-par.txt file. The format of lines in this file are described in the file while individual lines set out the parameters used for various size factoring jobs. I believe that you should be able to do what you want by modifying appropriate lines to suit your needs (note however that factmsieve.py changes the values for very large jobs of 160 digits or more).
Hey Brian,

I finally figured out (read correctly) the section of code I was trying to manage. I was missing that fact_pl['digs'] was equal to digits / 0.72 and therefore any composite over 115 digits was handled by the "if fact_p['digs' >= 160:" section, instead of def-par.txt. So, therefore factmsieve.py changes the values for composites over 115 digits.

Thanks for all,
Ed
EdH is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
Estimated relations Factmsieve cimpresovec Msieve 21 2016-01-17 15:58
I am new Running Factmsieve i am Stuck please help zukhruf Msieve 2 2015-11-25 12:58
Finding factmsieve.py ThomRuley Msieve 2 2015-06-27 04:23
I am very new to factoring and factmsieve Hailstone Msieve 10 2015-01-08 03:34
Factmsieve.py acting strange ThomRuley Msieve 11 2013-11-26 02:38

All times are UTC. The time now is 08:41.


Sun Dec 4 08:41:08 UTC 2022 up 108 days, 6:09, 0 users, load averages: 1.46, 1.02, 0.91

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.

≠ ± ∓ ÷ × · − √ ‰ ⊗ ⊕ ⊖ ⊘ ⊙ ≤ ≥ ≦ ≧ ≨ ≩ ≺ ≻ ≼ ≽ ⊏ ⊐ ⊑ ⊒ ² ³ °
∠ ∟ ° ≅ ~ ‖ ⟂ ⫛
≡ ≜ ≈ ∝ ∞ ≪ ≫ ⌊⌋ ⌈⌉ ∘ ∏ ∐ ∑ ∧ ∨ ∩ ∪ ⨀ ⊕ ⊗ 𝖕 𝖖 𝖗 ⊲ ⊳
∅ ∖ ∁ ↦ ↣ ∩ ∪ ⊆ ⊂ ⊄ ⊊ ⊇ ⊃ ⊅ ⊋ ⊖ ∈ ∉ ∋ ∌ ℕ ℤ ℚ ℝ ℂ ℵ ℶ ℷ ℸ 𝓟
¬ ∨ ∧ ⊕ → ← ⇒ ⇐ ⇔ ∀ ∃ ∄ ∴ ∵ ⊤ ⊥ ⊢ ⊨ ⫤ ⊣ … ⋯ ⋮ ⋰ ⋱
∫ ∬ ∭ ∮ ∯ ∰ ∇ ∆ δ ∂ ℱ ℒ ℓ
𝛢𝛼 𝛣𝛽 𝛤𝛾 𝛥𝛿 𝛦𝜀𝜖 𝛧𝜁 𝛨𝜂 𝛩𝜃𝜗 𝛪𝜄 𝛫𝜅 𝛬𝜆 𝛭𝜇 𝛮𝜈 𝛯𝜉 𝛰𝜊 𝛱𝜋 𝛲𝜌 𝛴𝜎𝜍 𝛵𝜏 𝛶𝜐 𝛷𝜙𝜑 𝛸𝜒 𝛹𝜓 𝛺𝜔