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-33453: Update pipeline subdirectories in response to RFC-775. #150
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think something's gone wrong with the move, because there are now both old-style and new-style directories: https://github.com/lsst/ap_pipe/tree/ad29150c5e43bd8d75438a7a013dac95e3120851/pipelines.
Please update pipelines/README.md
; its example uses the old-style directory name. (I've checked with GitHub search that this seems to be the only dangling reference, but GH doesn't let you search branches so you might want to double-check.)
I'm also a bit concerned about the wording of the commit message -- it sounds as if we were arbitrarily following the DRP group's lead, rather than implementing something we all agreed to (RFC-775). Maybe nobody will ever read it, but it still feels like a misrepresentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what the ../DECam/ApPipe.yaml
line is supposed to be?
(Also, GitHub seems to be doing something weird with this file. I tried to add a comment to the added line and it said "Line must be part of the diff and Diff hunk can't be blank".)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They're supposed to be symbolic links for backwards compatibility. I discussed it a bit with Ian and Eric, though there was no end date for when we'll get rid of the sym links.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, that makes sense. However, it's a bit problematic since we do need to get rid of those directories (that was the whole point!), and we don't have a way to add a deprecation warning to symlinks.
I think a hard break is the lesser evil in this case, but if not, please at least file a removal ticket and have one of the upcoming releases block on it as if we were following the deprecation policy.
EDIT: accidentally said the exact opposite of what would ensure this gets cleaned up eventually...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, one other request: could the symlinks be split off into their own commit? I think it might help git/GitHub be less confused about the net diff, as well as providing a natural division of the changes (essential vs. non-essential).
76c6a13
to
c6b8e04
Compare
@@ -10,6 +10,6 @@ For example, to visualize the `apPipe` subset from the [LSSTCam-imSim ApPipe pip | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, found a problem -- the link on line 9 needs to be updated as well.
c6b8e04
to
146d1b8
Compare
Changed
HyperSuprimeCam
toHSC
,DarkEnergyCamera
toDECam
, andLSSTCamImSim
toLSSTCam-imSim
in response to RFC-775.