[WIP] specparam v2.0.0

[ryanhammonds]

The next major release of the 'fooof' tool will update the name of the tool to 'specparam' (for spectral parameterization).

Plan for migrating from fooof to specparam.

Naming

• Name change across module ([MNT] - Name update for new version #205 )
• Sweep module to find naming discrepancies if any (i.e. understanding peak_params vs periodic_params)

API

• Flexibility for other aperiodic/periodic fit functions (i.e skewed gaussian, double exponential, gamma, etc).
  • The plan for this is to be post specparam release to speed up transition.

NOTE: Updated by Tom, and some milestones moved, as we organize updates across versions (1.1 / 2.0 / >2.0)

[ryanhammonds]

@TomDonoghue everything should be complete here (after review + merge), except the flexible fit func (#194) PR and the final naming changes.

[ryanhammonds]

@voytek This is the issue that can be used for the changelog and progress report.

[TomDonoghue]

Thanks for the organization and work on all this Ryan! With the name update in progress (#205) this should now all be done / in process, so I'm going to close this issue now.

[danieltomasz]

Is there any timeline for specparam release? So the best practice would be now to refer to the package as specparam instead of fooof while writing a new manuscript?

[TomDonoghue]

Hey @danieltomasz - there isn't an exact timeline layed out - but hopefully soon (I hope to finish and release the new version as SpecParam in the next month). Note that the model isn't changing, so practically the new SpecParam will be equivalent to the current fooof. In a manuscript, you can refer to either name, or I would perhaps write something like: "spectral parameterization (v.1.0.0; REF) was used to..." - I don't think it matters too much.