Skip to content

Group/organize model functions and corresponding parameter fitting functions #1621

Open
@adriesse

Description

@adriesse

One thing that is not clear is where various existing and future fitting functions should go. In general I think the best place for them would be as close as possible to the models they serve, both in the code (except if they are really long) and in the API reference. There could be a section listing just fitting functions as there is now, but I would see that as secondary.

Originally posted by @adriesse in #1598 (comment)

Let's take up @adriesse's point about where functions should live and be listed in a separate issue (Anton, can you open one?).

Originally posted by @kanderso-nrel in #1598 (comment)

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