Skip to content

Improve mixmode #603

@d7919

Description

@d7919

There are several possible modifications to the mixmode modifier that might be helpful in some scenarios.

  1. There are some precision issues with the logistic map used (see fix test-initial to allow more precise calculation #555), could we replace this with something better behaved (but avoiding library code which code change from version to version).
  2. User configurable index for the location of the peak amplitude -- currently always a fixed mode index that gets the largest amplitude (I think it may be 4) but this means the conditions are z resolution dependent (i.e. different n will be the peak depending on mz).
  3. User configurable cutoff -- currently always initialises up to the first 14 modes and then the rest are zero. Would be nice to be able to change this so that we could initialise all modes (for example) or just a larger subset, can avoid sharp boundaries in the spectrum, which might help some cases.

Maybe we should introduce a new modifier for this so we can maintain the existing behaviour for compatibility?

Any other suggestions?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions