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
Some sample-related data in our pipeline ends up in INFO fields: grouped information about multiple callers (e.g. VAF list for all callers), some annotation scores, etc.
As this data is in INFO fields, it is written over everytime a new sample is inserted, as expected.
However, it turns out that some biologists want to use those annotations, and they can't anymore.
I see 3 solutions, but feel free to suggest anything else:
Change our pipeline. This might be more work than changing cutevariant and all of our previous data won't fit cutevariant. Changing all the old VCFs might get tricky.
Make our biologists stop using those annotations
This cutevariant update so we can send the data to the genotype table when data is newly inserted:
The text was updated successfully, but these errors were encountered:
Some sample-related data in our pipeline ends up in INFO fields: grouped information about multiple callers (e.g. VAF list for all callers), some annotation scores, etc.
As this data is in INFO fields, it is written over everytime a new sample is inserted, as expected.
However, it turns out that some biologists want to use those annotations, and they can't anymore.
I see 3 solutions, but feel free to suggest anything else:
Change our pipeline. This might be more work than changing cutevariant and all of our previous data won't fit cutevariant. Changing all the old VCFs might get tricky.
Make our biologists stop using those annotations
This cutevariant update so we can send the data to the genotype table when data is newly inserted:
The text was updated successfully, but these errors were encountered: