Execution order

[ghost]

https://github.com/noaa-ocs-modeling/NEMSpy/blob/33323ae4135ca0b9cd3679bd7e53f6919afc0ad2/examples/example_1.py#L15-L20
How is the execution order defined?

[ghost]

https://github.com/noaa-ocs-modeling/NEMSpy/blob/33323ae4135ca0b9cd3679bd7e53f6919afc0ad2/examples/example_1.py#L11-L20

the order is currently defined by the .__init__() order, but I'm trying to think of a better way to define that more explicitly

[ghost]

I've added an initial implementation in 36bcb8e to make the sequence transparent and mutable from the interface level

[ghost]

made a pull request (#8 ) for mutable sequence

[jreniel]

https://github.com/noaa-ocs-modeling/NEMSpy/blob/33323ae4135ca0b9cd3679bd7e53f6919afc0ad2/examples/example_1.py#L11-L20

the order is currently defined by the .__init__() order, but I'm trying to think of a better way to define that more explicitly

I think we might need more than that, since the execution is not just about ordering, it can also call specific functions from the CAP. In this case, I think we need to make it so that the user builds the whole sequence (connectors, executors and subsequences) from the API methods.

[ghost]

alright, I will keep working on that

[ghost]

sequence API implemented in #8; second half of this issue is moved to #13