Data recommendations when publishing

[ljhwang]

We recently updated our Software Development Best Practices to include providing guidance on archiving model data for publishing (see Target Best Practices 5v).

Our full guidance on publishing with data is here:
https://geodynamics.org/software/software-bp/software-publishing

Some examples that have been implemented in our community here:
https://aspect.geodynamics.org/citing.html?ver=2.5.0&src=citehtml
https://pylith.readthedocs.io/en/latest/intro/preface.html#citation
https://rayleigh-documentation.readthedocs.io/en/latest/doc/source/citing_rayleigh.html

We are recommending that similar language be adapted and added to the SPECFEM manuals adding a section after information on citation the code (Citation). Recommended language could look something like:

What to Deposit
In general for SPECFEM simulations, you should deposit contents of your DATA/, input_directory, and output_directory. This includes your:

• Par_file and their dependencies,
• MESH/
• solver input e.g. CMTSOLUTION, FORCESOLUTION, and STATIONS
• Adjoints, tomography, noise, and gravity files required for input to SPECFEM.

Any modified source code should also be included as well as any custom pre- and post-processing scripts/codes.

Example
A simple form for non AGU publications:

We use SPECFEM3D (Komatitsch and Tromp, 2002; Komatitsch and Tromp, 2002; Komatitsch et al., 9999) which is available for download through its software landing page specfem.org. Model data necessary to reproduce these results including insert a description can be downloaded from Zenodo insert PID.

And where Komatitsch et al., 9999 is the citation to the version of the code used.