PAIRSEQ.PY(1)
π PAIRSEQ.PY(1) π
bestie, this is the User Commands page for PairSeq.py π¦
β¨ NAME β¨
PairSeq.py, okay so it sorts and matches sequence records that have matching coordinates across files π
π¦ DESCRIPTION π¦
Here's the usage line, copy-paste it exactly π
usage: PairSeq.py [--version] [-h] -1 SEQ_FILES_1 [SEQ_FILES_1 ...] -2
SEQ_FILES_2 [SEQ_FILES_2 ...] [--outdir OUT_DIR] [--outname OUT_NAME]
[--failed] [--fasta] [--delim DELIMITER DELIMITER DELIMITER]
[--1f FIELDS_1 [FIELDS_1 ...]] [--2f FIELDS_2 [FIELDS_2 ...]]
[--act {min,max,sum,set,cat}] [--coord {illumina,solexa,sra,454,presto}]
So basically, it sorts and matches sequence records with matching coordinates across files. Main character energy π
πΈ help
--versionβ the program flexes its version number and then bounces π-h,--helpβ pulls up the help message and then exits π
π standard arguments
-1 SEQ_FILES_1 [SEQ_FILES_1 ...]β an ordered list of FASTA/FASTQ files holding the head/primary sequences. (default: None)-2 SEQ_FILES_2 [SEQ_FILES_2 ...]β an ordered list of FASTA/FASTQ files holding the tail/secondary sequences. (default: None)--outdir OUT_DIRβ changes the output directory to the location you give. If you skip this, the input file's directory gets used instead. (default: None)--outname OUT_NAMEβ swaps the prefix of the successfully processed output file for whatever string you pass. > You can't use this with multiple input files, bestie π (default: None)--failedβ if you add this, it creates files full of the records that fail processing. (default: False)--fastaβ forces the output to be FASTA instead of FASTQ, no debate π§ (default: None)--delim DELIMITER DELIMITER DELIMITERβ three delimiters, in order: the ones that separate annotation blocks, the ones between field names and values, and the ones between values within a field. (default:('|', '=', ','))
π¦ pairing arguments
--1f FIELDS_1 [FIELDS_1 ...]β the annotation fields you want copied from file 1 records into file 2 records. If an annotation you copied is already in a file 2 record, the file 1 annotations get stuck on the front of the existing one π«Ά (default: None)--2f FIELDS_2 [FIELDS_2 ...]β the annotation fields you want copied from file 2 records into file 1 records. If an annotation you copied is already in a file 1 record, the file 2 annotations get tacked onto the end of the existing one β¨ (default: None)--act {min,max,sum,set,cat}β the collapse actions for combining duplicate copied fields into one value π₯min,max, andsumdo the matching math on numeric annotations.setsquishes the annotations into a comma-delimited list of unique values.catglues the values together into one single string.- This only kicks in if the field was already in the header before getting copied over from the other file. (default: None)
--coord {illumina,solexa,sra,454,presto}β the format of the sequence identifier that defines the shared coordinate info across mate pairs. (default: presto)
π§ output files
pair-passβ successfully paired reads, with their annotations all glowed up πpair-failβ raw reads that couldn't get assigned a mate-pair π
π output annotation fields
<user defined>β the annotation fields you picked with the--1for--2farguments π
π AUTHOR π
This manpage was written by Andreas Tille for the Debian distribution, and it can be used for any other usage of the program. Iconic behaviour from Andreas π«Ά
Okay that's the whole page, bestie π It's PairSeq.py 0.6.0, dated May 2020, and it lives on as PAIRSEQ.PY(1) πΈ Now go match some sequences and slay π β¨
π¦ where this page comes from
- debian bookworm: presto 0.7.1-1 Β· AGPL-3.0-only
- debian trixie: presto 0.7.2-2 Β· AGPL-3.0-only
- ubuntu jammy: presto 0.7.0-1 Β· AGPL-3.0-only
- ubuntu noble: presto 0.7.2-1 Β· AGPL-3.0-only
- ubuntu questing: presto 0.7.2-2
- ubuntu resolute: presto 0.7.6-1 Β· AGPL-3.0-only
- ubuntu stonking: presto 0.7.6-1 Β· AGPL-3.0-only
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms