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]: Hardware-Control: Instrument Control and Automation Package #2661
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:
|
|
|
👋 @Grant-Giesbrecht - thanks for your submission. Can you explain (and probably add to the paper) some examples of how this is (or will be) used in research, including what kinds of research? |
We're using this software in two different projects run by our research group. One project, ROOTS, uses hardware-control to interface with data acquisition modules and power supplies for a neutron-based measurement of carbon content in soil. The other project uses hardware-control to automate instrumentation used to run our compact RF particle accelerator. As for what type of research our software can be used for, the really nice part about our software is that it's very general and can be used for any type of experimental research that relies upon instrumentation. This is because it solves the broad problem of instrument control. So although we are using it for particle physics experiments, it could just as easily be applied to other fields like engineering or other sciences. |
I also added a brief description of these applications to the paper. |
@whedon generate pdf (@Grant-Giesbrecht - note that you can do this too if you make changes - whedon commands need to be at the start of a comment) |
👋 @timtroendle - I wonder if this might be a good first submission for you to edit? Perhaps you can check with your onboarding buddy |
@whedon invite @timtroendle as editor |
@timtroendle has been invited to edit this submission. |
Yes, can do. |
@whedon assign @timtroendle as editor |
OK, the editor is @timtroendle |
@danielskatz @sjpfenninger The license file is deviating slightly from BSD-3-Clause-LBNL. Is this fine or does this require a fix? Also: is there an automatic way for me to check the license? |
We do require an OSI approved license so this must be fixed, i.e. there should be a LICENSE file that contains the exact text of the BSD-3-Clause-LBNL license. Not aware of any automatic way to check this but maybe @danielskatz can enlighten us :-) |
There's no automatic way to check that I know. Also, please tag @openjournals/joss-eics in the future to get the on-duty AEiC (which is no longer me) |
Thank you both! @Grant-Giesbrecht could you please apply this tiny fix so that the license is in line with the OSI version? This concerns the first line only, which should read like the following:
|
Good catch - fixed it! |
Perfect. I will start looking for reviewers for your submission. If you can suggest anyone, please let me know @Grant-Giesbrecht . |
@timtroendle I would like to, but I have a feeling one can only truly review this package if they also have access to some of the physical instruments that it is programmed to interact with. |
Ok, I understand. |
Thanks @aquilesC for the offer! |
OK, @aquilesC is now a reviewer |
@timtroendle I can review this---it looks very relevant to what I'm interested in right now |
That's great @untzag, thanks! |
OK, @untzag is now a reviewer |
Hi @timtroendle I can review this project as well. |
Thanks @garrettj403 , that's good to hear. |
@whedon add @garrettj403 as reviewer |
OK, @garrettj403 is now a reviewer |
@whedon start review |
OK, I've started the review over in #2688. |
@bhajay, @ksunden, @sptennak, @caldarolamartin, thank you for considering to review this submission. I started the review with @aquilesC, @untzag, and @garrettj403 as reviewers. |
Submitting author: @Grant-Giesbrecht (Grant Giesbrecht)
Repository: https://bitbucket.org/berkeleylab/hardware-control/src/main/
Version: v1.0.0
Editor: @timtroendle
Reviewers: @aquilesC, @untzag, @garrettj403
Managing EiC: Daniel S. Katz
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.
Author instructions
Thanks for submitting your paper to JOSS @Grant-Giesbrecht. Currently, there isn't an JOSS editor assigned to your paper.
@Grant-Giesbrecht 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: