-
-
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]: funkyheatmap: Visualising data frames with mixed data types #7590
Comments
Hello human, I'm @editorialbot, a robot that can help you with some common editorial tasks. 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:
|
Software report:
Commit count by author:
|
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: 🟡 License found: |
|
👋 @LouiseDck - note that your paper does not compile. Please follow the example paper and note that you can click on the error above to find out more about it. Please feel free to make changes to your .md file, then use the command |
@editorialbot generate pdf |
Five most similar historical JOSS papers: HiPart: Hierarchical Divisive Clustering Toolbox cellanneal: A user-friendly deconvolution software for transcriptomics data MiscMetabar: an R package to facilitate visualization and reproducibility in metabarcoding analysis scTree: An R package to generate antibody-compatible classifiers from single-cell sequencing data MorphoPy: A python package for feature extraction of neural morphologies. |
👋 @LouiseDck - please add countries to all affiliations. I'm also unsure why you use "{funkyheatmap}" in your paper in a number of places. Are the {}s coming from some type of formatting instruction? Also, there is a References heading missing at the end of the paper, so the references look like they are part of the Acknowledgments. Please add this. Finally, I am going to ask the JOSS editors to take a look at this, as it's not clear to me that this is research software as defined by JOSS. You should hear back in a couple of weeks or so, due to the holidays. |
@editorialbot query scope |
Submission flagged for editorial review. |
@editorialbot generate pdf Thanks @danielskatz for the speed of your reply! I've adapted the references and added the references section. I hope this will be fine now 🤞 The curly-brace thing is a convention in the R community, and is used to denote the name of a package. I don't know where this convention originated, but it is common and still in use, e.g: here If I may make a case for this piece of software: I think benchmarking is a key part of the scientific process, and software like this enhances the usability of these benchmarks -- For big benchmarks it's a very useful way to communicate results clearly (you simply can't do this effectively with only a huge table full of numbers). For that reason I do think it fits within "extracting knowledge from data" or "supports the execution of research experiments" (as a benchmarking study is a kind of research experiment.) |
Five most similar historical JOSS papers: HiPart: Hierarchical Divisive Clustering Toolbox cellanneal: A user-friendly deconvolution software for transcriptomics data MiscMetabar: an R package to facilitate visualization and reproducibility in metabarcoding analysis MorphoPy: A python package for feature extraction of neural morphologies. scTree: An R package to generate antibody-compatible classifiers from single-cell sequencing data |
@editorialbot generate pdf Sorry, this should be fine now 😅 |
Five most similar historical JOSS papers: MiscMetabar: an R package to facilitate visualization and reproducibility in metabarcoding analysis tidyHeatmap: an R package for modular heatmap production based on tidy principles PCRedux: A Quantitative PCR Machine Learning Toolkit CGIMP: Real-time exploration and covariate projection for self-organizing map datasets pivmet: an R package proposing pivotal methods for consensus clustering and mixture modelling |
@danielskatz Thanks for being the managing EiC for this submission!
Just to weigh in on this -- I would argue it definitely falls under JOSS' definition of research software:
Since this package was developed and specifically catered to being able to showcase results from (bioinformatics) benchmarking studies. Therefore it supports the execution of research experiments, and extracts knowledge from the raw benchmarking results. A showcase of which studies (derivatives of) funkyheatmap have been used in is shown here. An example of how funkyheatmap extracts knowledge from large datasets: on the openproblems website funkyheatmap is used to summarise the results ( https://openproblems.bio/results/label_projection/ ) based on the raw data from the benchmark ( https://openproblems.bio/results/label_projection/data/results.json ). One final note, it was originally part of a repository from a different study ( https://github.com/dynverse/dynbenchmark/blob/master/package/R/funky_heatmap.R ) but we decided to turn into a standalone package since there was a lot of interest from the research community. 🙇 Thank you for taking this into consideration and hope for a positive response. |
Submitting author: @LouiseDck (Louise Deconinck)
Repository: https://github.com/funkyheatmap/funkyheatmap
Branch with paper.md (empty if default branch):
Version: 0.5.0
Editor: Pending
Reviewers: Pending
Managing EiC: Daniel S. Katz
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @LouiseDck. Currently, there isn't a JOSS editor assigned to your paper.
@LouiseDck if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: