Hi Liisa and Peter,
There was an issue if your workflows were created using the ncbi blast tools
from the distribution (e.g. versions 0.0.11) and you only had installed the
latest tools from the toolshed (e.g. versions 0.0.13). This has been corrected
in changesets 7754:371f6770d25c through 775
Hi Lance,
On Sep 27, 2012, at 4:37 PM, Lance Parsons wrote:
> I'm actually still a bit confused as to what the expected workflow is.
> Should I be able to clone the tool shed repo to my local development
> workstation (TOOL_DEV_LOCAL_DIR), commit a change, and then push that change
> back to
I'm actually still a bit confused as to what the expected workflow is.
Should I be able to clone the tool shed repo to my local development
workstation (TOOL_DEV_LOCAL_DIR), commit a change, and then push that
change back to the Tool Shed?
I've added some comments inline to clarify.
Greg Von
Hi Galaxy team,
I tried to do collapse FASTA sequences for removing the duplicate reads.
but error occured due to the lowercase letters at both the ends of the
sequences. Is there any option available to clean my reads? some of my
reads contains hyphen too.
Thanks,
D.
--
-
What version of Galaxy are you using? I cannot reproduce the issue using the
most recent distribution or galaxy-central.
Also, there should be a full stacktrace in your paster.log. Can you share that
please?
Thanks,
J.
On Sep 27, 2012, at 11:05 AM, Liisa Koski wrote:
> Hello,
> I'm t
On Thursday, September 27, 2012, Greg Von Kuster wrote:
> Hello Peter,
>
> My recent change set 7753:c28c5f906c6b added the ability to view a tool
> shed repository's README file from the pop-up menu on pages in the tool
> shed repository as well as in the Galaxy Admin UUI for installed
> reposito
Hi Peter,
I've handled this request in change set revision 7761:9972ac6ee91d, which will
be included in the next Galaxy release scheduled for about 10 days from now.
Thanks!
Greg Von Kuster
On Aug 28, 2012, at 9:48 AM, Peter Cock wrote:
> P.S. It would be nice to automatically line wrap the
Hello Peter,
My recent change set 7753:c28c5f906c6b added the ability to view a tool shed
repository's README file from the pop-up menu on pages in the tool shed
repository as well as in the Galaxy Admin UUI for installed repositories.
Since many of these README files are rather large, I neede
Hello,
I'm trying to create a custom visualization in Trackster. I am doing the
following steps. Visualization -> New Visualization -> Add a Custom Build
I get directed to the url below:
http://galaxy.ca:8080/user/dbkeys?use_panels=True
But the web page says:
Server Error
An error occurred. Se
On Sep 20, 2012, at 6:25 PM, Chebbi Mohamed Amine wrote:
> Hi Galaxy-team !
>
> I have uploaded the latest version of Galaxy of 05/09. However when I run
> run.sh I have the message below and I haven't found how to fix that:
>
> "TypeError: Invalid argument(s) 'server_side_cursors' sent to
> c
Hello Joachim,
It sounds like you may be pushing changes from your development environment to
your tool shed repository using hg from the command line - is this correct? if
so, you must manually make all changes you want to your local repository before
pushing the changes to the tool shed repo
Hi Greg,
Indeed, I mean the tool config wrapper, named razers3_wrapper.xml, when
I mention 'tool config'.
This xml is the alpha version, and is loaded correctly in my
development Galaxy. So I pushed it to the repository
=
Changeset 997118f8f033
added:
razers
Hello Joachim,
On Sep 27, 2012, at 8:05 AM, Joachim Jacob wrote:
> Hi all,
>
> As a test, I have uploaded some template files to a newly created repository
> on our test toolshed.
This is great! It's good to hear when the Galaxy community is using local tool
sheds within their environments.
Hi all,
As a test, I have uploaded some template files to a newly created
repository on our test toolshed. I pulled that repository on my
development machine using mercurial: from this folder I start now
developing the tool wrapper.
I have noticed that once the tool name has been set in the
On Thu, Sep 27, 2012 at 11:32 AM, Joachim Jacob wrote:
> Hi all,
>
>
> I am writing a wrapper around Razers mapper. Currentty, Razers has three
> versions, the latest being razers3.
>
> Since it's under development, what is the best way to deal with new
> versions?
>
> - write a different tool con
Hi all,
I am writing a wrapper around Razers mapper. Currentty, Razers has three
versions, the latest being razers3.
Since it's under development, what is the best way to deal with new
versions?
- write a different tool config for every version, giving them different
ids like 'razers3', '
16 matches
Mail list logo