Skip to content

Release v0.29.0

Choose a tag to compare

@github-actions github-actions released this 31 May 12:13
1b0e8e5

This release brings two additions to the interface. They should make it more easy to work with unpackaged genotype files.

trident genoconvert gets the option -o/--outPackagePath, which allows to redirect the conversion output to any directory. If the input data is read from a POSEIDON package and this option is used, then the POSEIDON.yml file of the source package is not updated.

The second, more significant change is an additional interface option to input unpackaged genotype data. This affects the trident subcommands init, genoconvert and forge. Besides the verbose interface with -r + -g + -s + -i, it is now also possible to only give -p/--genoOne to fully describe one unpackaged genotype data set. -p takes one of the genotype data files (so .bed, .bim or .fam for PLINK or .geno, .snp or .ind for EIGENSTRAT) and determines based on its extension the data format (PLINK/EIGENSTRAT) and the paths to the other files forming the dataset (assuming they have the same name and are in the same directory).

Coming back to the forge example below for V 0.28.0, we can now for example write:

trident forge \
  -d 2017_GonzalesFortesCurrentBiology \
  -p 2017_HaberAJHG/2017_HaberAJHG.bed \
  -p 2018_VeeramahPNAS/2018_VeeramahPNAS.bed \
  -f "<STR241.SG>,<ERS1790729.SG>,Iberia_HG.SG" \
  -o testpackage

So we replaced the verbose

-r PLINK -g 2017_HaberAJHG/2017_HaberAJHG.bed -s 2017_HaberAJHG/2017_HaberAJHG.bim -i 2017_HaberAJHG/2017_HaberAJHG.fam
-r PLINK -g 2018_VeeramahPNAS/2018_VeeramahPNAS.bed -i 2018_VeeramahPNAS/2018_VeeramahPNAS.fam -s 2018_VeeramahPNAS/2018_VeeramahPNAS.bim

with a much more concise

-p 2017_HaberAJHG/2017_HaberAJHG.bed
-p 2018_VeeramahPNAS/2018_VeeramahPNAS.bed

to the same effect.