Skip to content

feat: partially filled dynamic_value could still be useful #22

@ConnorStoneAstro

Description

@ConnorStoneAstro

If one only fills a subset of the dynamic_values for a simulator, one currently must still provide a full dynamic params object at runtime. It could be possible as a fallback to treat the dynamic_values as static and therefore not need to fill them at runtime. This would mean that with 9 params, where 3 are static, 4 have dynamic values, and 2 are fully dynamic it would be possible to choose to pass a list of 6 tensors as the params or a list of 2 tensors as the params. Internally each Module would need to track two tuples, one of dynamic_params and one of dynamic_only_params that is more strict. Or at least it would need to track the number of dynamic only, and then at runtime it could go through the dynamic_params tuple and skip any that are dynamic value type.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions