Microsatellite Instability: msiSENSOR
1
0
Entering edit mode
4.9 years ago
sruthi ▴ 40

Hi, I'm new to Microsatellite instability and trying to work on msiSENSOR tool. I tried uploading a bam file in msisensor using the command:

msisensor -d microsatellites.list -t tumor.bam -o output.tumor.prefix

And it says: failed to open homopolymers and microsatellites file I checked the path and it is correct. Could any one tell me what has gone wrong and how I must troubleshoot?

TIA

next-gen sequencing • 2.4k views
ADD COMMENT
0
Entering edit mode

Command:

msisensor -d microsatellites.list -t tumor.bam -e bed.file -o output.tumor.prefix
ADD REPLY
0
Entering edit mode

The error is rectified.

ADD REPLY
0
Entering edit mode

Hi, I was calculating MSI for tumor only sample using the below command:

msisensor msi -d microsatellites.list -t tumor.bam -e bed.file -o output.tumor.prefix

It shows:

[bam_index_load] Fail to load BAM index I checked the location of files and everything is in the same directory. Could anyone tell me where I have gone wrong and what must be done? TIA

ADD REPLY
0
Entering edit mode

And it also says,

Assertion 'idx' failed Aborted core dumped.

ADD REPLY
0
Entering edit mode

Hi all, I'm calculating MSI for tumor only sample using the below command: msisensor -d microsatellites.list -t tumor.bam -e bed.file -o output.tumor.prefix

I have tried the command for 3 different files and getting 0 for Number of MSI sites. Is there something that I've done wrongly? TIA

ADD REPLY
0
Entering edit mode
4.9 years ago
sruthi ▴ 40

When running msisensor msi command, the following error pops up. How should I take it further.

msisensor: bamreader.cpp:184: bool ReadInBamReads(const char*, conststring&, unsigned int, unsigned int, std::vector<split_read>&, std::string): Assertion `idx' failed. Aborted (core dumped)

ADD COMMENT

Login before adding your answer.

Traffic: 1380 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6