-
Notifications
You must be signed in to change notification settings - Fork 16
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
Comments
CC @gwaygenomics to keep you in the loop |
Thanks Roshan! Indeed, it would be helpful to know if there are any more specific instructions on how to troubleshoot misconstructed download paths |
@roshankern Thank you for your comment.
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 |
Works perfectly, thank you for the prompt response! |
Wonderful! Agreed - Thanks @pwalczysko for the very prompt reply :) |
Thanks all, closing this in favor of #159 which captures the remain documentation work |
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 runascp -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/
returnsSession Stop (Error: Server aborted session: No such file or directory)
.How should I use this relative path to complete a partial download?
Thanks!
The text was updated successfully, but these errors were encountered: