From a housekeeping perspective, is it possible to clear the particle stacks for a reference-based motion correction job but retain the hyperparameter outputs?
We would find this option useful particularly due to the need to run the particle stacks through Downsample Particles for non-standard F-crop values. And also, in the unfortunate instance where an RBMC run generates useful hyperparameters but fails in the later stages due to duplicate particles.
Hi @leetleyang ,
There are a few ways you can achieve this:
- Use multiple jobs for the reference motion pipeline. The different stages of processing can be done as separate jobs, as explained in the guide and the tutorial video. If you do hyperparameter search and final reconstruction as two different jobs, you can clear one and not the other.
- Write down the numeric values for the hyperparameters and input them in the override parameters in your future jobs.
- Export the result group before the job is cleared.
Many thanks. Having played around with it a bit more, it’s indeed straightforward to queue up two RBMC jobs, one for hyparameter/dose-weighting optimisation, feeding into a second for motion-correction. We will take this onboard going forward.