How to cite scikit-optimize?
See original GitHub issueHi,
Currently I’ve been performing some modelling for experimentalists (academic research).
I have found skopt
to be very useful and I would like to cite it.
Do you have any preferred format when citing skopt
? (I’ve searched the repo and docs but couldn’t find any guidance)
Also, do you offer any recommendations on what other references to cite (I’ve used forest_minimize
for example)?
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (14 by maintainers)
Top Results From Across the Web
Citing scikit-optimize · Issue #705 - GitHub
I am using scikit-optimize in an upcoming paper. What would be the preferred citation style for this library?
Read more >scikit-optimize/scikit-optimize | Zenodo
Scikit -Optimize, or skopt, is a simple and efficient library to minimize (very) expensive and noisy black-box functions.
Read more >scikit-optimize: sequential model-based optimization in Python ...
Scikit -learn hyperparameter search wrapper. Search for parameters of machine learning models that result in best cross-validation performance. Algorithms: ...
Read more >Citing Scikit-HEP
Citing Scikit -HEP or individual packages ... Kindly consider citing any specific package if that seems appropriate. Most package GitHub repositories contain at ......
Read more >How to optimize for speed — scikit-learn 1.2.0 documentation
Please cite us if you use the software. ... Python, Cython or C/C++?; Profiling Python code; Memory usage profiling; Performance tips for the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Any thoughts?
Otherwise I would say let’s create zenodo entry for every (future) release -> DOI for people to cite to signify which version they use.
If and when we do something nice that is original research (or otherwise should be documented in an article) we tackle that on a case by case basis.
(If you agree with this proposal use 👍 or 👎 on this comment for voting)
If we want to discuss this more I would suggest we start with collecting a list of the problems that we are trying to solve via citation as that will help us figure out what the solution should be.
A few days waiting time is no problem (I am guessing we will submit in a few weeks but I’m not the main author so hard to say for sure).
Not that it is any of my business, but I thought I could mention that there is also JORS (Journal of Open Research Software).