Keeping track of an ever changing vector

Question

Hi,
I have a strange problem that i can't seem to figure out.
i have a vector MemoryPool where early on another vector is added to it.
through further processing the vector that was added to the memory pool has cahnged in the memoryPool and i can't understand why because i don't use the memoryPool anywhere else.
heres a snippet of my code:
Vector BestMatch = new Vector();
BestMatch = t.bestMatch(MemoryPool,Antigen,stimIndex,memPoolStimulation);
          MemoryPool.removeElement(BestMatch);
          //so its at the end of vector
          MemoryPool.add(BestMatch);
          //point 1
          //here the memoryPool has BestMatch at the end
          ARB = t.ARBGeneration(BestMatch,hypermutationRate,clonalRate);
          //point 2
          //here Memory pool has best match at the end but missing a value
          Vector Candidate = c.runARBRefinement(ARB, Antigen, maxDist,stimulationValue,clonalRate, totalResources);     
          //point 3
          //here memoryPool has best match at the end but with added values
          MemoryPool = MS.addCandidateCell(Candidate, MemoryPool, affinityThreshold, affinityThresholdScalar, maxDist);
          ARB.removeAllElements();I want the MemoryPool at point 3 to be the same as point 1 but this isn't the case.
Can anybody try to explain what is going on please?
Cheers

Answer 1

Hi Elodie,
I don't know what happens within the methods ARBGeneration and runARBRefinement. What you could do is writing an monitorable BestMatch class:
import java.util.Vector;
public class BestMatch extends Vector {
     public boolean add(Object o) {
          new Exception("an object was added at the end")
               .printStackTrace();
          return super.add(o);
     public void add(int index,Object o) {
          new Exception("an object was added at index "+index)
               .printStackTrace();
          super.add(index,o);
     public boolean addAll(Collection c) {
          new Exception("a collection was added at the end")
               .printStackTrace();
          return super.addAll(c);
     public boolean addAll(int index,Object o) {
          new Exception("a collection was added at index "+index)
               .printStackTrace();
          return super.addAll(index,c);
     public void addElement(Object o) {
          new Exception("an element was added at the end")
               .printStackTrace();
          return super.addElement(o);
     public Object remove(int index) {
          new Exception("an object was removed at index "+index)
               .printStackTrace();
          return super.remove(index);
     public boolean remove(Object o) {
          new Exception("an object was removed")
               .printStackTrace();
          super.remove(o);
     public boolean removeAll(Collection c) {
          new Exception("a collection was removed")
               .printStackTrace();
          return super.removeAll(c);
     public void removeAllElements() {
          new Exception("all elements were removed")
               .printStackTrace();
          return super.removeAllElements();
     public boolean removeElement(Object o) {
          new Exception("an element was removed")
               .printStackTrace();
          return super.removeElement(o);
     public boolean removeElementAt(int index) {
          new Exception("an element was removed at index "+index)
               .printStackTrace();
          return super.removeElementAt(index);
     public boolean removeRange(int fromIndex, int toIndex) {
          new Exception("all objects from "+formIndex+
                    " to "+toIndex+" were removed")
               .printStackTrace();
          return super.removeElement(o);
}and then make your bestMetch of type BestMatch instead of Vector. This way all add/remove operations that are done in at the bestMatch can be viewed at the screen output.
I haven't tested the code above so there may be some minors in it.
Klaas