- galaxy-dev - lists.galaxyproject.org

Unnamed histories proliferating, can't get to my data
by Karger, Amir 06 Nov '12

06 Nov '12

I'm using Galaxy from June, 2012. (Sorry if there's already a fix.) We've got it "working" in production. We've gotten whole pipelines to run. However, we occasionally get situations where we upload file (using the FTP mechanism), which seems to be fine, but then I can't get to the data. I went to Saved Histories, and selected Switch, and it outlined the line in blue and wrote "current history" next to it. But the right pane still shows "Unnamed history" with no data in it. Then if I go back to Saved Histories, I get one or two new Unnamed histories, created within the last few minutes. I just tried to "View" the history, which worked (in the middle pane) and clicked "import and start using history". This seemed to work, but I got three panes inside the middle pane! When I go back (again) to saved histories, there are 3 histories - one the imported one with 2 steps, two unnamed histories, all created < 1 minute ago. We just asked a beta tester to play with things, and he uploaded two fastqs, but had what sounds like a similar problem. Any thoughts on what's happening? Thanks, -Amir Karger Research Computing Harvard Medical School

2 4

xgrid cluster computing
by Edward Hills 05 Nov '12

05 Nov '12

Hi Galaxy team, So our university has decided to switch our xgrid clusters back on and we are looking to set Galaxy up on these. Has anyone got (or tried) to set up Galaxy on xgrid before? xgrid supposedly conforms to DRMAA so technically Galaxy should work, correct? Cheers, Ed

1 0

Think I found a bug
by Juan González-Vallinas 05 Nov '12

05 Nov '12

Hi galaxy devs, We are in the final stages of deploying a new Galaxy instance. We downloaded the galaxy-dist version a month ago aprox. We realized that, when launching a job and deleting it in the middle of the execution (hitting the Delete button in the history bar) will output the following error in the logger: galaxy.jobs.handler DEBUG 2012-11-05 15:56:33,537 Stopping job 45: galaxy.jobs.handler DEBUG 2012-11-05 15:56:33,537 stopping job 45 in local runner galaxy.jobs.handler ERROR 2012-11-05 15:56:33,538 Exception in monitor_step Traceback (most recent call last): File "/usr/local/www/galaxy-dist/lib/galaxy/jobs/handler.py", line 298, in monitor self.monitor_step() File "/usr/local/www/galaxy-dist/lib/galaxy/jobs/handler.py", line 341, in monitor_step self.dispatcher.stop( job ) File "/usr/local/www/galaxy-dist/lib/galaxy/jobs/handler.py", line 438, in stop self.job_runners[runner_name].stop_job( job ) File "/usr/local/www/galaxy-dist/lib/galaxy/jobs/runners/local.py", line 180, in stop_job if job.get_external_output_metadata(): AttributeError: 'Job' object has no attribute 'get_external_output_metadata' By copying the definition of get_external_output_data from the Task class into the Job class, we fixed the problem and now the jobs are terminated successfully. This is the code I added: class Job( object ): ... def get_external_output_metadata( self ): return None ... In this file: https://bitbucket.org/galaxy/galaxy-central/src/9d6a61f060d359a0289b3163990… Do you think this fix is correct, or is it a potential problem? Also, sorry I sent you through this channel, I couldn't find the way of reporting this on BitBucket. Regards, -- Juan González-Vallinas PhD Student Regulatory Genomics Group Research Unit in Biomedical Informatics (GRIB) Universitat Pompeu Fabra (UPF) Barcelona Spain (Currently visitor at UPenn)

1 0

How to add the option "-c enabled" to the qsub command?
by Luobin Yang 05 Nov '12

05 Nov '12

Hi, guys, I would like to enable checkpoint and restart for some galaxy jobs. In order to do that, I need to add "-c enabled" option when using "qsub" to submit a job. What files should I change to add this option? I am using Torque PBS job runner. Thanks, Luobin

2 2

Dynamic job runner status? Could I use it in combination with job splitting?
by Carlos Borroto 05 Nov '12

05 Nov '12

Hi, I've been researching the possibility of using dynamic job runner in combination with job splitting for blast jobs. My main interest is to create a rule where both the size of the query and the database are taken into consideration in order to select DRMAA and splitting options. My first question is what is the status on dynamic job runner? I found these two threads, but is not clear to me if this feature is part of galaxy-dist already: http://lists.bx.psu.edu/pipermail/galaxy-dev/2011-October/007160.html http://lists.bx.psu.edu/pipermail/galaxy-dev/2012-June/010080.html My second question is if there is any documentation other than the threads above to configure something like what I describe? In any case, there is very good information from John in these emails and I think that should get me started at least. Cheers, Carlos

2 7

Re: [galaxy-dev] Where should I put a tool's required binaries?
by Joel Rosenberg 05 Nov '12

05 Nov '12

Sorry for bumping this, but it seems like such a standard boilerplate step of installing a tool that someone muts know how. -Joel > > I installed the?bedtools tool from the public toolshed to my galaxy cluster. The jobs were failing because I hadn't installed the required binaries: > > ? ?An error occurred running this job: /opt/sge/default/spool/execd/ip-10-194-50-118/job_scripts/2: line 13: genomeCoverageBed: command not found > > Taking a closer look at the toolshed's page, I noticed there were a handful of required binaries (genomeCoverageBed,?intersectBed, etc). > > So I downloaded BEDTools and compiled all the binaries. I've put them in well organized directories using symlinks to specific versions, etc. The final executable directory containing symlinks to these binaries is "/mnt/galaxyTools/shed_tool_binaries/bin/". > > I can make a snapshot of the tools volume so that these compiled binaries are always available to me when I bring up my cluster, but how do I integrate them into the PATH in a way that lets the bedtools galaxy tool see them, but also survive cluster shutdowns? > > Thanks, > > -Joel >

3 5

aaChanges
by Scooter Willis 05 Nov '12

05 Nov '12

Trying to work with aaChanges under Human Genome Variation using an Amazon EC2 cloudman launched instance. The output is generated by Filter Pileup and has HG19 associated for the Database/build. The gene set annotations imported from USCS also have HG19. I get the following errors when selecting input data set and appears to be the same problem reported 2/2011(http://user.list.galaxyproject.org/Problems-using-aaChanges-tool-td4… Also trying to sort through what looks to be an issue with using pileup for SNP calling in the 10 column format. Column 3 is the reference base and column 4 is the consensus base. I have numerous examples where reference base = consensus base with a breakout of the number of A T C G represented as a count. For aaChanges I need an input line for each non-zero count of A T C G from the pileup report to test which of those SNPs would actually result in an amino acid change. Doesn't seem to be an easy thing to do in Galaxy. Any recommendations on how others are doing SNP calling from exome data and detecting amino acid changes? Does anyone have a published workflow they would recommend or could share? [cid:197927B4-3E74-49CB-B585-E6FA6A0E8CC4]

1 0

phylotastic hackathon (Jan 28 - Feb 1, Tucson, AZ) of possible interest to galaxy developers
by Arlin Stoltzfus 05 Nov '12

05 Nov '12

Dear galaxy developers-- I'd like to bring your attention to the call for participation included below this message. A "Phylotastic" system is a distributed tree-of-life delivery system composed of web services. Although it is not readily apparent from the presentation linked below, the project includes some work on using Galaxy as a framework for managing a phylotastic workflow. See the demos page (http://phylotastic.org/demos.html) and the "Making Galaxy Phylotastic!" screencast (http://youtu.be/kMME658xOu4 for more. I would be happy to respond to questions about the project. Please consider applying if you are excited by the project and think that you can contribute. Regards, Arlin ----- Phylogenies! Hacking! Tucson in January! An implicit promise of the Tree of Life project is that, ultimately, expert knowledge of species phylogeny will be accessible and usable by everybody. In other words, we will all be able to get the species trees we need, in a useable form, when we need them. The Phylotastic project aims to make that vision a reality, by developing a loosely coupled system of components that, in response to a user’s query (a list of taxa plus conditions), will rectify names, find suitable source trees, prune and graft to get the right species, estimate branch lengths, and return the results with metadata on sources and methods. In June 2012, the HIP (Hackathons, Interoperability, Phylogenies) working group of NESCent staged a hackathon (http://en.wikipedia.org/wiki/Hackathon) to prototype components of a Phylotastic system, and implement demos to show their potential. Thanks to 25 participants who responded to an open call (just like this one), that hackathon was an extraordinary success (see http://phylotastic.org/) Now we are gearing up for a second hackathon, to take another step toward providing computable, convenient, credible access to the Tree of Life. We aim to recruit a diverse group of participants, including students, faculty, postdocs, and staff of both genders and from different backgrounds. Only some of the seats at the hackathon will be filled by expert hackers who spend their time coding. We also need folks who can: * Provide knowledge of workflows and downstream uses of trees * Design user interfaces * Test software * Make screencasts, develop tutorials, and document user experiences Applications are now being accepted to Phylotastic 2, which will take place January 28th, 2013 to February 1st, 2013 at the BIO5 facility in warm and sunny Tucson, AZ (http://bio5.arizona.edu/about-bio5) Information on how to apply is provided below. Partial support (and, if funds allow, full support) for travel, food and lodging will be available to each successful applicant who indicates need. We particularly welcome applications from women and members of underrepresented groups. To understand how you might be able to contribute, review the slideshow (ppt format, http://bit.ly/RWRgIc, or PDF format, http://bit.ly/POaoci) consult the web site (phylotastic.org) or contact a member of the HIP leadership team (listed below). Sincerely, the HIP (Hackathons, Interoperability and Phylogenies) Leadership Team HOW TO APPLY Before 16 November, 2012 at midnight, EST, fill out the online form here http://tinyurl.com/PhyloTastic2. Note that: * The application form asks you to describe how you can contribute to Phylotastic. Remember that we are not just looking for expert coders. There are many other ways to contribute. * Support for travel, housing and meals will be available to each successful applicant who indicates need. * Please understand that your application is not a guarantee of participation in the event. Funds and space are limited: we may not be able to sponsor every individual who is qualified to participate. LEADERSHIP TEAM Karen Cranston, karen.cranston(a)nescent.org Brian Sidlauskas, brian.sidlauskas(a)oregonstate.edu Arlin Stoltzfus, arlin(a)umd.edu Mike Rosenberg mrosenb(a)asu.edu Brian O’Meara, bomeara(a)utk.edu Mark Westneat mwestneat(a)fieldmuseum.org Enrico Pontelli epontell(a)cs.nmsu.edu Rutger Vos rutgeraldo(a)gmail.com Naim Matasci nmatasci(a)iplantcollaborative.org ------- Arlin Stoltzfus (arlin(a)umd.edu) Fellow, IBBR; Adj. Assoc. Prof., UMCP; Research Biologist, NIST IBBR, 9600 Gudelsky Drive, Rockville, MD, 20850 tel: 240 314 6208; web: www.molevol.org

2 1

Mapping tools
by Lee Hunt 05 Nov '12

05 Nov '12

Hi I'm a new Galaxy user and last week managed to map some sequences, but since Thursday the jobs won't start, even when I try re-running the one ones I did last week Lee --

1 0

Re: [galaxy-dev] Looking for recommendations: How to run galaxy workflows in batch
by Sascha Kastens 03 Nov '12

03 Nov '12

Hi Dev-Team, are you planning or maybe working on an update which enables the possiblilty to run workflows in batch mode with paired end data? Cheers, Sascha

3 3