-
Notifications
You must be signed in to change notification settings - Fork 22
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
Help with BIOMOD_4.2-5-2 - New "bm_ModelingOptions" function #481
Comments
Hi ! First, if you haven't already done it, you can have a look at the vignette Modeling Options . For your case, I will advise you to use the github version biomod2 4.2-6 as it will be easier. You can install it with: It will look like this:
Please note that we removed the In this case, the options you haven't changed and (I've added it for the example) the options for GLM will come from If you want to tuned one model, you can do it before :
Hope it helps ! Hélène |
Hey Hélène. That was very helpful and I was able to move forward following your script, thank you so much! However, I'm still having problems. When I open the user.val file, it seems that the script is prioritizing 'args.default' for all algorithms, instead of 'args.values' (defined by me). For example, when I run bm_ModelingOptions, it says that there is no maxent.jar in getwd(). Do you know how I can “force” the script to prioritize used.defined? Thank you again! |
Hi ! Your code is good. I didn't realize that this error message can be confusing 😬 I need to find another wording or remove it completely. Thanks for noticing and letting me know! Hélène |
Hey Hélène! When testing earlier (before sending the last message), Maxent didn't run. It seems that it actually recognized the path described in args.default, instead of following what was defined in args.values. I've now tested by manually moving maxent.jar to getwd() and Maxent runs normally (following the args.default path), so I think there's a conflict between args.values and args.default. Anyway, I was able to run it by moving maxent.jar to getwd(), so it's not a big deal. Thank you very much for your help! I'd also like to ask you something else, but if you think it might mess up this thread, I can open another one specifically for that. I'd like to understand the arguments of data.type. I'm using binary, but I assumed it would be better to use binary.PA since I don't have true absences. However, when testing binary.PA, the following message appeared:
Could you please explain what they are or where I can find out more about the other data.type arguments (binary.PA, abundance, and compositional)? I looked at the website but couldn't find them. I'd also like to know what I need to change so that the above error doesn't occur. Thank you very much for your attention and all the improvements in the biomod2. |
Hello ! This error is still strange. If you want to investigate more, could you send me the error message? But if you find a solution to run it smoothly, that's fine ! As for Hélène |
Hey Hélène! Sorry if my messages were confusing, I'll try to better explain and will send the error below. My maxent.jar file is in 'D:/OneDrive/Documents/R/maxent', the default directory of my computer. That way, I don't need to duplicate maxent.jar in each work directory. So I defined this address in args.values. Regardless of what I define in args.values, it seems that the script always recognizes the address in args.default, i.e. getwd(), since it shows a warning saying that it didn't find maxent.jar in the work directory ('D:/OneDrive/Documents/R/Scripts/23_TursiopsBiscayne/Output/P1_Forage') and doesn't run Maxent afterwards in BIOMOD_Modeling. To solve this, I had to make a copy of maxent.jar in the current work directory. This way it's working, but I'm just reporting this potential bug in case it can be fixed in the next versions (if it really is a bug, it might be a user problem haha). Thank you! Cheers.
|
Hello again! I see what is going here! So:
Sorry for all the "not so clear" infos! Documentation is a big part of the job and it can be hard to think about everything ! Hope everything will run smoothly now ! |
Hi Hélène. It worked, thank you! As you commented above, the warning continued but the model ran normally! I'll probably have more questions soon 😂, but that's all for now. I know these updates are a lot of hard work, but the package is getting even better. Thanks to you and the whole team for that. Cheers! |
Hi, it's me again! 😅 Today I went back to run the script but I couldn't do it. I didn't make any changes to the script I had run (previous message), I just updated the dev version (from 4.2-6 to 4.2-6-1). I checked my Thank you!
|
Hi !! I'm sorry: we were trying to make better error messages and I didn't realize it would make this error after. 🙈 Sorry again 🌸 Hélène |
Hey Hélène :) I ignored Maxent warning as you suggested and it worked perfectly at that time 🙏, but now I meant an error message that appeared when it wasn't possible to run Cheers!
|
Hello, I'm a little bit confused! Hélène |
I'm sorry, I didn't realize you released a new version this morning. Now it's running! Hopefully, it'll be a while before I have to come back and bother you again haha. Merci! |
No problem at all! |
Hello, biomod2 community,
I've recently migrated to the new version of biomod2 and am having some trouble transitioning from the BIOMOD_ModelingOptions function to the new bm_ModelingOptions function.
Previously, I used to specify the path to maxent.jar on my computer (instead of having multiple copies in working directories), but I'm not sure how to do this now. Additionally, I'm struggling with setting the directory for the explanatory .asc variables and the maximum number of background points created. I also used to set the GAM to a maximum of 4 knots.
Another question I have is regarding the "bigboss" and "tuned" strategies. Is it possible to manually adjust some algorithms using "user.defined" while having others follow the "bigboss" or "tuned" strategies, for example?
Thank you very much.
The text was updated successfully, but these errors were encountered: