GSL error

[Alokesh Manna]

Hi INLA Group,

Can you please tell me where INLA is failing? I did a few parallel computation. Some of them it worked. For some of the cases I obtained this following error.

How to resolve this issue? I ran for a GLM poisson with random spatial effect with some fixed value of the hyperparameters in besag kernel, loggamma with log(1e^-04) as initial value fixed so that we can cotrol over the spatial varying coefficients in their own way, should not be too restrictive.

```

gsl: interp.c:83: ERROR: x values must be strictly increasing
gsl: interp.c:83: ERROR: x values must be strictly increasing
Default GSL error handler invoked.
Default GSL error handler invoked.
sh: line 1: 3817259 Segmentation fault      (core dumped) '/gpfs/homefs1/alm20014/rlibs/INLA/bin/linux/64bit/inla.mkl.run' -s -v -t128:1 -P compact '/gpfs/sharedfs1/R_temp/RtmpGxRY8L/file3a363950b87095/Model.ini' > '/gpfs/sharedfs1/R_temp/RtmpGxRY8L/file3a363950b87095/Logfile.txt'
Error in inla.inlaprogram.has.crashed() :
  The inla-program exited with an error. Unless you interupted it yourself, please rerun with verbose=TRUE and check the output carefully.
  If this does not help, please contact the developers at <he...@r-inla.org>.
Calls: data_train_function ... do.call -> inla -> inla.core -> inla.inlaprogram.has.crashed
Execution halted

```

[Helpdesk (Haavard Rue)]

I would guess it fails due to a singularity that is imposed by the precision.
you can try to change values to see if it will recover.

> --
> You received this message because you are subscribed to the Google Groups "R-
> inla discussion group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to r-inla-discussion...@googlegroups.com.
> To view this discussion, visit
> https://groups.google.com/d/msgid/r-inla-discussion-group/fc29c461-0e28-476a-9926-9263c940581cn%40googlegroups.com
> .

--
Håvard Rue
he...@r-inla.org

[Alokesh Manna]

Thanks, I will! 

[Alokesh Manna]

Hi INLA group,

It seems this issue is still persisting.

I found some resource in github. <https://git.ligo.org/lscsoft/bayeswave/-/issues/112>

My errors looks like 

```

gsl: interp.c:83: ERROR: x values must be strictly increasing gsl: interp.c:83: ERROR: x values must be strictly increasing Default GSL error handler invoked. Default GSL error handler invoked. sh: line 1: 2105407 Segmentation fault (core dumped)

```

I keep changing initial values but for some cases, this is the reason. Do you know any solution?

[Alokesh Manna]

I am just adding a slurm file output if it helps!
Alokesh

[Alokesh Manna]

“Update: This issue can just be fixed by printing out doubles with more accuracy. C only prints doubles by default to 6 characters.”

Do you know if we can do so in INLA?

[Helpdesk (Haavard Rue)]

seems like this issue can be fixed by upgrading R-INLA to the most recent
testing version and use R-4.4

[Alokesh Manna]

Thanks. Can you tell me if there is any step size which can resolve this problem?

[Havard Rue]

The problem should be resolved by upgrading R and using the testing version of R-INLA

-- 

Håvard Rue 

hr...@r-inla.org

You received this message because you are subscribed to the Google Groups "R-inla discussion group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to r-inla-discussion...@googlegroups.com.

To view this discussion, visit https://groups.google.com/d/msgid/r-inla-discussion-group/CAGgS8MBWKze6Qw4xZg6FWCGyX%2BCkz-OFGKgofar1N5Kawz7COA%40mail.gmail.com.