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

Error message: wrong number of summary statistics in statobs file. #156

Open
rachelghester opened this issue Apr 11, 2024 · 3 comments
Open

Comments

@rachelghester
Copy link

Hello,

I was wondering if anyone has run into this issue when running DIYABC-RF? I am running the GUI as a shiny app on Mac (R4.2.1 and have also tried newer versions). The training set simulation has worked and all output files have been created. However, when I try to run the RF analysis, I get the below error message:

read reftable done.
wrong number of summary statistics in statobs file.

I have checked the statobs file and checked it in Excel to ensure it contains the correct number of summary stats (130), which it does. Has anyone had this issue before with statobsRF.txt? Thanks in advance!

@beeul25
Copy link

beeul25 commented Apr 16, 2024

It seems I solve that problem.

I checked 'abcranger' can only handle numbers with 8 decimal places.
So, when all numbers in statobsRF.txt are converted to 8 decimal places, you can run Random Forest analysis with no error.

good luck.

@GiulianoColosimo
Copy link

Had the same "wrong number of summary statistics in statobs" issue . Manually removed some decimal place as per @beeul25 from my summary statistics and that issue was overridden.

Now I do get a segmentation fault, but that's another story :-(

@gdurif
Copy link
Collaborator

gdurif commented Aug 30, 2024

Hi, I am really sorry for the very late reply.

Due to work overload, the development, support and maintenance for the project diyabcGUI is currently paused. Feel free to contact us (by submitting an issue) if you want to take over the development for this project. Pull request are also welcome to fix bug or implement missing functionalities.

I have updated the README file to announce this. This is the official announcement to clarify a situation that has been going on for quite some time.

You can still use the command line version of the software which is still maintained/supported. Check the documentation page here.

All my apologies for the trouble,
Best regards

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

No branches or pull requests

4 participants