Currently, xcetool identifies externally configurable parameters in the notebook by executing the tagged variables cell in isolation and collecting any new identifiers which this code creates in the local namespace.
This is insufficient for many real-world notebooks: since a notebook is written to be executed sequentially, the variables cell may refer to identifiers created in previous cells and the xcetool extraction code will fail.
For variable extraction, xcetool should execute all cells up to the variables cell, and identify as variables only the identifiers added in the variables cell itself.
Currently, xcetool identifies externally configurable parameters in the notebook by executing the tagged variables cell in isolation and collecting any new identifiers which this code creates in the local namespace.
This is insufficient for many real-world notebooks: since a notebook is written to be executed sequentially, the variables cell may refer to identifiers created in previous cells and the xcetool extraction code will fail.
For variable extraction, xcetool should execute all cells up to the variables cell, and identify as variables only the identifiers added in the variables cell itself.