Table Of Contents
Export Hypotheses¶
glycresoft stores its search spaces in a SQLite3 database like the one it writes hypotheses into. This lets it search for entries quickly, but the format is not as easy to read through as a text file, and adds extra layers of complexity to find information requiring complex SQL queries. It’s possible to export hypotheses in several other formats.
glycresoft export glycan-hypothesis¶
Write each theoretical glycan composition in CSV format
glycresoft export glycan-hypothesis [OPTIONS] DATABASE_CONNECTION
HYPOTHESIS_IDENTIFIER
Options
- -o, --output-path <path>¶
Path to write to instead of stdout
- -i, --importable¶
Make the file importable for later re-use, with less information. [default: False]
Arguments
- DATABASE_CONNECTION¶
Required argument <databaseconnectionparam> A connection URI for a database, or a path on the file system
- HYPOTHESIS_IDENTIFIER¶
Required argument <string> The ID number or name of the glycan hypothesis to use
glycresoft export glycopeptide-hypothesis¶
Write each theoretical glycopeptide in CSV format
glycresoft export glycopeptide-hypothesis [OPTIONS] DATABASE_CONNECTION
HYPOTHESIS_IDENTIFIER
Options
- -o, --output-path <path>¶
Path to write to instead of stdout
Arguments
- DATABASE_CONNECTION¶
Required argument <databaseconnectionparam> A connection URI for a database, or a path on the file system
- HYPOTHESIS_IDENTIFIER¶
Required argument <string> The ID number or name of the glycopeptide hypothesis to use