cass 0.0.1 → 0.0.2

data/CHANGELOG

@@ -1 +1,7 @@
-v0.0.1. Initial version.
+v0.0.2. 08/04/2010 -- Fixed bugs and added additional output information.
+	- No longer includes narray as a dependency upon installation due to presence of multiple narray gems. User must now manually install the correct version before running CASS.
+	- Fixed minor syntax issues that prevented CASS from running on Ruby 1.8.6 (mostly to do with the splat operator).
+	- Expanded output information; specifying verbose output will now produce more extensive information when CASS runs.
+	- Fixed bug that caused CASS to try (unsuccessfully) to parse all text using the built-in Parser.
+
+v0.0.1. 6/12/2010 -- Initial version.

data/README.rdoc

@@ -2,6 +2,10 @@
 
 CASS (Contrast Analysis of Semantic Similarity) is a set of tools for conducting contrast-based analyses of semantic similarity in text. CASS is based on the BEAGLE model described by Jones and Mewhort (2007). For a more detailed explanation, see Holtzman et al (under review).
 
+== Version
+
+The current version of the tools is 0.0.1 (6/15/2010).
+
 == License
 
 Copyright 2010 Tal Yarkoni and Nick Holtzman. Licensed under the GPL license. See the included LICENSE file for details.
@@ -31,16 +35,16 @@ There are two general ways to use CASS:
 
 === The easy way
 
-For users without prior programming experience, CASS is streamlined to make things as user-friendly as possible. Assuming you've installed CASS per the instructions above, you can run a full CASS analysis just by tweaking a few settings and running the analysis script (run_cass.rb) included in the sample analysis package (cass_sample.zip[http://casstools.org/downloads/cass_sample.zip]). Detailed instructions are available in [this] tutorial; in brief, here's what you need to do to get up and running:
+For users without prior programming experience, CASS is streamlined to make things as user-friendly as possible. Assuming you've installed CASS per the instructions above, you can run a full CASS analysis just by tweaking a few settings and running the analysis script (run_cass.rb) included in the sample analysis package (cass_sample.zip[http://casstools.org/downloads/cass_sample.zip]). Detailed instructions are forthcoming in a more detailed manual; in brief, here's what you need to do to get up and running:
 
 1. Download cass_sample.zip[http://casstools.org/downloads/cass_sample.zip] and unpack it somewhere. The package contains several files that tell CASS what to do, as well as some sample text you can process. These include:
-- contrasts.txt: a specification of the contrasts you'd like to run on the text, one per line. For a detailed explanation of the format, see the [tutorial].
-- default.spec: the main specification file containing all the key settings CASS needs in order to run. All settings are commented, but a more detailed explanation is provided in the [tutorial]. You can create as many .spec files as you like (no need to edit this one repeatedly!), just make sure to edit run_cass.rb to indicate which .spec file to use.
+- contrasts.txt: a specification of the contrasts you'd like to run on the text, one per line. For an explanation of the format the contrasts are in, see the next section.
+- default.spec: the main specification file containing all the key settings CASS needs in order to run. All settings are commented in detail in the file itself. You can create as many .spec files as you like (no need to edit this one repeatedly!), just make sure to edit run_cass.rb to indicate which .spec file to use.
 - stopwords.txt: A sample list of stopwords to exclude from analysis (CASS will use this file by default). These are mostly high-frequency function words that carry little meaning but can strongly bias a text.
 - sample1.txt and sample2.txt: two sample documents to get you started.
 - run_cass.rb: the script you'll use to run CASS.
 
-2. Edit the settings as you please. An explanation of what everything means is in the [tutorial]; if you're just getting started, you can just leave everything as is and run the sample analysis.
+2. Edit the settings as you please. An explanation of what everything means is in the .spec file itself; if you're just getting started, you can just leave everything as is and run the sample analysis.
 
 3. Run run_cass.rb. If you're on Windows, you may be able to double-click on the script to run it; however, if you do that, you won't see any of the output. On most platforms (and optionally on Windows), you'll have to run the script from the command prompt. You can do this by opening up a terminal window (or, in Windows, a command prompt), navigating to the directory that contains the sample analysis files, and typing:
 
@@ -48,7 +52,7 @@ For users without prior programming experience, CASS is streamlined to make thin
 	
 After doing that, you should get a bunch of output showing you exactly what's going on. There should also be some new files in the working directory containing the results of the analysis.
 
-Assuming the analysis ran successfully, you can now set about running your own analyses. We recommend reading the entire [tutorial] before diving in.
+Assuming the analysis ran successfully, you can now set about running your own analyses.
 
 === As a library
 
@@ -82,14 +86,14 @@ If we want to see some information about the contents of our document, we can ty
 	
 And that prints something like this to our screen:
 
-	> Summary for document 'cake.txt':
+	> Summary for document 'cake_vs_spinach':
 	> 4 target words (cake, spinach, good, bad)
 	> 35 words in context.
 	> Using 21 lines (containing at least one target word) for analysis.
 
 Nothing too fancy, just basic descriptive information. The summary method has some additional arguments we could use to get more detailed information (e.g., word_count, list_context, etc.), but we'll skip those for now.
 
-Now if we want to compute the interaction term for our contrast (i.e., the difference of differences, reflecting the equation (cake.good - spinach.bad) - (cake.bad - spinach.good)), all we have to do is:
+Now if we want to compute the interaction term for our contrast (i.e., the difference of differences, reflecting the equation (cake.good - cake.bad) - (spinach.good - spinach.bad)), all we have to do is:
 
 	contrast.apply(doc)
 
@@ -97,29 +101,30 @@ And we get back something that looks like this:
 
 	0.5117	0.4039	0.3256	0.4511	0.2333
 
-Where the first four values represent the similarity between the 4 pairs of words used to generate the interaction term (e.g., the first value reflects the correlation between 'cake' and 'good', the second between 'spinach' and 'bad', and so on), and the fifth is the interaction term. So in this case, the result (0.23) tells us that there's a positive bias in the text, such that cake is semantically more closely related to good (relative to bad) than spinach is. Hypothesis confirmed!
+Where the first four values represent the similarity between the 4 pairs of words used to generate the interaction term (e.g., the first value reflects the correlation between 'cake' and 'good', the second between 'cake' and 'bad', and so on), and the fifth is the interaction term. So in this case, the result (0.23) tells us that there's a positive bias in the text, such that cake is semantically more closely related to good (relative to bad) than spinach is. Hypothesis confirmed!
 
-Well, sort of. By itself, the number 0.23 doesn't mean very much. We don't know what the standard error is, so we have no idea whether 0.23 is a very large number or a very small one that might occur pretty often just by chance. Fortunately, we can generate some bootstrapped p values quite easily. First, we generate the bootstraps:
+Well, sort of. By itself, the number 0.23 doesn't mean very much. We don't know what the standard error is, so we have no idea whether 0.23 is a very large number or a very small one that might occur pretty often just by chance. Fortunately, we can get some p values by bootstrapping a distribution around our observed value. First, we generate the distribution:
 
 	Analysis.bootstrap_test(doc, contrasts, "speech_results.txt", 1000)
 
 Here we call the bootstrap_test method, feeding it the document we want to analyze, the Contrasts we want to apply, the filename root we want to use, and the number of iterations we want to run (generally, as many as is computationally viable). The results will be saved to a plaintext file with the specified name, and we can peruse that file at our leisure. If we open it up, the first few lines look like this:
 
+	contrast	result_id	doc_name	pair_1	pair_2	pair_3	pair_4	interaction_term
 	cake.spinach.good.bad	observed	cake.txt	0.5117	0.4039	0.3256	0.4511	0.2333
-	cake.spinach.good.bad	boot_1	cake.txt	0.4118	0.2569	0.1481	0.4086	0.4154
-	cake.spinach.good.bad	boot_2	cake.txt	0.5321	0.4353	0.4349	0.5396	0.2015
-	cake.spinach.good.bad	boot_3	cake.txt	0.51	0.4216	0.3043	0.6923	0.4764
-	cake.spinach.good.bad	boot_4	cake.txt	0.6222	0.3452	0.238	0.249	0.288
+	cake.spinach.good.bad	boot_1	cake.txt	0.5146	0.4585	0.1885	0.45	0.3176
+	cake.spinach.good.bad	boot_2	cake.txt	0.4606	0.4421	0.2984	0.4563	0.1764
+	cake.spinach.good.bad	boot_3	cake.txt	0.4215	0.438	0.0694	0.5695	0.4836
+	cake.spinach.good.bad	boot_4	cake.txt	0.5734	0.353	0.2094	0.5013	0.5123
 	...
 
 The columns tell us, respectively, what file the results came from, the bootstrap iteration (the first line shows us the actual, or observed value), and the observed interaction terms. Given this information, we can now compare the bootstrapped distribution to zero to test our hypothesis. We do that like this:
 
 	Analysis.p_values("speech_results.txt", 'boot')
 
-...where the first argument specifies the full path to the file containing the bootstrap results we want to summarize, and the second argument indicates the type of test that was conducted (either 'boot' or 'perm'). The results will be written to a file named speech_results_boot_p_values.txt. If we open that document up, we see this:
+...where the first argument specifies the full path to the file containing the bootstrap results we want to summarize, and the second argument indicates the type of test that was conducted (either 'boot' or 'perm'). The results will be written to a file named speech_results_p_values.txt. If we open that document up, we see this:
 
-file	contrast	N	value	p-value
-cake.txt	cake.spinach.good.bad	1000	0.2333	0.0
-cake.txt	mean	1000	0.2333	0.0
+	file	contrast	N	value	p-value
+	cake.txt	cake.spinach.good.bad	1000	0.2333	0.0
+	cake.txt	mean	1000	0.2333	0.0
 
-As you can see, the last column (p-value) reads 0.0, which is to say, none of the 1,000 iterations we ran had a value greater than 0. So we can reject the null hypothesis of zero effect at p < .001 in this case. Put differently, it's exceedingly unlikely that we would get this result (people having a positive bias towards cake relative to spinach) just by chance. Of course, that's a contrived example that won't surprise anyone. But the point is that you can use the CASS tools in a similar way to ask other much more interesting questions about the relation between different terms in semantic space. So that's the end of this overview; to learn more about the other functionality in CASS, read the [tutorial] document, or just surf around this RDoc.
+As you can see, the last column (p-value) reads 0.0, which is to say, none of the 1,000 iterations we ran had a value greater than 0. So we can reject the null hypothesis of zero effect at p < .001 in this case. Put differently, it's exceedingly unlikely that we would get this result (people having a positive bias towards cake relative to spinach) just by chance. Of course, that's a contrived example that won't surprise anyone. But the point is that you can use the CASS tools in a similar way to ask other much more interesting questions about the relation between different terms in semantic space. So that's the end of this overview; to learn more about the other functionality in CASS, you can surf around this RDoc, or just experiment with the software. Eventually, there will be a more comprehensive manual; in the meantime, if you have questions about usage, email[mailto:nick.holtzman@gmail.com] Nick Holtzman, and if you have technical questions about the Ruby code, email[mailto:tyarkoni@gmail.com] Tal Yarkoni.

data/Rakefile

@@ -2,11 +2,15 @@ require 'rubygems'
 require 'rake'
 require 'echoe'
 
-Echoe.new("cass", "0.0.1") { |p|
+Echoe.new("cass", "0.0.2") { |p|
   p.author = "Tal Yarkoni"
   p.email = "tyarkoni@gmail.com"
   p.summary = "A set of tools for conducting Contrast Analyses of Semantic Similarity (CASS)."
   p.url = "http://casstools.org"
   p.docs_host = "http://casstools.org/doc/"
-  p.runtime_dependencies = ['narray >=0.5.9.7']
+  # Currently we don't impose a run-time dependency because narray has different
+  # gems for < 1.9 and >= 1.9. Easier just to tell the user to install
+  # the right one.
+  # p.runtime_dependencies = ['narray >=0.5.9.7']
+  
 }

data/cass.gemspec

@@ -2,11 +2,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{cass}
-  s.version = "0.0.1"
+  s.version = "0.0.2"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 1.2") if s.respond_to? :required_rubygems_version=
   s.authors = ["Tal Yarkoni"]
-  s.date = %q{2010-06-15}
+  s.date = %q{2010-08-04}
   s.description = %q{A set of tools for conducting Contrast Analyses of Semantic Similarity (CASS).}
   s.email = %q{tyarkoni@gmail.com}
   s.extra_rdoc_files = ["CHANGELOG", "LICENSE", "README.rdoc", "lib/cass.rb", "lib/cass/analysis.rb", "lib/cass/context.rb", "lib/cass/contrast.rb", "lib/cass/document.rb", "lib/cass/extensions.rb", "lib/cass/parser.rb", "lib/cass/stats.rb"]
@@ -23,11 +23,8 @@ Gem::Specification.new do |s|
     s.specification_version = 3
 
     if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
-      s.add_runtime_dependency(%q<narray>, [">= 0.5.9.7"])
     else
-      s.add_dependency(%q<narray>, [">= 0.5.9.7"])
     end
   else
-    s.add_dependency(%q<narray>, [">= 0.5.9.7"])
   end
 end

data/lib/cass.rb

@@ -9,6 +9,6 @@ require 'cass/parser'
 
 module Cass
   
-  VERSION = '0.1.0'
+  VERSION = '0.0.2'
   
 end

data/lib/cass/analysis.rb

@@ -1,10 +1,9 @@
 module Cass
   
-  # Instantiates an analysis on one or more Documents.
-  # Currently, only the default processing stream (runSpec)
-  # is implemented. Eventually, direct methods for specific
-  # analyses (e.g., two-document permutation tests) will be
-  # supported.
+  # Various methods used to conduct analyses on one or more Documents.
+  # The primary processing stream is run_spec, which is essentially
+  # a wrapper arouond the other methods for conducting one and
+  # two-sample tests. 
   class Analysis
   
     attr_accessor :docs, :contexts, :targets
@@ -17,26 +16,34 @@ module Cass
       abort("Error: can't find spec file (#{spec_file}).") if !File.exist?(spec_file)
       load spec_file
       abort("Error: can't find contrast file (#{CONTRAST_FILE}).") if !File.exist?(CONTRAST_FILE) 
+      
+      # Create options hash
+      opts = {}
+      # Ruby 1.9 returns constants as symbols, 1.8.6 uses strings, so standardize
+      consts = Module.constants.map { |c| c.to_s }
+      %w[PARSE_TEXT N_PERM N_BOOT MAX_LINES RECODE CONTEXT_SIZE MIN_PROP STOP_FILE NORMALIZE_WEIGHTS VERBOSE].each { |c|
+        opts[c.downcase] = Module.const_get(c) if consts.include?(c)  
+      }
+      
+      if VERBOSE
+        puts "\nRunning CASS with the following options:"
+        opts.each { |k,v| puts "\t#{k}: #{v}" }
+      end
+      
       contrasts = parse_contrasts(CONTRAST_FILE)
     
       # Create contrasts
-      puts "Found #{contrasts.size} contrasts." if VERBOSE
+      puts "\nFound #{contrasts.size} contrasts." if VERBOSE
       
       # Set targets
       targets = contrasts.inject([]) { |t, c| t += c.words.flatten }.uniq
-      puts "Found #{targets.size} target words." if VERBOSE
-      
-      # Create options hash
-      opts = {}
-      %w[PARSE_TEXT N_PERM N_BOOT MAX_LINES RECODE CONTEXT_SIZE MIN_PROP STOP_FILE NORMALIZE_WEIGHTS].each { |c|
-        opts[c.downcase] = Module.const_get(c) if Module.constants.include?(c)  
-      }
+      puts "\nFound #{targets.size} target words." if VERBOSE
       
       # Read in files and create documents
       docs = []
       FILES.each { |f| 
         abort("Error: can't find input file #{f}.") if !File.exist?(f)
-        puts "Reading in file #{f}..."
+        puts "\nReading in file #{f}..."
         text = File.new(f).read
         docs << Document.new(f.split(/\//)[-1], targets, text, opts)
       }
@@ -55,15 +62,15 @@ module Cass
           base = File.basename(d.name, '.txt')
           puts "\nRunning one-sample analysis on document '#{d.name}'."
           puts "Generating #{n_perm} bootstraps..." if VERBOSE and STATS
-          bootstrap_test(d, contrasts, "#{OUTPUT_ROOT}_#{base}_results.txt", n_perm)
+          bootstrap_test(d, contrasts, "#{OUTPUT_ROOT}_#{base}_results.txt", n_perm, opts)
           p_values("#{OUTPUT_ROOT}_#{base}_results.txt", 'boot', true) if STATS
         }
         
       when 2
-        abort("Error: in order to run a permutation test, you need to pass exactly two files as input.") if FILES.size != 2
+        abort("Error: in order to run a permutation test, you need to pass exactly two files as input.") if FILES.size != 2 or docs.size != 2
         puts "Running two-sample comparison between '#{File.basename(FILES[0])}' and '#{File.basename(FILES[1])}'." if VERBOSE
         puts "Generating #{n_perm} permutations..." if VERBOSE and STATS
-        permutation_test(*docs, contrasts, "#{OUTPUT_ROOT}_results.txt", n_perm)
+        permutation_test(docs[0], docs[1], contrasts, "#{OUTPUT_ROOT}_results.txt", n_perm, opts)
         p_values("#{OUTPUT_ROOT}_results.txt", 'perm', true)
       
       # No other test types implemented for now.
@@ -84,8 +91,13 @@ module Cass
     # * contrasts: an array of Contrasts used to compare the documents
     # * output_file: name of output file
     # * n_perm: number of permutations to run
-    def self.permutation_test(doc1, doc2, contrasts, output_file, n_perm)
+    # * opts: an optional hash of additional settings. Currently, only
+    # 'verbose' and 'normalize_weights' apply here.
+    def self.permutation_test(doc1, doc2, contrasts, output_file, n_perm, opts={})
 
+      # Merge options with defaults
+      opts = {'verbose'=>true, 'normalize_weights'=>false }.merge(opts)
+      
       # Merge contexts. Could change this later to allow different contexts for each
       # document, but that would make processing substantially slower.
       context = doc1.context
@@ -94,8 +106,8 @@ module Cass
       doc1.context, doc2.context = context, context
 
       # Generate cooccurrence matrices and get observed difference.
-      doc1.cooccurrence(NORMALIZE_WEIGHTS)
-      doc2.cooccurrence(NORMALIZE_WEIGHTS)
+      doc1.cooccurrence(opts['normalize_weights'])
+      doc2.cooccurrence(opts['normalize_weights'])
     
       outf = File.new(output_file,'w')
       outf.puts "contrast\titeration\t#{doc1.name}\t#{doc2.name}\tdifference"
@@ -108,10 +120,10 @@ module Cass
       # Run permutations and save results
       d1, d2 = doc1.clone, doc2.clone
       n_perm.times { |i|
-        puts "\n\nRunning permutation #{i+1}..."
+        puts "Running permutation #{i+1}..." if opts['verbose']
         d1.clines, d2.clines = permute_labels(doc1.clines, doc2.clines)
-        d1.cooccurrence(NORMALIZE_WEIGHTS)
-        d2.cooccurrence(NORMALIZE_WEIGHTS)
+        d1.cooccurrence(opts['normalize_weights'])
+        d2.cooccurrence(opts['normalize_weights'])
         contrasts.each { |c|
           res1, res2, diff = compare_docs(c, d1, d2)
           outf.puts "#{c.words.join(".")}\tperm_#{i+1}\t#{res1}\t#{res2}\t#{diff}"
@@ -124,23 +136,28 @@ module Cass
     # * contrasts: an array of Contrast objects to apply
     # * output_file: name of output file
     # * n_boot: number of bootstrap iterations to run
-    def self.bootstrap_test(doc, contrasts, output_file, n_boot)
-    
+    # * opts: an optional hash of additional settings. Currently, only
+    # 'verbose' and 'normalize_weights' apply here.
+    def self.bootstrap_test(doc, contrasts, output_file, n_boot, opts={})
+
+      # Merge options with defaults
+      opts = {'verbose'=>true, 'normalize_weights'=>false }.merge(opts)
+          
       outf = File.new(output_file,'w')
       outf.puts(%w[contrast result_id doc_name pair_1 pair_2 pair_3 pair_4 interaction_term].join("\t"))	  
   		outf.sync = true
 		
-  		doc.cooccurrence(NORMALIZE_WEIGHTS)
+  		doc.cooccurrence(opts['normalize_weights'])
       contrasts.each { |c|
   			observed = c.apply(doc)
   			outf.puts "#{c.words.join(".")}\tobserved\t#{observed}"
   		}
   		d1 = doc.clone
   		n_boot.times { |i|
-  			puts "\n\nRunning bootstrap iteration #{i+1}..." if VERBOSE
+  			puts "Running bootstrap iteration #{i+1}..." if opts['verbose']
   			d1.clines = doc.resample(clines=true)
   			# d1.context = Context.new(d1)   # Currently uses the same context; can uncomment
-  			d1.cooccurrence(NORMALIZE_WEIGHTS)
+  			d1.cooccurrence(opts['normalize_weights'])
   			contrasts.each { |c|
   				res = c.apply(d1)
   				outf.puts "#{c.words.join(".")}\tboot_#{i+1}\t#{res}"

data/lib/cass/context.rb

@@ -9,6 +9,7 @@ module Cass
       min_prop = opts['min_prop'] || 0
       max_prop = opts['max_prop'] || 1
       puts "Creating new context..." if VERBOSE
+      puts "Using all words with token frequency in range of #{min_prop} and #{max_prop}."
       words = doc.lines.join(' ').split(/\s+/)
       nwords = words.size
       puts "Found #{nwords} words."
@@ -21,7 +22,15 @@ module Cass
         words.uniq!
       end
       # words = words - doc.targets
-      words -= opts['stop_file'].read.split(/\s+/) if opts.key?('stop_file')
+      if opts.key?('stop_file') and !opts['stop_file'].empty?
+        begin
+          stopwords = File.new(opts['stop_file']).read.split(/\s+/)
+        rescue
+          abort("Error: could not open stopword file #{opts['stop_file']}!")
+        end
+        puts "Removing #{stopwords.size} stopwords from context." if VERBOSE
+        words -= stopwords
+      end
       @words = opts.key?('context_size') ? words.sort_by{rand}[0, opts['context_size']] : words
       index_words
       puts "Using #{@words.size} words as context." if VERBOSE

data/lib/cass/document.rb

@@ -54,19 +54,19 @@ module Cass
     # skip certain preprocessing steps, on the assumption that
     # these have already been performed.
     def parse(opts={})
-      if opts.key?('skip_preproc')
+      if opts['skip_preproc']
         @lines = (text.class == Array) ? @text : text.split(/[\r\n]+/)
       else
         puts "Converting to lowercase..." if VERBOSE
-        @text.downcase! unless opts.key?('keep_case')
-        @text.gsub!(/[^a-z \n]+/, '') unless opts.key('keep_special')
+        @text.downcase! unless opts['keep_case']
+        @text.gsub!(/[^a-z \n]+/, '') unless opts['keep_special']
         if opts.key?('recode')
           puts "Recoding words..." if VERBOSE
           opts['recode'].each { |k,v| @text.gsub!(/(^|\s+)(#{k})($|\s+)/, "\\1#{v}\\3") }
         end
         puts "Parsing text..." if VERBOSE
-        @lines = opts.key?('parse_text') ? Parser.parse(@text, opts) : @text.split(/[\r\n]+/)
-        @lines = @lines[0, opts['max_lines']] if opts.key?('max_lines')
+        @lines = opts['parse_text'] ? Parser.parse(@text, opts) : @text.split(/[\r\n]+/)
+        @lines = @lines[0, opts['max_lines']] if opts['max_lines'] and opts['max_lines'] > 0
         trim!
       end
     end
@@ -217,7 +217,7 @@ module Cass
       
       # Basic info that always gets shown
       buffer << "Summary for document '#{@name}':"
-      buffer << "#{@targets.size} target words (#{@targets.join (", ")})"
+      buffer << "#{@targets.size} target words (#{@targets.join(", ")})"
       buffer << "#{@context.words.size} words in context."
       buffer << "Using #{@clines.size} lines (containing at least one target word) for analysis."
       

data/lib/cass/parser.rb

@@ -27,7 +27,7 @@ module Cass
         spfail = true
       end
     
-      if spfail or opts.key?('parser_basic')
+      if spfail or opts['parser_basic'] == true
         puts "Using a basic parser to split text into sentences. Note that this is intended as a last resort only; you are strongly encouraged to process all input texts yourself and make sure that lines are broken up the way you want them to be (with each line on a new line of text in the file). If you use this parser, we make no guarantees about the quality of the output."
         rx = opts.key?('parser_regex') ? opts['parser_regex'] : "[\r\n\.]+"
         text.split(/#{rx}/)

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: cass
 version: !ruby/object:Gem::Version 
-  hash: 29
+  hash: 27
   prerelease: false
   segments: 
   - 0
   - 0
-  - 1
-  version: 0.0.1
+  - 2
+  version: 0.0.2
 platform: ruby
 authors: 
 - Tal Yarkoni
@@ -15,26 +15,10 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-06-15 00:00:00 -06:00
+date: 2010-08-04 00:00:00 -06:00
 default_executable: 
-dependencies: 
-- !ruby/object:Gem::Dependency 
-  name: narray
-  prerelease: false
-  requirement: &id001 !ruby/object:Gem::Requirement 
-    none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        hash: 77
-        segments: 
-        - 0
-        - 5
-        - 9
-        - 7
-        version: 0.5.9.7
-  type: :runtime
-  version_requirements: *id001
+dependencies: []
+
 description: A set of tools for conducting Contrast Analyses of Semantic Similarity (CASS).
 email: tyarkoni@gmail.com
 executables: []