Summary: | NEEDINFO: Rkward crashes when calculating NMDS | ||
---|---|---|---|
Product: | [Applications] rkward | Reporter: | RKWard Team <rkward-devel> |
Component: | general | Assignee: | RKWard Team <rkward-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | All | ||
Latest Commit: | Version Fixed In: |
Description
RKWard Team
2015-05-19 13:43:29 UTC
- **summary**: Rkward crashes when calculating NMDS --> NEEDINFO: Rkward crashes when calculating NMDS Hi! Thanks for reporting (and sorry about the long silence). > If applicable: When doing the same thing in an R session outside of RKWard, do you see the same problem? > RStudio and R console do not produce any output, they just hang. This does look like an issue in R or package "vegan", then. You may want to report it to the vegan mainainters. Bug tracker appears to be at https://github.com/vegandevs/vegan/issues . While the symptoms are a bit different in RKWard vs. R console (crash vs. hang), this does not indicate a problem in RKWard to me. If I got you wrong on this, or you have any other particular reason to believe that this should be addressed in RKWard, rather than the package, please just reply. Otherwise, I'll close this report in a few weeks. Regards Thomas -- Originally posted by (AT sourceforge.net): vjtz -- It can be problem with vegan, but I wonder why it should crash Rkward... I reported the problem to vegan's developers, I'll see what they think about it. -- Originally posted by (AT sourceforge.net): vjtz -- OK, it was confirmed as vegan bug https://github.com/vegandevs/vegan/issues/152 but still it shouldn't crash whole Rkward, I think... > but still it shouldn't crash whole Rkward, I think... True. But as far as I understood your report, so far, you are not _technically_ seeing a crash, but rather "only" the message that the R backend has become unavailable. We can't really do anything about the latter: If package code crashes in the R backend, that means the backend is crahed. (This is more than just a regular error, it's an undefined execution state). What we _could_ do better, is to allow the R backend to be restarted, without having to close the entire session. That's on our TODO list, but it's not something entirely trivial to implement. Please let me know, if you are actually seeing a crash of the RKWard frontend. -- Originally posted by (AT sourceforge.net): vjtz -- Technically You are right, "just" backend crashes, but practically, You loose Your session and have to restore from backup. So that I vote for that restart feature and I hope to see it soon. - **status**: open --> closed Ok, thanks for the clarification. I'm closing this (specific) issue ticket, then. Thanks for reporting! |