jamovi

is your compilerMode set to 'tame'?

https://dev.jamovi.org/ui-basic-design.html

jonathon

hi,

what if we invite you to our slack group? send us an email to contact <at> jamovi.org, and i'll send you an invite. easier to help with such an issue over that medium.

jonathon

hey, as you've probably inferred, you don't need to worry about that warning ...

jonathon

> Documentations is about jamovi 2.5 that depends on R 4.3 but available jamovi release is 2.6 that depends on R 4.4 we mentioned the release of the 2.5 in the news, but the documentation is no less relevant for subsequent versions. > Also, node requirements are not mentioned in the manual i'm not a...

yeah, we're working on this sort of re-ordering functionality at the moment ... and having adopted such a document model, a ToC would be the logical next step.

jonathon

i think node 1.1 is outdated rather than the documentation.

update your node to 1.2 (R package), and come back to us if you're still having trouble.

jonathon

hi,

it sounds like the issue is that node was missing. i would try the command again:

install.packages('jmvtools', repos='https://repo.jamovi.org')

if node was missing, i could imagine nothing working.

jonathon

hi oliveros,

there are maybe one or two (fairly inconsequential) things that need a little update in the developer docs, but i think you'll find that it is mostly still correct.

could you provide the output from `jmvtools::install()`?

cheers

jonathon

yeah, i'd suggest it's not a straight-forward area ... you might be comfortable with a 5% error rate for each hypothesis you're testing.

... and if you are wanting to correct, it's unlikely that the number of tests you're performing are neatly contained within a single t-test analysis.

jonathon

i think this will be fixed in the 2.7, in the mean time you can read about the issue and how you can work around it here:

https://github.com/jamovi/jamovi/issues ... 2724888022

jonathon