Conversation
|
|
Currently, this tool can download from BioImages-core. Let me check if we can download from other collections. |
|
I don't find what the error is :( |
|
error code of one ... Try to not use the pipe and see where it is crashing. In the curl, or somewhere else... |
| curl https://www.ebi.ac.uk/biostudies/api/v1/studies/$study/info -s |jq -r .ftpLink >>ftpLink.txt | ||
| #end if | ||
| curl -s https://www.ebi.ac.uk/biostudies/api/v1/studies/$accession/info | jq -r .ftpLink >> ftpLink.txt && | ||
| wget -q -r -l 0 -i ftpLink.txt && |
There was a problem hiding this comment.
How do we make sure that we only get tif files?
There was a problem hiding this comment.
We get the whole ftp directory of that accession.
There was a problem hiding this comment.
There is no particular directory structure. So I download everything and filter for tif later.
There was a problem hiding this comment.
Can you not filter this file first, instead of downloading everything and throwing that away later?
| </data> | ||
| <data format="txt" name="ftplinks" from_work_dir="ftpLink.txt" label="FTP Links"> | ||
| <collection name="images" type="list" label="${tool.name} on ${on_string}: TIFF Images"> | ||
| <discover_datasets pattern="(?P<designation>.*)\.tif" format="tif" directory="ftp.ebi.ac.uk" recurse="true" /> |
There was a problem hiding this comment.
Do you know if the format is tiff or ome.tiff ?
There was a problem hiding this comment.
In the UI filtering options, it shows only tif as an option. I kept as it is.
Btw, there are also several other image formats like lif, lsm, mrc and so on. I skipped them because there is no Galaxy datatype.
There was a problem hiding this comment.
We can change the UI. The question is if the downloaded files are proper OME.tiff files. https://github.com/galaxyproject/galaxy/blob/5c686c62ecb5c23fa31ebae30db4f5a56c63630a/lib/galaxy/datatypes/images.py#L309
There was a problem hiding this comment.
how to check that?
There was a problem hiding this comment.
| <collection name="images" type="list" label="${tool.name} on ${on_string}: TIFF Images"> | ||
| <collection name="images" type="list" label="${tool.name} on ${on_string}: Images"> | ||
| <discover_datasets pattern="(?P<designation>.*)\.tif" format="tif" directory="ftp.ebi.ac.uk" recurse="true" /> | ||
| <discover_datasets pattern="(?P<designation>.*)\.png" format="png" directory="ftp.ebi.ac.uk" recurse="true" /> |
There was a problem hiding this comment.
should this 3 different collections? what is the usecase? Or should the users then filter the collection afterwards according to filetypes?
There was a problem hiding this comment.
in most cases, there is only one type of images. But it is better to create different collections.
Co-authored-by: Björn Grüning <bjoern@gruenings.eu>
modeparam as select