Skip to content

OC (Output Control) period specification #205

@mjreno

Description

@mjreno

The Output Control period block specification currently defines a set of records associated with output action, an output type and the setting. This format does not indicate how many records of each type is supported and is thus ambiguous with respect to the overall structure of the block. It also does not align with existing patterns for other dynamic input (period) blocks.

This is a proposal to convert the OC period block specification to align with list based input patterns, with fields OCACTION, OCTYPE, and OCSETTING: e.g. type recarray ocaction octype ocsetting. This specification format would most closely resemble list style input with no bound (e.g. the mfsim.nam models block or model name file packages block, but is also repeatable like any base stress package list input period block.

This adjustment is expected to be backwards compatible, i.e. although the specification would be adjusted to the modeler this change would be transparent and existing ascii OC files would not need to change. Validation and testing of the approach will be undertaken in:

Metadata

Metadata

Assignees

No one assigned

    Labels

    dfnDFN specification-relatedquestionInformation or decisions required

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions