The new software called MANTA makes power spectral density plots for various percentiles for any file or set of files you put into the GUI.
Bitbucket site for the software is here: https://bitbucket.org/CLO-BRP/manta-wiki/wiki/Home
When I look at the large excel file that it outputs, though I notice that it has a column for 1-Hz band bins up to 400 Hz, and then switches to millidecade bands. I am used to decidecade bands. The standards for modeling and measuring soundscape data as set by the ADEON project (https://adeon.unh.edu/sites/default/files/user-uploads/WEB-DRAFT%20ADEON%20Soundscape%20Specification_V2.pdf) define it as “one tenth of a decade (ISO 18405). Its value is approximately equal to that of one third of an octave, and for this reason is sometimes referred to as a ‘one‐third octave’.” I’m aware that these bands are based on the perception of how we hear as humans.
The ADEON standards also suggest that “individual (unweighted) decidecade levels shall be stored in such a way as to permit appropriate frequency weighting in the future as understanding of animal hearing improves.” So I expected MANTA software to output decidecade band power levels in the resulting excel sheet. (Decidecade bands are covered nicely in Wikipedia at: https://en.wikipedia.org/wiki/One-third_octave)
However, MANTA stores millidecade bands. I can extract sets of columns following this table of decidecade band limits and then incoherently sum them (i.e., convert their dB values to microPascals, sum those, and convert the answers back to dB), but that is a lot of extra steps.
So, I’m curious to know why millidecade bands are needed in MANTA software instead of decidecade bands. Are they more important? Are they an up-and-coming standard for soundscape metrics? Please clarify.