Comments (7)
This reminds me, the old prioritizr is archived on CRAN and has my email associated with submission. At some point I think I'll need to let them know to change the corresponding author so someone else can submit to CRAN. Jeff, will this be you?
from prioritizr.
Given comments via email, how about the following for now:
Hansen, Schuster, Strimas-Mackey, Watts, Arcese, Bennett, Possingham
We will of course have to ask Matt W and Hugh if that's okay with them.
from prioritizr.
@ricschuster Ok, I'll update the citation accordingly.
@mstrimas Yeah, you'll need to email CRAN that a new person will be maintaining the prioritizr package when this version is submitted. Yeah, I can be the package maintainer if that's the best. What do you think @ricschuster? I understand if you'd rather be the maintainer since this is you've been spearheading this project.
from prioritizr.
@jeffreyhanson Thank you.
re: maintainer. With the 3+ packages we will have under the prioritizr package, do you think its makes sense to have individual maintainers per package or should we try to have one for all? Not sure what your near to mid-term plans are @jeffreyhanson, but I should be able to continuously dedicate work to this project over the next ~3 years. Given that I would be happy to act as maintainer over that time, if that means the most consistency. Depending on what I will do after that time we might want to move this over to Joe or a person in his lab for consistency. What do you guys think?
from prioritizr.
Yeah, I think it makes sense to have the same maintainer for all the packages. I'm not sure how much time I'll have in the future to help maintain this pkg. So, I think having @ricschuster as the pkg maintainer would be great.
from prioritizr.
Alright, sounds good, once you're getting close to CRAN submission let me know and I'll email to transfer the maintainer over to Richard.
from prioritizr.
I'll close this issue since we seem to have resolved this.
from prioritizr.
Related Issues (20)
- Overly zealous assert causes spurious failure on problem(), breaking valid prioritizr 7.1.1 scripts HOT 2
- high boundary penalties, but solution has weird hole HOT 1
- Error while solving the problem HOT 10
- package overview manual entry
- Add linear constraints for multiple zones HOT 3
- lexicographic (hierachical) multi-objective optimization HOT 5
- Add max area threshold for zone and dealing with fragmented zones HOT 25
- Improve presolve checks HOT 1
- ℹ In argument to `x`. Caused by `problems(pu, features = multi_layer)` HOT 7
- write_problem() doesn't work
- Categorical `SpatRaster` layers break problem creation HOT 4
- Ph.D. HOT 2
- How should I incorporate a risk layer? Penalty, feature, feature weight? HOT 7
- Add proximity-based metrics for irreplaceability
- Cost in problems with zones HOT 2
- PrioritizR vs. traditional Weighted Overlay (land use planning example) HOT 5
- Optimization Suggestion: Excessive Memory Usage during Processing HOT 7
- Add new vignette to describe "lines" issue HOT 2
- Return the optimality gap of a solution HOT 3
- Invalid error message when using linear penalties/constraints with NA values
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from prioritizr.