mpiBLAST uses a shared storage system for the database index. It uses a = local (per compute node) local path on each machine where it wants to=20 place its database index fragments. So, if you place all your database indices in an NFS path which all your = cluster compute nodes can see named /database and you have all of the compute nodes use a local path for the database=20 fragments named /scratch then your mpiblast.conf would look like /database /scratch on every node. The problem is that you will see that the first user=20 writing database fragments owns them, so subsequent users cannot=20 over-write them. The run_mpiblast script handles all of this for you,=20 so that you don't stamp all over other peoples indices. Joe Ariana Priscila da Silva wrote: >Hi, > >i'm installing MPIBlast and i have any doubts. >What do mean /path/to/shared/storage and /path/to/local/storage in file = >mpiblast.conf? > > >thanks=20 > > >Ariana >-- >(Webmail DPI mantido e desenvolvido por lucaszc@dpi.ufv.br e gcbb@dpi.u= fv.br) > >----------------------------------- >WebMail DPI >Departamento de Inform=E1tica >Universidade Federal de Vi=E7osa >----------------------------------- > >_______________________________________________ >Bioclusters maillist - Bioclusters@bioinformatics.org >https://bioinformatics.org/mailman/listinfo/bioclusters > =20 > --=20 Joseph Landman, Ph.D Scalable Informatics LLC, email: landman@scalableinformatics.com web : http://scalableinformatics.com phone: +1 734 612 4615