konstantint/pyliftover

Issues

• different hg19 positions map to the same hg38 position

  #17 opened 2 years ago by LuoPangpang
  2

• Missing Output for Some Positions

  #16 opened 2 years ago by matty234
  2

• PAR1 and PAR2 liftover from hg19 to hg38?

  #15 opened 3 years ago by Shicheng-Guo
  1

• Interesting mapping and re-mapping results. Expert opinion please???

  #13 opened 4 years ago by Peter-J-Freeman
  1

• Difference from binary liftOver

  #14 opened 4 years ago by rkimoakbioinformatics
  0

• weird liftover

  #12 opened 5 years ago by wyatt-t-clark
  0

• Problem converting hg38 to hg19

  #11 opened 5 years ago by nicokrez
  2

• coordinate 2bp shift for some and not for others

  #10 opened 5 years ago by zhangtaowhu
  7

• problem with loading canFam3ToHg38.over.chain

  #9 opened 5 years ago by rkimoakbioinformatics
  6

• Deprecation warning - urlopen

  #7 opened 5 years ago by TeriForey
  1

• Conversion results may differ from what is obtained with LiftOver

  #8 opened 5 years ago by yvancluet
  1

• empty return for hg19 to hg38

  #6 opened 7 years ago by Seb-Leb
  1

• convert_coordinate fails with zero-based indices (but unity-based works)

  #5 opened 7 years ago by ofrei
  4

• Incorrect liftover from hg38 to scaffold in hg19

  #2 opened 9 years ago by iljungr
  5

• pyliftover won't map some locations on chr1 from hg38 to hg19

  #3 opened 9 years ago by iljungr
  1

• Some incorrect conversions from hg38 to hg19 even on '+' strand

  #4 opened 9 years ago by iljungr
  1