The TYGS is currently limited to 20 genomes not because of a limitation of the method but because we have to keep an eye on the compute cluster usage. But for most use cases this limit is clearly more than enough.
However, we usually offer to increase the upload cap for a given email address on TYGS beyond the default of 20 user genomes when asked for, assuming the requested upload cap is not exorbitantly high.
Before asking for an increased upload cap, please consider and prepare the following aspects though:
How large is your final dataset?
Is your dataset really final?
In case you want to analyze few own isolates together with a rather large list of
'reference strains' which you have obtained from some other web site:
Which insights do you expect to get from such an analysis?
Why can't you analyze your isolates through the TYGS without these
'reference strains' (also please read the FAQ item on type strains vs.
Have you removed redundant strains (e.g. clonal strains) from the dataset to reduce its size and, if not, why?
Is your dataset a rather diverse selection of strains or do the strains belong to a group of closely related strains?
Are your files properly labelled (e.g. labels will be shown in the trees)?
Does your dataset contain type-strain genomes and, if yes, why? The TYGS already provides type-strain genomes.
Do you want to restrict the TYGS analysis to the uploaded genome sequences or do you want
to use the TYGS in standard mode (i.e. the TYGS will determine closely related type
How does the procedure work?
We will set up an exception for your e-mail address which allows you to submit TYGS
requests with the requested number of user sequences. If the number of strains exceeds
~100, the web server might dislike this large amount of data and we have to submit the
files on your behalf from within our network. In that case the file exchange will be
organized via a confidential folder on our institutional cloud.
The exception will be usually valid for a week but can normally be extended on request. Please note that your job(s) will use some resources of our in-house compute cluster. That is, please do not start multiple redundant jobs of that size if this can be avoided.