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
The translators are able to standardize fusion caller output to AssayedFusion objects. In #228 I created pydantic classes for the relevant callers (I plan on ultimately dropping support FusionMap and MapSplice since there is no online documentation).
We should develop a series of extraction methods to convert fusion caller output to pydantic classes to enable downstream standardization. I realized that @jsstevenson implemented a similar feature in the MAVE work for processing score set records, so I think a similar thing can be implemented here. For example, if we had a csv that contained 100 detected fusions from JAFFA, we could create a list of 100 JAFFA objects using the following code:
Feature description
The translators are able to standardize fusion caller output to
AssayedFusion
objects. In #228 I created pydantic classes for the relevant callers (I plan on ultimately dropping support FusionMap and MapSplice since there is no online documentation).We should develop a series of extraction methods to convert fusion caller output to pydantic classes to enable downstream standardization. I realized that @jsstevenson implemented a similar feature in the MAVE work for processing score set records, so I think a similar thing can be implemented here. For example, if we had a csv that contained 100 detected fusions from JAFFA, we could create a list of 100
JAFFA
objects using the following code:Example output for the first item in the list:
We could then iterate through this list using
from_jaffa
to create the standardizedAssayedFusion
objectsUse case
This will make the standardization of the fusion data more efficient and allow for validation checks
Acceptance Criteria
Extraction methods have been created for each pydantic class and the attributes in the pydantic classes have been appropriately updated
Proposed solution
No response
Alternatives considered
No response
Implementation details
No response
Potential Impact
No response
Additional context
No response
Contribution
Yes, I can create a PR for this feature.
The text was updated successfully, but these errors were encountered: