-
Notifications
You must be signed in to change notification settings - Fork 29
Closed
Labels
Module: jaspTimeSeriesOS: macOS IntelStaleIssues and pull requests that have not had recent interactionIssues and pull requests that have not had recent interactionStale-closedClosed due to inactivityClosed due to inactivityWaiting for requesterIf waiting for a long time it is reasonable to close an issueIf waiting for a long time it is reasonable to close an issue
Description
JASP Version
0.19.0
Commit ID
No response
JASP Module
Time Series
What analysis are you seeing the problem on?
All time series analysis
What OS are you seeing the problem on?
macOS Intel
Bug Description
I see following termination when running an ITS analysis - n=25,000 sample:
This analysis terminated unexpectedly.
Error: vector memory limit of 16.0 Gb reached, see mem.maxVSize()
Slack trace - does seem to load.
File is formatted correctly. Model does run on prophet, but only on the maximum a posteriori option.,
Expected Behaviour
I think the model should run?
Steps to Reproduce
...
Log (if any)
No response
More Debug Information
No response
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.
Metadata
Metadata
Assignees
Labels
Module: jaspTimeSeriesOS: macOS IntelStaleIssues and pull requests that have not had recent interactionIssues and pull requests that have not had recent interactionStale-closedClosed due to inactivityClosed due to inactivityWaiting for requesterIf waiting for a long time it is reasonable to close an issueIf waiting for a long time it is reasonable to close an issue