Skip to content

Conversation

JonathanShor
Copy link
Contributor

Ensure nan positions in each input RDM match.

Addresses #452

Ensure nan positions in each input RDM match.
@JasperVanDenBosch
Copy link
Contributor

Good catch @JonathanShor !

I'd like us to have a unit test to make sure this won't be re-introduced in the future. If you have a chance to add this, great, otherwise I'll aim to add one later this week.

PS please ignore the style and typing checks, these are not working rn.

@JonathanShor
Copy link
Contributor Author

Sure, I could add something like my example in #452. Are there docs on how your testing is setup? Or point me to an example test and a location I can add the new one, that would be great.

Identify positions in any component RDM that are NaN, and propagates them across.
Only raises an error if rdm1 and rdm2 disagree on NaN placement after internal propagation.

Renamed nan_idx to nan_mask since the True values are not for the NaNs.
@JonathanShor
Copy link
Contributor Author

Corrected for the case that rdm1 and rdm2 have different n_rdm. Had NaNs propagate across RDMs within rdm1 or rdm2, and it only raises an error if the positions disagree after this propagation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants