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

can we dump update_column_range #415

Open
DougBurke opened this issue Nov 4, 2020 · 3 comments · May be fixed by #417
Open

can we dump update_column_range #415

DougBurke opened this issue Nov 4, 2020 · 3 comments · May be fixed by #417

Comments

@DougBurke
Copy link
Member

This was needed to ensure the metadata was set correctly. It may not need it anymore (but probably still is). I need to check.

@DougBurke
Copy link
Member Author

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.

@DougBurke
Copy link
Member Author

Although I also use it in a dmmerge call - does dmmerge handle the TLMIN/MAX column ranges?

@DougBurke
Copy link
Member Author

It does. Good.

@DougBurke DougBurke linked a pull request Nov 4, 2020 that will close this issue
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