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

update() faster than second marxan() #21

Open
javierfajnolla opened this issue Mar 3, 2017 · 1 comment
Open

update() faster than second marxan() #21

javierfajnolla opened this issue Mar 3, 2017 · 1 comment

Comments

@javierfajnolla
Copy link

Hi!

I have noticed that update() a MarxanSolved with new parameters is much faster on my computer than performing a new marxan() execution with those same new parameters.
As (I think) this update does not have an equivalent on running Marxan unconnected form R, I am wondering if there is any difference between those two ways, and if one is more appropriate than the other for any reason.
Thanks for the help! (and the package)

@jeffreyhanson
Copy link
Owner

Yeah, if you're using shapefiles as planning units if you use the update function this should be faster since it doesn't have to make the boundary data file again. So, using update would be better then creating a whole new problem each time.

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

2 participants