Skip to content

opus-i2s compatability #2

Description

@ndeutscher

Following on from issue #1, and once the opus-i2s.in files can be found, I have struck a series of problems getting the software to work with our files. These work just fine with opus-i2s itself, so it would be good to increase the flexibility here to handle that, as others might also strike similar issues.

I don't know if we want these listed as separate issues, as they are all related, but so far:

  • nonlin5 does not support including the path in the individual spectrum listing.
  • nonlin5 does not support run numbers with lengths greater than 4 digits (we use 6, and opus-i2s supports this). This means that the outputs of pre-nonlin5 create files such as 'nonlin5_20140101_****.inp' (with the asterisks and inverted commas).

I have yet to code solutions to these issues (and there are possible work arounds), but I will try to do so.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions