We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This was needed to ensure the metadata was set correctly. It may not need it anymore (but probably still is). I need to check.
The text was updated successfully, but these errors were encountered:
So, as of circa CIAO 4.6 reproject_events sets the TLMIN/MAX fields for the SKY column, so update_column_range should no-longer be needed.
Sorry, something went wrong.
Although I also use it in a dmmerge call - does dmmerge handle the TLMIN/MAX column ranges?
It does. Good.
Successfully merging a pull request may close this issue.
This was needed to ensure the metadata was set correctly. It may not need it anymore (but probably still is). I need to check.
The text was updated successfully, but these errors were encountered: