-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
[PRE REVIEW]: PIVC: A C/C++ Program for Particle Image Velocimetry Vector Computation #3603
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post. For a list of things I can do to help you, just type:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
Wordcount for |
|
|
Pausing as we don't have a GitHub handle for the author (I've emailed them about this). Also, querying scope due to size. |
@whedon query scope |
Submission flagged for editorial review. |
This is my Github account.
Take caution when observing the current line of code count. This program was originally much larger in terms of LoC, total files, and written to utilize a proprietary closed-source API. My coauthors and I started this work in 2017 to optimize the original code as much as possible, hence greatly reducing the total files and LoC present, obtain gains in computation speed, and eliminate the requirement of a proprietary closed-source API. |
@fibreglass2 thanks for this submission. I quickly scanned through your paper as part of the scope review. Some quick comments:
If you make any changes to the paper or bib file you can call the following in a comment to update the paper: |
@fibreglass2 we're going to go ahead and proceed with review on this one—can you please address the comments that @Kevin-Mattheus-Moerman raised? |
@kyleniemeyer FYI I can edit this one if you like |
@whedon assign @Kevin-Mattheus-Moerman as editor @Kevin-Mattheus-Moerman sure thing! Wasn't going to ask but happy to accept the offer. |
OK, the editor is @Kevin-Mattheus-Moerman |
Certainly. Expect to see updates soon. |
@whedon generate pdf |
@whedon check references |
|
@whedon check references |
|
@whedon generate pdf |
@Kevin-Mattheus-Moerman I worked on the installation today and was able to use both of the precompiled versions (windows + linux) and then compiled it successfully in windows (although with warnings). I did not have any luck compiling in linux, but I think that was a problem with the dependencies. I found a bunch of minor things that could be improved in the documentation. Do I raise issues individually or group them? |
@clarka34 thanks for doing that. If you would be okay with it it would be great if I can assign you as a reviewer, it sounds like you'd be able to help. This issue here is a pre-review issue. Once I have found enough reviewers I will open a dedicated review issue (which will show tickboxes to guide your review). Also we encourage reviewers to open issues on the software repository. You can group things or separate as you see fit. Then please refer to these opened issues in the review issue. Would it be okay to assign you as a reviewer at this point? |
@yosefm @eguvep @dcsale would you be interested in reviewing this work for JOSS? The review focuses on the software itself, as well as a short paper. The streamlined review process takes place on GitHub (here is an example of an ongoing review: #3611 (comment)). Let me know if you are interested. Note we can be flexible regarding time taken to review. |
@Kevin-Mattheus-Moerman Sure thing! Just to be clear though, I definitely cannot review the code itself |
OK, @clarka34 is now a reviewer |
@clarka34 thanks, that is fine. We will also include other reviewers that will look into the code structure itself. However, a line-by-line code review is not really expected. If you focus on install, documentation, and evaluation of the functionality, that would be great. |
@quynhneo @ZIQIANG059 @vitorvilela @lento234 @yosefm @eguvep @dcsale would you be interested in reviewing this work for JOSS? The review focuses on the software itself, as well as a short paper. The streamlined review process takes place on GitHub (here is an example of an ongoing review: #3611 (comment)). Let me know if you are interested. Note we can be flexible regarding time taken to review. |
@Kevin-Mattheus-Moerman Yeah I would. Which aspect of the code would you like my review? |
I've raised a few issues; links are at the bottom of this comment. As I understand it there were two main questions around the code: does the use of OpenMP help take advantage of multicore processors, and is the code well structured and a suitable foundation for a collaborative project implementing various PIV processing algorithms? On OpenMP: this appears to work as expected. On code structure: this is my main area of concern; the code need work to follow best practices in structure, legibility, efficiency and testing. Very little C++ is used, and this is a shame; modern C++ has powerful features for generic and functional style programming which would allow the code to be cleaner, more legible, and just as efficient. Currently, I don't believe it's in good enough shape to act as a foundation for significant collaborative development. issues:
|
OK, @quynhneo is now a reviewer |
@whedon start review |
OK, I've started the review over in #3736. |
thanks for the message Kevin, but I am cannot take on any more work at the
moment, good luck with the code, sounds interesting!
with best regards,
Daniel Sale
…On Sat, Sep 11, 2021 at 2:24 AM Kevin Mattheus Moerman < ***@***.***> wrote:
@alexlib <https://github.com/alexlib> @yosefm <https://github.com/yosefm>
@eguvep <https://github.com/eguvep> @clarka34
<https://github.com/clarka34> @andreall <https://github.com/andreall>
@dcsale <https://github.com/dcsale> would you be interested in reviewing
this work for JOSS?
The review focuses on the software <https://gitlab.com/fibreglass/pivc>
itself, as well as a short paper
<https://github.com/openjournals/joss-papers/blob/joss.03603/joss.03603/10.21105.joss.03603.pdf>.
The streamlined review process
<https://joss.readthedocs.io/en/latest/reviewer_guidelines.html> takes
place on GitHub (here is an example of an ongoing review: #3611 (comment)
<#3611 (comment)>
).
Let me know if you are interested. Note we can be flexible regarding time
taken to review.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3603 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5AZIP2DAC4YW7H7XR7Y2DUBMG2NANCNFSM5B6RGBBA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Submitting author: @fibreglass2 (Kadeem)
Repository: https://gitlab.com/fibreglass/pivc
Version: v1.0.0
Editor: @Kevin-Mattheus-Moerman
Reviewers: @timdewhirst, @clarka34, @quynhneo
Managing EiC: Arfon Smith
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @https://gitlab.com/fibreglass. Currently, there isn't an JOSS editor assigned to your paper.
@https://gitlab.com/fibreglass if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission (please start at the bottom of the list).
Editor instructions
The JOSS submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type:
The text was updated successfully, but these errors were encountered: