2040

14
+4  Q:

## Finding a single number in a list

What would be the best algorithm for finding a number that occurs only once in a list which has all other numbers occurring exactly twice.

So, in the list of integers (lets take it as an array) each integer repeats exactly twice, except one. To find that one, what is the best algorithm.

A:

You need to specify what you mean by "best" - to some, speed is all that matters and would qualify an answer as "best" - for others, they might forgive a few hundred milliseconds if the solution was more readable.

"Best" is subjective unless you are more specific.

That said:

Iterate through the numbers, for each number search the list for that number and when you reach the number that returns only a 1 for the number of search results, you are done.

+5  A:

O(N) time, O(N) memory

HT= Hash Table

HT.clear() go over the list in order for each item you see

``````if(HT.Contains(item)) -> HT.Remove(item)
else
``````

at the end, the item in the HT is the item you are looking for.

Note (credit @Jared Updike): This system will find all Odd instances of items.

comment: I don't see how can people vote up solutions that give you NLogN performance. in which universe is that "better" ? I am even more shocked you marked the accepted answer s NLogN solution...

I do agree however that if memory is required to be constant, then NLogN would be (so far) the best solution.

I don't see an accepted answer now, I wonder how that got unaccepted. Incidentally, I would have marked an accepted answer based on the answers available at the time. Also, accepted doesn't mean Best :)
Your's isn't that great either: it uses O(n) memory.
look at the first line, in bold: I explicitly say it is O(N) time, O(N) memoryso you are not criticizing my suggestion for anything I didn't point out already.
+1  A:

I would say that using a sorting algorithm and then going through the sorted list to find the number is a good way to do it.

And now the problem is finding "the best" sorting algorithm. There are a lot of sorting algorithms, each of them with its strong and weak points, so this is quite a complicated question. The Wikipedia entry seems like a nice source of info on that.

A:

Seems like the best you could do is to iterate through the list, for every item add it to a list of "seen" items or else remove it from the "seen" if it's already there, and at the end your list of "seen" items will include the singular element. This is O(n) in regards to time and n in regards to space (in the worst case, it will be much better if the list is sorted).

The fact that they're integers doesn't really factor in, since there's nothing special you can do with adding them up... is there?

Question

I don't understand why the selected answer is "best" by any standard. O(N*lgN) > O(N), and it changes the list (or else creates a copy of it, which is still more expensive in space and time). Am I missing something?

A:

I think that csmba's method is probably about as good as you can do.

Sorting the list first doesn't make any sense because then you have to evaluate each item for the sort, then evaluate the sorted list afterwards. You should only need to go through the list once.

A:

@csmba: Since you're criticizing the O(N*LogN) solution... can you elaborate on the performance of your solution? I'm not an expert in algoriths, but yours seems a little worse...

A:

You could simply put the elements in the set into a hash until you find a collision. In ruby, this is a one-liner.

``````def find_dupe(array)
h={}
array.detect { |e| h[e]||(h[e]=true; false) }
end
``````

So, `find_dupe([1,2,3,4,5,1])` would return 1.

This is actually a common "trick" interview question though. It is normally about a list of consecutive integers with one duplicate. In this case the interviewer is often looking for you to use the Gaussian sum of n-integers trick e.g. `n*(n+1)/2` subtracted from the actual sum. The textbook answer is something like this.

``````def find_dupe_for_consecutive_integers(array)
n=array.size-1   # subtract one from array.size because of the dupe
array.sum - n*(n+1)/2
end
``````
A:

Depends on how large/small/diverse the numbers are though. A radix sort might be applicable which would reduce the sorting time of the O(N log N) solution by a large degree.

A:

@csmba

You might want to mention that HT stands for Hash table and specify that you are starting with an empty HT.

Also of note: your approach finds all elements that occur an odd number of times.

+59  A:

The fastest (O(n)) and most memory efficient (O(1)) way is with the XOR operation.

In C:

``````int arr[] = {3, 2, 5, 2, 1, 5, 3};

int num = 0, i;

for (i=0; i < 7; i++)
num ^= arr[i];

printf("%i\n", num);
``````

This prints "1", which is the only one that occurs once.

This works because the first time you hit a number it marks the num variable with itself, and the second time it unmarks num with itself (more or less). The only one that remains unmarked is your non-duplicate.

this is the "best" solution as long as you can actually XOR the items. Meaning, it depends on the data type. I am not sure if you can do this or not if the items are strings. of course, in that case it can be solved with one more layer of abstraction...
There are ways of XORing strings by XORing the individual chars - you would just have to have a temporary variable as large as the largest string. What wouldn't work is trying to XOR a linked list or some other complicated data structure, but this problem is simply about integers.
You could do it with any object you can take a cryptographically secure hash of, too. It just requires a second pass to figure out which item you matched. :)
Clever solution, but I think that negative numbers might screw it up a little. You could potentially XOR in a mask which entirely threw off the rest of your masking results.
A negative number is a bitfield just like a positive number. XOR doesn't care
Of course, you must document the function as such that it will only work if there is only one sole number and the rest are in even pairs. Though I do love the solution you posted :)
+4  A:

By the way, you can expand on this idea to very quickly find two unique numbers among a list of duplicates.

Let's call the unique numbers a and b. First take the XOR of everything, as Kyle suggested. What we get is a^b. We know a^b != 0, since a != b. Choose any 1 bit of a^b, and use that as a mask -- in more detail: choose x as a power of 2 so that x & (a^b) is nonzero.

Now split the list into two sublists -- one sublist contains all numbers y with y&x == 0, and the rest go in the other sublist. By the way we chose x, we know that a and b are in different buckets. We also know that each pair of duplicates is still in the same bucket. So we can now apply ye olde "XOR-em-all" trick to each bucket independently, and discover what a and b are completely.

Bam.

+1  A:

Clearly, the guy has a point. This entire thread is retarded. Making certain reasonable assumptions, his solution (Kyle's) is the best possible.

A:

The sorting method and the XOR method have the same time complexity. The XOR method is only O(n) if you assume that bitwise XOR of two strings is a constant time operation. This is equivalent to saying that the size of the integers in the array is bounded by a constant. In that case you can use Radix sort to sort the array in O(n).

If the numbers are not bounded, then bitwise XOR takes time O(k) where k is the length of the bit string, and the XOR method takes O(nk). Now again Radix sort will sort the array in time O(nk).

+1  A:

Kyle's solution would obviously not catch situations were the data set does not follow the rules. If all numbers were in pairs the algorithm would give a result of zero, the exact same value as if zero would be the only value with single occurance.

If there were multiple single occurance values or triples, the result would be errouness as well.

Testing the data set might well end up with a more costly algorithm, either in memory or time.

Csmba's solution does show some errouness data (no or more then one single occurence value), but not other (quadrouples). Regarding his solution, depending on the implementation of HT, either memory and/or time is more then O(n).

If we cannot be sure about the correctness of the input set, sorting and counting or using a hashtable counting occurances with the integer itself being the hash key would both be feasible.