Comparing results from codes used for the old and new S3 tuning

I performed a preliminary tuning of the S3 playground data which can be found here. However when I reanalysed the tuning procedure which is described here, results seem to differ. Particularly the tripple coincident efficiency seems to have changed between the two runs. Hence I took the code in cvs v 1.164 and the one used for the old run (tmpexe/20050304/) and ran on a subset of data(400 sec.s) both with and without the injections. Results from both the codes match totally with each other. So I suspect that the diff. in 50% efficiency is probably due to some statistical effects

0-lag with current code

This is the script used for the run: [script]
This is the trigger file: [triggers]

0-lag with old code

This is the script used for the run: [script]
This is the trigger file: [triggers]

The diff between the two trigger files is here. As one may see from this that the triggers produced by both the codes are identically same.

Injection with current code

This is the script used to generate sim_burst(binj function): [inj script]
This is the script used for the run: [script]
This is the injection file: [injections]
This is the trigger file: [triggers]

Injection with old code

To ensure that we do the exact same injections as in the run with new code, I copied the injections and just deleted the distance column from them.

This is the script used to generate sim_burst(oldbinj function): [inj script]
This is the script used for the run: [script]
This is the injection file: [injections]
This is the trigger file: [triggers]

The diff between the two trigger files is here. As one may see from this that the triggers produced by both the codes are identically same.