<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/varianttools/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/varianttools/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 09 Dec 2011 17:25:05 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/varianttools/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Properly handle soft-kill (Ctrl-C)</title><link>https://sourceforge.net/p/varianttools/feature-requests/5/</link><description>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\(\)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 09 Dec 2011 17:25:05 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netf9db8139f8545e2252f710a60ef92768888f077c</guid></item><item><title>import_ped</title><link>https://sourceforge.net/p/varianttools/feature-requests/4/</link><description>needed to import map/ped file</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gao Wang</dc:creator><pubDate>Tue, 02 Aug 2011 15:18:16 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netc9740264e69cba4a8f49273cf0b475e83094d0fb</guid></item><item><title> add a force option to forcefully import a file</title><link>https://sourceforge.net/p/varianttools/feature-requests/3/</link><description>We might also add a force option to forcefully import a file, for import\_txt and import\_vcf commands</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gao Wang</dc:creator><pubDate>Sun, 31 Jul 2011 03:02:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net5914ce742b8052933bbb0f4127002ce94b152d72</guid></item><item><title>Illustration of the basic idea of vtools</title><link>https://sourceforge.net/p/varianttools/feature-requests/2/</link><description>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


</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sat, 16 Jul 2011 21:06:17 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net6a2cfedc81fdd10305acd52a1ba64f1fbdabfedb</guid></item><item><title>vtools import_bed</title><link>https://sourceforge.net/p/varianttools/feature-requests/1/</link><description>The bed format is a common format to store variants, we should be able to import it.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bo Peng</dc:creator><pubDate>Sat, 16 Jul 2011 16:04:22 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netefc484720563b290f2281f793c91069e266df3b5</guid></item></channel></rss>