Original report (archived issue) by Philip Starkey (Bitbucket: pstarkey, GitHub: philipstarkey).
I believe the API won't automatically detect zip groups when compiling a sequence of shots. I'm not sure if this makes sense or not.
On the one hand, we could argue that if you are using the API, then the globals file should explicitly specify the expansion column correctly for every global and not expect the runmanager API to work things out.
On the other hand, this is a real PITA if you just want programmatic control over compilation of shots, but otherwise identical behaviour to the GUI.
The solution is probably supporting both ways. Anyway, the missing thing is the fact that guess_expansion_modes exists in the GUI code, not in the API code for runmanager, and that this needs to be iteratively called until the expansion types settle to a steady state (see preparse_globals in the GUI code.
Original report (archived issue) by Philip Starkey (Bitbucket: pstarkey, GitHub: philipstarkey).
I believe the API won't automatically detect zip groups when compiling a sequence of shots. I'm not sure if this makes sense or not.
On the one hand, we could argue that if you are using the API, then the globals file should explicitly specify the expansion column correctly for every global and not expect the runmanager API to work things out.
On the other hand, this is a real PITA if you just want programmatic control over compilation of shots, but otherwise identical behaviour to the GUI.
The solution is probably supporting both ways. Anyway, the missing thing is the fact that
guess_expansion_modesexists in the GUI code, not in the API code for runmanager, and that this needs to be iteratively called until the expansion types settle to a steady state (seepreparse_globalsin the GUI code.