Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Irregular Download Path Usage #158

Closed
roshankern opened this issue May 24, 2022 · 6 comments
Closed

Irregular Download Path Usage #158

roshankern opened this issue May 24, 2022 · 6 comments

Comments

@roshankern
Copy link

I trying to download just the first plate for idr0013-screenA and am struggling to use the aspera download client to complete this partial download. The IDR download tutoral mentions to remove the leading /uod/idr/filesets/<idrNNN>-<author>-<description>/ when submitting a partial download command. However, the download paths for idr0013 do not follow the /uod/idr/filesets/<idrNNN>-<author>-<description>/ format.

For example, plate LT0001_02 lists its relative path as ../screens/LT0001_02--ex2005_11_16--sp2005_02_17--tt17--c3.screen. Attempting to run
ascp -TQ -l40m -P 33001 -i "path/to/asperaweb_id_dsa.openssh" idr0013@fasp.ebi.ac.uk:screens/LT0001_02--ex2005_11_16--sp2005_02_17--tt17--c3.screen /tmp/data/ returns Session Stop (Error: Server aborted session: No such file or directory).

How should I use this relative path to complete a partial download?
Thanks!

@roshankern roshankern closed this as not planned Won't fix, can't repro, duplicate, stale May 24, 2022
@roshankern
Copy link
Author

CC @gwaygenomics to keep you in the loop

@roshankern roshankern reopened this May 24, 2022
@gwaybio
Copy link

gwaybio commented May 24, 2022

Thanks Roshan! Indeed, it would be helpful to know if there are any more specific instructions on how to troubleshoot misconstructed download paths

@pwalczysko
Copy link
Contributor

pwalczysko commented May 25, 2022

@roshankern Thank you for your comment.
The study idr0013 uses a screen format. This means that the .screen files are just textfiles which are read at the moment of importing the Plates into OMERO (and thus IDR). The .screen textfiles are pointing to the image files and these can in turn be downloaded by aspera. Your workflow to get these image files could be:

  1. Study the .screen file https://github.com/IDR/idr-metadata/blob/cb649f6e65b5cf1690eb4f29804eae234fc2dece/idr0013-neumann-mitocheck/screens/LT0001_02--ex2005_11_16--sp2005_02_17--tt17--c3.screen which you attempted to download
  2. Take the line https://github.com/IDR/idr-metadata/blob/cb649f6e65b5cf1690eb4f29804eae234fc2dece/idr0013-neumann-mitocheck/screens/LT0001_02--ex2005_11_16--sp2005_02_17--tt17--c3.screen#L10
  3. Copy the path to the image file, which is /uod/idr/filesets/idr0013-neumann-mitocheck/20150916-mitocheck-analysis/mitocheck/LT0001_02--ex2005_11_16--sp2005_02_17--tt17--c3/hdf5/00001_01.ch5 from that line.
  4. Adjust the path you just copied to remove the /uod/idr/filesets/idrxxxx-xxxx-xxxx motif.
  5. Insert the adjusted path to the image file into your aspera command, which gives you

ascp -TQ -l40m -P 33001 -i "path/to/asperaweb_id_dsa.openssh" idr0013@fasp.ebi.ac.uk:20150916-mitocheck-analysis/mitocheck/LT0001_02--ex2005_11_16--sp2005_02_17--tt17--c3/hdf5/00001_01.ch5
  1. You can write a script which automates the workflow 1. - 6. above, parsing the .screen file(s) and creating the aspera commands to download more image files.

We will fix the documentation on the IDR page https://idr.openmicroscopy.org/about/download.html as it is oversimplistic for the case of the particular study download you were attempting (the doc is correct for most of the studies though). I have opened an issue for that #159
Sorry about that.
Petr, OME Team

@roshankern
Copy link
Author

Works perfectly, thank you for the prompt response!

@gwaybio
Copy link

gwaybio commented May 25, 2022

Wonderful! Agreed - Thanks @pwalczysko for the very prompt reply :)

@sbesson
Copy link
Member

sbesson commented May 25, 2022

Thanks all, closing this in favor of #159 which captures the remain documentation work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants