When may and when must software be released as a USGS scientific software information product? [077]

Software may be released as a USGS scientific software information product when all the following conditions apply:

1. The software project has reached a stable development status that may be identified by a static version tag.
2. Interpretive methods implemented while developing the software are fully described in published literature that are released prior to, or concurrent with, the scientific software information product.
3. Requirements defined by SM 502.11 are fully satisfied.

As an example, consider USGS scientists developing a standalone R or Python package for an existing, appropriately documented model application. Once the software is ready to be used for its intended purpose, the scientist may choose to complete a USGS scientific software information product to create a stable version that they or others may use and cite. 

Software must be released as a USGS scientific software information product prior to, or concurrent with, any of the following conditions:

1. The software is formally cited by another USGS information product.
2. The results of the software are critical to the scientific interpretation in another USGS information product.

As an example, USGS scientists write custom scientific code to support a USGS information product. The software must be released prior to, or concurrent with, the publication of the manuscript as a USGS information product.