Fix old bug when accessing an int as an array

This is due to an inconsistent representation of activities in different transformers. Thanks to Erik Mallory for catching this!

This still needs to be tested thoroughly.