Re: [rkward-devel] power analysis plugin
Hi, On Tue, 14 Oct 2014 12:44:09 +0200 meik michalke meik.micha...@uni-duesseldorf.de wrote: Am Montag, 6. Oktober 2014, 20:28:45 schrieb Thomas Friedrichsmeier: - Providing better control over which plugins are active. I'm still not convinced, the level of individual plugins is (typically) the right granularity of control, but in fact, control should be more fine-grained than the current official pluginmaps, and esp. more fine-grained than simply using all.pluginmap, by default. are there R functions yet to enable/disable plugins? you know, if there were, in combination with rk.list.plugins() i could simply write my own plugin for that control. here you go, finally: rk.set.plugin.status(). So far, the only thing that can be controlled is visibility. More could be added to that interface, if there is a real need for that, but initially, this should cover the most important bit. So: Your turn, now ;-) a function which lists all meta (like about, dependencies and info on the menu structure) information on plugins would also be great, because the name alone doesn't explain so much. rk.list.plugins() now lists a lot more information. Dependencies, and most of about is not yet included, and I guess it does not make too much sense to include all of this? (In fact, plugins with unmet dependencies will not even be visible in rk.list.plugins(); users do get a warning when loading a pluginmap with a plugin with unmet dependencies, though). Let me know about the bits you'd like to use in your meta-plugin. Most should be easy enough to add. Regards Thomas signature.asc Description: PGP signature -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
Hi, On Saturday 11 October 2014 21:35:54 meik michalke wrote: that exactly is the plan. for re-use of the ID later on (e.g., in the logic section), you should also store it in an object: list ( First option=c (val=1), Second option=c (val=2, chk=TRUE), option3 - rk.XML.option (Optional option, val=3, id.name=three) ) just in case you have missed it: I have modified the rk.power plugin, using this (only in the script, so far). Please take a look. Dynamically disabling the radio option works fine with this. I'm also finally done with the documentation. So the only missing bit would be automated tests. Regards Thomas signature.asc Description: This is a digitally signed message part. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
hi, Am Montag, 6. Oktober 2014, 20:28:45 schrieb Thomas Friedrichsmeier: - Providing better control over which plugins are active. I'm still not convinced, the level of individual plugins is (typically) the right granularity of control, but in fact, control should be more fine-grained than the current official pluginmaps, and esp. more fine-grained than simply using all.pluginmap, by default. are there R functions yet to enable/disable plugins? you know, if there were, in combination with rk.list.plugins() i could simply write my own plugin for that control. a function which lists all meta (like about, dependencies and info on the menu structure) information on plugins would also be great, because the name alone doesn't explain so much. viele grüße :: m.eik -- dipl. psych. meik michalke institut fur experimentelle psychologie abt. fur diagnostik und differentielle psychologie heinrich-heine-universitat d-40204 dusseldorf signature.asc Description: This is a digitally signed message part. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
Hi, On Tuesday 14 October 2014 12:44:09 meik michalke wrote: Am Montag, 6. Oktober 2014, 20:28:45 schrieb Thomas Friedrichsmeier: - Providing better control over which plugins are active. I'm still not convinced, the level of individual plugins is (typically) the right granularity of control, but in fact, control should be more fine-grained than the current official pluginmaps, and esp. more fine-grained than simply using all.pluginmap, by default. are there R functions yet to enable/disable plugins? you know, if there were, in combination with rk.list.plugins() i could simply write my own plugin for that control. a function which lists all meta (like about, dependencies and info on the menu structure) information on plugins would also be great, because the name alone doesn't explain so much. interesting idea. But no, rk.list.plugins() is the only piece of that picture, that exists, so far. Let's keep it in mind for 0.6.3. (Although I'll start by working on plugin i18n; that's long overdue at any rate). And when I say let's keep it in mind, I mean: Do remind me! BTW, including (incubating ;-)) rk.power (and other) external plugins will have to wait for 0.6.3, too. As you can see, I did not make any further progress, yet, and we're just too close to release time, by now. Further BTW, the code that's going to become 0.6.2 is in a separate branch, now. SVN trunk is open to riskier commits, again. Regards Thomas signature.asc Description: This is a digitally signed message part. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
Hi Meik, On Wednesday 08 October 2014 11:49:56 meik michalke wrote: Am Dienstag, 7. Oktober 2014, 13:43:33 schrieb Thomas Friedrichsmeier: - For the two sample tests, when estimating the size of one of the samples, why not always make it the second sample (i.e. first sample size provided)? fixed (in the script). hm, what I meant was: Why not get rid of that radio control, completely, not just changing the default. I can see that for the R function signature, it would have been more cumbersome to explain Exactly one of the parameters needs to be NULL, except it can't be n1. But for the GUI, I don't see the point of showing an additional control Now select, whether you want to estimate n1 given n2 or n2 given n1, when it really doesn't make any difference (but adds complexity both to the UI, and to the logic behind it). Then, after that, I had the idea to get rid of the other hidden radio (controlling which df to estimate for GLM), too. My plan was: 1. Move test specification to the left, making it the first step, logically 2. In the target measure radio, add a fifth option numerator df, which would be enabled for GLM, only. The main reason is that - logically - it makes little sense to read numerator df as a sub-item of sample size, and I had difficulty thinking up an appropriate help snippet due to this. Well, when I wanted to make that experiment, I found that rkwarddev does not yet handle ids on radio-options. And then I found out, that the fact that radio-options can be disabled, dynamically, was not really documented, so far. (See Import Text / CSV Data-Plugin for an example usage). I have fixed the documentation. Could you add this to rk.XML.option()? Regards Thomas signature.asc Description: This is a digitally signed message part. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
hi, Am Samstag, 11. Oktober 2014, 14:46:39 schrieb Thomas Friedrichsmeier: Well, when I wanted to make that experiment, I found that rkwarddev does not yet handle ids on radio-options. And then I found out, that the fact that radio-options can be disabled, dynamically, was not really documented, so far. (See Import Text / CSV Data-Plugin for an example usage). I have fixed the documentation. Could you add this to rk.XML.option()? well, in fact there is no rk.XML.option() yet ;-) all options are directly defined by rk.XML.radio() as a list. but if one needs the possibility of getting an ID from an option, adding rk.XML.option() seems to be inevitable. i don't se another way to clearly specify which option you mean, except directly naming the ID yourself. viele grüße :: m.eik -- dipl. psych. meik michalke institut fur experimentelle psychologie abt. fur diagnostik und differentielle psychologie heinrich-heine-universitat d-40204 dusseldorf signature.asc Description: This is a digitally signed message part. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
On Saturday 11 October 2014 16:56:39 meik michalke wrote: well, in fact there is no rk.XML.option() yet ;-) all options are directly defined by rk.XML.radio() as a list. but if one needs the possibility of getting an ID from an option, adding rk.XML.option() seems to be inevitable. i don't se another way to clearly specify which option you mean, except directly naming the ID yourself. Oh, I wasn't paying attention. Well, I'm not sure about the implications. Few options will ever need an id, and those that don't need one, should not be given one (to avoid name clashes, and for better performance). And inside one radio/dropdown, the number of id'ed options will certainly be limited, anyway. Thus, perhaps, naming an id manually, is the way to go. I.e rk.XML.radio() could accept options like this: list (First option=c (val=1), Second option=c (val=2, chk=TRUE), Optional option=c (val=3, id=three)) Regards Thomas signature.asc Description: This is a digitally signed message part. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
Hi again, On Saturday 11 October 2014 17:44:33 Thomas Friedrichsmeier wrote: Thus, perhaps, naming an id manually, is the way to go. I.e rk.XML.radio() could accept options like this: ok, I was too slow... Well, perhaps if you can make it so that rk.XML.radio() can accept a mixed list like this? list (First option=c (val=1), Second option=c (val=2, chk=TRUE), rk.XML.option (Optional option, val=3, id.name=three)) The point would be to make sure that options that don't need an id don't get one, automatically. Regards Thomas signature.asc Description: This is a digitally signed message part. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
hi there, Am Samstag, 11. Oktober 2014, 17:50:57 schrieb Thomas Friedrichsmeier: On Saturday 11 October 2014 17:44:33 Thomas Friedrichsmeier wrote: Thus, perhaps, naming an id manually, is the way to go. I.e rk.XML.radio() could accept options like this: ok, I was too slow... sorry ;-) in rkwarddev you're used to feeding your XML objects to other functions to get their ID, so you will expect this to be possible here as well. the problem is that using the radio-node that way leaves the problem of identifying one of the options. so i thought the clearest way of doing it would be to make the option an object of its own. Well, perhaps if you can make it so that rk.XML.radio() can accept a mixed list like this? list (First option=c (val=1), Second option=c (val=2, chk=TRUE), rk.XML.option (Optional option, val=3, id.name=three)) that exactly is the plan. for re-use of the ID later on (e.g., in the logic section), you should also store it in an object: list ( First option=c (val=1), Second option=c (val=2, chk=TRUE), option3 - rk.XML.option (Optional option, val=3, id.name=three) ) the last remaining problem here is that you cannot access the node by its ID alone, you still need the radio node ID as well (rID.oID). i'm not sure yet how to solve this elegantly (it's similar to identification in optionsets). [maybe using an environment like for the help text is an idea here... as long as IDs are unique, finding the parent ID of an option ID shouldn't be so hard] i also want to write a check for the chk argument, so only one option can have it set to TRUE. i've also seen that i repeatedly wrote several lines of code to check for the kind of node which is nested in other nodes, that calls for a dedicated function and a central list of valid child nodes as well. The point would be to make sure that options that don't need an id don't get one, automatically. yes, and in contrast to other functions, where the default is id.name=auto, in rk.XML.option() the default is already set to id.name=NULL: even if you want an auto-ID, you have to manually call for it. viele grüße :: m.eik -- dipl. psych. meik michalke institut fur experimentelle psychologie abt. fur diagnostik und differentielle psychologie heinrich-heine-universitat d-40204 dusseldorf signature.asc Description: This is a digitally signed message part. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
hi thomas, Am Dienstag, 7. Oktober 2014, 13:43:33 schrieb Thomas Friedrichsmeier: - For the two sample tests, when estimating the size of one of the samples, why not always make it the second sample (i.e. first sample size provided)? fixed (in the script). - Syntax error for estimating sample size in different sample sizes proportion test. fixed (in the script). not the first time, all those commas are a mess :-D - In some cases, you get the not-so-helpful error message: Error in uniroot(function(n2) eval(p.body) - power, c(2 + 1e-10, 1e+07)) : f() values at end points not of opposite sign fixed (in the script). applied you suggested message, seems to work. - For GLM, would it make sense to allow to specify number of parameters to estimate, and sample size (N), instead of numerator / denominator df? i went for the wording used by ?pwr.f2.test, but i admit it sounds a bit scary ;-) - In the generated printout() code, things might get slightly simpler, if you print the header earlier: ok, partly changed it already in the script. will look at it later. - That said, I wonder, whether the following printout would be good enough (after the rk.header()): rk.print.literal (capture.output (print (x))) (we could add a new function rk.print.simple(x) for this kind of output. It would probably make sense in other places, too). to me it looks a bit more consistent with the RKWard output you're used to now. it partly emulates what print.power.htest() does, but with rk.* functions. for copypaste scenarios, i'd prefer that table. btw, if you have text for the help file, i would like to try to put it in the rkwarddev script, to test a new possibility to generate .rkh files i implemented just yesterday. it stores text for elements by ID in an environement, and when rk.plugin.component() or rk.plugin.skeleton() use the scan option for setting nodes, that text is automatically filled in. to get the text into the environment, you can now provide it with the same functions which generates the XML element, e.g. rk.set.comp(Example component) rk.XML.cbox( label=Cherry, value=cherry, help=Check this to get a cherry on top.) without rk.set.comp() you'd have to 'add component=Example component' to the rk.XML.cbox() call, which is a bit annoying after the third time... to see the stored text, run rk.get.rkh.prompter() viele grüße :: m.eik -- dipl. psych. meik michalke institut fur experimentelle psychologie abt. fur diagnostik und differentielle psychologie heinrich-heine-universitat d-40204 dusseldorf signature.asc Description: This is a digitally signed message part. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
Hi, On Wednesday 08 October 2014 11:49:56 meik michalke wrote: - For GLM, would it make sense to allow to specify number of parameters to estimate, and sample size (N), instead of numerator / denominator df? i went for the wording used by ?pwr.f2.test, but i admit it sounds a bit scary ;-) thinking about it, there is one scenario, where my idea won't work, namely when estimating the number of estimatable parameters (or numerator df). In this case there is no trivial mapping from sample size to denominator df. Well, a small reminder on the relation between parameter count, number of observations, and df, in the help file will come in handy... - That said, I wonder, whether the following printout would be good enough (after the rk.header()): rk.print.literal (capture.output (print (x))) (we could add a new function rk.print.simple(x) for this kind of output. It would probably make sense in other places, too). to me it looks a bit more consistent with the RKWard output you're used to now. it partly emulates what print.power.htest() does, but with rk.* functions. for copypaste scenarios, i'd prefer that table. True, that would be somewhat inconsistent. But actually for some plugins, I'm not entirely satisfied with the output generated by rk.print()/HTML(). Esp. print lm estimation results. So that's where the idea came from. But we'll leave it for now. btw, if you have text for the help file, i would like to try to put it in the rkwarddev script, to test a new possibility to generate .rkh files i implemented just yesterday. Not much. I started, then stumbled across those issues, then got side-tracked. This is all I got so far: ## Documentation pwr.rkh.summary - rk.rkh.summary (Perform power anaylsis for a variety of statistcal methods.) pwr.rkh.usage - rk.rkh.usage (Given three of the parameters 'power of test', 'sample size', 'effect size', and 'significance level', this plugin will estimate the fourth, i.e. for example the test power of a t.test at a given sample size, effect size, and level of significance. On the left hand control, select which of the parameters to estimate. In the middle, specify the statistical method, on the right hand side, enter the values of the given parameters.) pwr.rkh.settings - rk.rkh.settings ( rk.rkh.setting (pwr.parameter.rad, text=Parameter to estimate, given the others.), rk.rkh.setting (pwr.parameter.towsamples.rad, text=Only shown when applicable: For estimating the required sample sizes for a test with two differently sized samples, specify which should be estimated, and which is given.) ) it stores text for elements by ID in an environement, and when rk.plugin.component() or rk.plugin.skeleton() use the scan option for setting nodes, that text is automatically filled in. to get the text into the environment, you can now provide it with the same functions which generates the XML element, e.g. rk.set.comp(Example component) rk.XML.cbox( label=Cherry, value=cherry, help=Check this to get a cherry on top.) without rk.set.comp() you'd have to 'add component=Example component' to the rk.XML.cbox() call, which is a bit annoying after the third time... to see the stored text, run rk.get.rkh.prompter() Not pretending, I understood this, completely, but sounds good. Will try when I have a bit of time (not today). Regards Thomas signature.asc Description: This is a digitally signed message part. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
Hi Meik,
On Sunday 05 October 2014 16:01:27 meik michalke wrote:
sure, why not. would someone jump in to do write the help file? ;-)
trying to write a help file sometimes helps to spot non-intuitive controls, or
ones that could be simplified. Oh, and of course bugs...:
- For the two sample tests, when estimating the size of one of the samples,
why not always make it the second sample (i.e. first sample size provided)?
- Syntax error for estimating sample size in different sample sizes proportion
test.
- In some cases, you get the not-so-helpful error message:
Error in uniroot(function(n2) eval(p.body) - power, c(2 + 1e-10, 1e+07)) :
f() values at end points not of opposite sign
e.g. when no finite n2 sample size is enough to satisfy the given n1 sample
size, effect size, power, significance level. I am not sure, whether this
applies in all cases, but where it does, it would be good to print a more
helpful message. That might mean
pwr.result - try (pwr.whatever(...))
if (class (pwr.result) == try-error) {
rk.print (Power anaylsis not possible at the given specification)
return () # Exits local(), so no need to put the rest inside an else{}.
}
- For GLM, would it make sense to allow to specify number of parameters to
estimate, and sample size (N), instead of numerator / denominator df?
- In the generated printout() code, things might get slightly simpler, if you
print the header earlier:
# Prepare printout
rk.header(pwr.result[[method]], parameters= c (list(Target
measure=Whatever), pwr.result[alternative]))
note - pwr.result[[note]]
pwr.result[c(method, note, alternative)] - NULL
rk.results(as.data.frame (unlist (pwr.result)), titles=c (,
Parameters))
if(!is.null(note)){
rk.print(paste(strongNote:/strong , note))
}
[...]
- That said, I wonder, whether the following printout would be good enough
(after the rk.header()):
rk.print.literal (capture.output (print (x)))
(we could add a new function rk.print.simple(x) for this kind of output. It
would probably make sense in other places, too).
Regards
Thomas
signature.asc
Description: This is a digitally signed message part.
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
RKWard-devel mailing list
RKWard-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
Hi, On Sunday 05 October 2014 16:01:27 meik michalke wrote: That might even help work around the squeezing you get when switching from single sample to two samples (depending on dialog height). that's still an annoying bug, isn't it? by the way, while working on this i came to notice that the squeezing only happens on my laptop, not on my desktop machine -- both run the same distro, KDE and Qt versions and, from what i can see, use the same desktop theme, window layout stlye etc. on my desktop, the window is always resized accordingly (it only never shrinks after it had grown due to new elements appearing). Well, no idea why it works in some cases but not in others. Not much point in debugging such details before porting to KF5/Qt5, though. One thing that has always been slightly buggy regarding Qt layout is when text is word-wrapped. Any chance this could be the difference (i.e. note is word- wrapped on your laptop, but not on your desktop)? Another thing is: Considering this looks fairly finished (apart from documentation), and useful to a wide audience, should we make this part of the 0.6.2 release? sure, why not. would someone jump in to do write the help file? ;-) I'll see what I can do. how would you like to do this? generally, i'd prefer to add it as a kind of bundle, so it remains a plugin on its own, at least so it can be disabled easily in the plugin configuration. this makes it easier to release updates of that part without having to wait for another RKWard release. but that's probably a bit more complex to do right, at least for the debian packaging? On a more general note, which external plugins are ready for inclusion? don't you think the menus might get a bit to crowded if we include it all? Well, yes, the menus are starting to be crowded (although I don't think it's a real problem, yet). But are they crowded with the right things? If / when we make a plan on which plugins should be enabled/disabled by default, power analysis would _not_ be among the first to go, IMO. perhaps we can re-think the plugin installations process instead, to make it more obvious which plugins are available (at least the ones in our own repo). That's true in it's own right. But I think having to install a plugin, in order to be able to use it, is always going to be more cumbersome / less discoverable. And at least from a bandwidth point of view, including plugins has a barely noticable impact on the size of releases. From another point of view, there are two areas that could be improved: - Having an easy way to provide updates for official plugins without a full release. That might be as simple as changing the rule first to be defined wins to latest version wins, when dealing with conflicting plugin declarations. (Well, actually, that's easier said than done, implementation- wise, but conceptually, it's straight-forward...) - Providing better control over which plugins are active. I'm still not convinced, the level of individual plugins is (typically) the right granularity of control, but in fact, control should be more fine-grained than the current official pluginmaps, and esp. more fine-grained than simply using all.pluginmap, by default. Anyway, that's both for another release. Keep nagging me about it. But IMO it should not keep us from including more plugins, that are currently external, ATM. that said, i think the plugins for ANOVA, factor and cluster analysis are quite useable -- except they all lack docs... Ok. More than I can handle for 0.6.2, probably, but should be on the list for 0.6.3, then. (Well, yes, I really should have thought about this, earlier. OTOH, I think there is a point for releasing 0.6.3 rather shortly after 0.6.2 - i.e. before end of this year - anyway. This could include dynamic i18n for plugins, and some other bits that are mostly orthogonal to porting to KF5, technically.) you mean like a restart button for the R backend? :-D Well, I was rather thinking about some other _easy_ bits ;-). Regards Thomas signature.asc Description: This is a digitally signed message part. -- Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
hi, Am Samstag, 4. Oktober 2014, 12:08:49 schrieb meik michalke: Am Samstag, 4. Oktober 2014, 10:34:58 schrieb Thomas Friedrichsmeier: - Don't forget to require(pwr) fixed. I figured out that for less you want to specify a _negative_ effect size (and in fact, you can't enter that in the GUI). good catch. yes, right now effect sizes can't be negative, i'll try to come up with something. effect size range now covers -1 to 1 globally. it's pretty usual for correlations, at least. I suggest, either going with greater, only, or showing a warning, when the specified effect size contradicts the hypothesis. if i take the first road and go astray from the pwr options, i'll probably rename greater to something like one sided test (first is greater). i included a warning instead. it's also shown if you give a negative effect size for the other alternatives, respectively. - I wouldn't write the results to the workspace _by default_. fixed. i also fixed the sample size controls for two sample designs, and added the possibility to provide eta squared instead of cohen's f. to make it easier to test, i've released 0.01-1 last night. viele grüße :: m.eik -- dipl. psych. meik michalke institut fur experimentelle psychologie abt. fur diagnostik und differentielle psychologie heinrich-heine-universitat d-40204 dusseldorf signature.asc Description: This is a digitally signed message part. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
Hi, On Sunday 05 October 2014 12:00:05 meik michalke wrote: i also fixed the sample size controls for two sample designs, and added the possibility to provide eta squared instead of cohen's f. a thought on that: For two samples, you could hide the number of observations _per sample_ note. That might even help work around the squeezing you get when switching from single sample to two samples (depending on dialog height). Another thing is: Considering this looks fairly finished (apart from documentation), and useful to a wide audience, should we make this part of the 0.6.2 release? On a more general note, which external plugins are ready for inclusion? (Well, yes, I really should have thought about this, earlier. OTOH, I think there is a point for releasing 0.6.3 rather shortly after 0.6.2 - i.e. before end of this year - anyway. This could include dynamic i18n for plugins, and some other bits that are mostly orthogonal to porting to KF5, technically.) Regards Thomas signature.asc Description: This is a digitally signed message part. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
hi, Am Sonntag, 5. Oktober 2014, 14:49:40 schrieb Thomas Friedrichsmeier: On Sunday 05 October 2014 12:00:05 meik michalke wrote: i also fixed the sample size controls for two sample designs, and added the possibility to provide eta squared instead of cohen's f. a thought on that: For two samples, you could hide the number of observations _per sample_ note. ok, i'd have to change the spinbox label then, to make it clear that these numbers represent the sample size. but you're right of course, when there's two of them it's obvious it's per sample ;-) i'm amazed that almost half of that plugin code already is logic rules. That might even help work around the squeezing you get when switching from single sample to two samples (depending on dialog height). that's still an annoying bug, isn't it? by the way, while working on this i came to notice that the squeezing only happens on my laptop, not on my desktop machine -- both run the same distro, KDE and Qt versions and, from what i can see, use the same desktop theme, window layout stlye etc. on my desktop, the window is always resized accordingly (it only never shrinks after it had grown due to new elements appearing). Another thing is: Considering this looks fairly finished (apart from documentation), and useful to a wide audience, should we make this part of the 0.6.2 release? sure, why not. would someone jump in to do write the help file? ;-) how would you like to do this? generally, i'd prefer to add it as a kind of bundle, so it remains a plugin on its own, at least so it can be disabled easily in the plugin configuration. this makes it easier to release updates of that part without having to wait for another RKWard release. but that's probably a bit more complex to do right, at least for the debian packaging? On a more general note, which external plugins are ready for inclusion? don't you think the menus might get a bit to crowded if we include it all? perhaps we can re-think the plugin installations process instead, to make it more obvious which plugins are available (at least the ones in our own repo). that said, i think the plugins for ANOVA, factor and cluster analysis are quite useable -- except they all lack docs... (Well, yes, I really should have thought about this, earlier. OTOH, I think there is a point for releasing 0.6.3 rather shortly after 0.6.2 - i.e. before end of this year - anyway. This could include dynamic i18n for plugins, and some other bits that are mostly orthogonal to porting to KF5, technically.) you mean like a restart button for the R backend? :-D viele grüße :: m.eik -- dipl. psych. meik michalke institut fur experimentelle psychologie abt. fur diagnostik und differentielle psychologie heinrich-heine-universitat d-40204 dusseldorf signature.asc Description: This is a digitally signed message part. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
Re: [rkward-devel] power analysis plugin
hi thomas, Am Samstag, 4. Oktober 2014, 10:34:58 schrieb Thomas Friedrichsmeier: looks really nice, already. thanks :-) - Don't forget to require(pwr) ouch... - I was rather confused by the distinction between greater and less alternatives for one-sided tests. erm, yes, me too. only as a first step, i simply implemented all options from the functions and then wanted to check on the details later. btw, i wished the documentation of pwr would be a little more elaborate on stuff like this. This should not really make any difference, or should it? Then I tried, and didn't believe my eyes, until I figured out that for less you want to specify a _negative_ effect size (and in fact, you can't enter that in the GUI). good catch. yes, right now effect sizes can't be negative, i'll try to come up with something. I suggest, either going with greater, only, or showing a warning, when the specified effect size contradicts the hypothesis. if i take the first road and go astray from the pwr options, i'll probably rename greater to something like one sided test (first is greater). would anyone consider it too much a limitation to not being able to use negative effect sizes? - I wouldn't write the results to the workspace _by default_. I guess the more common case is that the printout is all you want. ok. - This is really something where a generalized preview (similar to the plot previews, but showing e.g. a piece of HTML printout) would be nice. But of course, we don't have that, yet... absolutely. these calculations are really quick, and in reality you probably want to see how your target measure behaves if one of the assumed parameters changes, without clicking through a dialog a dozen times. in this particular case, it would be awesome if i could loop parts of the result back to the GUI, right to the control of the target measure, which is now greyed out when selected. maybe with a green border or something, so you understand that you cannot change it directly. viele grüße :: m.eik -- dipl. psych. meik michalke institut fur experimentelle psychologie abt. fur diagnostik und differentielle psychologie heinrich-heine-universitat d-40204 dusseldorf signature.asc Description: This is a digitally signed message part. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
