Closed DLBPointon closed 1 year ago
nf-core lint
overall result: Passed :white_check_mark: :warning:Posted for pipeline commit 6328583
+| ✅ 125 tests passed |+
#| ❔ 17 tests were ignored |#
!| ❗ 8 tests had warnings |!
Hi @muffato , again thanks for the code. I've attributed the changes to you.
Changes to the stats collection work and avoid any red lettered errors. Only issue is that because this is technically pre-workflow completion, we no longer have pipeline completion time and pipeline execution time. However, I should be able to time stamp that point and calculate what I need as it is practically completed. This isn't currently needed for the graphs I'm making so I'm happy to leave that for 1.0.1
Pipeline at this point has been tested on farm in full and rapid modes on the OschSubset data.
Both took 25 mins using whatever resources they wanted. I'll test this using the GitHub resource limits.
I've created 4 test profiles, 2 full Osc dataset test for on the farm and 2 subset data for GitHub runner.
How should I set up the data for these? I have an s3 bucket containing a very minimal set for the BGAcademy based on nxOscSubset.
Should we have a data download step to set up the gene alignment and busco data?
I'll sort the linting too.
I've just tested the pipeline locally using the github settings, but the cram_et_al module refuses to run. I'm assuming the restriction on resources is too much and it just silently dies.
Command in use is:
bsub -Is -tty -e error -o out -n 2 -q oversubscribed -M4000 -R'select[mem>4000] rusage[mem=4000] span[hosts=1]' 'nextflow run main.nf -profile github_rapid,singularity --input assets/local_testing/nxOscSUBSET.yaml --outdir OscSUBSET-TEST -entry RAPID'
Everything runs fine using non github profiles
Hi,
I can confirm that the farm_*
profiles work locally 👍🏼
There's an issue with the github_*
profiles: they seem to be missing some of the keys the farm_*
profiles have:
$ nextflow run ../src/sanger-tol/treeval/ -entry RAPID -profile github_rapid,singularity
ERROR ~ Cannot get property 'lineage' on null object
-- Check script '/lustre/scratch123/tol/teams/tolit/users/mm49/nextflow/src/sanger-tol/treeval/./workflows/../subworkflows/local/yaml_input.nf' at line: 99 or see '.nextflow.log' file for more details
ERROR ~ Cannot get property 'teloseq' on null object
-- Check script '/lustre/scratch123/tol/teams/tolit/users/mm49/nextflow/src/sanger-tol/treeval/./workflows/../subworkflows/local/yaml_input.nf' at line: 92 or see '.nextflow.log' file for more details
Finally, in my tests, the results/treeval_info/TreeVal_run_Oscheius*
files only have a few lines under RESOURCES
. They're meant to have the complete trace file, aren't they ? It feels like Nextflow had not finished writing / closed the trace file when TreeVal opened it for reading and copying.
EDIT: I checked out the code yesterday afternoon, so didn't test the changes you pushed this morning.
The github profiles weren't working yesterday as they were waiting on the new data set.
I've set a couple of jobs running over night so i'll have a look in the morning about the summary file output.
For now, CI works!
black
) is failingTo keep the code consistent with lots of contributors, we run automated code consistency checks. To fix this CI test, please run:
black
: pip install black
black .
Once you push these changes the test should pass, and you can hide this comment :+1:
We highly recommend setting up Black in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!
Thanks again for your contribution!
At this point, I believe the code is stable and tests will pass. However, we've realised that documentation needs to be improved. We are working on this now and hope to have a substantial amount done to day ready for merge and hopefully tagging. closes #138
Awesome job getting the tests to work.
Hi @muffato and @priyanka-surana,
We now believe TreeVal is now ready for a full review. We have now completed pre-pipeline data prep, adding the BGA23 gitpod.yaml, fixing the TreeValProject.summary (to a usable state, there are unfortunate limitations) and generally fixed it up.
Thanks.
A general suggestion for the website is to use full urls rather than relative paths.
Links to markdowns within the same directory (i.e. docs/
) should work, but let's check once everything is on dev/the pipeline website
Here are some suggestions about the documentation. See #140 for a couple of code suggestions.
Also, before merging
dev
intomain
I'd very much like to see how the documentation looks like on the pipelines website, especially the fact there are more files than justusage.md
andoutput.md
.
I've actioned everything now, merged your code suggestions, and tested everything. Thanks for the help.
Prettier failing due to odd number of underscores....
This leaves us with a file called `bTaeGut1_4.fasta` the genomic assembly of bTaeGut1_4 (the [Tree of Life ID](https://id.tol.sanger.ac.uk/) for this species) also known as _Taeniopygia guttata_, the Australian Zebrafinch.
Prettier failing due to odd number of underscores....
Try escaping the one inside the assembly names with \
?
Prettier failing due to odd number of underscores....
Try escaping the one inside the assembly names with
\
?
Fixed, escaping wouldn't work. It would get "corrected". I've instead put the assembly name inside of backticks. Which also signifies importance so win-win.
Pre-release PR
Talking with @priyanka-surana , we only need to get testing up and running (+ zenodo) and then we are ready for release.
To get that sorted i've been told to rope you in @muffato