Skip to content

Consistency checking doesn't take into account selected model #41

@LourensVeen

Description

@LourensVeen

If a configuration contains multiple models, and a MUSCLE3 user has selected a specific one to run, then we should be checking only that model and everything in it for resource declarations. Currently we require that all models have resources, also the ones that don't run, and that doesn't make sense.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions