-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
should all nodes be in edges (if edges exist)? #66
Comments
Definitely seems warn-worthy. |
should I just add a validator in the BIDSStatsModel class ? |
I guess those could warn instead of raising exceptions, but if they aren't easy to skip, it will make it annoying to program with this class, as every copy will emit a new warning. |
ah true! so maybe something like validate method on the Edge class? |
No, I think it still needs to operate on the whole model, as it needs to know about both nodes and edges. I can see a couple approaches.
|
All nodes mentioned in edges should refer to an existing node, but I am not sure about the other way around: have some nodes that exist but not mentioned in edges and that would thus be ignore when running the model.
Sounds practical from a user perspective to be able to develop some models where not all nodes are used while tweaking things around.
But validation could possibly throw a warning.
The text was updated successfully, but these errors were encountered: