Skip to content

[BI-1230] Truly Unknown Germplasm#260

Merged
HMS17 merged 3 commits intodevelopfrom
feature/BI-1230
Sep 21, 2022
Merged

[BI-1230] Truly Unknown Germplasm#260
HMS17 merged 3 commits intodevelopfrom
feature/BI-1230

Conversation

@HMS17
Copy link
Contributor

@HMS17 HMS17 commented Aug 17, 2022

Description

Story: BI-1230 - Truly Unknown Germplasm

Updates to support importing germplasm with truly unknown parents without using a dummy parent. This development also ensures that unrelated germplasm with unknown parents are not falsely attributed as siblings in the pedigree view display.

To import a file with unknown parents, a GID or entry number of 0 must be used. Presently only both parents unknown or female parent known and male parent unknown are supported.

Unknown parents will be displayed as "Unknown" in the parent GID columns in the All Germplasm table and in the pedigree in Germplasm Details page.

Due to Breedbase limitations, parents with more than 10 progeny will cause the pedigree viewer to error (to be fixed in BI-1579.

Dependencies

bi-api/BI-1230

Testing

For both import with parent entry numbers and import with germplasm gids, import germplasm file with:

  • Germplasm with no parents (should not be labeled unknown)
  • Germplasm with unknown female parent
  • Germplasm with known female parent and unknown male parent
  • Germplasm with unknown female parent and unknown male parent

Check import occurs successfully
Check that Unknown is displayed in GID column for All Germplasm Table for germplasm with Unknown parent
Check that Unknown displayed in pedigree on Germplasm Details page for germplasm with Unknown parent

Look at pedigree viewer and expand generations, unknown parents should be displayed and be separate nodes from each other

Checklist:

  • I have performed a self-review of my own code
  • I have tested my code and ensured it meets the acceptance criteria of the story
  • I have create/modified unit tests to cover this change
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to documentation
  • I have run TAF: <link to TAF run>

@HMS17 HMS17 marked this pull request as ready for review September 7, 2022 21:23
Copy link
Member

@timparsons timparsons left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dev testing passed. Code looks good with one minor change request

* @param femaleParentUnknown
* @param maleParentUnknown
*/
public static parsePedigreeStringWithUnknowns(pedigreeString: string, femaleParentUnknown: string, maleParentUnknown: string, gid: string) : Pedigree {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like the femaleParentUnknown and maleParentUnknown additionalInfo fields are booleans. Can the types of the parameters in this method can be updated to reflect this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vue yells at me if I change the parameter type to boolean despite it being very clearly processed as a boolean in the method. It is strange.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, thanks for looking into this!

* @param femaleParentUnknown
* @param maleParentUnknown
*/
public static parsePedigreeStringWithUnknowns(pedigreeString: string, femaleParentUnknown: string, maleParentUnknown: string, gid: string) : Pedigree {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, thanks for looking into this!

@HMS17 HMS17 merged commit b3ace4d into develop Sep 21, 2022
@HMS17 HMS17 deleted the feature/BI-1230 branch September 21, 2022 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants