While looking through our current slate of tags, the software tag stuck out to me. Its our second most used tag, but that seems to because its serving a couple different purposes:
- To label questions that use any Matter Modeling software (e.g. How to convert a molecular structure made in Avogadro to a LAMMPS coordinate file?, MM-GBSA from Induced Fit Docking on Maestro)
- To look for software that serves some function (e.g. Molecular Dynamics simulation software for Windows, Plotting of natural bond orbitals (NBOs), Software to draw 3d micelle configuration, Is there a repository for DFT pre/postprocessing scripts?)
- Advice/insight on the development of Matter Modeling software (e.g. Since MKL is not optimized for AMD hardware, should I use a math library specific to AMD, or would an open-source one be just as good?, Did the 2019 discovery of O(N log(N)) multiplication have a practical outcome?, What is a good programming language for matter modeling?)
My view on these is that  is probably an overly general use of the tag (can just include tags for the specific program(s), while  and  are different enough to warrant separate tag (perhaps
software-recommendations or just
software for  and
software-development for ).
What are your thoughts on this? Does the software tag match your expectations the way it is currently or would you likely to see it broken into more specific tags (not necessarily the ones I recommended)?