Difference between revisions of "Frequently Asked Questions"
From SHORE wiki
(→What happened if I received a bad write error?) |
|||
| Line 9: | Line 9: | ||
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. | 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 <code>-B</code> switch to [[shore import]], e. g. <code>shore import -B 1000000 ...</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>. |
Revision as of 13:17, 19 February 2012
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 ....
