Skip to content

Adding flexibility with the .RNAfinder.cfg file #3

Description

Hello!

Is there a reason why we require the RNAfinder config file to be hidden rather than out in the open like, e.g., the erpin models? Perhaps we can define RNAFINDER_CFG_PATH to point to the file directly rather than its parent directory? I can draft a PR for this modification.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions