Error in Maxnet and ENMeval

[carlosed...@gmail.com]

Hi, 

I found this error in maxnet and ENMeval

Error in mm %*% object$betas: non-conformable arguments 

I tried to run the following commands:

rms <- seq(0.5, 5, 0.5)

# iterate model building over all chosen parameter settings

e <- ENMeval::ENMevaluate(occs.xy, envsBgMsk, bg.coords = bg.xy, RMvalues = rms, fc = c("L", "LQ", "H", "LQH", "LQHP", "LQHPT"),

method = 'user', occs.grp, bg.grp, clamp = TRUE, algorithm = "maxnet")

I did not find how to solve it, does anyone have any ideas?

best,

[Belay Ejigu]

dear blessed brother,

i think it is better if you use the maxent model in GUI mode if you are a beginner!

because with the GUI maxent model you can learn a lot about it and after that you can run it with R, Python, etc programming languages.

Love you! by!

--
You received this message because you are subscribed to the Google Groups "Maxent" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maxent+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/maxent/fafb120f-80f5-471b-9bbb-b14cbf0a5b8en%40googlegroups.com.

[Jamie M. Kass]

This error is due to an issue with maxnet. The new ENMeval 2.0.0 takes care of this by inserting the argument "addsamplestobackground=TRUE", which is an addition to the newest maxnet version. This usually fixes this error, if I'm not mistaken. Otherwise, you can always use maxent.jar to avoid errors with maxnet.

Jamie

[carlosed...@gmail.com]

Thanks, I updated and it worked.

[carlosed...@gmail.com]

Dear friend, 

I'm now using the Wallace package, and then I export the code to rscript. This is amazing. 

Jamie, I realized that regardless of the version, the error remains with some of my species. 

my script is here - https://colab.research.google.com/drive/1ipkFSXhc98qS2TS_pfcmZ3IDSUB4qJal?usp=sharing

[Jamie M. Kass]

Hey Carlos,

Sorry to get back to you so late. This seems to be an issue that occurs when hinge features and a categorical variable with 2 levels is used. Have you made sure the categorical variable is declared categorical in the implementation? Earlier versions of Wallace did not give the option to specify categoricals, but I believe the dev version on Github does. Although it has not been fully resolved yet, please see this open issue for the topic here: https://github.com/jamiemkass/ENMeval/issues/57

Jamie