Skip to content

Commit

Permalink
Fix broken link, fix wildcards not supported for fastq_mergepairs
Browse files Browse the repository at this point in the history
  • Loading branch information
rcedgar committed Jun 18, 2024
1 parent 28c3767 commit 3b56151
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 9 deletions.
9 changes: 1 addition & 8 deletions cmd_fastq_mergepairs.html
Original file line number Diff line number Diff line change
Expand Up @@ -190,16 +190,9 @@ <h1>
<br/>
<br/>
<strong>
Using shell wildcards to merge multiple FASTQ file pairs in a single command
Using shell wildcards is not supported in v12.
<br/>
</strong>
You can use shell wildcards (* and ?) to give a pattern that matches the FASTQ files you want to merge. For example, this will merge all R1 files in the current directory:
<br/>
<br/>
<span class="ManCode">
usearch -fastq_mergepairs *R1*.fastq -fastqout merged.fq
</span>
<br/>
<br/>
<strong>
Adding sample identifiers to read labels
Expand Down
1 change: 0 additions & 1 deletion install.html
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,6 @@ <h1>Installing USEARCH</h1>
&nbsp;&nbsp; <a href="multiple_versions.html">Installing multiple versions on the same computer</a></p>
<p class="ManText"><span class="ManText c3">There is no installer -- <span class="c2">don't double-click on the download filename</span></span><b><span class="c2">!</span><br></b>USEARCH is distributed as one file, known as the binary file or executable file. It is completely self-contained: it does not require configuration files, environment variables, third-party libraries or other external dependencies. There is no setup script or installer because they're not needed. To install it, all you do is download or copy the binary to a directory that is accessible from the computer where you want to run the code. For convenience, you may want to <a href="binary_filename.html">rename the binary file to usearch</a> to avoid typing long names like <span class="ManText">usearch6.0.98_i86linux32.</span></p>
<p class="ManText"><span class="ManText"><b>No graphical user interface<br></b> USEARCH does not have a GUI.</span> USEARCH <span class="c2">will not work</span> if you try to start it <span class="c2">in a graphical interface</span> like Windows Explorer or the Mac Finder. You <span class="c2">must run USEARCH from within a command window or shell</span>. <span class="ManText">See table below for how to get a shell prompt. If you're not familiar with using command-line programs, you're probably going to have trouble figuring out how to use USEARCH -- I recommend getting a colleague to help you who is familiar with using command-line programs.</span></p>
<p class="ManText"><span class="ManText"><b>Missing DLL problem in Windows<br></b> See here if you get missing a <a href="vcomp100.html">vcomp140.dll error</a>.</span></p>
<p class="ManText"><span class="ManText"><b>Execute permissions<br></b> Under Linux and OSX you must ensure that you have read and execute permissions for the binary file. If needed, use the <a href="http://en.wikipedia.org/wiki/Chmod">chmod command</a> to set the execute bit, e.g.:</span></p>
<p class="ManText"><span class="ManText">chmod +x /usr/bin/usearch6.0.98_i86linux32</span></p>
<p class="ManText"><span class="ManText"><b>PATH or pathname<br></b> The binary file must be in one of the directories specified in your <a href="http://en.wikipedia.org/wiki/PATH_(variable)">PATH</a> variable, or you must type the full path to the file, e.g. for Linux:</span></p>
Expand Down

0 comments on commit 3b56151

Please sign in to comment.