Suppose we want to generate a list of primes p for which p + 2 is also prime.
A quick solution is to generate a complete list of the first n primes and use the Select function to return the elements which meet the condition.
Select[Table[Prime[k], {k, n}], PrimeQ[# + 2] &]
However, this is inefficient as it loads a large list into the memory before returning the filtered list. A For loop with Sow/Reap (or l = {}; AppendTo[l, k]
) solves the memory issue, but it is far from elegant and is cumbersome to implement a number of times in a Mathematica script.
Reap[
For[k = 1, k <= n, k++,
p = Prime[k];
If[PrimeQ[p + 2], Sow[p]]
]
][[-1, 1]]
An ideal solution would be a built-in function which allows an option similar to this.
Table[Prime[k], {k, n}, AddIf -> PrimeQ[# + 2] &]
You can perhaps try something like this:
If you want both the prime
p
and the primep+2
, then the solution isI think the Reap/Sow approach is likely to be most efficient in terms of memory usage. Some alternatives might be:
Or (this one might need some sort of DeleteCases to eliminate Null results):
Both hold a big list of integers 1 to K in memory, but the Primes are scoped inside the With[] construct.
Well, someone has to allocate memory somewhere for the full table size, since it is not known before hand what the final size will be.
In the good old days before functional programming :), this sort of thing was solved by allocating the maximum array size, and then using a separate index to insert to it so no holes are made. Like this
Yes, this is another answer. Another alternative that includes the flavour of the Reap/Sow approach and the FoldList approach would be to use Scan.
Again, this involves a long list of integers, but the intermediate Prime results are not stored because they are in the local scope of With. Because p is a constant in the scope of the With function, you can use With rather than Module, and gain a bit of speed.
I will interpret this more as a question about automation and software engineering rather than about the specific problem at hand, and given a large number of solutions posted already.
Reap
andSow
are good means (possibly, the best in the symbolic setting) to collect intermediate results. Let us just make it general, to avoid code duplication.What we need is to write a higher-order function. I will not do anything radically new, but will simply package your solution to make it more generally applicable:
The advantages of using
Do
overFor
are that the loop variable is localized dynamically (so, no global modifications for it outside the scope ofDo
), and also the iterator syntax ofDo
is closer to that ofTable
(Do
is also slightly faster).Now, here is the usage
EDIT
This version is closer to the syntax you mentioned (it takes an expression rather than a function):
It has an added advantage that you may even have iterator symbols defined globally, since they are passed unevaluated and dynamically localized. Examples of use:
Note that since the syntax is different now, we had to use the
Hold
-attribute to prevent the passed expressionexpr
from premature evaluation.EDIT 2
Per @Simon's request, here is the generalization for many dimensions:
It is considerably less trivial, since I had to
Sow
the indices together with the added values, and then split the resulting flat list according to the indices. Here is an example of use:I assigned the values to
i,j,k
iterator variables to illustrate that this function does localize the iterator variables and is insensitive to possible global values for them. To check the result, we may useTable
and then delete the elements not satisfying the condition:Note that I did not do extensive checks so the current version may contain bugs and needs some more testing.
EDIT 3 - BUG FIX
Note the important bug-fix: in all functions, I now use
Sow
with a custom unique tag, andReap
as well. Without this change, the functions would not work properly when expression they evaluate also usesSow
. This is a general situation withReap
-Sow
, and resembles that for exceptions (Throw
-Catch
).EDIT 4 -
SyntaxInformation
Since this is such a potentially useful function, it is nice to make it behave more like a built-in function. First we add syntax highlighting and basic argument checking through
Then, adding a usage message allows the menu item "Make Template" (
Shift+Ctrl+k
) to work:A more complete and formatted usage message can be found in this gist.
Here's another couple of alternatives using
NextPrime
:and a modification of your Reap/Sow solution that lets you specify the maximum prime:
The above are in order of increasing speed.