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

DM-15599: Stop using boost persistence in afw #98

Merged
merged 2 commits into from Sep 11, 2018
Merged

Conversation

r-owen
Copy link
Contributor

@r-owen r-owen commented Aug 30, 2018

No description provided.

@r-owen r-owen changed the title Stop using boost persistence in afw except for PropertyList DM-15599: Stop using boost persistence in afw except for PropertyList Aug 30, 2018
@r-owen r-owen changed the title DM-15599: Stop using boost persistence in afw except for PropertyList DM-15599: Stop using boost persistence in afw Sep 7, 2018
@r-owen r-owen force-pushed the tickets/DM-15599 branch 2 times, most recently from 33ebe81 to 803378f Compare September 8, 2018 18:25
Simplify FITS I/O for "FitsStorage" by calling new methods
readFitsWithOptions or writeFitsWithOptions on those objects.
instead of using boost persistence.


def boostReadFitsStorage(butlerLocation):
"""Read a FITS image from a butlerLocation using boost peristence
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like we should remove this function and check that we don't actually use it anywhere anymore.

I also don't think it actually makes sense - we've never used Boost to read FITS code. At most this could be using Boost to read daf::base::Persistable, but that has nothing to do with FITS.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds great! I will try that and see what Jenkins thinks.

Copy link
Contributor Author

@r-owen r-owen Sep 11, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You were right. After removing this Jenkins still ran, including ci_hsc! Please have another look. I plan to leave removal of the "BoostStorage" entry in the posix registry as a second commit because feels like an separate step from changing how the "FitsStorage" entry works.

@r-owen r-owen merged commit 10498df into master Sep 11, 2018
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 this pull request may close these issues.

None yet

2 participants