-
Notifications
You must be signed in to change notification settings - Fork 2
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
DeleteVariable should clean up _variableOrderSymbols in neighbor factors #20
Comments
I hope I understand |
at least one major use is that factors are order sensitive to the variables being passed in and this is where that info is stored |
I would say a definite no on this, and close issue? |
Sorry didn't mean to close |
umm i think it’s a definite yes — perhaps we thinking of different things. if you delete a variable, then it cannot possibly exist in a factor lookup? means the factor is incomplete and should fail if evaluated. default should probably be to also delete factors attached to the deleted variable too, no? |
As usual, @Affie convinced me to NOT delete from IF a variable is deleted from DFG object, then default is to delete surrounding factors also. This can be avoided with a keyword argument. If a factor is not deleted and a new variable is introduced, then a new factor must be created by one of the verbs and replace the current factor which has (by this time) a stale but immutable One reason is that deleting and adding variables will not preserve the all important order. Another reason is that deleting both the edges in the graph and variables from this list undermines the test where one compares the two lists against each other -- currently used for orphan test. Third reason is when using the |
Close in favor of #296 |
No description provided.
The text was updated successfully, but these errors were encountered: