Question: Galaxy On Cloud Not Recognizing .Txt Files As Fastq
0
gravatar for karlerhard@berkeley.edu
7.7 years ago by
Hello, I have been able to get Galaxy to instantiate on our Cloud account, and would like to use the NGS tools to trim and map Illumina libraries. However, when I tried to import .txt files (the data contained in these files are in fastq format) located in an S3 bucket, Galaxy did not recognize them as fastq data. I tried to import the files via the URL of the S3 bucket, and Galaxy just imported the actual name of the URL rather than the file itself. Do I need to change the extension of these .txt files to .fastq? Or have I gotten something wrong with respect to the location of the data in the S3 bucket? thanks for any help! karl
galaxy • 1.7k views
ADD COMMENTlink modified 7.7 years ago by Enis Afgan680 • written 7.7 years ago by karlerhard@berkeley.edu90
0
gravatar for Dannon Baker
7.7 years ago by
Dannon Baker3.7k
United States
Dannon Baker3.7k wrote:
Karl, For the URL you're pasting, is it the full path to a file in your s3 bucket, including the protocol (http://) ? For galaxy to recognize that it needs to pull from a URL rather than the contents of the box, you need to use the full string. -Dannon
ADD COMMENTlink written 7.7 years ago by Dannon Baker3.7k
I have uploaded Illumina fastq file and use the Groomer
ADD REPLYlink written 7.7 years ago by Wong,Kwong K10
0
gravatar for Enis Afgan
7.7 years ago by
Enis Afgan680
Enis Afgan680 wrote:
Hi Karl, As a quick check, are the permissions for the S3 file set so anyone can read the file? That's required before Galaxy's upload tool will be able to access the file. Alternatively, if you don't want to set such loose permissions, you should be able to get a a signed URL for the given file using a Firefox extension S3Fox. Enis
ADD COMMENTlink written 7.7 years ago by Enis Afgan680
Ah, permissions, that may be the ticket. I will try again and see. thanks a lot! karl
ADD REPLYlink written 7.7 years ago by karlerhard@berkeley.edu90
I changed the permission for the files to public (everyone can open/download), but this did not fix the problem. Also, to answer Dannon's question, I am entering the full path for these files, eg. https://s3.amazonaws.com/bucketname/xyz.txt (from an S3 bucket or from elsewhere) always had a .fastq extension. Not sure whether this is an issue for galaxy or not.
ADD REPLYlink written 7.7 years ago by karlerhard@berkeley.edu90
0
gravatar for Daniel Blankenberg
7.7 years ago by
Daniel Blankenberg ♦♦ 1.7k
United States
Daniel Blankenberg ♦♦ 1.7k wrote:
Hi Karl, Using the upload tool for https URLs was added in changeset 5220:425076fe5ea0. I am not sure when this will make it to the Cloud image, but meanwhile, if you can access the file without using ssl (just 'http'), you should be able to upload. If this is not the issue you are experiencing please let us know. Do not hesitate to contact us if you need further assistance. Thanks for using Galaxy, Dan
ADD COMMENTlink written 7.7 years ago by Daniel Blankenberg ♦♦ 1.7k
Thanks Dan. The revision of Galaxy is the problem - the instance of Galaxy on the cloud is a month old now; it is at revision 5064 so. I'll release an update in the coming days along with an updated CloudMan. Enis
ADD REPLYlink written 7.7 years ago by Enis Afgan680
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 181 users visited in the last hour