Avoid breaking up unit circle components during shift permutations by enforcing (shift%2==0)

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1115 483481f0-a63c-0410-a8a8-396719eec1a4
Attempt at rendering the generation of determinsitic vectors at Search time consistent with the "-elementalmethod" flag use elsewhere.

So we'd now configure this using -queryvectorfile orthographic and and -elementalmethod,  for example:

java -cp semanticvectors-5.5.jar pitt.search.semanticvectors.Search -queryvectorfile deterministic -vectortype binary -dimension 8000 -searchvectorfile elementalvectors.bin -elementalmethod contenthash prozac


git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1116 483481f0-a63c-0410-a8a8-396719eec1a4
Updated the "PROXIMITY" method, so that the same set of demarcator vectors are used for the left and right side of the sliding window - as permutation is used to encode directionality, there's no need to have more than (windowradius+2) demarcator vectors (including alpha and omega, which we'd rather not include as this would make the beginning of the left window orthogonal to the end of it). 

This also means that the distances on the left are consistent with those on the right, which would not have been the case previously in the complex and real vector representations. 

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1117 483481f0-a63c-0410-a8a8-396719eec1a4
Numerous small modifications to accommodate more flexible command line PSI queries with QI in mind. One of these is definitely temporary - "-bindnotreleasehack", which will ultimately be replaced by an expanded query syntax with a different symbol for bind and release.

Nonetheless, it seemed worth checking in the status quo.

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1121 483481f0-a63c-0410-a8a8-396719eec1a4
Added interface to Lucene document search

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1122 483481f0-a63c-0410-a8a8-396719eec1a4
Factoring out results-printing methods to simplify main flow of Search.java.

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1123 483481f0-a63c-0410-a8a8-396719eec1a4
This may have been the root of the issue with "GetGlobalTermWeightFromString" I ran into awhile back - changed the variable that is returned from an int to a float.

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1124 483481f0-a63c-0410-a8a8-396719eec1a4
Added weighting for PSI searches 

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1125 483481f0-a63c-0410-a8a8-396719eec1a4
Added term weighting for PSI query vector generation - but only for the single query string edition (e.g. P(X)+E(Y)*S(Z))

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1126 483481f0-a63c-0410-a8a8-396719eec1a4
First attempt at batch search, i.e. hold vectors in RAM and work through a list of queries in a text file (one per line).

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1127 483481f0-a63c-0410-a8a8-396719eec1a4
Not a definitive change, but it does seem worth being consistent with respect to the Hermitian vs. Angular debate - prior to this change we had angular normalization with hermitian overlap. I'll look into making these consistent in accordance with the flag I seem to recall you created awhile back, but thought I'd check this in as a record of what was used for the QI submission.

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1128 483481f0-a63c-0410-a8a8-396719eec1a4
Cleaned up the PROXIMITY sliding window code, such that permutation affects the demarcator vectors only, and the permuted demarcator vectors are output to facilitate queries along the lines of:

 "E(king)*P(-1)"
Opening elemental query vector store from file: deterministic
Opening semantic query vector store from file: proxtermvectors.bin
Opening predicate query vector store from file: numbervectors.bin
Opening search vector store from file: proxtermvectors.bin
Searching term vectors, searchtype BOUNDPRODUCT
Found vector for '-1'
Search output follows ...
12.726996:minos
12.423948:aegeus
11.939073:midas
10.666273:lear
8.423721:cheng

Interestingly, this allows for a (very simple) sort of analogy query:
"E(king)*S(minos)*E(duke)"
Search output follows ...
5.511599:ellington

"E(king)*S(minos)*E(queen)"...
6.596088:sheba
5.246219:victoria
4.796262:anne's
4.410585:elizabeth
4.282026:finches



git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1129 483481f0-a63c-0410-a8a8-396719eec1a4
Added a command line flag, -mintermlength, that allows for the specification of a minimum term length so as to exclude single characters and such if need be. 

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1137 483481f0-a63c-0410-a8a8-396719eec1a4
Fixed what I believe I broke with the last commit (a call to TermFilter that didn't include the new parameter)

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1138 483481f0-a63c-0410-a8a8-396719eec1a4
Some improvements to the Pathfinder implementation, courtesy of Roger Schvaneveldt

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1139 483481f0-a63c-0410-a8a8-396719eec1a4
A small detail, to get the direction of the arrows right for "INV" predications.

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1140 483481f0-a63c-0410-a8a8-396719eec1a4
Introducing experiments using learned character vectors. Some refactoring and testing of orthography code to support learned character vectors.

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1143 483481f0-a63c-0410-a8a8-396719eec1a4
Improved logging messages to include contentsField.

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1144 483481f0-a63c-0410-a8a8-396719eec1a4
Presidents tabular datasets.

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1145 483481f0-a63c-0410-a8a8-396719eec1a4
Informative exceptions here and there.

git-svn-id: http://semanticvectors.googlecode.com/svn/trunk@1146 483481f0-a63c-0410-a8a8-396719eec1a4