Hi Alan, https://dl.dropboxusercontent.com/u/69741069/cross_querying.rar
Not sure if this is what you're after but it establishes a relationship between the parent and the clone which enables the parent to later query the clone's attributes and set data on itself. It's quite hacky in that the only way I could quickly get a parent to know which particles it had cloned was via Get Closest Points on instantiation of the clones. In this scene the parent looks up the second strand position in the clone and shows you the resulting vector. I tried to figure out the ID allocation (making assumptions, for example, that the cloned particle would have the next ID along from its parent but that didn't seem to work) and it would be interesting to understand better how ICE allocates IDs to clones.
On the other hand, I think it would be more elegant to do your stuff the other way round - it's always much easier to give a clone the id of its parent since it can directly inherit a custom attribute based on the original particles ID and then always find it again using ID to Location. So, in your case, maybe have the strand on the original particle and querying that from the cloned one (using the easier ID to Location stuff)?
Julian
