-
Notifications
You must be signed in to change notification settings - Fork 6
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
Support per-sample weights #7
Comments
Hi Alex, I forgot why I said it was hard before in the other issue but I think you'd need to add an argument to circacompare for the weights vector and then pass it to the call to I'm busy for the next week or two but may have time to have another look at this after that. I'll keep it open but please give me an update on how you go over the next week or two before I have a go. Thanks, |
Hi Rex, thank you for the response! I think I managed now in https://github.com/ATpoint/circacompare/commit/0ceb788e0338db4dbe75e3cbbc6c22ffcb3db8c8 The tricky part was to realize that the Limitation: I only added this to the Edit: Will make a PR with the points you mention below once I find the time, thanks! |
Thanks Alex, Looks like this is a good fix that I'm sure would be helpful to others too. I'm happy to merge this in and add you as a contributor. Before you do a pull request, could you please add the sample_weights arg and functionality to the other circacompare functions (*_single and the *_mixed variants)? |
All done in #8 :) |
Dear Rex,
I would like to follow up on (#3) towards support of per-sample weights. Did you happen to have any time supporting this for
circacompare()
? I tried naive solutions by providing a numeric vector of weights tonls()
as an argument -- turns out it is more complex than that...Do you currently have the capacity to help out here, or alternatively, can you point me to the sections in the source code that I need to dig myself into to address this?
Thank you very much!
-Alex
The text was updated successfully, but these errors were encountered: