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

BICtab #35

Open
davidatkaritane opened this issue Apr 21, 2023 · 0 comments
Open

BICtab #35

davidatkaritane opened this issue Apr 21, 2023 · 0 comments

Comments

@davidatkaritane
Copy link

For binomial data, the sample size to use in the calculation of BIC should be the total number of trials, not the number of binomial observations: see p779 of Kass and Raftery (1995), which I have attached below.

Currently, BICtab (and BIC in base R) use the number of binomial observations, unless, of course, the data are entered in binary format.

In order to avoid having to put the data in binary format, it would be helpful to be able to change the value of k in BICtab so that it uses the correct definition of sample size.

Is it possible to allow for this?

As Kass and Raftery point out, when analysing a contingency table, the sample size used in BIC should be the sum of the frequencies, not the number of cells in the table (so again BICtab and BIC in base R will be wrong if the data are in contingency-table format).

In these two settings (binomial data and contingency tables) the problem arises because we are analysing a summary of the data, rather than the original data collected at the "sampling unit" level.

It is possible that the definition of sample size in AICc needs to be thought about carefully in these settings as well, but I haven't seen any theoretical work on this. I seem to recall that there has been some discussion in the mark-recapture world about what we mean by "sample size" when calculating AICc (after fitting a Cormack-Jolly-Seber multinomial model, for example).

Kass 1995.pdf

@davidatkaritane davidatkaritane changed the title B BICtab May 23, 2023
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

No branches or pull requests

1 participant