Eric Riebling

I had another possibly crazy idea to make the repos/ folder reside on the host, not exclusively in the VM. This would enable people to 'git pull' a particular repo...

oh yes I remember running ELAN and discovering it had menu options  to directly import other formats, but not RTTM. Wasn't CLAN one of the formats?

gues it was export, not import

I just learned yesterday, there is only 1 line of RTTM produced, because the result applies to an entire audio file. "aha!" :)

Will we enforce the 10th "SLAT" column of RTTM, or make it optional? I"m not sure our tools treat it consistently but should probably accept both 9 and 10 fields...

This is great to have RTTM formats be better standardized. I know there is one tool which may still produce improperly formatted RTTM; http://github.com/srvk/TALNet I believe uses double quotes around...

I'd like to add: any RTTM our tools _produce_ will use the Space character to separate fields, but just to err on the side of caution, maybe our tools should...

Progress on this: can now run evalSad.sh (which uses dscore now, not ldc_sad_hmm) in a way such as this: ``` vagrant@vagrant-ubuntu-trusty-64:/vagrant$ evalSad.sh data/VanDam-Daylong/BN32/test noisemesSad --keep-temp mkdir -p /vagrant/data/VanDam-Daylong/BN32/test/temp_ref creating: /vagrant/data/VanDam-Daylong/BN32/test/temp_ref/BN32_010007_test.lab...

dscore's score_batch.py only produces the columns we see, with facility to "by hand" add additional column/value pairs. I don't see anywhere in the code's internal documentation or usage info ```...

oh! I somehow failed to look for code in perl files... this looks like where M FA and AE can be exposed! But will take some hacking...