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.
Problem
Node.js can handle neural network sizes of 100K+ neurons with fairly minimal CPU/memory consumption on most laptops.
Problem is that most browsers can only display around 5-10K using @sdesalas/3d-force-graph via Canvas/WebGL. We need a way to be able to visualize a larger network.
This can be accomplished in one of two ways:
While approach No 1 is definitely worth dedicating some time and energy to. There will always be a limit to the number of neurons that can be displayed simultaneously on a screen via Canvas/WebGL, which will in turn limit the number of neurons that can run on the 'backend' to a smaller number than could otherwise be acomplished.
Approach No 2 ensures that the 'backend' or server-side of the network can be increased to its theoretical limit (probably 100M neurons) while still making the UI 'adaptive' so it can display the whole network and its the neurons firing regardless of how big the underlying network is.