You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was just reviewing the tiledbsoma guide and noticed that it'd be very hard to reconstruct the lineage in particular of this AnnData that's appended here:
But in general, while the run_uid allows to go back to the generating run for every row in the store, if a run appends 100 AnnDatas, it's complicated to know which AnnData ends up there.
Hence, two suggestions:
We encourage users to append AnnData-like artifacts rather than AnnData objects to a store
In addition to the lamin_run_uid, we also store a lamin_source_artifact_uid column
The text was updated successfully, but these errors were encountered:
I was just reviewing the tiledbsoma guide and noticed that it'd be very hard to reconstruct the lineage in particular of this AnnData that's appended here:
But in general, while the
run_uid
allows to go back to the generating run for every row in the store, if a run appends 100 AnnDatas, it's complicated to know which AnnData ends up there.Hence, two suggestions:
lamin_run_uid
, we also store alamin_source_artifact_uid
columnThe text was updated successfully, but these errors were encountered: