@anguta @jsdillon Having pulled down new versions of hera_cal on lustre for the first time in a few months I am discovering new changes that were made to vis_clean in May that I don't think I was consulted on, specifically a "vis_clean revamp" API change that is now breaking my code (#597). I see that I was asked for a review but didn't get to it and the PR was merged anyways. In the future, let's try to be a little more careful about API changes and getting all invested parties signed off on a PR before it is merged (vis_clean is kind of a standout b/c I wrote it entirely and was probably its only user up until now).
I'll see if I can edit my analysis code to fit the new API. If I can I'll close the issue, otherwise we need to open a new PR to make vis_clean backwards compatible with the stuff that was in there.
@anguta @jsdillon Having pulled down new versions of hera_cal on lustre for the first time in a few months I am discovering new changes that were made to
vis_clean
in May that I don't think I was consulted on, specifically a "vis_clean revamp" API change that is now breaking my code (#597). I see that I was asked for a review but didn't get to it and the PR was merged anyways. In the future, let's try to be a little more careful about API changes and getting all invested parties signed off on a PR before it is merged (vis_clean is kind of a standout b/c I wrote it entirely and was probably its only user up until now).I'll see if I can edit my analysis code to fit the new API. If I can I'll close the issue, otherwise we need to open a new PR to make vis_clean backwards compatible with the stuff that was in there.