Running FunSeq2 through the online application

Q:
I’m trying to run FunSeq2 through the online application. I’ve tried a few times over the past few days, but always get this error message: "Sorry, but the requested page is unavailable due to a server hiccup." Can you please advise?

I am still not able to run FunSeq2 online; I’m getting the same error message as before. I also downloaded the source scripts and can run example input, however, it is extremely slow when trying to run >1,000 input SNPs (20hr+ on cluster computing). I noticed that Supplemental Table 5 says it can process 2,000 SNPs in 2 minutes – is this for the online version only?

Do you have suggestions for working with the online version? I’ve tried tab delimited .bed and a mix of double spacing for the positions and tabs for the alleles .bed (as suggested by the ARVIN method), and neither work for me.

A:
I have double-checked the webserver and done some testing, the server works as usual. But I noticed some input formatting may cause the error you had. for example, please follow the format we suggested, and use <tab> delimiter not space. If you still have problems, could you share your input file, so we can help to figure out the problem?

However, considering the webserver is based on an old version of FunSeq2, we recommend you use our latest version. We have also prepared a pre-calculated whole-genome score on hg19 and hg38(leftover). You just need to download the score and use tabix tools and bed to query. For details, please refer http://funseq2.gersteinlab.org/downloads

Funseq2 Web Server

Q:
The Funseq2 Web Server goes down these days. Would it be available in the next few days?

A:
The Funseq2 web server is up and running now. It has some suspicious activity on the server recently and we are keeping on monitoring it.
If you are submitting your own query, please try to use the correct format, or it will shows ‘service unavailable’ service.

As an alternative, you can also download the whole genome annotations for both hg19 and hg38 from funseq3.gersteinlab.org, then use tabix to query.

Running FunSeq

Q:
I recently read your paper on Funseq, and I am pretty interested in using it in solving some of my interested questions regarding cortex plasticiy. However, I’m not very familiar with Linux/UNIX running environment for this software, and what I have is just a mac laptop….Could you give me some information about how I could use this software on a mac computer, or where I could find some useful information instructing me how I could use this software on a mac computer?

A:
You should be able to download this software on a mac and use it.
You can download it from funseq.gersteinlab.org.

Since you are not familiar with downloading software, have you tried to use the online version at http://funseq.gersteinlab.org/analysis .
You can upload your file and see what you get.

interested in Funseq2

Q:
I found your paper regarding to Funseq2 and quite interested at how do you assign weight or calculated weight for each category. From weighted scoring schema, I could see different categories have different weight, but I am not sure how do you decide them .

A lot bit about me: I am interested pediatric genetic diseases and working on a birth cohort at Beijing Children Hospital as assistant professor.

A:
It’s an entropy-based scheme in the paper. It’s also described in
various FunSeq lectures (on lectures.gersteinlab.org).

The details of Funseq2 can be found in our paper: https://genomebiology.biomedcentral.com/articles/10.1186/s13059-014-0480-5. Simply, In Funseq2, we firstly to define a weighted score for each feature based on their distribution of features in random selected common variants. Discrete and continuous features use slightly different way (refer the formula 1 and 2 in the paper).
for a discrete feature, like ‘In sensitive regions’: [see image]

if there are 20 out of 2000000 random common variants are overlapping with sensitive regions, the Pd will be 20/2000000 = 0.0001 , then [see image]
will be used to get the weight for ‘In sensitive regions’

For the continuous feature, it uses:
[see image]

Ask for the information of data funseq

Q:
I have downloaded the Whole genome scores(hg19) both Version 2.1.6 and 2.1.0 in the project website you provided http://funseq2.gersteinlab.org/downloads. There no score when I queried the codign region, but in the Whole Genome Query interface displays the results, such as chr1:11073808-11073808. I will be so appreciated if you could kindly tell me the reason of this problem. Thank you for your kind consideration of this request.

A:
The genome score you downloaded only includes non-coding variants. For coding regions, the score mostly reply on VAT annotation (another tool by our lab: vat.gersteinlab.org). Also whole genome score including both coding and non-coding will be a very large file, which over 50G after compressed. So we provide a query server: http://funseq3.gersteinlab.org/ . Thanks also for pointing out this issue on the download page, and we will update the webpage with clear and detailed file descriptions.

Questions about FunSeq2

Q:
Recently, I used FunSeq2 to identify non-coding regulatory variations in my
bladder cancer research. In promoter analysis, I discovered the original
file, gencode.v19.promoter.bed, which downloaded from
http://funseq2.gersteinlab.org/static/data_context2.1.2/gencode/, having the
promoter areas of ranking from 1 to 8979 bp, that was inconsistent with the
definition in your article (promoters defined as -2.5 kb from transcription
starting sites).

So, I checked the process script 3.gencode.process.pl, which was downloaded
from http://funseq2.gersteinlab.org/scripts_dev/ and suited for gencode.v16.
This script generated gencode.v16.promoter.bed
(http://funseq2.gersteinlab.org/static/data_context2.1.0/gencode/), and the
BED file’s 3rd column minus 2nd column all equals 2500 (2.5 Kb). After
comparing, I noticed that the latest gencode.v19.promoter.bed has the
additional 5th column, so I realized the 3.gencode.process.pl script had
been re-edited, but I did’t find the latest version on the internet.
Therefore, I wonder whether the latest 3.gencode.process.pl redefined the
meaning of promoter. If it does, can I get one copy of this script?

A:
The promoter file was derived from PCAWG promoter set, which may consider chromHMM segmentation information. Yao have updated this in the v2.1.2, then I keep it in the latest version. User can replace the right file using their own definition of promoters.

The promoter file included in Funseq 2.1.2 is based on PCAWG consortium’s definition, which considers ChromHMM segmentation information. So it will not be exactly 2kb or 2.5kb upstream of TSS.

Using LARVA and FunSeq2 for variant analysis

Q:
I have read your articles describing FunSeq2 and LARVA. I
find these two frameworks to be the most complete and well-adapted and so, I
am very interested in using them for my analysis. I have installed both
tools and started to run them following the instructions in the
documentation, but I am still encountering a few problems.

First, I have run the web-based version of FunSeq2 on several of my VCF
files and it seems to return the wanted result, with around 10,000+ entries
for each sample. However, when running the tool on the same files in command
line (with the -nc option), I obtain a different result, with no significant
entries returned.

The output returned is:

… Input format check : vcf …
… Format ok …
… Start filtering SNVs with minor allele frequency = 0 …
Warning: sample Sample1 – no SNVs left after filtering against natrual
variations …

I receive a similar result when attempting to run the program on multiple
files at once (both in command line and on the web).

I am also trying to use LARVA on these files; I have managed to install the
tool and I am currently testing it using the example-variants-1.txt file
from the regression suite as the variant file, but the program returns
“Segmentation Fault: 11” with no other error message.

Therefore, I would like to know if you have encountered these errors before
and if so, please let me know about any steps that I can try to correct
them.

A:
I’m glad to hear that you’ve decided to use LARVA for your analyses. I did some investigating with the LARVA codebase to try to figure out what might be causing the segmentation fault. One thing I found was that one of the helper scripts (bigWigAverageOverBed) is provided in its Linux (64-bit) version, so if you run LARVA on a different type of system (e.g. a Mac), the script won’t work. There are versions for other operating systems here (at the end of the page), but for simplicity we only provided the 64-bit Linux version. If that doesn’t fix the issue, could you please tell me everything you can about the environment in which you’re running LARVA (CPU, RAM, operating system, etc.) and the command line parameters you used.

Also, for help on Funseq2, I refer you to my colleague, Shake Lou (cc’ed).

One more thing I just thought of: how are all your input files formatted?

As to the issue about Funseq2, here is some suggestions:

1. The Funseq webserver version is obsolete, and we recommend you to use github version.
2. The latest 2.1.6 version has fixed a bug that might lead to some variant missed from the output.
3. Please use bed format as the output format. I will update vcf format output later.
4. You can also try funseq3.gersteinlab.org, which we have pre-calculated each position’s score for the hg19 genome. If you have a large number of variants to query, we have another good news. We are also testing a rich format whole genome Funseq output file and can let you retrieve the Funseq annotation simply from the command line. If you are interested in this file, we can give you the pre-release testing once it passed our internal QC very soon.

Question about Classification of human genomic regions based on experimentally determined binding sites of more than 100 transcription-related factors

Q:
I was intrigued by your paper about classifying the human genomic regions based on experimentally determined transcription factor binding sites. I was wondering if you can share genomic loci of the six types of regions that you were able to identify in this paper. I was also wondering if by your analysis you were able to conclude which regions are not tissue specific. I was also curious to know if you have done similar analysis on other species. It would be great if you would be able to share the scripts that you used to generate these results if they are available in some sort of a program/package.

A:
see
funseq2.gersteinlab.org
+
metatracks.gersteinlab.org

FunSeq2 encountered issues processing whole-genome data

Q1:
I am attempting to use FunSeq2 to complete analysis on whole-genome data, and unfortunately have encountered issues. As there is no contact listed in the documentation, I thought I would try contacting you to inquire about troubleshooting. After loading a BED file in the appropriate format, a message is returned stating that the requested page is unavailable due to a server hiccup.

A1:
Could you send me a few lines of your input ? or id provided by the website ?

Q2:
The ID provided by the website is: 201511510325290607. I’ve also included a few sample lines from my input below. Please let me know if I can provide any further information.

chr1,203214078,203214078,T,C,98-22532-1

chr1,203275292,203275292,C,G,06-14634-1

chr1,203808954,203808954,C,T,06-14634-1

A2:
Your input format is different from the usual BED format. Could you separate the fields with tab (instead of comma) and try again ? The last column will be treated as sample name.

Funseq2 output: missing variants

Q:
We are trying to implement the scores of Funseq2 (running locally).
However, we would like to have a score for each variation in the
input-vcf: this is not the case if we look at the Output.vcf.
Can I conclude from this output, that the missing variants in
Output.vcf have a score of zero?

A:
The somatic variants that overlap 1000 Genomes variants are filtered out.
Those might be the variants being removed from your output vcf.
You can check one or two manually and you should be able to confirm that.