Salvus 0.11.22

Salvus uses a job database to keep track of asynchronously launched jobs. Over time this database can become quite big to the point of negatively effecting the total performance.

With this change Salvus will now perform periodic maintenance of the database to optimize it and keep its size in check.

Additionally finished jobs are no longer moved into the “archived” group in the database but removed from the database upon job deletion. We don’t expect this to have an effect on any user.

Provide a workaround for externally computed and incorrect adjoint sources. It is strongly recommend to verify the implementation of custom misfits and adjoint sources with a finite-difference test. Using the optional parameter force_trust_region_scaling badly scaled adjont sources can be mitigated by enforcing to scale the proposed model update to the trust region radius.

When re-launching simulations for which data already exist (e.g. to compute checkpoints), previously computed outputs are kept in the project file structure and only overwritten once the new jobs have finished. Additionally, a utility to manually clean the simulation store has been added.