-
Notifications
You must be signed in to change notification settings - Fork 3
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
test data upload with different files #38
Comments
We should probably wait to decide what the exact input will be before implementing this. For instance starting users won't have tsne, then many users might not bother with using sparse matrices and can have different data structures, So data upload probably should be placed at the very front of the pipeline after everything else is done. Till then we can experiment with other datasets. To start from zero I have several single cell datasets that I'm working on that can be useful. GSE67835, GSE67835 and GSE71585. Here's the code to download and process them if you want to play around This also gives a decent idea how single cell data sharing looks like right now. character delimeted expression matrices are fairly common. |
is there a (or several) standardized data formats for scRNA seq yet? We will need to specify at least some degree of formatting requirements to the user. |
the most standard thing you can find right side of assembly is an expression matrix in any shape and form possible. I think it'll be enough for us to take in the matrix - sparse or not. If not sparse -> sparsify on intake. Gene name and cell ID (barcode) matrices might be problematic but in reality, we don't really need the cell id matrix. Order is a good enough identifier. I believe sparse matrices do not have row-column names so gene names will have to be supplied as a separate file to those or embedded in somehow (as a first row) |
right now I'm just testing by re-uploading the same files and it seems to work but should test with different data or at least with truncated .tsv files to make sure it's working.
The text was updated successfully, but these errors were encountered: