Hi I am very new to RNA-seq analysis. But I need to complete the mapping of my data using SpliceMap. I am not able to edit the run.cfg file and I am getting the following error
""ls: cannot access /cluster/rnaseq/genome/hg18/chr*.fa: No such file or directory
ERROR: I found no chromosomes, please check the genome_dir (/cluster/rnaseq/genome/hg18/) and the chromosome_wildcard (chr*.fa)"".
Could anyone tell me how to correct the same? I put the index files like hg18_c.1.ebwt
etc and the .fa files in different folders in the working directory.
Unconfigured Ad
Collapse
X
-
I hope that works.Originally posted by SolexaNewbie View PostHi John,
Thank you very much for your prompt reply. Yes, I've just run the tutorial and all went well. I will try moving the chr1.fa (downloaded from UCSC) to the genome folder used in the tutorial.
I'm trying to think why that might be the case.. If it still doesn't work
could you email me the log files as described in
You can directly send to me at johnmu (at) stanford.edu
Sorry for the trouble!
John Mu
Leave a comment:
-
Hi John,
Thank you very much for your prompt reply. Yes, I've just run the tutorial and all went well. I will try moving the chr1.fa (downloaded from UCSC) to the genome folder used in the tutorial.
Leave a comment:
-
Hi,Originally posted by SolexaNewbie View PostHi,
I was doing on trial run for SpliceMap on my data and got this error message after Bowtie mapping:
Genereating mapping file!...
Total mapping index creation section execution time: 541.607 s.
Total Mapping section time: 11970.7 s.
Running SpliceMap on /home/bowtie/chr1.fa ...
COMMAND: ./bin/SpliceMap test.cfg /home/bowtie/chr1.fa
ERROR: fork failed
Has anyone else had this problem / knows of a fix?
Thank you.
Does the example data set in the tutorial work?
Leave a comment:
-
Hi,
I was doing on trial run for SpliceMap on my data and got this error message after Bowtie mapping:
Genereating mapping file!...
Total mapping index creation section execution time: 541.607 s.
Total Mapping section time: 11970.7 s.
Running SpliceMap on /home/bowtie/chr1.fa ...
COMMAND: ./bin/SpliceMap test.cfg /home/bowtie/chr1.fa
ERROR: fork failed
Has anyone else had this problem / knows of a fix?
Thank you.
Leave a comment:
-
Thanks a lot. Unfortunately I did not save the STDOUT and the only log file produced by SpliceMap contains:Originally posted by john_mu View Posthmm... are you saying that you get output in the coverage and SAM file but no junctions? That is extremely odd....
Could you email me your terminal output? johnmu (at) stanford (dot) edu
I'll take a look and see if I can work out what is going on.
Also, I will have a new version out soon (in a few days) with many more additional checks to make sure the data and genome files are as expected. Hopefully that will fix your issue.
Look forward to hearing from you!
####Total####alljunction##########
total: 0
ave: nan
1: 0 nan%
2-5: 0 nan%
6-20: 0 nan%
21-50: 0 nan%
51-200: 0 nan%
201-1000: 0 nan%
1000+: 0 nan%
####nNR####alljunction#########
This supports the fact that no splice junctions were found. I checked the transcript.gtf produced by Cufflinks against a transcript.gtf which was based on a TopHat run in the GenomeBrowser manually for some samples of chr1: The results of the SpliceMap run seem to be ok.
I just started a new run on the same run.cfg and I'll send you an email with the output when it is finished (this will take > 20h).Last edited by Enrico Palazzo; 08-12-2010, 12:54 PM.
Leave a comment:
-
hmm... are you saying that you get output in the coverage and SAM file but no junctions? That is extremely odd....
Could you email me your terminal output? johnmu (at) stanford (dot) edu
I'll take a look and see if I can work out what is going on.
Also, I will have a new version out soon (in a few days) with many more additional checks to make sure the data and genome files are as expected. Hopefully that will fix your issue.
Look forward to hearing from you!
Originally posted by Enrico Palazzo View PostHi,
I ran SpliceMap on 2*76bp paired end reads (Mouse) and it did not produce any splice junction. (the bed files are empty). I expected that the problem was connected to the problem Lix had, so I downloaded the mm9 Bowtie index from UCSC again.
But the problem was still the same : no junctions.
The coverage_all.wig file has more than 1Mio. entries and Cufflinks was able to produce a lot of transcripts using the sorted good_hits.sam file.
Is this a problem with SpliceMap output processing or did I do a mistake?
The parameters in my run.cfg are:
##########################################
genome_dir = /cluster/rnaseq/genome/Mus_musculus_9/
> reads_list1
/cluster/rnaseq/readfiles/SRR037950_1.fastq
<
> reads_list2
/cluster/rnaseq/readfiles/SRR037950_2.fastq
<
read_format = FASTQ
mapper = bowtie
head_clip_length = 0
seed_mismatch = 1
sam_file = cuff
ud_coverage = no
bowtie_base_dir = /cluster/rnaseq/genome/Mus_musculus_9/mm9
num_threads = 3
##########################################
(spliceMap Version 3.3.1.3, Bowtie version 0.12.5)
Thanks,
C.
Leave a comment:
-
Hi,
I ran SpliceMap on 2*76bp paired end reads (Mouse) and it did not produce any splice junction. (the bed files are empty). I expected that the problem was connected to the problem Lix had, so I downloaded the mm9 Bowtie index from UCSC again.
But the problem was still the same : no junctions.
The coverage_all.wig file has more than 1Mio. entries and Cufflinks was able to produce a lot of transcripts using the sorted good_hits.sam file.
Is this a problem with SpliceMap output processing or did I do a mistake?
The parameters in my run.cfg are:
##########################################
genome_dir = /cluster/rnaseq/genome/Mus_musculus_9/
> reads_list1
/cluster/rnaseq/readfiles/SRR037950_1.fastq
<
> reads_list2
/cluster/rnaseq/readfiles/SRR037950_2.fastq
<
read_format = FASTQ
mapper = bowtie
head_clip_length = 0
seed_mismatch = 1
sam_file = cuff
ud_coverage = no
bowtie_base_dir = /cluster/rnaseq/genome/Mus_musculus_9/mm9
num_threads = 3
##########################################
(spliceMap Version 3.3.1.3, Bowtie version 0.12.5)
Thanks,
C.
Leave a comment:
-
The single-read bug has been fixed. Also, a small bug with the display of the "max_intron" and "min_intron" parameters.
I would just like to remind everyone that SpliceMap can't work with reads that are not uniform in length. We will endeavor to add this in future versions as well as read quality information.
Leave a comment:
-
Hi mfischer,Originally posted by mfischer View PostHi,
first of all thanks for the great tool!
As already mentioned at you homepage there is bug concerning single-reads. I tried to analyzed 50-76 bp (different read length is due to previous read trimming based on Illumina's Read Segment Quality Control Indicator) single-reads with SpliceMap 3.3.1.2 and the output's log file contains just NANs.
Since I'm a little bit in a hurry (my group is waiting impatiently for the data
) and we do not have reads >100 bp I'd like to ask if it would be possible to get SpliceMap Version 3.2.2. I had a look at the homepage but I couldn't find a link to that particular version.
By the way, while running the analysis I got a lot of "Skipping read ... because it is less than 4 characters long" warnings. Is this behaviour expected for read lengths between 50 and 76 bp?
Thank you very much!
Best regards
I'll be happy to help you get SpliceMap working on your data as soon as possible.
Firstly, are you using single reads? If so I already have the fixed code on my computer. It has been tested on some example data of various lengths, so it should be ok. I just haven't had time to run it on the bigger datasets yet.
I can send you this version via email if you need it very soon, otherwise if you can wait about 3 days, I will put it on the website.
However, you say there is the error "Skipping read ... because it is less than 4 characters long" This error looks a bit odd to me. Do you mind emailing me you output from the terminal and your run.cfg? I have not seen this error before and it looks like it is from Eland or Bowtie. Which version of each are you using?
Regardless, fire me an email (johnmu at stanford.edu) and I'll get back to you soon. However, I'm leaving home (Australia) and heading back to the US tomorrow, so I might be a bit late with my reply.
Thanks for the feedback!
John Mu
EDIT: Also, I don't recommend you try to use 3.2.2 because where were some bugs in the SAM output that have been fixed in recent versions. You can see this in the "news" on the website.
Leave a comment:
-
Problems with single-reads
Hi,
first of all thanks for the great tool!
As already mentioned at you homepage there is bug concerning single-reads. I tried to analyzed 50-76 bp (different read length is due to previous read trimming based on Illumina's Read Segment Quality Control Indicator) single-reads with SpliceMap 3.3.1.2 and the output's log file contains just NANs.
Since I'm a little bit in a hurry (my group is waiting impatiently for the data
) and we do not have reads >100 bp I'd like to ask if it would be possible to get SpliceMap Version 3.2.2. I had a look at the homepage but I couldn't find a link to that particular version.
By the way, while running the analysis I got a lot of "Skipping read ... because it is less than 4 characters long" warnings. Is this behaviour expected for read lengths between 50 and 76 bp?
Thank you very much!
Best regards
Leave a comment:
-
SpliceMap has been updated again!
There was a tiny bug in the SAM output (an extra tab at the end) and also it is updated for people with older version of g++.
Leave a comment:
-
Thanks for this convenient tool. It runs extremely fast and very easy to use. And, thank John for the very kindful help.Originally posted by john_mu View PostJust updating for everyone else. The reason for this was possibly because the original bowtie index was corrupted during download from the bowtie website.
Last edited by lix; 06-21-2010, 05:18 PM.
Leave a comment:
-
Runtime Error
Hi, I try to this useful tool for aligning 75*2 nt RNA-seq data
But when I execute this step:
find genome/ -name "chr*.fa" -print -exec ./bin/SpliceMap run.cfg {} \;
Loading configuration file... run.cfg
Reading read-file-list files!...
Sequencer full read length: 75
List 1:
temp/read_1_1
List 2:
temp/read_1_2
____________
Reading and indexing reference genome!...
Chromosone name: chr21
Chromosone Size: 46944323
Index creation time: 9.66561 s.
Index sorting time: 0.435851 s.
____________
Reading and finding search seeds!...
in ... read_1_1.1-50.seq
terminate called after throwing an instance of 'std:
ut_of_range'
what(): basic_string::substr
find: `./bin/SpliceMap' terminated by signal 6
what's the problem and how can I do to slove it?
Thanks very much!
Leave a comment:
Latest Articles
Collapse
-
by SEQadmin2
Tumors contain complex mixtures of cell populations that evolve in response to treatment and host-specific factors. Tissue biopsies provide only static snapshots of a tumor’s state. But what if we could follow that evolution over time using a minimally invasive technique?
Liquid biopsies can detect tumor-derived material circulating in the bloodstream, providing a way to study treatment response, detect emerging resistance, and discover new biomarkers. Circulating...-
Channel: Articles
10-14-2026, 09:55 AM -
-
by SEQadmin2
Researchers using sequencing and genomics tools often have to make trade-offs. They can choose between speed or scale, short reads or long-range information, or targeted panels or a view of the whole transcriptome. New technologies that have been released this year are built to address those tough choices.
We asked six companies the same four questions to learn about their latest products. The new technologies bring a lot to the table, including rethinking sequencing...-
Channel: Articles
-
ad_right_rmr
Collapse
News
Collapse
| Topics | Statistics | Last Post | ||
|---|---|---|---|---|
|
Started by SEQadmin2, 10-22-2026, 11:13 AM
|
0 responses
23 views
0 reactions
|
Last Post
by SEQadmin2
10-22-2026, 11:13 AM
|
||
|
Started by SEQadmin2, 10-22-2026, 10:48 AM
|
0 responses
20 views
0 reactions
|
Last Post
by SEQadmin2
10-22-2026, 10:48 AM
|
||
|
Started by SEQadmin2, 10-15-2026, 10:52 AM
|
0 responses
36 views
0 reactions
|
Last Post
by SEQadmin2
10-15-2026, 10:52 AM
|
||
|
Started by SEQadmin2, 10-14-2026, 05:39 AM
|
0 responses
42 views
0 reactions
|
Last Post
by SEQadmin2
10-14-2026, 05:39 AM
|
Leave a comment: