identical agilent v3 and v4 resources

[anoronh4]

We found in roslin_resources.json that certain resources were identical between AgilentExon_51MB_b37_v3 and Agilent_v4_51MB_Human. The baits files had the exact positional info and the targets files also had the exact same positional info. For example:

## Targets
$ cut -f1-3 /juno/work/ci/resources/roslin_resources/targets/Agilent_v4_51MB_Human/b37/Agilent_v4_51MB_Human_b37_targets.bed  | md5sum
e3cc9b442b6cd483adb840b80af5bc58  -
$ cut -f 1-3 /juno/work/ci/resources/roslin_resources/targets/AgilentExon_51MB_b37_v3/b37/AgilentExon_51MB_b37_v3_targets.bed | md5sum 
e3cc9b442b6cd483adb840b80af5bc58  -
## Baits
$ cut -f1-3 /juno/work/ci/resources/roslin_resources/targets/Agilent_v4_51MB_Human/b37/Agilent_v4_51MB_Human_b37_baits.bed  | md5sum
facb4d6e88281100d5e7f6ec72a3a94f  -
$ cut -f 1-3 /juno/work/ci/resources/roslin_resources/targets/AgilentExon_51MB_b37_v3/b37/AgilentExon_51MB_b37_v3_baits.bed | md5sum 
facb4d6e88281100d5e7f6ec72a3a94f  -

We thought this was strange because the versions should certainly have different positions, and we have double-checked by downloading the bed files directly from agilent.

Would it be possible to know more info about how the resources were generated, and if there is a potential mix-up in the bed files?