Skip to content
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

[Bug]: This analysis terminated unexpectedly. Error in .extractErrorMessage(e): length(error) = 1 is not TRUE #2704

Closed
3 tasks done
ShunitAm opened this issue May 6, 2024 · 14 comments
Assignees
Labels

Comments

@ShunitAm
Copy link

ShunitAm commented May 6, 2024

JASP Version

0.18.3

Commit ID

No response

JASP Module

Network

What analysis are you seeing the problem on?

classical network analysis

What OS are you seeing the problem on?

Windows 11

Bug Description

Whenever i'm trying the bootstrap options- bootsrap network i get this erorr massage:

This analysis terminated unexpectedly.

Error in .extractErrorMessage(e): length(error) = 1 is not TRUE

Stack trace
.networkAnalysisBootstrap(mainContainer, network, options)

.networkAnalysisComputeBootstrap(bootstrapContainer, network, options)

tryCatch({
jaspBase::.suppressGrDevice({
for (nm in names(allNetworks)) {
bootstrapResult[[nm]] <- bootnet::bootnet(data = allNetworks[[nm]], nBoots = options[['bootstrapSamples']], type = options[['bootstrapType']], nCores = nCores, statistics = c('edge', 'strength', 'closeness', 'betweenness'), labels = options[['variables']])
}
})
}, error = function(e) bootstrapContainer$setError(.extractErrorMessage(e)))

tryCatchList(expr, classes, parentenv, handlers)

tryCatchOne(expr, names, parentenv, handlers[[1]])

value[3]

bootstrapContainer$setError(.extractErrorMessage(e))

private$jaspObject$setError(x)

.extractErrorMessage(e)

stopifnot(length(error) = 1)

To receive assistance with this problem, please report the message above at: https://jasp-stats.org/bug-reports
Screenshot 2024-05-06 114531

Expected Behaviour

It should give me the data

Steps to Reproduce

1.classical network analysis
2.added the variables
3.network plot+clustering plot
4. bootstrap options- bootstrap network- number of bootstrap- i tried 100 and 1000
...

Log (if any)

JASP 2024-05-06 10_51_23 Desktop.log
JASP 2024-05-06 10_51_23 Engine 0.log

Final Checklist

  • I have included a screenshot showcasing the issue, if possible.
  • I have included a JASP file (zipped) or data file that causes the crash/bug, if applicable.
  • I have accurately described the bug, and steps to reproduce it.
@tomtomme
Copy link
Member

tomtomme commented May 6, 2024

@ShunitAm
I cannot confirm this for 0.18.3 on linux (flatpak) - so this might be windows specific, but I doubt it. I cannot test on win, sorry. But someone from the team might.
Can you share your data file in the mean time? I suspect it is data related

@tomtomme tomtomme added the Waiting for requester If waiting for a long time it is reasonable to close an issue label May 6, 2024
@ShunitAm
Copy link
Author

ShunitAm commented May 6, 2024 via email

@tomtomme
Copy link
Member

tomtomme commented May 6, 2024

Appending the file via mail does not work, sorry. Pleas drag and drop as described above.

@ShunitAm
Copy link
Author

ShunitAm commented May 6, 2024 via email

@EJWagenmakers
Copy link
Collaborator

I'll forward this file to Don.

@tomtomme
Copy link
Member

@vandenman
Did you have a chance to look at that file? Can you reproduce the bug on windows?

@tomtomme tomtomme removed the Bug label May 24, 2024
Copy link

github-actions bot commented Jul 6, 2024

This issue will be automatically closed in 42 days due to inactivity. Feel free to leave a comment if you believe this is still relevant.

@github-actions github-actions bot added the Stale Issues and pull requests that have not had recent interaction label Jul 6, 2024
@sitnok67155
Copy link

Hi,

I have the same problem on Windows when trying to use the bootstrapping feature when running a classical network analysis.

Is there a known fix for this? I must analyse my data by the end of the week but can't if I am unable to employ bootstrapping.

image

@github-actions github-actions bot removed Stale Issues and pull requests that have not had recent interaction Waiting for requester If waiting for a long time it is reasonable to close an issue labels Aug 6, 2024
@tomtomme
Copy link
Member

tomtomme commented Sep 2, 2024

@sitnok67155
@ShunitAm

Is this still a problem with JASP 0.19?

@sitnok67155
Can you share the data file here by renaming to zip and drag and dropping it here?

@tomtomme tomtomme added Waiting for requester If waiting for a long time it is reasonable to close an issue Bug: Medium Bugs that don't influence the basic function of the app, but it's better to fix them at some point. labels Sep 2, 2024
@ShunitAm
Copy link
Author

ShunitAm commented Sep 4, 2024 via email

@github-actions github-actions bot removed the Waiting for requester If waiting for a long time it is reasonable to close an issue label Sep 4, 2024
@tomtomme
Copy link
Member

tomtomme commented Sep 4, 2024

So you do not know if the error persists with 0.19?
If not we will wait for @sitnok67155 or @vandenman to confirm for 0.19 or send a file.

@tomtomme tomtomme added Waiting for requester If waiting for a long time it is reasonable to close an issue and removed Bug: Medium Bugs that don't influence the basic function of the app, but it's better to fix them at some point. labels Sep 4, 2024
@ShunitAm
Copy link
Author

ShunitAm commented Sep 4, 2024 via email

@github-actions github-actions bot removed the Waiting for requester If waiting for a long time it is reasonable to close an issue label Sep 4, 2024
@tomtomme tomtomme added the Waiting for requester If waiting for a long time it is reasonable to close an issue label Sep 4, 2024
@tomtomme
Copy link
Member

tomtomme commented Sep 6, 2024

This seems to be a duplicate of #2863 and it only occurs with certain data + nonparametric or case type bootstrap.
With the example from the data library everything is fine.
I wil close this one, so that we can discuss all this at #2863

@tomtomme tomtomme closed this as completed Sep 6, 2024
@tomtomme tomtomme added Duplicate This issue or pull request already exists OS: Linux and removed Waiting for requester If waiting for a long time it is reasonable to close an issue labels Sep 19, 2024
@tomtomme
Copy link
Member

tomtomme commented Sep 19, 2024

@ShunitAm @sitnok67155

More Infos on this but from vandenman, who wrote this in #2088:

Thanks for reporting the issue! What goes wrong internally is that the correlation matrix is not positive definite. If you change the correlation method to Cor or the method for Missing values to Exclude listwise then the error disappears and you do get output. I'll adjust the code so you receive a more informative error message in the future.

Also switching form non-parametric to parametric bootstrapping could help

Sorry for the huge delay. The better error message for the network module was added at some point but seems not to work in all cases. We will work on a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants