-
-
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]: py-opc: operate the Alphasense OPC-N2 from a raspberry pi or other popular microcontrollers/microcomputers #540
Comments
Hello human, I'm @whedon. I'm here to help you with some common editorial tasks. For a list of things I can do to help you, just type:
|
|
|
👋 @dhhagan - thanks for your submission to JOSS. It looks like the From a quick inspection of this submission it's not entirely obvious that it meets our submission criteria. In particular, this item:
Could you confirm here that there is a research application for this software (and explain what that application is)? The section 'what should my paper contain' has some guidance for the sort of content we're looking to be present in the Many thanks! |
Hey @arfon , thanks for the PR (now merged). The research purpose is that it allows researchers to operate the particle counter from any microcontroller, rather than a PC, and is used by many research organizations (EPA, UNEP, MIT, Leeds, etc) to do aerosol research. Maybe a bit more information is given in a pre-submission inquiry I posted last month (openjournals/joss#362). Let me know if this doesn't fit and I can withdraw. |
@whedon generate pdf |
|
|
Thanks @dhhagan - I'd forgotten that you'd already enquired. We should be able to proceed here. While we wait for an editor to volunteer (and then find a reviewer) would you mind fleshing out your paper with a little more detail? Our goal is to have short papers that are understandable by a non-specialist audience. Right now I don't think this paper is quite there. |
Okay. I gave a rewrite a stab. I read a bunch of the accepted papers and tried to model it based on those, so hopefully it is okay now. |
@whedon generate pdf |
|
|
👋 @rajeshxsankaran @jared711 @skgrange would you be interested in reviewing this project for the Journal of Open Source Software, the review process focuses largely on the software and a short paper. Let me know if you are available to help so I can open a review issue for this submission. |
@whedon assign @Kevin-Mattheus-Moerman as editor |
OK, the editor is @Kevin-Mattheus-Moerman |
@dhhagan thanks for submitting this paper to JOSS. I've started looking for reviewers. If you could suggest suitable reviewers that would be very helpful. Also your work appears to rely on hardware. Will reviewers require this hardware for review? Can some aspects of the code be reviewed without the hardware? |
Hey @Kevin-Mattheus-Moerman: it does rely on hardware - I guess it depends on exactly what the review entails, but it would probably work better with the hardware. I suppose, depending on where the reviewers are located, I could lend a unit for review? What has been done in the past with code that relies on hardware? |
@amjaeger17 could you help review this please if @dhhagan drops off the device at the Media Lab? |
@Kevin-Mattheus-Moerman I can look at this next week if you have not found anyone else yet. |
@dhhagan could you drop off the device at the MIT Media Lab E14-274G (my office)? I'll then pass it on to @amjaeger17 who can help with review. |
Yup. Absolutely. Do you need a Pi as well?
On Thu, Mar 1, 2018 at 4:56 PM Kevin Mattheus Moerman < ***@***.***> wrote:
@dhhagan <https://github.com/dhhagan> could you drop off the device at
the MIT Media Lab E14-274G (my office)? I'll then pass it on to
@amjaeger17 <https://github.com/amjaeger17> who can help with review.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#540 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEKwSGWv_soTduHh18v4bb9Mk6Z2YvKLks5taG6UgaJpZM4RkkOf>
.
--
Regards,
David H Hagan
PhD Candidate | Atmospheric Chemistry & Physics
Department of Civil & Environmental Engineering
Massachusetts Institute of Technology
Cambridge, MA 02139
707.227.6695 | dhagan@mit.edu | https://www.davidhagan.me
|
We should have lots of pi's but bring yours if you think it is different. |
Perfect. @Kevin-Mattheus-Moerman I'll drop it off Monday mid-morning. |
@amjaeger17 Could you please give us an estimated timeline for your review to be completed? Thanks |
Hey @Kevin-Mattheus-Moerman Anything I can do to speed this along? |
Hey @Kevin-Mattheus-Moerman I dropped off the device with you, right? Could I come and grab it sometime this week - it needs to go out into the field soon. Thanks! |
Yes you can. Does Friday work? |
👋 how are we doing here? |
The device is still here at the MIT media lab. My colleague @amjaeger17 can unfortunately no longer do this review. I will ask another colleague to take a look but if he cannot then perhaps we are at a dead end for now. Apologies for the delay this has caused with this submission. |
OK, the reviewer is @tshu |
@whedon start review magic-word=bananas |
OK, I've started the review over in #782. Feel free to close this issue now! |
Submitting author: @dhhagan (David Henry Hagan)
Repository: https://github.com/dhhagan/py-opc
Version: 1.4.1
Editor: @Kevin-Mattheus-Moerman
Reviewers: @tshu
Author instructions
Thanks for submitting your paper to JOSS @dhhagan. The JOSS editor (shown at the top of this issue) will work with you on this issue to find a reviewer for your submission before creating the main review issue.
@dhhagan if you have any suggestions for potential reviewers then please mention them here in this thread. In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission.
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: