-
Registered User
Thanks for your answers.
And sorry that I didn't react, but I was on holidays *g*
I got answers in the project's forum, and they want the results for lower values too, to be sure, that they didn't miss anything in a "pre-sieve-phase" or something. So, I'll keep the range.
-
Moderator
no problem
In most cases please stick with the project supplied dat or get everyone to switch for a good reason based on efficency. Even if the one that's currently being used is not optimal the headache from switching dats is
Shirinking the range is less of a problem but only when all tests are double checked with matching residuals and yada yada, even then the speed increase is generally not worth it.
Or the speed increase you get now is offset by the "non-optimal approach of sieve at higher n values" ( somewhat difficult to explain ) when you cut the high end.
Anyways I thought my first response was at least somewhat humorous, did anyone else get it?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules