Skip to content

[Stats results mapper] - Include viability category field on final stats_results_parquet#538

Open
francisco-ebi wants to merge 3 commits into
devfrom
feature/viability-category-field
Open

[Stats results mapper] - Include viability category field on final stats_results_parquet#538
francisco-ebi wants to merge 3 commits into
devfrom
feature/viability-category-field

Conversation

@francisco-ebi
Copy link
Copy Markdown
Contributor

I noticed that in the function that generates the viability_stats dataframe (viability_stats_results) is already picking the correct field(the viability statement) based on the VIA parameter version. So it would only be a matter of propagating the field through the intermediate parquets.

So I updated 2 stages of the statistical results mapper to make the "category" field available on the final statistical_results parquet:

  • Updated the 1st stage (manual phenotype calls processing), when the viability dataframe is updated based on the columns of the stats_analysis_out_parquet, I added the missing "category" field.
  • Updated the last stage (generate doc_id and final output), before the stats_results dataframe is saved to disk, I have added the category field to stats_results_column_list

Let me know if I have missed anything.

@francisco-ebi francisco-ebi requested a review from ficolo January 27, 2026 15:21
@francisco-ebi francisco-ebi changed the title [Stats results mapper] - Include viability category field on final parquet [Stats results mapper] - Include viability category field on final stats_results_parquet Jan 27, 2026
@ficolo ficolo force-pushed the feature/viability-category-field branch from 7f0a23a to 405a219 Compare May 1, 2026 22:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant