-
-
Notifications
You must be signed in to change notification settings - Fork 41
[PRE REVIEW]: CRED: a rapid peak caller for Chem-seq data #1374
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
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. For a list of things I can do to help you, just type:
What happens now? This submission is currently in a You can help the editor by looking at this list of potential reviewers to identify individuals who might be able to review your submission (please start at the bottom of the list). Also, feel free to suggest individuals who are not on this list by mentioning their GitHub handles here. |
|
PDF failed to compile for issue #1374 with the following error: Can't find any papers to compile :-( |
👋 @lpantano — It looks like this submission is one you can help us with... I'll assign you as handling editor now, but do let me know if I got this wrong 🤓 |
OK, the editor is @lpantano |
Here are some things you can ask me to do:
|
|
PDF failed to compile for issue #1374 with the following error: /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-a1723d160bb6/lib/whedon/author.rb:58:in |
|
PDF failed to compile for issue #1374 with the following error: /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-a1723d160bb6/lib/whedon/author.rb:58:in |
|
PDF failed to compile for issue #1374 with the following error: /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-a1723d160bb6/lib/whedon/author.rb:58:in |
|
|
Thanks for picking up the review. I noticed that whedon was unable to generate a PDF, so looked around and fixed some things in the paper. Hopefully this wouldn't affect the review process. |
@labarba @lpantano this is my first time submitting to JOSS (and TBH first time submitting a software paper), so I'm actually not sure on what sort of criteria a suitable reviewer should meet. With that said, looking at the previous JOSS referee list and perhaps one of the following may work? MDebasish I just filtered the list for the following criteria:
|
Hi @jlincbio , I will take this tool through the process. I just came back from vacations, so give me a couple of days to organize myself. Cheers |
Thanks for agreeing to handle this submission, @lpantano - it is my first software submission, so I am a bit over-anxious about the whole experience. I made a list of possible referees in an earlier post, but they were not tagged with mentions. If there is anything you need from me please do not hesitate to let me know. |
@lpantano - sorry I don't mean to rush you at all with this, but I am going to be out of the office for a few days next week. Is there anything I should do before that? |
Hi @jlincbio I am still trying to find a reviewer, I hope I can get somebody this week. I think you are all set, it is my fault. Thanks! |
OK, @darogan is now a reviewer |
@whedon check references |
|
|
@whedon start review |
OK, I've started the review over in #1423. Feel free to close this issue now! |
Submitting author: @jlincbio (Jason Lin)
Repository: https://github.com/jlincbio/cred
Version: 0.1
Editor: @lpantano
Reviewers: @darogan
Author instructions
Thanks for submitting your paper to JOSS @jlincbio. Currently, there isn't an JOSS editor assigned to your paper.
@jlincbio 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: