Closed TkNiw closed 4 months ago
NOOB Question: Can you provide detailed instructions on how to actually do this for people who are unfamiliar with Singularity containers?
Well, I'm new to singularity, actually. What I did is like this. First I logged in the shell in braker3 docker container, installed and replaced the augustus binary files in docker container (download & make), logged out, then built docker image from the container by docker commit. Lastly I generated the singularity image from the docker image by singularity build.
I guess this is not a straightforward way, comming from the root-less feature of default singularity setting. I think this could be solved also by fakeroot mode of singularity (Sandbox) instead of the docker-singularity conversion, but I haven't tried this method.
I pushed a new docker container with the latest augustus and etraining, today.
I recommend to hold off a few days, though. It solves your problem, but not all problems that we will address in the next couple of days
Dear Braker3 developers,
Thank you for releasing such an useful pipeline! I just want to report a bug about Augustus binary files wrapped by Braker3.0.6 singularity image. We are working on an organism with relatively large genome (6.5 Gb assembly size), and faced with an error below.
./braker/errors/gbFilterEtraining.stderr
Then, we found a similar issue in Augustus repository, explaining the problem is related to the data type handling in C++ script. https://github.com/Gaius-Augustus/Augustus/issues/105
This was fixed in Augustus 3.0.5, released after this report, but the one inside braker 3.0.6 (also 3.0.7) singularity image is 3.0.4. Finally, This was solved by replacing original Augustus binary files by v3.0.5 inside of braker singularity container. I hope this will make the pipeline more versatile.