Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jbrowse2: fix for pif; deprecate blastxml #1529

Merged
merged 27 commits into from
Oct 20, 2024
Merged

Conversation

fubar2
Copy link
Collaborator

@fubar2 fubar2 commented Oct 19, 2024

@bgruening:
Finally fixed the pif problem
blastxml is now non-functional and has been deprecated because the old JB1 converter emits gff that 2.15.4 refuses to display with an improved parser. All removed including tests...

fubar2 and others added 27 commits September 1, 2023 21:31
…m/fubar2/nftoolmaker

It actually does work. Sort of.
Hope this is useful to someone.
Allows single ended fastq or fasta to be mapped, or a pair of forward and reverse - both must be fastq
Pity the built in fails in biocontainers.
revert to paf until sorted
…om the

old JB1 converter so deprecating everything

Fixes to pif finally working
Turns out that the SHELL env variable must be set when calling
jbrowse command line functions to
prevent node.js from asking for some ID which does not end well
in the bare bones biocontainer.
@fubar2
Copy link
Collaborator Author

fubar2 commented Oct 19, 2024

@bgruening
Nothing is really lost. Blastxml was part of JB1 and should never have been included in JB2 really, because the python converter code is available as the original tool: toolshed.g2.bx.psu.edu/repos/iuc/blastxml_to_gapped_gff3/blastxml_to_gapped_gff3/1.1 so anyone wanting a GFF3 track from a blast xml output can use that and then load the GFF into JBrowse2.

It was passing tests because everything works except display - the inputs convert, but when loaded as a GFF3 JBrowse2 track, show validation errors with some (not all!) blastxml samples I tried. There have been a number of changes to the GFF parsing noted in recent release notes and it looks like it is now more strict. A GFF3 track loaded into Jbrowse2 from converting a blastxml using that existing tool shows the same errors I saw when loading the same blastxml before I removed it:

image

Point being, the blastxml input option has been redundant since I started because of the existing coverter. That tool code is from 2017-11-15 and now slightly broken due to bitrot, so let's move the copy out of this tool.

Users can use the existing converter and then load the GFF3 in JBrowse2.

The converter can be fixed separately if anyone needs it, but there's no point in having identical complicated code that needs subtle fixing in 2 places - one is more than enough and it is way beyond my skills to fix.

@fubar2
Copy link
Collaborator Author

fubar2 commented Oct 20, 2024

For the record,
https://usegalaxy.eu/u/fubar/h/imported-from-archive-jb2testout contains a GFF3 made using the blastxml converter tool. In this 2.15.4 version the track shows the error above. In this 2.14.0 version, the same track works normally. Help | About shows the JBrowse2 version and there have been no relevant code changes. Something seems to have changed in the JBrowse2 GFF parser.

@bgruening
Copy link
Owner

Ok this makes sense. Thanks for writing this down!

@bgruening bgruening merged commit bb67368 into bgruening:master Oct 20, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants