Difference between revisions of "Frequently Asked Questions"
(→When trying to run the precompiled SHORE binary, it says something like locale::facet::_S_create_c_locale name not valid.) |
|||
| Line 12: | Line 12: | ||
To reduce disk space requirements for read import and alignment, try adding the <code>-B</code> switch to [[shore import]], e. g. <code>shore import -B 1000000 ...</code>; or provide an alternate temporary file directory with sufficient disk space, e. g. <code>shore -T /very_large_tmp mapflowcell ...</code>. | To reduce disk space requirements for read import and alignment, try adding the <code>-B</code> switch to [[shore import]], e. g. <code>shore import -B 1000000 ...</code>; or provide an alternate temporary file directory with sufficient disk space, e. g. <code>shore -T /very_large_tmp mapflowcell ...</code>. | ||
| − | ===When trying to run the precompiled SHORE binary, it | + | ===When trying to run the precompiled SHORE binary, it aborts with a message like ''locale::facet::_S_create_c_locale name not valid''.=== |
As a workaround, set the current locale to ''C'' by doing | As a workaround, set the current locale to ''C'' by doing | ||
Revision as of 16:44, 5 February 2013
Contents
- 1 Does SHORE include the SHOREmap package for mutation mapping?
- 2 What happened if I received a bad write error?
- 3 When trying to run the precompiled SHORE binary, it aborts with a message like locale::facet::_S_create_c_locale name not valid.
- 4 I generated SAM files using shore convert, but now SAMtools states that the CIGAR strings are invalid
Does SHORE include the SHOREmap package for mutation mapping?
No. SHOREmap is an add-on that is distributed as a separate package. However, SHOREmap requires the output of shore consensus as an input.
What happened if I received a bad write error?
-
read/write failure --- bad write
-
thread N: error - bad write
terminate called after throwing an instance of 'std::ios_base::failure'
These errors indicate a failure writing to disk, usually after running out of disk space either in the temporary file directory or in your output directory.
To reduce disk space requirements for read import and alignment, try adding the -B switch to shore import, e. g. shore import -B 1000000 ...; or provide an alternate temporary file directory with sufficient disk space, e. g. shore -T /very_large_tmp mapflowcell ....
When trying to run the precompiled SHORE binary, it aborts with a message like locale::facet::_S_create_c_locale name not valid.
As a workaround, set the current locale to C by doing
export LC_ALL=C
Alternatively, this problem can be fixed by compiling shore using the source package.
I generated SAM files using shore convert, but now SAMtools states that the CIGAR strings are invalid
SHORE uses the CIGAR characters = and X to indicate a match or mismatch, respectively. This format is only understood by recent versions of SAMtools (>= version 0.18).
