A blog post about Computo #1177
Conversation
|
Hi @astamm, sorry I missed your PR last week, I'll take a look this week and get back to you soon! |
There was a problem hiding this comment.
Hi @astamm,
Thank you for your blog post! It's very cool to see how Computo works, how it came about and where it's going. I think the rOpenSci community will definitely be interested.
I've made some suggestions, sometimes technical (like with the author files) and sometimes editorial (I suggest some alternate wordings and some clarification, as well suggesting you include an introductory statement explaining why share Computo on ropensci.org)
Take a look and see what you think of my comments suggestions. Let me know when you've had a chance to review and make edits as you see fit.
If you have time to review soon (by Wednesday November 5th), I think we can publish on Thursday November 6th, but there's a technically problem with the link which may not be resolved in time (but we can always fix it after the fact). If that's too soon for you, we can absolutely pick a later date (we try to avoid Fridays and Mondays to keep posts from being missed over the weekends).
Thank you again!
- post follows Content Guidelines
- post follows Style Guide
- title is in Title Case
- publication date is ok
- I think next Thursday, November 6th will work, but I need to check with Maëlle about the link issue and she won't be available until next week.
- slug is ok
- alternative text of images is informative
- author metadata is provided with correct folder name for each language
- See my suggestions
- html not included in pull request of Rmd post
- I ran
roblog::ro_lint_md()on index.md - I ran
roblog::ro_check_urls()on index.md - I ran a spell-check on index.md
- YAML subject tags are ok ("tech notes" for tech notes; "community" for non-staff non-editor)
- YAML field 'editor' is filled with your name
- YAML field 'translator' is filled as needed
- YAML field 'interviewee' is filled as needed
- YAML field 'preface' is present if necessary
- YAML field 'params.doi' is filled with a new DOI
|
|
||
| ## Why we created Computo | ||
|
|
||
| The idea of Computo was born out of a need to address several challenges in the current scientific publishing landscape, particularly within statistics and machine learning. While the reproducibility crisis is a significant concern, with an increasing volume of publications straining the review process and potentially impacting quality \[1\], Computo also aims to foster a deeper scientific understanding. |
There was a problem hiding this comment.
I'm a bit unclear about which challenges Computo aims to address. The reproducivility crisis? The strain fo the increasing volume of publications on the review process? What do you think of the following suggestion?
| The idea of Computo was born out of a need to address several challenges in the current scientific publishing landscape, particularly within statistics and machine learning. While the reproducibility crisis is a significant concern, with an increasing volume of publications straining the review process and potentially impacting quality \[1\], Computo also aims to foster a deeper scientific understanding. | |
| The idea of Computo was born out of a desire to foster a deeper scientific understanding as well as a need to address several challenges in the current scientific publishing landscape, especially within statistics and machine learning. In particular the reproducibility crisis is a significant concern, and the increasing volume of publications straining the review process is potentially impacting quality of scientific publications[^1]. |
There was a problem hiding this comment.
I will check with the editorial board today and get back to you on this later in the day.
|
|
||
| The idea of Computo was born out of a need to address several challenges in the current scientific publishing landscape, particularly within statistics and machine learning. While the reproducibility crisis is a significant concern, with an increasing volume of publications straining the review process and potentially impacting quality \[1\], Computo also aims to foster a deeper scientific understanding. | ||
|
|
||
| The rapid proliferation of new methods in machine learning and statistics can make it difficult to establish a clear state of the art for specific scientific questions. There is often a lack of established, subject-specific benchmark datasets, and the pressure to demonstrate the superiority of novel methods can sometimes lead to less-than-objective performance evaluations. Furthermore, publishing negative results (e.g. failure to demonstrate a statistically significant improvement), which are crucial for scientific progress, remains challenging. |
There was a problem hiding this comment.
I feel like there's something missing in "A clear state of the art [---] for specific scientific questions.".
A clear state of the art what? "Procedure"? "Roadmap"? "Method"?
There was a problem hiding this comment.
You'll need to use françois-david-collin as the folder name to ensure this works correctly (i.e. keep special characters)
| github: astamm | ||
| orcid: 0000-0002-8725-3654 | ||
| linkedin: https://www.linkedin.com/in/aymeric-stamm-65a420179/ | ||
| img: https://github.com/astamm/astamm.github.io/blob/master/images/aymeric.jpg |
There was a problem hiding this comment.
Images need to be stored on ropensci, if you give me permission to edit the PR I'll add them to the correct location for you.
There was a problem hiding this comment.
Of course you can edit. I think I granted you write access to the branch when I created the PR, but if not, let me know and I can do so.
There was a problem hiding this comment.
I think you'll need to give me permission to edit the branch, neither Maëlle nor I were able to to.
| github: fradav | ||
| orcid: 0000-0002-8374-7163 | ||
| linkedin: fradav | ||
| img: https://www.gravatar.com/avatar/e538a1497c43683e0ab4f36c5c1a30d4 |
There was a problem hiding this comment.
To use your GitHub avatar, omit the img, this way it will always show your GitHub avatar, even if you later update it.
| img: https://www.gravatar.com/avatar/e538a1497c43683e0ab4f36c5c1a30d4 |
| # editor: ~ | ||
| --- | ||
|
|
||
| {{< imgtxt src="https://computo-journal.org/assets/img/logo_text_vertical.svg" alt="Computo logo" link="https://computo-journal.org/site/about.html" >}} |
There was a problem hiding this comment.
This link isn't working at the moment, but I've opened an issue (#1181) as I think it's a website issue.
There was a problem hiding this comment.
In the browser, it works fine. I would not know how to help debug this further.
There was a problem hiding this comment.
Oh glad to hear it works for you, perhaps it's a browser-related thing. At any rate Maëlle pushed a fix (it wasn't your problem 😁) so we're hopefully good to go!
| --- | ||
|
|
||
| {{< imgtxt src="https://computo-journal.org/assets/img/logo_text_vertical.svg" alt="Computo logo" link="https://computo-journal.org/site/about.html" >}} | ||
| [Computo](https://computo-journal.org) is a journal promoting methodological, computational, and algorithmic contributions in statistics and machine learning that provide a better understanding of which models or methods are most appropriate to answer specific scientific questions. Computo leverages modern tools in programming and scientific reporting to support more transparent, interactive, and reproducible research outputs. |
There was a problem hiding this comment.
Perhaps add something explicitly explaining why an article about Computo is on the rOpenSci blog? e.g., add a sentence at the end like "We're excited to introduce Computo to the rOpenSci community as a complementary...."
2 participants
roblog::ro_lint_md()on index.md (optional).roblog::ro_check_urls()on index.md (optional).I wonder how to add a default post draft for LinkedIn in the YAML header.