You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
problem:
sometimes you need to run run_all_postannotation several times before it executes successfully.
this seems to occur universally across macs. unknown if this happened w/ PCs (@sarpu might possibly recall?). this seems also to occur both when working through the pn-opus network drive, and when using local clones of the script and .opf.
example:
in the example below, run_all_postannotation ran successfully on the third try. in general, the number of tries it takes is random. the order and kinds of complaints are random as well.
analysis:
it looks like run_all_postannotation has sporadic difficulties with accessing library methods
1) FIRST TRY: angry
*************************
Running Script: run_all_postannotation.rb on project: 09_12_sparse_code
*************************
NoMethodError: private method `getVariable' called for nil:NilClass
get_column at file:/Applications/datavyu.app/Contents/Java/datavyu-1.3.7-jfx.jar!/Datavyu_API.rb:722
(root) at <script>:255
each at org/jruby/RubyArray.java:1613
(root) at <script>:253
***** SCRIPT ERROR *****
NoMethodError: private method `getVariable' called for nil:NilClass
get_column at file:/Applications/datavyu.app/Contents/Java/datavyu-1.3.7-jfx.jar!/Datavyu_API.rb:722
(root) at <script>:255
each at org/jruby/RubyArray.java:1613
(root) at <script>:253
See line 253 of /Volumes/pn-opus/Seedlings/Scripts_and_Apps/Github/seedlings/datavyu/run_all_postannotation.rb:
for column in columns
See line 255 of /Volumes/pn-opus/Seedlings/Scripts_and_Apps/Github/seedlings/datavyu/run_all_postannotation.rb:
col = get_column(column)
*************************
2) SECOND TRY: angry in a different way
now, change nothing, just run it again
*************************
Running Script: run_all_postannotation.rb on project: 09_12_sparse_code
*************************
NoMethodError: undefined method `include?' for nil:NilClass
checkCodes at <script>:19
(root) at <script>:84
each at org/jruby/RubyArray.java:1613
(root) at <script>:77
each at org/jruby/RubyArray.java:1613
(root) at <script>:72
See line 72 of /Volumes/pn-opus/Seedlings/Scripts_and_Apps/Github/seedlings/datavyu/run_all_postannotation.rb:
for column in columns
See line 77 of /Volumes/pn-opus/Seedlings/Scripts_and_Apps/Github/seedlings/datavyu/run_all_postannotation.rb:
for cell in col.cells
See line 84 of /Volumes/pn-opus/Seedlings/Scripts_and_Apps/Github/seedlings/datavyu/run_all_postannotation.rb:
checkCodes(cell)
See line 19 of /Volumes/pn-opus/Seedlings/Scripts_and_Apps/Github/seedlings/datavyu/run_all_postannotation.rb:
if not $valid_utt_type.include?(cell.utterance_type.to_s)
*************************
3) THIRD TRY: no longer angry, successfully points out errors
still change nothing, just run it again
*************************
Running Script: run_all_postannotation.rb on project: 09_12_sparse_code
*************************
intervals ERROR: onset is greater than offset: [Column] labeled_object [Cell#]: 144
The text was updated successfully, but these errors were encountered:
I am looking into this. I had tried to debug these before, and inconclusively, I think they are network drive issues, but will come up with a definitive answer. In the meanwhile, for testing, could you run the scripts by cloning this repo to your own machine@itang1 ? If we don't get them that way, then that is a big hint that this is due to network drive. Also, keep the issues coming, I like them :)
problem:
sometimes you need to run
run_all_postannotation
several times before it executes successfully.this seems to occur universally across macs. unknown if this happened w/ PCs (@sarpu might possibly recall?). this seems also to occur both when working through the pn-opus network drive, and when using local clones of the script and .opf.
example:
in the example below,
run_all_postannotation
ran successfully on the third try. in general, the number of tries it takes is random. the order and kinds of complaints are random as well.analysis:
it looks like
run_all_postannotation
has sporadic difficulties with accessing library methods1) FIRST TRY: angry
2) SECOND TRY: angry in a different way
now, change nothing, just run it again
3) THIRD TRY: no longer angry, successfully points out errors
still change nothing, just run it again
The text was updated successfully, but these errors were encountered: