<<Back to main

Gsuite files come in three variants:

• - Remote GSuite: when compiling from external databases, the resulting GSuite will essentially be a list of URLs to files on external servers. One can also manually construct a remote GSuite as a simple text file of URLs to remote files. Before working on this data, the files need to be downloaded to the local server (to achieve a local textual GSuite).
• - Local textual GSuite: When compilling from history elements, the resulting GSuite will essentially be a list of references to textual files in the Galaxy history. Using the tool "Fetch remote GSuite datasets" also results in a GSuite of this variant (the tool will implicitly download the remote files to hidden local history elements to form the basis for this variant of GSuite). Such a GSuite can be used in tools that manipulate textual track files. Before analyzing the tracks, they need to be preprocessed (to achieve a local binary GSuite).
• - Local binary GSuite: When compiling from HyperBrowser repository, the resulting GSuite will essentially be a list of references to tracks in binary, indexed format at the server. Using the tool "Preprocess tracks in GSuite for analysis" also results in a GSuite of this variant (the tool will implicitly preprocess the tracks to binary format to form the basis for this variant of GSuite). Such a GSuite can be used in all the analysis tools, as well as some other tools that operate on preprocessed data.