-
Notifications
You must be signed in to change notification settings - Fork 29
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
[Feature Request]: Rename BF10 when comparing to best model? #129
Comments
@EJWagenmakers, any thoughts? |
In that case we could replace the "0" by a "b" in the subscripts. However this may create confusion as well. What do you think, @JohnnyDoorn @vandenman |
This is indeed a confusing thing!
and if comparing to null model
@vandenman do you agree? Then I can update the code (also for Bayesian regression?). |
I agree with the change, and in fact wanted to implement this sometime in the past. It's a bit more difficult to implement than you'd think though. The main issue is that we use Unicode for subscript 0 and 1 but unfortunately the subscript b does not exist in Unicode... (see https://en.wikipedia.org/wiki/Unicode_subscripts_and_superscripts#Latin,_Greek_and_Cyrillic_tables). Instead you have to somehow use html tags but those are (intentionally) removed in jaspTables so this will require some more work. @JorisGoosen do you remember what needs to be done to allow for HTML tags in jaspTables? |
We could simply add a workaround for the HTML removal part to not remove those subscripts? |
Only thing necessary is changing
|
Another alternative would be to implement LaTeX expressions in our output. That would be nice and enable much more cool functionality, but since my light testing of KaTeX (https://github.com/jasp-stats/INTERNAL-jasp/issues/395) I did not have any time to push this forward. |
That would be much more complicated, although it would allow for some nicer output. I think for the short-term we could create a function like tb <- createJaspTable()
tb$addColumnInfo(name = "data", title = asHTML("BF<sub><B1/sub>"))
tb[["data"]] = asHTML(paste0("data<sub>", letters, "</sub>")) which would then show up like so
alternatively, we could add two arguments to @Kucharssim any preferences for either approach? perhaps adding two more arguments to |
Well it doesn't have to be that difficult, see jasp-stats/jasp-desktop#5073. Considering @shun2wang picked this up and it looks like we could potentially have LaTeX support already for the next release, I would prefer to handle it that way than adding short-term solutions, otherwise we'll end up having to support both approaches. But I don't mind too much if we go this way - it obviously depends on how pressing this issue is. |
Well, I'm not sure if that will go into 0.17.2, some testing is needed there. if we want to have a short-term solution that would probably be a low risky and it's easy to clean it up after 0.17.2 be released? I don't have any particular preference for this Katex.js but it's an adjunct for me to import formula for JASP note, in fact it's easy to use with jaspHtml too😀 you can comment on this PR jasp-stats/jasp-desktop#5073 and I will have a look if something need to be done. |
definitely not in 0.17.2, I meant the one after that |
The fix I mention in #129 (comment) should be real easy, low errorchance and should allow for I can do this in like 5 minutes right now for 0.17.2. And I can also add |
In katex I seted only render a formula with |
The Im just assuming if subscript is wanted superscript is too? Not related to katex |
Ill just make a branch of this |
Also show richtext in column names and data-items
It should also work in everything else btw |
Also show richtext in column names and data-items
* dont replace `<sub>`, `</sub>`, `<sup>` and `</sup>` in escapeHtmlStuff * keep <sub> et al intact for jasp-stats/jasp-issues#129
@Kucharssim @JohnnyDoorn But the tables in ANOVA and Regression still need to be updated to use that code and show BFRB. |
still valid with flatpak 0.19.2 beta (december 2.), see BF10 instead of BF_{R, B} in table header, see: |
Personally, I find it a bit confusing that when the option "Compare to best model" is selected, the output table says "BF10" which is in fact not the Bayes factor against the null model but against the best model. Maybe we could change this in the tables/interface to something more informative?
The text was updated successfully, but these errors were encountered: