Closed spoonbender76 closed 1 year ago
Hi,
Thanks for checking out Earl Grey!
The Gitpod was initially made to demonstrate the basic Earl Grey pipeline, so some changes might need to be made to run other parts of the pipeline.
In this case, run this line and it should add the script to the gitpod enviroment path:
export PATH=$PATH:/workspace/conda/envs/earlGrey/share/RepeatMasker/
Hi,
Thank you for the quick reply. I tried the line you suggested and rerun the same command in gitpod.
export PATH=$PATH:/workspace/conda/envs/earlGrey/share/RepeatMasker/
nohup /usr/bin/time -v earlGrey -g /workspace/ne_1019.fa -s v1019 -o ./repeatAnnotation -r insecta -t 4 > 1.log 2>2.err &
There goes another error
ERROR:__main__:Error reading file: [Errno 2] Unable to synchronously open file (unable to open file: name = '/workspace/conda/envs/earlGrey/bin/Libraries/RepeatMaskerLib.h5', errno = 2, error message = 'No such file or directory', flags = 0, o_flags = 0)
I've just pushed a fix for this. This was a bug arising in the transition to a conda environment which did not arise with local installs. Release 3.2.1 will fix this. If you do not want to reconfigure the gitpod environment, you can replace the main earlGrey script with the updated one in this repository. Alternatively, you should be able to pull the changes:
cd /workspace/EarlGrey/
git stash
git pull
chmod +x ./configure
./configure
Closing as fixed, but feel free to reopen if this is still bugged for you and I can look for further solutions
Hi,
Thank you for making earlGrey. I tried to use it through gitpod and wanted to include RepBase. I uploaded
RMRBSeqs.embl
andRMRBSeqs.embl
in/workspace/conda/envs/earlGrey/share/RepeatMasker/Libraries
and runperl ./configure
It changed RMBlast: [ Configured, Default ] and leaving others unconfigured
and I run the command
nohup /usr/bin/time -v earlGrey -g /workspace/ne_1019.fa -s v1019 -o ./repeatAnnotation -r insecta -t 4 > 1.log 2>2.err &
I noticed in logfile it reported/workspace/EarlGrey/earlGrey: line 83: famdb.py: command not found
Is it a bug or it's ok to ignore? Am I doing the configuration/running right?
1.log