-
-
Notifications
You must be signed in to change notification settings - Fork 41
[PRE REVIEW]: SpecpolFlow: a new software package for spectropolarimetry using Python #7515
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 @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: |
|
Five most similar historical JOSS papers: MCALF: Multi-Component Atmospheric Line Fitting PyAstroPol: A Python package for the instrumental polarization analysis of the astronomical optics. EISPAC - The EIS Python Analysis Code Astronomical échelle spectroscopy data analysis with PypeIt: The Python Spectroscopic Data Reduction Pipeline |
@folsomcp — Thanks for your submission! All the suitable JOSS editors are currently working at capacity so I'm going to "waitlist" this review until an editor with the relevant expertise is available to take it on. Thanks for your patience! |
Note also that the paper is a bit long. Our docs say
The "Overview of SpecpolFlow" in particular can probably be pared down somewhat. Please try to get the word count closer to 1000 words while we wait for an editor to pick this up. Thanks! |
Has there been any progress on finding an editor for this paper? It has been a couple months now. @warrickball do you happen to have any updates? If there is anything we can do to help speed things up please let us know. In the mean time we will try to edit the paper down some more. |
@editorialbot check repository |
Software report:
Commit count by author:
|
Paper file info:
✅ The paper includes a |
License info: 🟡 License found: |
I'm afraid so @folsomcp. If no-one else step forwards, I should have another space within the next week or so. If you can recommend any reviewers, either from our reviewer database, previous JOSS publications (see the authors of the articles suggested above, though these aren't guaranteed to be useful...) or your own network, that'll help whichever editor picks this up get started with looking for reviewers when the time comes. Sorry for the wait! |
Thanks for the update! For potential reviewers, here are some colleagues who have experience with similar analysis techniques to the ones used in the paper, and who might be willing to provide a report. Julien Morin (Université de Montpellier) At a quick look those people don't seem to be in the reviewer database. In the papers above, the paper by gully, reviewed by bmorris3 and wtgee seems to be the most similar to our project. So perhaps one of them could be suitable. |
@editorialbot assign me as editor |
Assigned! @warrickball is now the editor |
Thanks @folsomcp, I'll pick this one up as editor and start looking for reviewers. Thanks very much for the recommendations! |
By the way, are those suggestions all members of the BCool collaboration, as you are yourself? The BCool website seems to be down right now but that's what I glean from the author list of e.g. Bellotti et al. (2025). JOSS does have a conflict of interest policy for reviewers (and editors):
|
Thanks for being the editor on for this! I should have read that policy before suggesting reviewers. oops! On my list Julien Morin, Pascal Petit, Sandra Jeffers, and Stephen Marsden are BCool members. (It is an un-funded collaboration, but it leads to some publications together). In a similar vein, Oleg Kochukhov is part of the EXOHOST collaboration that I am also involved with (although we're not directly working together on a project at the moment). Coralie Neiner and Alexandre David-Uraz are not members of those collaborations, although I have published with them. If you want to avoid anyone I have been a coauthor with in the last 4 years, that narrows down the list of people I can recommend quite a bit. Maybe: James Sikora or Viktor Khalack could be possibilities? (I haven't thoroughly checked if an of the co-authors have published with them recently.) I would rather avoid a reviewer from the Potsdam stellar physics group. I was recently involved in a competing paper that contradicted some of their work, and so I'm not 100% sure they would be unbiased. One limitation with my suggestions is that these are people with astronomy expertise (particularly spectropolarimetric observations of stars or stellar magnetic fields) but not necessarily software engineering expertise. |
One of our coauthors suggested Heloise Stevance as another possibility. She is not really involved in the stellar magnetism community, but has more experience with software development, and familiarity with spectropolarimetry. She seems to be in the reviewer database as HeloiseS. |
@editorialbot add @DerekAstro as reviewer |
@DerekAstro added to the reviewers list! |
@editorialbot add @gully as reviewer |
@gully added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #7891. |
Submitting author: @folsomcp (Colin Folsom)
Repository: https://github.com/folsomcp/specpolFlow
Branch with paper.md (empty if default branch):
Version: v0.4.3
Editor: @warrickball
Reviewers: @DerekAstro, @gully
Managing EiC: Warrick Ball
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @folsomcp. Currently, there isn't a JOSS editor assigned to your paper.
@folsomcp 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: