I changed the SpicyVCF output name to differentiate the files before/after the latest change. That was silly, the database query relies on the files having the same names, so we'd lose the connection to previous runs.
Forcing a re-run can be accomplished instead through deactivating the dodgy analysis entries, and/or forcing stages where the execution order has now been changed to rerun in the latest callset (through config)
I changed the SpicyVCF output name to differentiate the files before/after the latest change. That was silly, the database query relies on the files having the same names, so we'd lose the connection to previous runs.
Forcing a re-run can be accomplished instead through deactivating the dodgy analysis entries, and/or forcing stages where the execution order has now been changed to rerun in the latest callset (through config)