Skip to content

STO (storage) period specification #206

Description

@mjreno

This is an issue to track the evaluation of alternative ways of specifying dynamic (period) input for the storage package. The intent is to more closely align storage with existing patterns of specifying dynamic input, if possible, or to formalize a new general approach that both storage and other packages can use.

Currently storage period input comes in the form of two optional keywords, steady-state or transient. This specification is more like you'd expect to see in an OPTIONS block- does this represent a more generic class of dynamic input for utilities and packages?

An list style specification is being evaluated here:

Metadata

Metadata

Assignees

Labels

dfnDFN specification-relatedquestionInformation or decisions required

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