Closed apbonilauri closed 12 years ago
I added the explanation for Bhapkar http://goo.gl/jKPjy -- please check this out and then let me know if this format is OK. what i mean is: if we were to have this format for all tests, would you feel comfortable both using and interpreting them?
In practice, I think that we will have a number of incomplete input and output documentation, which we can augment over time, as needed. More than having a complete document for every test, i'd rather have something that will solve the immediate problem and then improve it over time
On Sat, Jul 7, 2012 at 11:44 AM, apbonilauri < reply@reply.github.com
wrote:
Ricardo, I don't know how to interpretate the output, like, bhapkar, finn.
building documentation for the input-output components of each common stats test. this will help them with interpretation. we will likely write these input-output pages with knitr since it will allow us to embed tables, graphics, and have the basic formatting tools (headings, bullets, etc), and then export it to html (stored within the github project) so that clinical researchers can just click there and get the latest information. we will obviously have to test and see how that works
input - add template for methods section output -- add annotated bibliography + standard section to go into the results section
Reply to this email directly or view it on GitHub: https://github.com/rpietro/OlecranonFracture/issues/16
Yes, it was easy to understand.
Just one question, we ran some tests, like agreement, finn, bhapkar, icc and kappam, right? Will we use all of them in the results section of the manuscript?
i would use all of them since it will add validity. could you please send me the full list of functions you would like to have a toolbox for?
On Tue, Jul 10, 2012 at 6:58 PM, apbonilauri < reply@reply.github.com
wrote:
Yes, it was easy to understand.
Just one question, we ran some tests, like agreement, finn, bhapkar, icc and kappam, right? Will we use all of them in the results section of the manuscript?
Reply to this email directly or view it on GitHub: https://github.com/rpietro/OlecranonFracture/issues/16#issuecomment-6892739
agree(olecranon_spday1vsspday30, tolerance=0) finn(olecranon_spday1vsspday30, 6, model="twoway") icc(olecranon_spday1vsspday30, model="twoway", type="agreement") kappam.fleiss(olecranon_spday1vsspday30)
just to make sure, are these the ones where you need help with interpretation?
On Wed, Jul 11, 2012 at 5:40 PM, apbonilauri < reply@reply.github.com
wrote:
agree(olecranon_spday1vsspday30, tolerance=0) finn(olecranon_spday1vsspday30, 6, model="twoway") icc(olecranon_spday1vsspday30, model="twoway", type="agreement") kappam.fleiss(olecranon_spday1vsspday30)
Reply to this email directly or view it on GitHub: https://github.com/rpietro/OlecranonFracture/issues/16#issuecomment-6920630
Sorry.
finn(olecranon_spday1vsspday30, 6, model="twoway") icc(olecranon_spday1vsspday30, model="twoway", type="agreement")
Ricardo, did you have a chance to work on this? Thanks.
I will work on this, but i would proceed with the whole paper, this thing is just a final detail
On Wed, Jul 11, 2012 at 5:49 PM, apbonilauri < reply@reply.github.com
wrote:
Sorry.
finn(olecranon_spday1vsspday30, 6, model="twoway") icc(olecranon_spday1vsspday30, model="twoway", type="agreement")
Reply to this email directly or view it on GitHub: https://github.com/rpietro/OlecranonFracture/issues/16#issuecomment-6920881
Ricardo, are there referencial values for Bhapkar Coefficient? I could not find them in the toolbox http://goo.gl/jKPjy So, I don't know how to interpretate the results values.
please check the document i sent, there is a p value there
On Mon, Aug 6, 2012 at 2:22 PM, apbonilauri < reply@reply.github.com
wrote:
Ricardo, are there referencial values for Bhapkar Coefficient? I could not find them in the toolbox http://goo.gl/jKPjy So, I don't know how to interpretate the results values.
Reply to this email directly or view it on GitHub: https://github.com/rpietro/OlecranonFracture/issues/16#issuecomment-7531189
Oh, ok, really sorry.
Ricardo, I don't know how to interpretate the output, like, bhapkar, finn.
building documentation for the input-output components of each common stats test. this will help them with interpretation. we will likely write these input-output pages with knitr since it will allow us to embed tables, graphics, and have the basic formatting tools (headings, bullets, etc), and then export it to html (stored within the github project) so that clinical researchers can just click there and get the latest information. we will obviously have to test and see how that works
input - add template for methods section output -- add annotated bibliography + standard section to go into the results section