Thanks for the major update of the Freebayes wrapper, excellent!
I've run into two issues, however.
1) When using "set allelic scope" I get the following error:
Fatal error: Exit code 1 ()
freebayes: unrecognized option `--min-repeat-length'
did you mean --min-repeat-size ?
2) When using a vcf file as input I get the following error:
Fatal error: Exit code 1 ()
open: No such file or directory
[bgzf_check_bgzf] failed to open the file: input_variant_vcf.vcf.gz
[tabix++] was bgzip used to compress this file? input_variant_vcf.vcf.gz
I'd be happy to help resolve these. Is there a bitbucket repo somewhere
to submit pull requests? Also, I'm not sure if this is best sent to
this list or put into Trello, etc.
Lance Parsons - Scientific Programmer
134 Carl C. Icahn Laboratory
Lewis-Sigler Institute for Integrative Genomics
I hope this isn't a FAQ; I have not yet found the question (or answer)
online, though I can't imagine I'm the first to ask:
Are there plans to make a mobile version of the Galaxy website? Many of
the biologists with whom I work would like to be able to monitor and start
Galaxy jobs from their iPhones (or other smart phone). While it is
possible to do so using the regular website, a mobile-specific site could
make it easier.
We searched in vain for an app, but I gather that would be a headache to
maintain with such a dynamic website. A mobile site seems the right
approach, unless there are good reasons not to try it?
We may experiment with creating one for our own local Galaxy installation,
but would prefer to use existing code if it's available.
Dr. Mark Rogers
Intelligent Systems Laboratory
Department of Engineering Mathematics
University of Bristol
I’m interested in accessing the 'Tasmanian devil SNPs’ dataset, which I believe should be on your ’shared data’ homepage. It seems to have disappeared. Can you make it accessible, thanks.
It is from Miller et al. PNAS (2011) (http://www.pnas.org/content/early/2011/06/23/1102838108). In their paper and on their 'Tasmanian Devil Genome Project’ webpage (http://tasmaniandevil.psu.edu/data_access/index.html), they refer to accessing this SNP dataset using Galaxy.
Thanks in advance.
School of Biological Sciences
University of Tasmania
Private Bag 55
Hobart, Tasmania 7001
Phone: +61 488 330 679
I'd like to set the job_working_directory to the user's home directory.
I'm using an apache proxy with ldap authentication. I'm assuming I need to strip the remote_user_maildomain off the user name to do something like...
job_working_directory = ~%user/galaxy_working_directory
Is this possible?
When installing and testing the cd-hit tool from jjohnson from the main galaxy toolshed into my local instance of galaxy, I encountered a problem where galaxy cannot find the cd-hit program.
The error was:
"/bin/sh: 1: cd-hit-est: not found"
As I debugged the problem, I found that there is an bug in the tool dependency. It installs the cd-hit programs but never moves the programs into the configurable galaxy install directory. This could cause many problems in the situation where users don't have cd-hit already installed on their computer and must depend on the tool dependency to run the tool.
I propose we add the following code to the tool dependency:
After I made these changes, I pushed the changes into a new repo on my local toolshed, I managed to successfully install cd-hit into a local and dev-test instance of galaxy and the cd-hit tool ran successfully.
Thanks for your understanding,
In "Upload files to a data library" form, seems like whatever valid path I enter for linking to data on the server, even with "galaxy" as user and r permissions on the folder and files - I get the "invalid paths" message after submitting? The basic form info:
Upload option: Upload files from filesystem paths
File Format: blastxml
Paths to upload
Preserve directory structure?
[yes or no]
Copy data into Galaxy?
Link to files without copying into Galaxy
Does anyone know a trick to this? Would be nice to have more helpful error explanation here!
My galaxy: 5e605ed6069f+ (stable) release_2014.02.10 . I think it is a pretty normal installation.
Thanks for any tips,
Hsiao lab, BC Public Health Microbiology & Reference Laboratory, BC Centre for Disease Control
655 West 12th Avenue, Vancouver, British Columbia, V5Z 4R4 Canada
Quick question. When two different users use the same Galaxy instance
without logging in, how does Galaxy keep their identities straight, such
that when they come back to their computers the next day, they see only
their own workspace and not the other user's workspace?
I noticed a strange behaviour in our local galaxy installation. First of all, my universe_wsgi.ini contains "retry_metadata_internally = False" and "cleanup_job = always". The tool writes its output simply into the job_working_directory and we move it via && mv static_filename.txt $output in the <command>-tag. This works fine.
When restarting the galaxy server and executing the tool after a fresh restart, everything is ok, there are no errors.
When executing the same tool a second time, galaxy brings a "tool error" stating that it was unable to finish the job. Nevertheless, the output files are all correct (but marked as red or failed).
The error report states:
Traceback (most recent call last):
File "/home/galaxy/galaxy-dist/lib/galaxy/jobs/runners/local.py", line 129, in queue_job
job_wrapper.finish( stdout, stderr, exit_code )
File "/home/galaxy/galaxy-dist/lib/galaxy/jobs/__init__.py", line 997, in finish
if ( not self.external_output_metadata.external_metadata_set_successfully( dataset, self.sa_session ) and self.app.config.retry_metadata_internally ):
File "/home/galaxy/galaxy-dist/lib/galaxy/datatypes/metadata.py", line 731, in external_metadata_set_successfully
rval, rstring = json.load( open( metadata_files.filename_results_code ) )
IOError: [Errno 2] No such file or directory: u'/home/galaxy/galaxy-dist/database/job_working_directory/000/59/metadata_results_HistoryDatasetAssociation_281_oHFjx0'
And in the logfile you can find multiple entries like that:
galaxy.datatypes.metadata DEBUG 2014-06-25 14:29:35,466 Failed to cleanup external metadata file (filename_results_code) for HistoryDatasetAssociation_281: [Errno 2] No such file or directory: '/home/galaxy/galaxy-dist/database/job_working_directory/000/59/metadata_results_HistoryDatasetAssociation_281_oHFjx0'
The if-statement in /home/galaxy/galaxy-dist/lib/galaxy/jobs/__init__.py", line 997 should evaluate to False, since self.app.config.retry_metadata_internally is set to False in the universe_wsgi.ini but it seems it doesn't in this case?
Anyone having experienced such a behavior? Any suggestions how to go on and solve the issue?
I am working for USD Bioinformatics and trying to integrate Galaxy tools in an application. I have been looking at this site: https://wiki.galaxyproject.org/Admin/Tools/ToolConfigSyntax? but was wondering if there was anyway to get the actual DTD or Schema for your tool definitions.
Is this possible?
Thanks! I think
solve my problem!
Because I want to use R which has multiple layers of dependencies
rebuilding it locally seemed a bit labor intensive but this capsule thing
sounds exactly what I need. I'll take a look into it.
Thanks for the fast response.
On 24 June 2014 15:00, Greg Von Kuster <greg(a)bx.psu.edu> wrote:
> your tool in your local Galaxy environment, using the local Tool Shed as
> a source code repository if necessary.
> 6. When development is finished, make sure the finished tool is
> available in hyour local Tool Shed's repository and execute your local Tool
> Shed's Install and Test framework to validate the tool - see the "Using the
> Install an
Central Veterinary Institute of Wageningen UR (CVI)
Department of Infection Biology
PO box 65, 8200 AB Lelystad, NL
Visiting address: ASG, Edelhertweg 15, 8219 PH Lelystad