You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This comes from this very strict comparison on multivariate coordinates mvcrds:
ifmvcrdsand (
notall(mvcrds[0].equals(mv) formvinmvcrds[1:])
orlen(mvcrds) !=len(inputs)
):
coords= {mv.nameformvinmvcrds}
raiseValueError(
f"Inputs have different multivariate coordinates: {', '.join(coords)}."
)
Additional context
I guess we want to be very strict with a multivariate coordinate because it's a weird object? period is a special type of coordinate where we accept in the context of bias adjustment, it can differ on various datasets
I could skip_input_checks or drop the period coordinate, it's just a bit impractical
Contribution
I would be willing/able to open a Pull Request to address this bug.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Setup Information
Description
I think I should be able to use stacked periods & variables together:
Steps To Reproduce
This comes from this very strict comparison on multivariate coordinates
mvcrds
:Additional context
I guess we want to be very strict with a multivariate coordinate because it's a weird object?
period
is a special type of coordinate where we accept in the context of bias adjustment, it can differ on various datasetsI could skip_input_checks or drop the
period
coordinate, it's just a bit impracticalContribution
Code of Conduct
The text was updated successfully, but these errors were encountered: