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:

@whedon commands

What happens now?

This submission is currently in a pre-review state which means we are waiting for an editor to be assigned and for them to find some reviewers for your submission. This may take anything between a few hours to a couple of weeks. Thanks for your patience 😸

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.

Attempting PDF compilation. Reticulating splines etc...

PDF failed to compile for issue #1472 with the following error:

/app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-fc4c5c749ca9/lib/whedon.rb:115:in check_fields': Paper YAML header is missing expected fields: bibliography (RuntimeError) from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-fc4c5c749ca9/lib/whedon.rb:80:in initialize'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-fc4c5c749ca9/lib/whedon/processor.rb:36:in new' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-fc4c5c749ca9/lib/whedon/processor.rb:36:in set_paper'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-fc4c5c749ca9/bin/whedon:55:in prepare' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/command.rb:27:in run'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in invoke_command' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor.rb:387:in dispatch'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/base.rb:466:in start' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-fc4c5c749ca9/bin/whedon:116:in <top (required)>'
from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in load' from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in

👋 @marshallward - I think a bibliography is needed by @whedon - perhaps you can reference the Fortran standard if nothing else seems appropriate. Once you've added a .bib file and updated the .md to use it, you can enter @whedon generate pdf here as a new comment to check the build process

Thank you @danielskatz, I've updated the doc to include a reference to the ISO document. (Not sure what else to cite here, since it's a pretty low level tool). I will direct @whedon in the next post.

Also, I believe that @zbeekman may be a suitable referee for this paper, based on his contributions to the Fortran community.

@whedon generate pdf

Attempting PDF compilation. Reticulating splines etc...

PDF failed to compile for issue #1472 with the following error:

Error producing PDF.
! Undefined control sequence.
\s

l.300 ...hierarchical tree of \texttt{Namelists}\s

Looks like we failed to compile the PDF

@whedon generate pdf

Attempting PDF compilation. Reticulating splines etc...

👉 Check article proof 📄 👈

Please see marshallward/f90nml#94

For submissions to JOSS, papers should talk a bit about the research use and users of the software - see https://joss.readthedocs.io/en/latest/submitting.html#what-should-my-paper-contain

Given that this is more of a Fortran tool rather than addressing a specific research activity, would you recommend submitting to a different journal?

FWIW (maybe not much!) I can see great value in research contexts for such a tool. Two immediate use cases jump to mind (although they are sort of two sides of the same coin):

1. Research code modernization & portability
2. Mixed language programming

1. Modernization & Portability

Namelist files are better than old school "input deck" formatted input files, but they still are not as widely used (and easy to work with) as JSON and YAML. Research codes like NASA's FUN3D rely heavily on namelists for input files as do weather & climate codes like WRF. Increasingly these types of Engineering, Geoscience & Physics codes are needing to be integrated into workflows and analysis pipelines using other tools. As such, namelists are a poor choice of data format for both input files and outputs, as they are not easily generated or read by other tools. Increasingly research code inputs may need to be assimilated from more diverse sources, and analysis with tools like Jupyter notebooks or further processing of outputs is desired.

f90nml can help researchers with modernization and porability in two ways:

1. Translate namelists into more modern and widely utilized (portable) data formats. These might be research code outputs, for example.
2. Provide bulk, easy translation of namelist input files for Fortran research codes utilizing tools like JSON-Fortran or petaca, which are being increasingly adopted during code modernization and ongoing development.

2. Mixed Language Programming

Python is often used as glue code in scientific and engineering software. For example Helios integrates components written in different languages, mostly Fortran and C++, and can swap in modular near-body CFD solvers for various rotorcraft and wind energy problems, including FUN3D, mentioned above. The glue code, and main driver application is written in python, but needs to generate namelist files to help talk to the Fortran based components. A framework like f90nml that can read and write namelists easily from Python could be attractive as a 3rd party library to be utilized in such applications.

It is my (completely unsolicited and possibly worthless) opinion that, with suitable research, edits and references, that this f90nml joss article could be crafted into one that highlights the research uses, users and applications, and is appropriate for review. (But I haven't read the draft yet, this is based solely on my opinion and familiarity with the software.)

P.S. I'm on that list, but recently added, so you must scroll down to the 582nd row.

Should the submission proceed, I hope my enthusiasm above is not mis-interpreted. I do not know, nor have I ever worked with or for the same company as @marshallward; I just appreciate the f90nml tool.

Pymagicc (https://doi.org/10.21105/joss.00516) has used f90nml and switching to it has replaced a bunch of hacky code in a previous version, thus greatly speeding up Pymagicc development.

I'm at GitHub's satellite conference right now, where it was just announced that GitHub repos will display "Used by" other projects button.

For f90nml there are 45 repos and 10 packages.

https://github.com/marshallward/f90nml/network/dependents

I have no doubts about the usefulness of this software, I'm just trying to make sure if fits JOSS - I'll confer with other editors and be back soon

Thanks all for the kind feedback. I will modify the manuscript over the next day or so and try to consolidate some of the uses cases from these projects, including the ones linked by @rgieseke. (I was aware of a few via Google, but I'm surprised to see much more).

@whedon generate pdf

Attempting PDF compilation. Reticulating splines etc...

PDF failed to compile for issue #1472 with the following error:

Error reading bibliography ./paper.bib (line 51, column 5):
unexpected "a"
expecting space, ",", white space or "}"
Error running filter pandoc-citeproc:
Filter returned error status 1
Looks like we failed to compile the PDF

@whedon generate pdf

Attempting PDF compilation. Reticulating splines etc...

👉 Check article proof 📄 👈

@whedon generate pdf

Attempting PDF compilation. Reticulating splines etc...

@whedon generate pdf

Attempting PDF compilation. Reticulating splines etc...

👉 Check article proof 📄 👈

👋 @zbeekman - it sounds like you are willing to review this?

sorry, now I see you said so earlier. I'll assign you, but until we get a second reviewer, nothing will start, and your delay to next weekend is fine

@whedon assign @danielskatz as editor

OK, the editor is @danielskatz

@whedon assign @zbeekman as reviewer

OK, the reviewer is @zbeekman

👋 @rouson - Are you willing to review this for JOSS?

Ok, let's see if Damian is available, or we will stick with you. In any case, we need another reviewer. Suggestions from @marshallward or @zbeekman ?

@tclune, @kc9qey - would either of you be willing to review this submission to JOSS? (A JOSS review covers the short paper and the code repository, using this set of criteria)

Thanks @tclune - with 2 reviewers now, we'll get going.

@whedon add @tclune as reviewer

OK, @tclune is now a reviewer

@whedon start review

OK, I've started the review over in #1474. Feel free to close this issue now!

@danielskatz It sounds like you have enough reviewers. If not, another person I would recommend is Craig Rasmussen. I'm not sure if my tagging him here work, but here goes: @rasmussn. My experience with python is very limited so I'm probably not the best reviewer.

Yes, we're all set, but thanks anyhow.