Matthew
Matthew
Thanks for the pointers @keewis ! @dcherian > I would search for _binary_op and specify compat in align There is actually no `compat` argument to `align`, in fact `align` doesn't...
OK, yeah that's fair enough, I guess I wasn't quite clear on the intention behind align.
OK so I got an `arithmetic_compat` working in the above PR. One issue with moving away from `arithmetic_compat='minimal'` (the setting which silently drops clashing coordinates) is that it's quite common...
> For now, I would just add the new configuration option. OK I've updated #10943 to just do this. Any thoughts on whether we should let materialization errors like TracerBoolConversionError...
I think something along these lines wouldn't be the end of the world: ```python SYMBOLIC_COMPARISON_ERRORS = () try: import jax SYMBOLIC_COMPARISON_ERRORS += (jax.errors.ConcretizationTypeError,) except ImportError: pass ... try: ... except...
At any rate maybe we could start with the `arithmetic_compat` thing for now -- if anyone's able to take a look at the PR (#10943) that'd be brilliant :)
Thanks, have now added a DataTree test too.