<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/varianttools/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/varianttools/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/varianttools/bugs/</id><updated>2011-11-17T18:05:47Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>Remove variant slowness</title><link href="https://sourceforge.net/p/varianttools/bugs/7/" rel="alternate"/><published>2011-11-17T18:05:47Z</published><updated>2011-11-17T18:05:47Z</updated><author><name>Bo Peng</name><uri>https://sourceforge.net/u/bpeng2000/</uri></author><id>https://sourceforge.nete244969af574ea83ac2e614f7a5f28f85ad06c78</id><summary type="html">When I delete a large proportion of variants from a project, 'vtools remove variants table' takes a very long time. This is because the query

'DELETE FROM variant WHERE variant\_id IN \(SELECT variant\_id in table\)' 

needs to update indexes for every record, and remove records one by one is slow. A better method would be to

1\. create a new table temp \(with structure from variant\)
2\. INSERT INTO temp SELECT \* FROM variant WHERE variant IN SELECT variant\_id FROM table\) 
3\. DROP TABLE variant;
4\. rename temp to varant
5\. rebuild indexes.

</summary></entry><entry><title>No module named argparse</title><link href="https://sourceforge.net/p/varianttools/bugs/6/" rel="alternate"/><published>2011-10-21T17:17:38Z</published><updated>2011-10-21T17:17:38Z</updated><author><name>Xavier de Pedro</name><uri>https://sourceforge.net/u/xavidp/</uri></author><id>https://sourceforge.netb157cbfbea7f66c9fdb8721347f21de29f18f3ff</id><summary type="html">Hi\!

I've just discovered your "variant tools" package, and it looks promising\!
I tried installing it on a Ubuntu GNU/Linux 10.04 \(64 bits\), using python 3.1 from repositories. 

Installing it seemed to work \(see output below\), but after attempting to init a project, I get an error message about missing argparse:

\---------------------------------------------------------------
ueb@mainhead:~/varianttools$ vtools init RA
Traceback \(most recent call last\):
File "/usr/local/bin/vtools", line 28, in &amp;lt;module&amp;gt;
import argparse
ImportError: No module named argparse
\----------------------------------------------------------------

Any tip on what can be wrong? May we be missing some package that is not referenced in the variant tools documentation yet? A bug in the code?

Thanks for your feedback, and for releasing your  project with a FLOSS license\!

Cheers

Xavier


Output at installation:
\---------------------------------------------------
ueb@mainhead:~/varianttools$ sudo python3 setup.py install
running install
running build
running build\_py
creating build/lib.linux-x86\_64-3.1
creating build/lib.linux-x86\_64-3.1/variant\_tools
copying variant\_tools/\_\_init\_\_.py -&amp;gt; build/lib.linux-x86\_64-3.1/variant\_tools
copying variant\_tools/utils.py -&amp;gt; build/lib.linux-x86\_64-3.1/variant\_tools
copying variant\_tools/project.py -&amp;gt; build/lib.linux-x86\_64-3.1/variant\_tools
copying variant\_tools/importer.py -&amp;gt; build/lib.linux-x86\_64-3.1/variant\_tools
copying variant\_tools/exporter.py -&amp;gt; build/lib.linux-x86\_64-3.1/variant\_tools
copying variant\_tools/sample.py -&amp;gt; build/lib.linux-x86\_64-3.1/variant\_tools
copying variant\_tools/variant.py -&amp;gt; build/lib.linux-x86\_64-3.1/variant\_tools
copying variant\_tools/annotation.py -&amp;gt; build/lib.linux-x86\_64-3.1/variant\_tools
copying variant\_tools/liftOver.py -&amp;gt; build/lib.linux-x86\_64-3.1/variant\_tools
Skipping implicit fixer: buffer
Skipping implicit fixer: idioms
Skipping implicit fixer: set\_literal
Skipping implicit fixer: ws\_comma
running build\_scripts
creating build/scripts-3.1
copying and adjusting vtools -&amp;gt; build/scripts-3.1
copying and adjusting vtools\_report -&amp;gt; build/scripts-3.1
changing mode of build/scripts-3.1/vtools from 644 to 755
changing mode of build/scripts-3.1/vtools\_report from 644 to 755
running install\_lib
creating /usr/local/lib/python3.1/dist-packages/variant\_tools
copying build/lib.linux-x86\_64-3.1/variant\_tools/annotation.py -&amp;gt; /usr/local/lib/python3.1/dist-packages/variant\_tools
copying build/lib.linux-x86\_64-3.1/variant\_tools/sample.py -&amp;gt; /usr/local/lib/python3.1/dist-packages/variant\_tools
copying build/lib.linux-x86\_64-3.1/variant\_tools/importer.py -&amp;gt; /usr/local/lib/python3.1/dist-packages/variant\_tools
copying build/lib.linux-x86\_64-3.1/variant\_tools/exporter.py -&amp;gt; /usr/local/lib/python3.1/dist-packages/variant\_tools
copying build/lib.linux-x86\_64-3.1/variant\_tools/liftOver.py -&amp;gt; /usr/local/lib/python3.1/dist-packages/variant\_tools
copying build/lib.linux-x86\_64-3.1/variant\_tools/\_\_init\_\_.py -&amp;gt; /usr/local/lib/python3.1/dist-packages/variant\_tools
copying build/lib.linux-x86\_64-3.1/variant\_tools/variant.py -&amp;gt; /usr/local/lib/python3.1/dist-packages/variant\_tools
copying build/lib.linux-x86\_64-3.1/variant\_tools/project.py -&amp;gt; /usr/local/lib/python3.1/dist-packages/variant\_tools
copying build/lib.linux-x86\_64-3.1/variant\_tools/utils.py -&amp;gt; /usr/local/lib/python3.1/dist-packages/variant\_tools
byte-compiling /usr/local/lib/python3.1/dist-packages/variant\_tools/annotation.py to annotation.pyc
byte-compiling /usr/local/lib/python3.1/dist-packages/variant\_tools/sample.py to sample.pyc
byte-compiling /usr/local/lib/python3.1/dist-packages/variant\_tools/importer.py to importer.pyc
byte-compiling /usr/local/lib/python3.1/dist-packages/variant\_tools/exporter.py to exporter.pyc
byte-compiling /usr/local/lib/python3.1/dist-packages/variant\_tools/liftOver.py to liftOver.pyc
byte-compiling /usr/local/lib/python3.1/dist-packages/variant\_tools/\_\_init\_\_.py to \_\_init\_\_.pyc
byte-compiling /usr/local/lib/python3.1/dist-packages/variant\_tools/variant.py to variant.pyc
byte-compiling /usr/local/lib/python3.1/dist-packages/variant\_tools/project.py to project.pyc
byte-compiling /usr/local/lib/python3.1/dist-packages/variant\_tools/utils.py to utils.pyc
running install\_scripts
copying build/scripts-3.1/vtools\_report -&amp;gt; /usr/local/bin
copying build/scripts-3.1/vtools -&amp;gt; /usr/local/bin
changing mode of /usr/local/bin/vtools\_report to 755
changing mode of /usr/local/bin/vtools to 755
running install\_egg\_info
Writing /usr/local/lib/python3.1/dist-packages/variant\_tools-1.0rc2.egg-info
\------------------------------------------------------------------
</summary></entry><entry><title>import_txt: cannot use the alternative reference</title><link href="https://sourceforge.net/p/varianttools/bugs/5/" rel="alternate"/><published>2011-07-28T17:32:25Z</published><updated>2011-07-28T17:32:25Z</updated><author><name>Min Qiao</name><uri>https://sourceforge.net/u/qiaomin/</uri></author><id>https://sourceforge.netd865ddca0335aaf1b8722e5473293d2f02227a83</id><summary type="html">When I use, for example, hg18 as reference, I cannot add hg19 as alternative. In addition, the error prompt is confusing.

% vtools import\_txt ../TSV/input.tsv --build hg18 -c 1 2 4 5
INFO: Opening project myproj.proj
INFO: Importing genotype from ../TSV/input.tsv \(1/1\)
input.tsv: 100.0% \[==========================&amp;gt;\] 131 0.7/s in 00:00:00
INFO: 131 new variants from 131 records are imported, with 0 invalid records.
INFO: All files imported. A total of 131 new records are inserted.

% vtools import\_txt ../TSV/input.tsv --build hg19 -c 1 3 4 5
INFO: Opening project myproj.proj
global name 'valueError' is not defined</summary></entry><entry><title>"import_txt":cannot give me a 2nd chance to properly import </title><link href="https://sourceforge.net/p/varianttools/bugs/4/" rel="alternate"/><published>2011-07-28T17:17:51Z</published><updated>2011-07-28T17:17:51Z</updated><author><name>Min Qiao</name><uri>https://sourceforge.net/u/qiaomin/</uri></author><id>https://sourceforge.net684b6149e24c9d666eb1c87af79da85585ff8a93</id><summary type="html">When I failed to import a txt file due to lack of optional arguments, and tried to import it again correctly, I cannot re-import the same file unless I change its name.

\# First time import
$ vtools import\_txt ../TSV/input.tsv --build hg19
INFO: Opening project myproj.proj
INFO: Importing genotype from ../TSV/input.tsv \(1/1\)
input.tsv: 100.0% \[==============================&amp;gt;\] 131 1.3K/s in 00:00:00
INFO: 0 new variants from 131 records are imported, with 131 invalid records.
INFO: All files imported. A total of 0 new records are inserted.

\# 2nd attempt, fail
$ vtools import\_txt ../TSV/input.tsv --build hg19 -c 1 3 4 5
INFO: Opening project myproj.proj
INFO: Ignoring imported file input.tsv
INFO: All files imported. A total of 0 new records are inserted.

\# Sucess after rename the input file
$ vtools import\_txt ../TSV/input.txt --build hg19 -c 1 3 4 5
INFO: Opening project myproj.proj
INFO: Importing genotype from ../TSV/input.txt \(1/1\)
input.txt: 100.0% \[============================&amp;gt;\] 131 0.8/s in 00:00:00
INFO: 131 new variants from 131 records are imported, with 0 invalid records.
INFO: All files imported. A total of 131 new records are inserted.</summary></entry><entry><title>Cannot run vtools as background job</title><link href="https://sourceforge.net/p/varianttools/bugs/3/" rel="alternate"/><published>2011-07-25T21:14:43Z</published><updated>2011-07-25T21:14:43Z</updated><author><name>Gao Wang</name><uri>https://sourceforge.net/u/wanggao/</uri></author><id>https://sourceforge.net0e5af75ecf7e856ba84425d302715d98e79c8e94</id><summary type="html">Cannot run vtools in the background: when execute time "vtools output ... &amp;" or "vtools import\_vcf ...&amp;" then type "exit" to quit the shell, then the program would quit, too, leaving the exported/imported files incomplete. This should be considered proper exit in Linux and supposedly programs should continue to work.</summary></entry><entry><title>Add -m option.</title><link href="https://sourceforge.net/p/varianttools/bugs/2/" rel="alternate"/><published>2011-07-19T15:55:22Z</published><updated>2011-07-19T15:55:22Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netb92295afd73d862f08909ac165c4151fbc9be3ef</id><summary type="html">Per discussion in http://sourceforge.net/mailarchive/forum.php?thread\_name=CAGX8AEnXojDL2ZqOT63\_fOngz02WqRRdzpEJWVqfxGuptby18Q%40mail.gmail.com&amp;forum\_name=varianttools-devel , we should allow users to specify a message for each variant table.</summary></entry><entry><title>Fail to call vtools from vtools_report under windows.</title><link href="https://sourceforge.net/p/varianttools/bugs/1/" rel="alternate"/><published>2011-07-19T04:20:22Z</published><updated>2011-07-19T04:20:22Z</updated><author><name>Bo Peng</name><uri>https://sourceforge.net/u/bpeng2000/</uri></author><id>https://sourceforge.net963bf5e8bd9147bee6aae6f0648477601db44481</id><summary type="html">Under windows, vtools cannot be executed directly because it must have an extension .py to be recognized as Python file. The installation instruction suggests that windows users rename vtools to vtools.py and vtools\_report to vtools\_report.py. However, vtools\_report.py calls vtools, not vtools.py, so this command will fail under windows.

The windows installer should do something to address this problem.</summary></entry></feed>