<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/varianttools/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/varianttools/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/varianttools/feature-requests/</id><updated>2011-12-09T17:25:05Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Properly handle soft-kill (Ctrl-C)</title><link href="https://sourceforge.net/p/varianttools/feature-requests/5/" rel="alternate"/><published>2011-12-09T17:25:05Z</published><updated>2011-12-09T17:25:05Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netf9db8139f8545e2252f710a60ef92768888f077c</id><summary type="html">Currently, if user press Ctr-C, vtools will exit immediately, leaving possibly a damaged project. We should

1\. at least make sure the project is properly closed before exit
2\. allow a command to quite properly \(e.g. after completion of a task, or reverting to a status before command is executed\)
3\. set a break point where the next command can pick up from the middle.

The method to handle soft-kill signal is listed below.

import signal
import sys
def signal\_handler\(signal, frame\):
print 'You pressed Ctrl+C\!'
sys.exit\(0\)
signal.signal\(signal.SIGINT, signal\_handler\)
print 'Press Ctrl+C'
signal.pause\(\)</summary></entry><entry><title>import_ped</title><link href="https://sourceforge.net/p/varianttools/feature-requests/4/" rel="alternate"/><published>2011-08-02T15:18:16Z</published><updated>2011-08-02T15:18:16Z</updated><author><name>Gao Wang</name><uri>https://sourceforge.net/u/wanggao/</uri></author><id>https://sourceforge.netc9740264e69cba4a8f49273cf0b475e83094d0fb</id><summary type="html">needed to import map/ped file</summary></entry><entry><title> add a force option to forcefully import a file</title><link href="https://sourceforge.net/p/varianttools/feature-requests/3/" rel="alternate"/><published>2011-07-31T03:02:20Z</published><updated>2011-07-31T03:02:20Z</updated><author><name>Gao Wang</name><uri>https://sourceforge.net/u/wanggao/</uri></author><id>https://sourceforge.net5914ce742b8052933bbb0f4127002ce94b152d72</id><summary type="html">We might also add a force option to forcefully import a file, for import\_txt and import\_vcf commands</summary></entry><entry><title>Illustration of the basic idea of vtools</title><link href="https://sourceforge.net/p/varianttools/feature-requests/2/" rel="alternate"/><published>2011-07-16T21:06:17Z</published><updated>2011-07-16T21:06:17Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net6a2cfedc81fdd10305acd52a1ba64f1fbdabfedb</id><summary type="html">Can anyone draw a figure that demonstrates the basic idea of vtools. I am thinking of a figure with a rectangle that are split into blocks of fields and variants

sample stat |   anno db 1 | anno db 2 | imported | statistics
variants \(all\) 

subsets of variants


</summary></entry><entry><title>vtools import_bed</title><link href="https://sourceforge.net/p/varianttools/feature-requests/1/" rel="alternate"/><published>2011-07-16T16:04:22Z</published><updated>2011-07-16T16:04:22Z</updated><author><name>Bo Peng</name><uri>https://sourceforge.net/u/bpeng2000/</uri></author><id>https://sourceforge.netefc484720563b290f2281f793c91069e266df3b5</id><summary type="html">The bed format is a common format to store variants, we should be able to import it.</summary></entry></feed>