You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rather than providing general guidance (screenshot below) for the need to increase memory/processing power for larger proteins, it would be nice if there was a step in the notebook that would analyze the .fasta file prior to kicking off the pipeline run. This step could either throw an error if the memory/processing settings are likely too small, and/or provide recommended memory/processing settings.
New users will often hit errors when first processing larger proteins, and they are less familiar of where to find the logs, and when they do find them the errors can be a bit cryptic (screenshot below).
Existing General Guidance:
Common Error Message:
The text was updated successfully, but these errors were encountered:
Suggestion accepted.
In order to implement this "recommendation engine" we will need to run several benchmarks to determine the optimal hardware configuration.
I will start running these benchmarks next week and let you know as soon as we finish.
Thanks for the suggestions.
leiterenato
changed the title
Enhancement Request: Check size of proteins prior to pipeline run creation
[FEAT] Check size of proteins prior to pipeline run creation
Oct 21, 2022
Rather than providing general guidance (screenshot below) for the need to increase memory/processing power for larger proteins, it would be nice if there was a step in the notebook that would analyze the .fasta file prior to kicking off the pipeline run. This step could either throw an error if the memory/processing settings are likely too small, and/or provide recommended memory/processing settings.
New users will often hit errors when first processing larger proteins, and they are less familiar of where to find the logs, and when they do find them the errors can be a bit cryptic (screenshot below).
Existing General Guidance:
Common Error Message:
The text was updated successfully, but these errors were encountered: