-
Notifications
You must be signed in to change notification settings - Fork 0
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
cell_to_library lines don't seem to be written into the MANIFEST #13
Comments
There is more bundle interacting code at https://github.com/ebi-gene-expression-group/scxa-control-workflow/blob/develop/main.nf#L1237 . And while there is also a lot of mention of CELL_TO_LIBRARY there , I don't see there either where the lines for cell_to_library in the manifest would go. |
I think that the issue is that in atlas-prod develop it simply interacts directly with the file if it exists, but in the anndata-tweak branch, it is asking for the cell_to_library entry in the manifests (and failing): as that has never lived in the MANIFESTs. So it doesn't get copied and then condensed SDRF for single cell doesn't find the file and fails at https://github.com/ebi-gene-expression-group/experiment_metadata/blob/1afc9fd63cb224f09ce74d48423b8fcdc0f1cb06/single_cell_condensed_sdrf.sh#L100 . |
I have partly alleviated this through https://github.com/ebi-gene-expression-group/atlas-prod/pull/246/commits/7edc3126c8b60a0c0bb0ef3cc0388e1497969a31 but we should add a PR to this repo that makes sure that the MANIFEST file gets as well the cell_to_library line. Could you please take care of that @irisdianauy ? Thanks! |
It seems that somehow MANIFESTS are not getting the cell_to_library lines written even though studies do have cell_to_library.txt files within the bundle:
this is breaking the loading as we get errors of the type:
I don't see any lines in this workflow that implies that that is being written. Note that the E-MTAB-8848 has been quite recently generated and it doesn't include either the line in the manifest.
The text was updated successfully, but these errors were encountered: