search

Circuitscape / cloudCS

Circuitscape HTML interface
Other
0 stars 0 forks source link

CloudCS fails with gz ascii grid inputs #15

Open bmcrae opened 10 years ago

bmcrae commented 10 years ago

When loading ascii grids compressed in .gz format, the following error is returned. Not sure if this is a bona fide bug since I'm not sure we currently support .gz format for CloudCS. The same files work with standalone Circuitscape, however.

Failed.
02/18/2014 06.07.22.PM:INFO:Reading maps
Storing final configuration...
Landscape size: 40000
Output maps required for - voltage: False, current: False, cumulative only: False
Parallelization requested: False
Your roles: ['user']
Verifying profile limits...
Verifying configuration...
Reading from cloud store: gdrive://200x200mag6points.asc.gz/0B2RyqHhLbsf9T1pkaE40eGJzVGs
Reading from cloud store: gdrive://200x200mag6resist.asc.gz/0B2RyqHhLbsf9UE5vZEZ3Z08wWFk
Preparing cloud store output folder: gdrive://cs/0B2RyqHhLbsf9OXhmcG1haE9wSWs
tanmaykm commented 10 years ago

We do have support for gz files. Looking at the logs, it seems your gz files are getting identified as uncompressed text (text/plain) when they should be application/x-gzip for gzipped files:

02/14/2014 03.51.08.PM:DEBUG:cloudCS.store: got file_id gdrive://2000x3000mag8resist.asc.gz/0B2RyqHhLbsf9SXlsRVI3eEJyd0E of type <type 'unicode'>
02/14/2014 03.51.09.PM:DEBUG:cloudCS.store: file mime type: text/plain

Could you double check / e-mail the file that was uploaded?

tanmaykm commented 10 years ago

This turned out to be an issue with the automatic Google Drive sync program, which is probably setting incorrect mime type. Works fine when uploaded from the browser interface.

Closing this as it is not an issue with cloudCS.

bmcrae commented 10 years ago

Good to know. I've reported this on the drive forum. Thanks Tan.

On Sun, Feb 23, 2014 at 5:28 AM, Tanmay Mohapatra notifications@github.comwrote:

Closed #15 https://github.com/Circuitscape/cloudCS/issues/15.

Reply to this email directly or view it on GitHubhttps://github.com/Circuitscape/cloudCS/issues/15 .

ViralBShah commented 10 years ago

Should we leave it open as upstream and close when fixed upstream?

Perhaps, also include the issue in Notes on the main page?

tanmaykm commented 10 years ago

Yes, let's keep it open. Here's the link to the report Brad filed in the Google Drive forum: https://productforums.google.com/forum/#!category-topic/drive/report-a-problem/G58uEQCSHlQ

tanmaykm commented 10 years ago

Actually I faced this today even when I uploaded using the browser interface. We will have to build some checks of our own to handle this.