Adds character spans to all time operators

[bethard]

All the time operators in Types.scala now have character offsets, and they're read in from the Anafora XML when present. The eventual goal is to be able to get rid of the redundant TimeExpression class in TemporalNeuralParser.

[bethard]

I have now also modified the APIs so that they all return either org.clulab.timenorm.formal.TimeExpression or com.codecommit.antixml.Elem, and removed all the redundant types that were declared in TemporalNeuralParser.

I have not maintained the duration calculations since those are not so useful when you have access to the real org.clulab.timenorm.formal.TimeExpression objects. I think those hacks belong in Eidos, not in timenorm.

[EgoLaparra]

I have realized that we are not including properties without values into the xml, so all <none> cases fail when running the scorer. Besides that, everything seems to run fine.

[bethard]

Which version of the scorer are you using? I updated anaforatools about 3 weeks ago to make a missing property and an empty property equivalent.

Also, what command are you running, so I can do the same locally and make sure I'm getting the same scores too?

[EgoLaparra]

Great. I have updated it. I am evaluating the 3 document from the South Sudan corpus. I exclude Season-Of-Year to compare to the result we have in the slides of the Virtual Site Visit.

python -m anafora.evaluate -r ~/Documents/Projects/WM/SixMonthEval/Test/ -p ~/Documents/Projects/WM/SixMonthEval/OnlyTextOuts/ -e Event Modifier Season-Of-Year

The results for the identification are slightly different, 70.8 vs 70.5. We didn't report any result for parsing, now I'm getting 46.4. Time to revisit the rules.

[EgoLaparra]

The model we are using in the scala version is the combination of News+Colon, so the results are not totally comparable to the published ones and this could explain the differences you are observing.

I've seen that the change in the performance is caused by a drop in the precision, right?. This drop happens also in the identification and, besides Operators, Periods and Calendar-Intervals are also highly affected. This seems to fit the fact that we are including the Colon data.

[bethard]

The version from my last commit gets 0.610 for the complete task (identification + parsing) on the TempEval 2013 test set. I copy-pasted back in the version from master, made the absolute minimum amount of changes for it to work with the changed APIs, and got exactly the same F1. So it looks like my translation of that code is at least not making anything worse.