Comments (4)
You can change $tax_dir in Phylotyping.pl to a directory where the user has permission to write.
On Mar 30, 2016, at 3:07 AM, samfux84 <[email protected] mailto:[email protected]> wrote:
Dear Martin Wu,
I recently installed Phyla_AMPHORA on the HPC cluster of ETH Zurich. Then one of our users reported problems when running the script Phylotyping.pl, because it crashed with the following error:
[samapps@euler01 ~]$ module load gcc/4.8.2 gdc raxml/8.2.4 hmmer/3.1 emboss/6.5.7 perl/5.18.4 phyla_amphora
Now run 'perl-init' to initialize your environment for Perl
[samapps@euler01 ~]$ perl-init
[samapps@euler01 ~]$ Phylotyping.pl------------- EXCEPTION: Bio::Root::Exception -------------
MSG: Cannot open file '/cluster/apps/gdc/phyla_amphora/Taxonomy/nodes': Permission denied
STACK: Error::throw
STACK: Bio::Root::Root::throw /cluster/apps/gdc/perl5/perls/perl-5.18.4/lib/site_perl/5.18.4/Bio/Root/Root.pm:449
STACK: Bio::DB::Taxonomy::flatfile::_build_index /cluster/apps/gdc/perl5/perls/perl-5.18.4/lib/site_perl/5.18.4/Bio/DB/Taxonomy/flatfile.pm:370
STACK: Bio::DB::Taxonomy::flatfile::new /cluster/apps/gdc/perl5/perls/perl-5.18.4/lib/site_perl/5.18.4/Bio/DB/Taxonomy/flatfile.pm:138
STACK: Bio::DB::Taxonomy::new /cluster/apps/gdc/perl5/perls/perl-5.18.4/lib/site_perl/5.18.4/Bio/DB/Taxonomy.pm:119STACK: /cluster/apps/gdc/phyla_amphora/Scripts/Phylotyping.pl:59
[samapps@euler01 ~]$
After investigating the problem, I figured out that the program tries to write files into the directory $Phyla_AMPHORA_home/Taxonomy, which is part of the installation directory of the software. On a HPC cluster, this is a problem. We strictly separate installation directories from the data, that is created during a job. The installation directory is owned by a technical user, and the users running jobs on the cluster do not have write permission in any of the software installation directories.Is there a way to redirect the files "nodes", "parents", "id2names" and "names2id" to a different directory in user space ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub #4
from amphora2.
Thank you very much for the fast reply. I will change $tax_dir.
from amphora2.
I had another look at this issue and figured out that the files are not directly created by Phyla_AMPHORA, but rather by calling the perl function Bio::DB::Taxonomy->new(). Are these files only useful during a single Phyla_APMPHORA run or do users need to keep them for a longer time ?
If they are only useful for the time span of a single job, then I would rather change the Phylotyping.pl script and replace the line
my $taxdb = Bio::DB::Taxonomy->new( -source => 'flatfile',
-directory=>$tax_dir,
-nodesfile => "$tax_dir/nodes.dmp",
-namesfile => "$tax_dir/names.dmp");
with
my $taxdb = Bio::DB::Taxonomy->new( -source => 'flatfile',
-directory=> $ENV{'TMPDIR'},
-nodesfile => "$tax_dir/nodes.dmp",
-namesfile => "$tax_dir/names.dmp");
$TMPDIR is the temporary directory created by the cluster's batch system (IBM LSF). Can you please comment on this ?
Best regards
from amphora2.
These files can be used by multiple users and only need to be created once. You should keep them for a longer time.
On Apr 4, 2016, at 4:34 AM, samfux84 [email protected] wrote:
I had another look at this issue and figured out that the files are not directly created by Phyla_AMPHORA, but rather by calling the perl function Bio::DB::Taxonomy->new(). Are these files only useful during a single Phyla_APMPHORA run or do users need to keep them for a longer time ?
If they are only useful for the time span of a single job, then I would rather change the Phylotyping.pl script and replace the line
my $taxdb = Bio::DB::Taxonomy->new( -source => 'flatfile',
-directory=>$tax_dir,
-nodesfile => "$tax_dir/nodes.dmp",
-namesfile => "$tax_dir/names.dmp");
withmy $taxdb = Bio::DB::Taxonomy->new( -source => 'flatfile',
-directory=> $ENV{'TMPDIR'},
-nodesfile => "$tax_dir/nodes.dmp",
-namesfile => "$tax_dir/names.dmp");
$TMPDIR is the temporary directory created by the cluster's batch system (IBM LSF). Can you please comment on this ?Best regards
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub #4 (comment)
from amphora2.
Related Issues (6)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from amphora2.