Closed asizemore closed 10 months ago
Note this is probably that the metadata var is missing data for a sample
wouldnt that produce an empty row? rather than a missing one? i was going to guess a sample failed the dada2 workflow and so has no associated assay record
I thought we restricted to complete cases somewhere, so if one sample had NA for age then that sample gets kicked out and we'd get differing numbers of rows. I also thought that we already removed all samples without assay records because why have them for mbio, but maybe that didn't happen. Not sure
The check from completeness is baked into the correlation calculation I'm pretty sure. Do a sample that doesn't have age but does have height will still be included in the height calculation for ex. The row remains, and is contextually ignored.
I'm pretty sure they removed the assay record and left the upstream records. But I'll check
I'm pretty sure they removed the assay record and left the upstream records. But I'll check
Ahhhh that could be it. But that also confuses me because AbundanceData
has a check to ensure the sampleids from the metadata and sample ids from the assay data are the same. Wouldn't we see an error from making the AbundanceData
object if we were missing assay records?
hmmmm. yea.. plus, were asking for both the taxa and metadata as a single stream, which means we shouldnt get back samples without assays in the first place. this is becoming interesting.
its bc there isnt actually any metadata.. the AbundanceData object checks the ids, which exist. but the helper to getSampleMetadata has an option to strip the ids. when it does this it returns a completely empty 0 rows/ 0 cols data.table.
I think itd make sense to add a warning to the getSampleMetadata helper about this case, but otherwise rely on graying the app to handle this case.
Found in a few studies, most recently in corr v metadata with
Error