Conversation
Update Spacepharer to point at the latest version and make sure each YAML file neatly ends with a newline character.
- Update the index, removing old entries and adding new ones. - Fill in links to output file documentation. - Move link to the user manual to the top.
- Include MLST in documentation - Tick box in to do
- Add output to 'rule all' - Include rules to concatenate output in one file - Include PADLOC documentation - Reference additional functions in index
- Add 'extra functions' and 'output files' entries
Necopy-byte
reviewed
Aug 29, 2025
Collaborator
Necopy-byte
left a comment
There was a problem hiding this comment.
Looks good, there are some minor spelling errors and I remembered that phagescope does not need to take up 320GB as spacepharer should be able to accept it Gzipped
|
|
||
| The Phagescope database says that it can filter genomes based on criteria, | ||
| but actually downloading these fastas is impossible due to an error. | ||
| Additionally, `wget` and `curl` do not properly download the databases in a way that |
Collaborator
There was a problem hiding this comment.
This has been solved with the script i wrote, apparently the server was just down when i tried to download it originally via wget.
| page cannot be solved using the recommended 'strict channel priority' setting. | ||
| We could only get it to work with the flexible or disabled channel priority. | ||
| We have adapted to YAML so that it can be solved using strict priority mode, | ||
| but this does make strand prediction in CRISPRidentify non-functional. |
Collaborator
There was a problem hiding this comment.
Strand prediction and also apparently the optional cas prediction module CRISPRcasidentifier
| - [PLSDB](spacepharer.md#plsdb-2024_05_31_v2): ~80GB | ||
| - [PLSDB](spacepharer.md#plsdb-2024_05_31_v2): ~80GB | ||
|
|
||
| - [Phagescope](spacepharer.md#phagescope): ~320GB |
Collaborator
There was a problem hiding this comment.
The file size does remind me that spacepharer should be able to accept gzipped files for its database creation, i will make an issue for this.
Member
Author
|
Thanks for checking and suggesting fixes @Necopy-byte ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
General workflow refinement, including code updates and expansion of the documentation.