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

Noorain drift detection #5

Open
wants to merge 13 commits into
base: main
Choose a base branch
from
Open

Noorain drift detection #5

wants to merge 13 commits into from

Conversation

noorains
Copy link
Collaborator

drift detection for mean ensemble and step_6

@Polichinel Polichinel self-assigned this Feb 29, 2024
Copy link
Collaborator

@Polichinel Polichinel left a comment

Choose a reason for hiding this comment

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

I'm holding off on reviewing this PR since it builds upon the baseline and ensemble branches, which need to be finalized first. It's apparent that this PR is dependent on prior work, but differentiating it from the existing baseline and ensemble PRs would require a significant investment of time—likely an hour or more. Considering there are already identified issues within those foundational PRs, diving into this new PR would not be the most efficient use of our time at the moment.

To streamline our review process and ensure we're working as effectively as possible, I recommend the following steps:

  1. Resolve Existing Issues: Please prioritize addressing and resolving any outstanding issues in the baseline and ensemble branches. This will provide a clear and stable foundation for any additional work.

  2. Separate Branches for Separate Features: Moving forward, ensure that new features or projects are developed on new branches created from the main branch. This will help in keeping our codebase organized and making the review process more manageable.

  3. Update on Resolution: Once the issues in the baseline and ensemble PRs have been addressed, let me know. We can then revisit this PR with a clearer understanding of its unique contributions and changes.

By focusing on these steps, we'll maintain a clean and efficient workflow, ensuring that each part of the project is reviewed thoroughly and integrated seamlessly.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Not gonna comment on the PR as it builds on your baseline and ensemble branches. These need to be in order first. I recognize that this PR is inherently one that builds on your branch, but it would take me an hour or so at least to figure out the difference between this and the two other PR - and since there are a number of this that needs to be fixed in those, it would not be a prudent use of time right now

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