-
-
Notifications
You must be signed in to change notification settings - Fork 33
Open
Description
This issue tracks getting going with adding data intended for use in the spatial workshop. For the first instruction notebook, we plan to use SCPCS000190/SCPCL000429, so we'll want to add this to S3. There is no setup needed as this data can be read in directly.
I think this makes sense to store as (of course includes making some new prefixes)
s3://ccdl-training-data/training-modules/spatial/data/wilms-tumor/raw/SCPCS000190/
For demo, we might structure content like space ranger output, aka inside an outs folder, which would leave us with:
s3://ccdl-training-data/training-modules/spatial/data/wilms-tumor/raw/SCPCS000190/outs/raw_feature_bc_matrix/
s3://ccdl-training-data/training-modules/spatial/data/wilms-tumor/raw/SCPCS000190/outs/filtered_feature_bc_matrix/
s3://ccdl-training-data/training-modules/spatial/data/wilms-tumor/raw/SCPCS000190/outs/spatial/
Storing this in raw allows us to export in the workshop to data/wilms-tumor/processed/SCPCS000190, but I'm honestly not tied to the raw/processed divide here if others aren't into it.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels