[Docs] Visualizing gflownet's codebase via diagrams#150
Open
ivanmilevtues wants to merge 1 commit intorecursionpharma:trunkfrom
Open
[Docs] Visualizing gflownet's codebase via diagrams#150ivanmilevtues wants to merge 1 commit intorecursionpharma:trunkfrom
ivanmilevtues wants to merge 1 commit intorecursionpharma:trunkfrom
Conversation
Author
|
Hey, a quick update on our side, this week we released our diagram generaiton engine as an open-source project! If you are interested to see more on how the generation works you can do so at https://github.com/CodeBoarding/CodeBoarding |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have generated high-level diagrams for the gflownet project. The idea is to help people get up-to-speed with the codebase you can see how it renders here:
https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/gflownet/on_boarding.md
I have generated a diagram first documentation for gflownet. As a lot of scientists interact with this codebase, I am sure that they are rather interested in the main flow and method then reading the source code in details. That is the main idea of the diagrams they show the main components and how they interact with each other. Then one can dive deeper by clicking on a component of interest. This allow scientists to quickly modify and extend the project as they can focus only on the component of interest with the full codebase context.
Any feedback is more than welcome! We also just released a free GitHub Action that can automatically update the diagrams so they are always up-to-date.
If this sounds interesting I'd love to connect and chat if such thing can have more impact and how can we help the dev process for scientists. We already became part of the recursionpharma/EFAAR_benchmarking#104.
Full disclosure: we're trying to turn this into a startup, but we're still in a very early stage and figuring out what will actually be useful for people.