-
Notifications
You must be signed in to change notification settings - Fork 82
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
BRAKER3 - Finished, with a wierd message #782
Comments
I am trying to figure this out but the current braker.pl has only 10005
lines. Your job complains about line 10022. So something was updated since
you git cloned BRAKER. Can you please git pull your BRAKER version to
update to the latest version and provide the output for that?
…On Mon, Mar 18, 2024 at 3:28 PM Andor J Kiss ***@***.***> wrote:
Manually installed and compiled BRAKER3 on Ubuntu 22.04 LTS;
Loaded up BRAKER3 and ran it; it *looks* as if it finished properly (all
expected files are out put and the script seems to have done all the
cleanup WITHOUT errors) and the end of the log says this:
#**********************************************************************************
# BRAKER RUN FINISHED
#**********************************************************************************
But, I got a couple of weird messages to the terminal:
$ braker.pl --threads 48 --makehub --email=************* --busco_lineage=vertebrata_odb10 --species=Goob_goober --genome=goob.softmasked.fasta --prot_seq=vertebrata.fa --rnaseq_sets_ids=ACAGTG,ACTTGA,CTTGTA,GATCAG,GCCAAT,TAGCTT,TGACCA,TTAGGC --rnaseq_sets_dir=/home/RNA-Seq
# Fri Mar 15 10:31:27 2024:Both protein and RNA-Seq data in input detected. BRAKER will be executed in ETP mode (BRAKER3).
#*********
**Use of uninitialized value in subroutine entry at /home/Programs/BRAKER/scripts/braker.pl line 1918.**
# Fri Mar 15 10:31:28 2024: Log information is stored in file /home/goob-Final_Assembly/braker3/braker/braker.log
#*********
# WARNING: in file /home/Programs/BRAKER/scripts/braker.pl at line 1411
file /home/goob-Final_Assembly/braker3/braker/genome.fa contains a highly fragmented assembly (45535 scaffolds). This may lead to problems when running AUGUSTUS via braker in parallelized mode. You set --threads=48. You should run braker.pl in linear mode on such genomes, though (--threads=1).
#*********
**Use of uninitialized value in print at /home/Programs/BRAKER/scripts/braker.pl line 10022.**
The first one, use of uninitialized value looks as if it was an empty
input file, and I'm hoping the second (last) issue at line (almost at the
end) 10022 is related.
—
Reply to this email directly, view it on GitHub
<#782>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJMC6JHVNY25DQPUXEOVGM3YY322TAVCNFSM6AAAAABE3WSBJWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE4TEMZXHA4TIOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
So, I have the latest gitpull. I've uploaded the braker.pl script from my machine: |
Thanks, yes, I was in a different branch. My mistake. It's a harmless problem, you can ignore the warning. I fixed it in commit f6480f5 |
Cool, then BRAKER3 complleted on a 6.3 Gbp genome! (with a LOT of repeats). |
Good to know! Thx for the feedback!
Andor J Kiss ***@***.***> schrieb am Mo. 1. Apr. 2024 um
19:47:
… Cool, then BRAKER3 complleted on a 6.3 Gbp genome! (with a LOT of repeats).
—
Reply to this email directly, view it on GitHub
<#782 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJMC6JCIWADRLADFQSKKLR3Y3GMSZAVCNFSM6AAAAABE3WSBJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZQGIZTMMZTGQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Manually installed and compiled BRAKER3 on Ubuntu 22.04 LTS;
Loaded up BRAKER3 and ran it; it looks as if it finished properly (all expected files are out put and the script seems to have done all the cleanup WITHOUT errors) and the end of the log says this:
But, I got a couple of weird messages to the terminal:
The first one, use of uninitialized value looks as if it was an empty input file (related to the default location of the AUGUSTUS global install), and looks as if the second one is related to the make_hub.py script (almost at the end), LINE 10022.
The text was updated successfully, but these errors were encountered: