Re: [galaxy-dev] visualization button

[Philippe Moncuquet]

Hi Hans-Rudolph,

Ok so the syntax in the wrapper was not the problem. My file was tabular
but the first column contained string and numbers whereas the second column
contained only numbers. When I added a 3rd column with numbers to test I
was able to see the button and generate some graphics. I wish It could have
taken the first column as the label for the second but I understand that
would produces unwanted behavior in other context. Anyway, all good, thanks
for the help.

Regards,
Philip


2014-04-08 17:33 GMT+10:00 Hans-Rudolf Hotz :

>
>
> On 04/08/2014 02:05 AM, Philippe Moncuquet wrote:
>
>> Hi Rudolph,
>>
>> Thanks for the answer. I understand that it would make no sense to allow
>> generation of graphics on non relevant data. My data is in tabular
>> format and that is the reason why I was surprise not to see that button.
>>
>>
>>  >   format="tabular" />
>>
>>
>>
> I would re-write this like:
>
> 
>   
> 
>
>
> Also, make sure your output is actually a table, ie it does consist of
> more than one (tab-separated) column.
>
>
> Hans-Rudolf
>
>
>  I wouldn't be surprised if something was wrong in my syntax. Thanks for
>> the help anyway.
>>
>> Cheers,
>> Philip
>>
>>
>> 2014-04-07 16:52 GMT+10:00 Hans-Rudolf Hotz > >:
>>
>>
>> Hi Philip
>>
>> The appearance of the visualization button depends on the datatype
>> of your output. E.g. when it is set to 'tabular', you should get the
>> button allowing you to create a scatter plot.
>>
>> However, depending on your data, it might not make much sense to
>> visualize it in 'Trackster', 'Circster' or as scatter plot.
>>
>>
>> Regards, Hans-Rudolf
>>
>>
>>
>> On 04/07/2014 02:11 AM, Philippe Moncuquet wrote:
>>
>> Hi,
>>
>> I have developed a simple script that give some statistics on an
>> assemble. It generates a tabular output. The visualization
>> button is not
>> available when I extend the output in the history pane. Is there
>> any
>> code that I need to put in my xml wrapper to get this button
>> available ?
>>
>> Regards,
>> Philip
>>
>>
>> _
>>
>> 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/

[galaxy-dev] automatically adding fasta files to "built-in" databases and selecting files questions

[Nikhil Joshi]

Hi all,

We have a local install of Galaxy that we use for testing for our
bioinformatics courses. I am creating some new tool interfaces for the
install. I want to create a tool that will allow a user to automatically
add a fasta database to the "built-in" databases (without needing to reboot
the server). Is this possible?

Along with that issue is that the number of databases for this tool can
number in the thousands. Is there a way to easily search the built-in
databases for the database you are looking for, and then use that database
in a tool? Right now, it is an enormous drop down list which is really
annoying and unwieldy.

Finally, these tools can take multiple input files, but I really don't like
the way galaxy handles that where you have to continually click on "Add
another file". Is there a method or work-around in galaxy where you can
have a multi-file select?

- Nik.

-- 
Nikhil Joshi
Bioinformatics Analyst/Programmer
UC Davis Bioinformatics Core
http://bioinformatics.ucdavis.edu/
najoshi -at- ucdavis -dot- edu
530.752.2698 (w)
___
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/

Re: [galaxy-dev] Check file before uploading

[John Chilton]

There is no mechanism in Galaxy for doing this. Galaxy for the most
part (or entirely?) does not use extensions for determining data
formats - datatypes define sniffer methods and the sniffing methods
all inspect the data on the filesystem so require completed uploads
and in turn the upload process requires a database entry.

-John

On Tue, Apr 8, 2014 at 12:39 AM,   wrote:
> Hi
>
> When selecting a file or after clicking on "Execute" to upload a file is
> it possible to check the file is appropriate i.e. by checking file extension
> etc, before the file is actually uploaded and put into the database? So the
> user can't upload the wrong file/format
>
>
>
> Thanks
>
> Neil
>
>
>
> Neil Burdett
>
> Software Engineer | The Australian e-Health Research Centre
>
> Computational Informatics
>
> CSIRO
>
> E: neil.burd...@csiro.au T: 07 3253 3626
>
> Address: Level 5, UQ Health Science Building 901/16 Royal Brisbane and
> Women's Hospital, Herston, Brisbane, QLD, 4029
>
> www.csiro.au | http://milxview.csiro.au
>
>
>
>
> ___
> 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/

[galaxy-dev] Installing S-Mart on Mac OSX local instance (updated)

[Bernardo Bello]

Hi,

I am having problems to install a tool from tool shed named S_MART on my
local Galaxy. In fact, its the first tool I'm trying to install.
The reason to install S-MART is to use DETR'PROK in Galaxy.

Here is the 'error' Galaxy shows after installing some programs from
toolshed.

I've seen this related post, but I don't know if we are talking about the
same 
problem.


Here are the commands aI've used up to now:

Thanks, Bernardo

P.S. Sorry for the duplicated email,  I mistyped the subject in the
previous one.


hg clone https://bitbucket.org/galaxy/galaxy-dist/
cd galaxy-dist
hg update stable

sh run.sh # gave errors, so see below

# solve problem at startup (
https://www.mail-archive.com/galaxy-dev@lists.bx.psu.edu/msg13354.html)
% export LC_ALL='en_US.UTF-8'
% sh run.sh

done # Go to http://localhost:8080/ and register as popn...@gmail.com
# Setup admin user (https://wiki.galaxyproject.org/Admin/Interface). To
give a user Galaxy admin privileges, add their Galaxy login ( email ) to
the list in the following config setting in the Galaxy configuration file
universe_wsgi.ini.

admin_users = popn...@gmail.com

# Set 'Tool Dependencies'
https://wiki.galaxyproject.org/Admin/Config/ToolDependencies?action=show&redirect=Admin%2FConfig%2FTool+Dependencies
mkdir tool_dependency_dir

done # add tool dependencies folder to 'universe_wsgi.ini' -> Galaxy
provides a method for managing the dependencies of Galaxy tools installed
from the Tool Shed.  In this case, it is simply necessary to set the
tool_dependency_dir option of universe_wsgi.ini to a path writable by the
Galaxy server.

done # restart server

First, I modified the universe_wsgi.ini file by removing the "#" before the
tool_config_file and tool_path lines. #
http://user.list.galaxyproject.org/Installing-new-tools-from-the-tool-shed-td4655241.html

# Then, I created a shed_tools folder in my $HOME directory before
modifying the shed_tool_conf.xml file




done # INSTALL R
done # ADD R PACKAGES
R --slave --no-save --no-restore --quiet -e 'if("RColorBrewer" %in%
rownames(installed.packages()) == FALSE){install.packages("RColorBrewer",
repos = c("http://cran.rstudio.com/";), dependencies = TRUE)}'
R --slave --no-save --no-restore --quiet -e 'if("Hmisc" %in%
rownames(installed.packages()) == FALSE){install.packages("Hmisc", repos =
c("http://cran.rstudio.com/";), dependencies = TRUE)}'


-- 

*Bernardo Bello Ortí*

PhD student

CReSA-IRTA

Campus de Bellaterra-Universitat Autònoma de Barcelona

Edifici CReSA

08193  Bellaterra (Barcelona, Spain)

Tel.: 647 42 52 63 *www.cresa.es   *
___
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/

Re: [galaxy-dev] Package/Module RPY

[Greg Von Kuster]

Hello Curt,

I believe that version 1.0.3 of the rpy package should be installing 
successfully from the main tool shed if you have a repository that contains a 
tool that defines a dependency to the rpy repository owned by devteam at 
http://toolshed.g2.bx.psu.edu/view/devteam/package_rpy_1_0_3
 
Here is the last test run for the tool shed's install and test framework for 
that repository.  I believe tis should install correctly using the dist 
repository, but if you're seeing problems, let us know.  Also, the next release 
is coming soon ( tentatively a week or so from now )..

Test runs  
2014-04-07 17:25:49  
Automated test environment  
Successful installations  
Repository dependencies - installation of these additional repositories is 
required  
Tool shed   NameOwner   Changeset revision
toolshed.g2.bx.psu.edu  package_r_2_11_0devteam 5824d2b3bc8b
Tool dependencies  
TypeNameVersion
R   package 2.11.0
Installation directory
/ToolDepsMain/R/2.11.0/devteam/package_rpy_1_0_3/82170c94ca7c
TypeNameVersion
rpy package 1.0.3
Installation directory
/ToolDepsMain/rpy/1.0.3/devteam/package_rpy_1_0_3/82170c94ca7c



On Apr 8, 2014, at 3:28 PM, "Hayes, Curt"  
wrote:

> Hi there all,
> Does anyone have RPY working? I install via toolshed and the folder is empty, 
> and shows missing dependencies.
> I have searched previous posts, nothing since 2010. I have a local install 
> (production config – postgres, etc – on CENTOS 6.5). I posted last week and 
> it fell off the list. 
> 
> From Galaxy User interface:
> Dataset generation errors
> Dataset 81: Build base quality distribution on data 9
>  
> Tool execution generated the following error message:
> Traceback (most recent call last):
>   File 
> "/apps/galaxy/galaxy-dist/tools/metag_tools/short_reads_figure_score.py", 
> line 12, in 
> from rpy import *
> ImportError: No module named rpy
>  
> I have attempted to download/install the scripts but they fail with multiple 
> errors (most posts out there have a bad URL) - 
> http://getgalaxyp.org/install.html says use: 
> curlhttp://rpy.svn.sourceforge.net/viewvc/rpy/trunk/rpy/?view=tar > rpy.tar.gz
> if you view that it redirects you to another URL.  
>  
> Via shell: R is installed: R version 2.13.0 (2011-04-13)
>  
> Can someone provide me some help please to get it working via Galaxy? I 
> understand it works in Central.
>  
> From Toolshed:
> Name
> Version
> Type
> Installation status
> rpy
> 1.0.3
> package
> Error
>  
> Toolshed Error:
> In file included from src/rpymodule2110.c:51: src/RPy.h:56:20: error: 
> Python.h: No such file or directory In file included from 
> /usr/lib64/python2.6/site-packages/numpy/core/include/numpy/ndarrayobject.h:68,
>  from 
> /usr/lib64/python2.6/site-packages/numpy/core/include/numpy/arrayobject.h:14, 
> from src/RPy.h:89, from src/rpymodule2110.c:51: 
> /usr/lib64/python2.6/site-packages/numpy/core/include/numpy/npy_common.h:79:2:
>  error: #error Must use Python with unicode enabled. 
> 
> Thanks,
> Curt
>  
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is 
> for the sole use of the intended recipient(s) and may contain confidential 
> and privileged information protected by law. Any unauthorized review, use, 
> disclosure or distribution is prohibited. If you are not the intended 
> recipient, please contact the sender by reply e-mail and destroy all copies 
> of the original message. 
> ___
> 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/

[galaxy-dev] Package/Module RPY

[Hayes, Curt]

Hi there all,
Does anyone have RPY working? I install via toolshed and the folder is empty, 
and shows missing dependencies.
I have searched previous posts, nothing since 2010. I have a local install 
(production config - postgres, etc - on CENTOS 6.5). I posted last week and it 
fell off the list.

>From Galaxy User interface:
Dataset generation errors
Dataset 81: Build base quality distribution on data 9

Tool execution generated the following error message:
Traceback (most recent call last):
  File 
"/apps/galaxy/galaxy-dist/tools/metag_tools/short_reads_figure_score.py", line 
12, in 
from rpy import *
ImportError: No module named rpy

I have attempted to download/install the scripts but they fail with multiple 
errors (most posts out there have a bad URL) - 
http://getgalaxyp.org/install.html says use: curl 
http://rpy.svn.sourceforge.net/viewvc/rpy/trunk/rpy/?view=tar > rpy.tar.gz
if you view that it redirects you to another URL.

Via shell: R is installed: R version 2.13.0 (2011-04-13)

Can someone provide me some help please to get it working via Galaxy? I 
understand it works in Central.

>From Toolshed:
Name

Version

Type

Installation status

rpy

1.0.3

package

Error


Toolshed Error:
In file included from src/rpymodule2110.c:51: src/RPy.h:56:20: error: Python.h: 
No such file or directory In file included from 
/usr/lib64/python2.6/site-packages/numpy/core/include/numpy/ndarrayobject.h:68, 
from 
/usr/lib64/python2.6/site-packages/numpy/core/include/numpy/arrayobject.h:14, 
from src/RPy.h:89, from src/rpymodule2110.c:51: 
/usr/lib64/python2.6/site-packages/numpy/core/include/numpy/npy_common.h:79:2: 
error: #error Must use Python with unicode enabled. 

Thanks,
Curt

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for 
the sole use of the intended recipient(s) and may contain confidential and 
privileged information protected by law. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply e-mail and destroy all copies of 
the original message.

___
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/

Re: [galaxy-dev] krona to metaphlan patch

[Dannon Baker]

Hey Brad, thanks for this!  I've added these to the metaphlan toolshed
repository as-is, and will be adding tests shortly.


On Tue, Apr 8, 2014 at 1:24 AM, Langhorst, Brad  wrote:

>  I'm running with these local additions to Dannon's metaphlan repo.
>
>  I think it would be better to add these to the current metaphlan repo
> than to release them standalone.
>
>
> ___
> 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/

Re: [galaxy-dev] extract_genomic_dna.py

[Jennifer Jackson]

Hi Adhemar,

Very glad this is working out for your own use. I created a ticket to 
include your suggested enhancement globally:

https://trello.com/c/jbhy3dSM

Should you wish to create a ticket in the future, this is how:
https://wiki.galaxyproject.org/Issues

Community contributions are reviewed/incorporated through pull-requests, 
if you would like to submit. No guarantees, but either way this moves it 
along and you'll then know the status:

https://wiki.galaxyproject.org/Develop
 -> See ' Source code and documentation'
https://bitbucket.org/galaxy/galaxy-central/pull-requests

Best,

Jen
Galaxy team

On 3/28/14 5:41 AM, Adhemar wrote:

Hi,
In order to have the transcript_id for each sequence extracted from 
the cuffmerge .gtf file I had to change the extract_genomic_dna.py by 
adding the following lines after line 153:


attributes = gff_util.parse_gff_attributes( feature[8] )
if ( "transcript_id" in attributes ):
 name = attributes.get( "transcript_id", None )


This way the variable name gets the transcript_id if it exists.

If it's correct, I would appreciate this modification in future galaxy 
distributions.


Thanks!
Adhemar


___
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/


--
Jennifer Hillman-Jackson
http://galaxyproject.org

___
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/

[galaxy-dev] Problem with executing newly installed tools (via admin)

[Nicolas Cybulski]

Ok,

a small update on this problem.
I have set up a local tool shed with in it a repository that holds 2 
tool definitions of the same tool but with different verision nbrs



  Dummy Tool
  
dummyTool.py $inputFile $operand $outputFile
  

  



  

  


  

  

  
  
  

  

and:


  Dummy Tool v2
  
dummyTool_v2.py $inputFile $operand $outputFile
  

  



  

  


  

  

  
  
  

  





I am successful in installing these tools in Galaxy using out own toolshed.
I get the following lines in shed_tool_conf.xml


  file="galaxy.psb.ugent.be/repos/nicyb/testbla2/4c7117d7f90d/testbla2/dummyTool_wrapper.xml" 
guid="galaxy.psb.ugent.be:/toolshed/repos/nicyb/testbla2/NicybDummyTool/1.0">

galaxy.psb.ugent.be:/toolshed
testbla2
nicyb
4c7117d7f90d
galaxy.psb.ugent.be:/toolshed/repos/nicyb/testbla2/NicybDummyTool/1.0
1.0

file="galaxy.psb.ugent.be/repos/nicyb/testbla2/4c7117d7f90d/testbla2/dummyTool_wrapper_v2.xml" 
guid="galaxy.psb.ugent.be:/toolshed/repos/nicyb/testbla2/NicybDummyTool/2.0">

galaxy.psb.ugent.be:/toolshed
testbla2
nicyb
4c7117d7f90d
galaxy.psb.ugent.be:/toolshed/repos/nicyb/testbla2/NicybDummyTool/2.0
2.0




When I look in the tool panel I can see both tools under section nicyb 
test3.
Upon selecting one I get Nicyb Dummy Tool and then a drop down with 
"version 1.0" and "version 2.0"

However, when I change the version nbrs I get the following error:

 Module MySQLdb.connections:36 in defaulterrorhandler view
OperationalError: (OperationalError) (1241, 'Operand should contain 1 
column(s)') 'INSERT INTO event (create_time, update_time, history_id, 
user_id, message, session_id, tool_id) VALUES (%s, %s, %s, %s, %s, %s, 
%s)' (datetime.datetime(2014, 4, 8, 14, 34, 48, 567645), 
datetime.datetime(2014, 4, 8, 14, 34, 48, 567654), 1L, 1L, "Tool params: 
{'operand': u'', 'tool_state': 
u'800255db31333430373735653731613935346362633961356235633261356166623236313166623137643a3762323236663730363537323631366536343232336132303232356332323465366636653635356332323232326332303232356635663730363136373635356635663232336132303330326332303232356635663732363537323735366535663732363536643631373035663661366636323566363936343566356632323361323036653735366336633263323032323639366537303735373434363639366336353232336132303232333233323232376471002e', 
'refresh': u'refresh', 'inputFile': u'22'}", 16L, 
[u'galaxy.psb.ugent.be:/toolshed/repos/nicyb/testbla2/NicybDummyTool/2.0', 
u'galaxy.psb.ugent.be:/toolshed/repos/nicyb/testbla2/NicybDummyTool/1.0'])


Is there anyone with similar experiences or an explanation for this ?

Kind regards,

Nicolas

On 04/02/2014 06:00 PM, galaxy-dev-requ...@lists.bx.psu.edu wrote:

Subject:
[galaxy-dev] Problem with executing newly installed tools (via admin)
From:
"Nicolas Cybulski" 
Date:
04/02/2014 10:38 AM

To:
galaxy-dev@lists.bx.psu.edu


Hi,

I have installed the Picard tools using the Tool-shed functionality in 
the admin tools.

The tools and requisites have been correctly installed and run correctly.
The insert statement to the event table fails however. I get the 
following error on screen:


|OperationalError: (OperationalError) (1241, 'Operand should contain 1 
column(s)') 'INSERT INTO event (create_time, update_time, history_id, 
user_id, message, session_id, tool_id) VALUES (%s, %s, %s, %s, %s, %s, 
%s)' (datetime.datetime(2014, 4, 2, 9, 32, 47, 823142), 
datetime.datetime(2014, 4, 2, 9, 32, 47, 823170), 35L, 4L, "Tool 
params: {'histWidth': u'0', 'deviations': u'10.0', 'malevel': 
u'ALL_READS', 'input_file': u'5266', 'out_prefix': u'Insertion size 
metrics', 'refresh': u'refresh', 'minPct': u'0.05', 'tool_state': 
u'800254cf01316164663833323133363237333739303833323639353065346362343762393730383966363664313a37623232363836393733373435373639363437343638323233613230323235633232333035633232323232633230323236343635373636393631373436393666366537333232336132303232356332323331333032653330356332323232326332303232363936653730373537343566363636393663363532323361323032323335333233363336323232633230323235663566373036313637363535663566323233613230333032633230323235663566373236353732373536653566373236353664363137303566366136663632356636393634356635663232336132303665373536633663326332303232366436313663363537363635366332323361323032323563323234313463346335663532343534313434353335633232323232633230323236663735373435663730373236353636363937383232336132303232356332323439366537333635373237343639366636653230373336393761363532303664363537343", 
1468L, 
[u'toolshed.g2.bx.psu.edu/repos/devteam/picard/PicardInsertSize/1.56.0', 
u'toolshed.g2.bx.psu.edu/repos/devteam/picard/PicardInsertSize/1.56.0'])


|The problem seems to be a duplicate entry of the tool_id

|[u'toolshed.g2.bx.psu.edu/repos/devteam/picard/PicardInsertSize/1.56.0', 
u'toolshed.g2.bx.psu.edu/repos/devteam/picard/PicardInsertSize/1.56.0']


|In th

Re: [galaxy-dev] Fwd: [galaxy-user] known name outputs shown in /database/files but not in galaxy windows

[ANGELICA GOMEZ ROIG]

Thanks.  Finally it worked!!  I pass the solution:
My python file:
import sys,os

def __main__():



# Command to run GEM tool. Here the Gem indexer is getting invoked along
with arguments to be passed.

cmd="gem-indexer -i "+sys.argv[1]+" -o "+sys.argv[2]
os.system(cmd)
name_gem=sys.argv[2]+".gem"
os.rename(name_gem,sys.argv[2])

if __name__ == "__main__" : __main__()

Take care



2014-04-07 15:51 GMT+02:00 John Chilton :

> Just to add to what Peter said - you definitely don't want to use
> from_work_dir and reference the outputs ($output1) in the same
> command. If you know where the file is going to be relative to your
> working directory there should be no reason to pass it to your script.
> Also I think you want format instead of format_source as the attribute
> on output.
>
> On Mon, Apr 7, 2014 at 8:49 AM, Peter Cock 
> wrote:
> > On Sat, Apr 5, 2014 at 8:07 AM, ANGELICA GOMEZ ROIG
> >  wrote:
> >> Hi Jen,
> >> I tried what you explain, but still doens't work.
> >> I did create a new datatype, gem.  And I modified my code as you
> suggested.
> >> The tool i'm using always generates by default two archives . gem and
> .log.
> >> Those are the ones that I can't show in the galaxy interface, the
> output I
> >> get is empty, the dataset_54.dat and the dataset_55.dat.  I can't
> handle to
> >> show me the .dat.gem and .dat.log ones.
> >>
> >>
> >>
> >> dataset_54.dat   (my first declared output that it's empty)
> >> dataset_54.dat.gem (the output that throws the tool)
> >> dataset_54.dat.log (the other output file that throws the tool)
> >> dataset_55.dat (my second declared output that it's empty)
> >>
> >> Here it is the gem_indexer.xml
> >>
> >> 
> >>gem_indexer.py  $input $output1
> >> $output2
> >> 
> >> 
> >> 
> >> 
> >>  >> />
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >>
> >> And the gem_indexer.py
> >>
> >> import sys,os
> >>
> >> def __main__():
> >>
> >>
> >>
> >> # Command to run GEM tool. Here the Gem indexer is getting invoked along
> >> with arguments to be passed.
> >>
> >> cmd="gem-indexer -i "+sys.argv[1]+" -o salida"
> >> os.system(cmd)
> >>
> >>
> >> if __name__ == "__main__" : __main__()
> >>
> >
> > Since you are using a wrapper script already, I would add
> > lines to rename the generated files (based on sys.argv[1]
> > plus the extensions) to the filename Galaxy is providing
> > (here sys.argv[2] and sys.argv[3]).
> >
> > Peter
> > ___
> > 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/

Re: [galaxy-dev] Can a tool upload a .loc file that is then reused by subsequent versions of the tool?

[Peter Cock]

Better test it to make sure ;)

Of course, if you really want the use the *.loc file as a static configuration
file which should be updated in sync with the tool code, that might be a
problem...

Peter

On Mon, Apr 7, 2014 at 11:09 PM, Dooley, Damion  wrote:
> Oh, great!  I'd assumed new tool versions would overwrite them so they could 
> implement changes.  But what you say is simpler and more straightforward!
>
> Thanks,
>
> D.
> 
> From: Peter Cock [p.j.a.c...@googlemail.com]
> Sent: Monday, April 07, 2014 2:23 PM
> To: Dooley, Damion
> Cc: galaxy-dev@lists.bx.psu.edu
> Subject: Re: [galaxy-dev] Can a tool upload a .loc file that is then reused 
> by subsequent versions of the tool?
>
> Isn't this how *.loc.sample files already work? If there is
> no pre-existing *.loc file, the *.loc.sample file is copied
> to become the initial *.loc file which the local Galaxy
> administrator can update/fill in as needed.
>
> Peter
___
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/

Re: [galaxy-dev] patches to bjorn's bismark wrapper

[Björn Grüning]

Hi Brad,

thanks for your patch. Do you mind to create a pull-request to my github 
account?


https://github.com/bgruening/galaxytools

Otherwise, are you ok if I push it and reference you by name?
Also, it would be good the make the non-sorting optional. Many of us 
using the calling program from methtools:


https://github.com/bgruening/methtools

And that requires a sorted BAM file to use multiple cores.

Thanks for your work!
Bjoern

Am 08.04.2014 07:39, schrieb Langhorst, Brad:

This patch updates bjorn’s bismark wrapper to work with latest bismark and 
allows methylation extraction from SAM or BAM files.
It no longer sorts the BAM from bismark (to allow methylation extraction to 
work).



___
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/

Re: [galaxy-dev] visualization button

[Hans-Rudolf Hotz]

On 04/08/2014 02:05 AM, Philippe Moncuquet wrote:

Hi Rudolph,

Thanks for the answer. I understand that it would make no sense to allow
generation of graphics on non relevant data. My data is in tabular
format and that is the reason why I was surprise not to see that button.

   
 
   



I would re-write this like:


  



Also, make sure your output is actually a table, ie it does consist of 
more than one (tab-separated) column.



Hans-Rudolf



I wouldn't be surprised if something was wrong in my syntax. Thanks for
the help anyway.

Cheers,
Philip


2014-04-07 16:52 GMT+10:00 Hans-Rudolf Hotz mailto:h...@fmi.ch>>:

Hi Philip

The appearance of the visualization button depends on the datatype
of your output. E.g. when it is set to 'tabular', you should get the
button allowing you to create a scatter plot.

However, depending on your data, it might not make much sense to
visualize it in 'Trackster', 'Circster' or as scatter plot.


Regards, Hans-Rudolf



On 04/07/2014 02:11 AM, Philippe Moncuquet wrote:

Hi,

I have developed a simple script that give some statistics on an
assemble. It generates a tabular output. The visualization
button is not
available when I extend the output in the history pane. Is there any
code that I need to put in my xml wrapper to get this button
available ?

Regards,
Philip


_
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/