"not a valid id code"

[itang1]

run_all_postannotation has a problem with some of the annotIDs, mainly those attached to %coms

Examples

Example 1

*************************
Running Script: run_all_postannotation.rb on project: 27_11_sparse_code
*************************
Cell# 81:  "0xb7d171" is not a valid id code (this id is not in the list of used IDs)
Cell# 82:  "0x621e95" is not a valid id code (this id is not in the list of used IDs)

Script has finished running.

Example 2

*************************
Running Script: run_all_postannotation.rb on project: 14_08_sparse_code
*************************
Cell# 146:  "0x3d62c1" is not a valid id code (this id is not in the list of used IDs)

Script has finished running.

Example 3

*************************
Running Script: run_all_postannotation.rb on project: 18_11_sparse_code
*************************
Cell# 22:  "0xf96e8f" is not a valid id code (this id is not in the list of used IDs)
Cell# 163:  "0x42bd86" is not a valid id code (this id is not in the list of used IDs)

Script has finished running.

Example 4

*************************
Running Script: run_all_postannotation.rb on project: 08_12_sparse_code
*************************
Cell# 184:  "0x6d134a" is not a valid id code (this id is not in the list of used IDs)
Cell# 210:  "0x723b04" is not a valid id code (this id is not in the list of used IDs)
Cell# 236:  "0xed8f80" is not a valid id code (this id is not in the list of used IDs)

Script has finished running.

Analysis

• all of these cells are comments (%com); both point cells and non-point cells
• there are other %coms elsewhere throughout, and those received no complaint
• ran the script a few times, the complaints about these particular cells always appear every time
• all of these annotid's are indeed not listed in usedID.txt
• there used to be more of these not-a-valid-id-complaints, corresponding to %pho cells. but since all %pho cells got deleted recently, all of those complaints disappeared

[itang1]

Add'l note about usedID truncating

We concluded that add_annotid.rb sometimes causes usedID.txt to truncate, especially if you run it twice in a row on the same file.

Below are two errors associated with truncation. They were both generated after I took the following actions:

1. ran add_annot_video -- it added two new annotIDS as intended
2. ran add_annot_video again for sanity -- script error (see below for the two example errors that we discovered); we've verified that here is where the truncation occurs.
3. ran add_annot_video again for sanit -- script has finished running successfully with no problems

We do not know why two different errors (possibly more undiscovered errors would result from the same set of actions.

The effect of this is that run_all_postannotation.rb then flags way too many annotations as not having a valid id code, since their IDs were purged from usedID.txt.

Example error 1

*************************
Running Script: add_annotid_video.rb on project: 10_15_sparse_code
*************************
***** SCRIPT ERROR *****
org.jruby.embed.EvalFailedException: java.nio.BufferOverflowException
*************************

Example error 2

*************************
Running Script: add_annotid_video.rb on project: 10_15_sparse_code
*************************
TypeError: can't convert nil into String
  initialize at org/jruby/RubyFile.java:363
        open at org/jruby/RubyIO.java:1179
      (root) at <script>:79
***** SCRIPT ERROR *****
TypeError: can't convert nil into String
  initialize at org/jruby/RubyFile.java:363
        open at org/jruby/RubyIO.java:1179
      (root) at <script>:79
See line 79 of /Volumes/pn-opus/Seedlings/Scripts_and_Apps/Github/seedlings/datavyu/add_annotid_video.rb:
	File.open($usedIDFile, 'w') {
*************************