You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed that the function ancestral.pars produces significantly different outputs when comparing the stable version (v2.11.1) to the developmental version (v3.0.0). I am currently preparing a package submission to CRAN and am working under a tight deadline. This discrepancy is causing issues with my package's functionality and validation (specifically with passing WinBuilder's devel check).
I will attach an example script with inputs and the different outputs from both versions for you. I would greatly appreciate any insight into why these differences are occurring and how they might be resolved.
Hello,
I have noticed that the function
ancestral.pars
produces significantly different outputs when comparing the stable version (v2.11.1) to the developmental version (v3.0.0). I am currently preparing a package submission to CRAN and am working under a tight deadline. This discrepancy is causing issues with my package's functionality and validation (specifically with passing WinBuilder's devel check).I will attach an example script with inputs and the different outputs from both versions for you. I would greatly appreciate any insight into why these differences are occurring and how they might be resolved.
Thank you so much for your help.
Best regards,
Cole
ancestral_pars.zip
The text was updated successfully, but these errors were encountered: