-
Notifications
You must be signed in to change notification settings - Fork 13
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
[Question] Is the blastn blast in working state? #113
Comments
Thank you for this and for the detailed steps to reproduce! Sorry for the delay in getting back to you -it was a long weekend here in Canada. I'll have to look a bit deeper into the module to see where it is at for the actually running of a blast job functionality-wise. I'll get back to you likely tomorrow but feel free to follow up often as there is a lot on my plate so sometimes things get dropped. The state of this module is in big part because of all the work I've been doing on Tripal core and there are only so many hours in the day unfortunately! 😅 |
I totally get it, @laceysanderson. We all have only so much time per day left to work on projects, right :) It's totally fine. Look into it when you get some extra time. In the meantime, I will continue testing the same and add any more info that I am gathering in the discussion. |
Following up here: The blast is definitely not in a working state just yet ReproducibleFollowing a similar procedure to @shreyas-a-s above... specifically:
I would have expected to see a page telling me that the job was submitted and I was in a queue. With that expectation in mind I went to I then ran the blast job on the command-line and observed: Next StepsTWIG updates neededThe error shown in step 3 indicates that our twig files are not using the correct syntax for comparison. I would guess this is because they were developed against a much older version of twig. To fix, we'll want to update the files in the Blastn service issues with advanced parametersThis is implied by these errors on the page loaded after the job is submitted.
likely caused by a disagreement between the name of the form element and the name the service expects the value to have. These need to match so the form would be updated to match.
This implies we need a check in the programSetGap to only explode if we are able to retrieve the value. This is directly linked to the first one.
This is also directly linked to the first one. We tried to access the first value in our exploded array without checking to see if it was there. Look in the files mentioned to fix these issues. Blast report controller not finding report variableThis is an assumption that doesn't hold true in the controller. We assumed that a report variable was always available but it is actually only set in one case. I would fix this by defining the $report variable outside of the if block and setting it to NULL. Blast Tripal Job not receiving all the parameters it needs.The blast job expects to have the output filename passed to it but the code that submits the job does not populate that. In Tripal 3 this was calculated based on configuration and the value of the job. This needs to be fixed in the code that submits the Tripal job. |
Hi there!
I have tried multiple ways including running the docker version of blast and every time I am not able to complete the blast run. It probably is something I am doing differently, but I am unable to find out the reason myself.
Obtained Result:
BLAST
:Steps I followed:
curl -O 'https://api.ncbi.nlm.nih.gov/datasets/v2alpha/genome/accession/GCF_000365185.1/download?include_annotation_type=GENOME_FASTA&include_annotation_type=GENOME_GFF&include_annotation_type=RNA_FASTA&include_annotation_type=CDS_FASTA&include_annotation_type=PROT_FASTA&include_annotation_type=SEQUENCE_REPORT&hydrated=FULLY_HYDRATED' -o nelumbo-nucifera.zip unzip nelumbo-nucifera.zip mv ncbi_dataset/data/GCF_000365185.1/GCF_000365185.1_Chinese_Lotus_1.1_genomic.fna ./nelumbo-nucifera.fna
makeblastdb -dbtype nucl -parse_seqids -hash_index -in nelumbo-nucifera.fna -input_type fasta -title "Nelumbo Nucifera DB Test" -out nelumbo_nucifera
localhost:80
The text was updated successfully, but these errors were encountered: