I'm also thinking that we should probably fix this for the RELS-INT version as well. I believe it also has a function that is very similar, that assumes a lot about the datastream not changing under your feet. It may be possible to do a little refactor so that the initalize function is shared and have some code reuse, but we should at least catch the same error in that initialization code.