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

About "ORmin_" and "ProbMin" #1

Open
LuzReyesE opened this issue Apr 12, 2021 · 2 comments
Open

About "ORmin_" and "ProbMin" #1

LuzReyesE opened this issue Apr 12, 2021 · 2 comments

Comments

@LuzReyesE
Copy link

Hi!
I am implementing the proposed code, but I have a question ..

In "results" I do not see the columns "ORmin_" or "ProbMin". Therefore, when exercising the functions:

resultsData <- acherENM @ results
resultsData% <>% select (settings, contains ('ORmin_'), contains ('ProbMin'))
probs <- resultsData%>% select (contains ('ProbMin'))%>% unlist (., use.names = TRUE)
obsState <- resultsData%>% select (contains ('ORmin_'))%>% unlist (., use.names = TRUE)

"probs" and "obsState" give me null values.

What are you calling in this function? In the case of "ORmin_" it seems to me that it is the minimize ommission rate which is indicated as "avg.test.orMTP" in the ENMevaluate output. But as for "ProbMin", I can't locate the information you mean.

Thanks.

@jmbarrios
Copy link
Owner

Hi @LuzReyesE, these values are not visible from the ENMEval package as you already notice.

It is correct, ORmin is avg.test.orMTP but the ProbMin values are not easy to get.

ProbMin value is the minimum training presence area but to get this value it is necessary to catch the MaxEnt results and extract it.

A modified ENMEval package can be found on CONABIO/ENMeval. The forked package is outdated but if you look at R/tuning.R file you can find how the ProbMin are extracted from the MaxEnt results.

I might look to an update to that package but I can't give you an ETA.

@LuzReyesE
Copy link
Author

Thank you very much for your answer...

I will review the code you share with me...
Regarding what you mention, for a moment I thought that the area predicted as present when the i-th record is removed would be equivalent to the "AUC.bin" part of the ENMevaluate output when "bin.output = T". But it is not logical.
What I do believe is correct is that the part of "test.orMTP_bin" refers to the success-failure variable by excluding the i-th record. However, this data alone is not sufficient to implement the jackknife test as an evaluation metric.
It seems to me that I will select the model configurations with the AICc metric, then with those configurations I will generate models with n-1 of the records to extract the Fractional predicted area values. The modeling with the ENMevaluate and the extraction with the code that you recommend.

Thanks.

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

No branches or pull requests

2 participants