Dimensions node undesirable behaviors
Open
- Dominant language
- Python
- Stars
- 14
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
The dimensions node has numerous bugs and undesirable behavior.
The only repeatable issue I have is with the split functionality - given a new input, split will revert to N and 1. I think this has to do with how the validate function runs and adjusts the values to fit with the input data, but it is problematic when saving networks with Dimensions nodes, or when loading new data from a file in the same network.
(porting from @nckz on GitLab a while back)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.