Merged metafounder code inconsistency

[XingerTang]

The changes of Pedigree.py made in the PR #27 set self.Metafounder to be lists, while in the AlphaPeel, tinypeel.runPeelingCycles still treats it as strings. So it would raise an error like the following:

if pedigree.AAP.get(mfx) is None:
       ^^^^^^^^^^^^^^^^^^^^^
TypeError: unhashable type: 'list'

Since the current AlphaPeel release is using an older commit, it is not affected by this inconsistency.

But we need to set up a test and quality-assurance pipeline for tinyhouse as well to ensure this won't happen again.

[XingerTang]

@RosCraddock has updated the AlphaPeel, and the tests have all passed with her new code (RosCraddock/AlphaPeel@32bab25). Changes would be pulled to the upstream repository soon.

Our next question is how to set up workflows of submodule testing to make everything work more efficiently.

[gregorgorjanc]

This should have been picked up by Github actions, no!?

[XingerTang]

This should have been picked up by Github actions, no!?

The AlphaPeel reference is not updated in the GitHub repo, so the test action is not affected. I was updating the local AlphaPeel tinyhouse reference and therefore captured the error. Ros has already implemented the relevant changes for AlphaPeel, so a new AlphaPeel PR open soon with new tinyhouse and new changes implemented in AlphaPeel.

[gregorgorjanc]

Hmm, you mean:

A) tinyhouse git submodule ref is not captured in AlphaPeel -that must be false or we are doing something wrong or

B) AlphaPeel version is not captured in tinyhouse - that is true and no way for us to ensure link between tinyhouse with AlphaPeel, but since we have A, all should be well, unless I am missunderstanding the issue here