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

[JOSS Review]: Performance #6

Closed
jbytecode opened this issue Nov 19, 2020 · 9 comments
Closed

[JOSS Review]: Performance #6

jbytecode opened this issue Nov 19, 2020 · 9 comments

Comments

@jbytecode
Copy link

jbytecode commented Nov 19, 2020

Due to paper submission in JOSS

There is an item in reviewing list that states

Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Since, the paper does not directly include any performance claims, the README.md file includes

...c-lasso has a default algorithm setting that proved to be the fastest in our numerical experiments...

If this claim is current, please add a small micro-benchmark script that reports performances of implemented methods so people can reproduce the results and make comparisons.

@jbytecode
Copy link
Author

jbytecode commented Nov 19, 2020

Note:

It is also mentioned in paper

Note that the run time for this d = 100-dimensional example for a single path computation
is about 0.5 seconds on a standard Laptop.

and this is definitely a performance claim. Please follow the instructions commented above. microbenchmark script is the solution. The standard Laptop is also an ambiguous term. Please specify.

@muellsen
Copy link
Collaborator

Thanks for the suggestion! Yes, absolutely. Most of our computational work was actually to test the performance of the different methods. We will add a benchmark and include it, and clarify the run time statements.

@jbytecode
Copy link
Author

Dear authors,

This is the last issue. Whenever you finish this work, I will finalize my review.

Thank you for your great effort.

@muellsen
Copy link
Collaborator

muellsen commented Dec 9, 2020

Update regarding performance benchmarks: We will provide this in the upcoming days, including a comparison to cvx. Will ping you once done!

@muellsen
Copy link
Collaborator

We ran a comprehensive run time comparison now... Currently in the process of providing the result in a presentable format (and including it in the paper); sneak peak here: https://github.com/Leo-Simpson/c-lasso/tree/master/benchmark

@jbytecode
Copy link
Author

@muellsen does your output underpin the performance claims in the paper?

Will you make a change in the paper? Please let me know, so I can re-compile it in the review page.

@jbytecode
Copy link
Author

@muellsen can you please, update your status of progress?

Thank you.

@muellsen
Copy link
Collaborator

muellsen commented Jan 6, 2021

Happy New Year! Here is a heads-up. We updated the Paper.md and included a section on numerical benchmarks. We also finalized a README in the benchmark folder https://github.com/Leo-Simpson/c-lasso/tree/master/benchmark that shows the micro-benchmarks. We think, now our performance statements in the paper are backed up by these experiments now.

@jbytecode
Copy link
Author

seems okay. Thank you. I am now closing this issue.

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