Skip to content
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

Consider supporting backwards compatiblity between ophys and pophys #62

Open
bruno-f-cruz opened this issue Aug 20, 2024 · 0 comments · May be fixed by #61
Open

Consider supporting backwards compatiblity between ophys and pophys #62

bruno-f-cruz opened this issue Aug 20, 2024 · 0 comments · May be fixed by #61

Comments

@bruno-f-cruz
Copy link

A recent change made the previous tag ophys incompatible with the new pophys modality. In order to support previously serialized schemas, it would be nice to have some custom logic to coerce the previous definition to the current one.

This coercion mechanism should ideally make things compatible at the level of the python API (e.g. calling Modality.OPHYS) and at the level of deserialization. In both cases, the output should coerce to the new Modality.POPHYS object.

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 a pull request may close this issue.

1 participant