Create a System Diagram

[anisham197]

Create a System Diagram

[anisham197]

https://docs.google.com/document/d/1yjjP3cIfvOWuLhptJP5S65Az0byGXbNObedTlrNk7ts/edit?usp=sharing - Initial doc containing the various components needed for a PoC and questions we would have to answer for each component

[craffel]

Thanks a lot for making that. The only component I'm confused about is the validator - what do you see that as doing?

[anisham197]

I'm not sure if we need this for a PoC or if it's needed at all. But since the changes to the model are passed by the user and not computed by us, there could be discrepancies?

For eg. A model M_O (stored on our VCS) is trained with some changes A to become model M_A. The model M_A is then trained again with some changes B to become M_B. If the training code is written such that only changes B are communicated to our Diff File creator, and the current model we have access to from the VCS is M_O, then when we try to reconstruct the model i.e. apply B to M_O we won't get the model M_B. The Validator would check if M_O + B == M_B and catch errors like this.

Ideally the user should communicate both changes A and B to our Diff file creator, and the validator would prevent errors when there are breaks to this pattern.