Create and analyse dependency graph

[AlexandraVolokhova]

Observation:
Currently there're no documented conventions on how different methods in different modules (environments, gflownet agent, policies, proxies) interact with each other and it makes it difficult to introduce changes in each of the module without breaking something in this interaction. It has been a source of bugs in the past multiple times.

Proposal:
Let's create and analyse the graph of the existing dependencies, document it, and then look into how we may want to simplify it. I remember @josephdviviano generated such a graph sometime ago, maybe we could revive this effort and look into it together?

[josephdviviano]

Yes feel feee to include me in this effort :) Joseph (Mobile)

…

On Wed, Jul 10, 2024 at 11:14 Alexandra ***@***.***> wrote: *Observation:* Currently there're no documented conventions on how different methods in different modules (environments, gflownet agent, policies, proxies) interact with each other and it makes it difficult to introduce changes in each of the module without breaking something in this interaction. It has been a source of bugs in the past multiple times. *Proposal:* Let's create and analyse the graph of the existing dependencies, document it, and then look into how we may want to simplify it. I remember @josephdviviano <https://github.com/josephdviviano> generated such a graph sometime ago, maybe we could revive this effort and look into it together? — Reply to this email directly, view it on GitHub <#333>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7TL2ROXSEJBDLIHFMSCWLZLVFUNAVCNFSM6AAAAABKVECN76VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYDCMBUGM3DQOA> . You are receiving this because you were mentioned.Message ID: ***@***.***>