Hi Ricardo, do you run velvet on your own cluster with SGE? Sometimes, "No Peak found" can also mean that velvet used to much resources and was killed by your cluster engine. In that case it often happens to us that we get no result. A solution is a give velvet more resources or adjust the resources dependant on the file size.
Cheers, Bjoern > Dear all, > > Today when running velvet oprimizer vlsci, we encountered that if you use two > long files as input then the output is a file that its description is "no > peek". However when I run the files seperately the velvet optimizer seems to > work fine. I am not sure if this is a bug or not. > > Thank you for your time, > --Ricardo Perez > ___________________________________________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > http://lists.bx.psu.edu/ > > To search Galaxy mailing lists use the unified search at: > http://galaxyproject.org/search/mailinglists/ ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
