[Bug]: Network Analysis created in previous version now creates error #3027
Description
JASP Version
0.19.1
Commit ID
No response
JASP Module
Network
What analysis are you seeing the problem on?
Network Analysis
What OS are you seeing the problem on?
Windows 10
Bug Description
I create a network analysis in a prior version, updated to 0.19.1, I could open and view the model, but when I change anything I now receive an error. I have tried uploading new/different binary data and it appears that I always get the same error when I try to use the isingfit model. The I can't share the data, but I can display screenshots:
Before:
After:
Expected Behaviour
I should be able to change estimators and back again, for example change IsingFit to huge and back again. In eth previous version of JASP this was not a problem.
Steps to Reproduce
- Open the file
- Change estimator to huge (model appears, plot created)
- Change back to IsingFit, error produced, no model produced.
Log (if any)
No response
More Debug Information
-------- Application Info --------
JASP Version: JASP 0.19.1
Build Branch: lockfiletesting
Build Date: Sep 9 2024 19:00:04 (Netherlands)
Last Commit: 8ac10c9c7aec029fdd695262d7bb4c3742a8ec89
-------- Basic Info --------
Operating System: Windows 10 Version 22H2
Product Version: 10
Kernel Type: winnt
Kernel Version: 10.0.19045
Architecture: x86_64
Install Path: C:/Program Files (x86)/JASP
Platfotm Name: windows
System Local: en_GB
-------- Extra Info --------
Current code page
Active code page: 850
Active code page: 65001
Host Name: A39072
OS Name: Microsoft Windows 10 Enterprise
OS Version: 10.0.19045 N/A Build 19045
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Workstation
OS Build Type: Multiprocessor Free
Registered Owner: Vice Chancellor
Registered Organization: Anglia Ruskin University
Product ID: 00329-00000-00003-AA313
Original Install Date: 16/01/2024, 15:24:40
System Boot Time: 21/11/2024, 17:04:32
System Manufacturer: Dell Inc.
System Model: Precision 3660
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 183 Stepping 1 GenuineIntel ~2100 Mhz
BIOS Version: Dell Inc. 2.9.3, 22/11/2023
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume2
System Locale: en-gb;English (United Kingdom)
Input Locale: en-gb;English (United Kingdom)
Time Zone: (UTC+00:00) Dublin, Edinburgh, Lisbon, London
Total Physical Memory: 65,225 MB
Available Physical Memory: 46,411 MB
Virtual Memory: Max Size: 74,953 MB
Virtual Memory: Available: 53,258 MB
Virtual Memory: In Use: 21,695 MB
Page File Location(s): C:\pagefile.sys
Domain: ANGLIA.LOCAL
Logon Server: \CHEDC02
Hotfix(s): 16 Hotfix(s) Installed.
[01]: KB5045936
[02]: KB5015684
[03]: KB5046613
[04]: KB5014032
[05]: KB5031539
[06]: KB5032392
[07]: KB5032907
[08]: KB5034224
[09]: KB5036447
[10]: KB5037018
[11]: KB5037240
[12]: KB5037995
[13]: KB5039336
[14]: KB5043935
[15]: KB5043130
[16]: KB5046823
Network Card(s): 1 NIC(s) Installed.
[01]: Intel(R) Ethernet Connection (17) I219-LM
Connection Name: Ethernet
DHCP Enabled: Yes
DHCP Server: 10.21.210.24
IP address(es)
[01]: 10.21.97.161
[02]: fe80::3d12:5af6:8b8f:c4a6
Hyper-V Requirements: VM Monitor Mode Extensions: Yes
Virtualization Enabled In Firmware: Yes
Second Level Address Translation: Yes
Data Execution Prevention Available: Yes
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.