Currently, SpinePeriods creates a copy of your DB with the period data added into it. This creates problems when we subsequently want to update the datastore - if we want to avoid having to run SpinePeriods in each execution, we then have to dbs to try and keep in sync. It would be more convenient if SpinePeriods instead created a small sqlite datastore that could be imported into the desired DB. It also gives us the option of having a mimumal SpinePeriods input DB containing just the input data required to generate the representative periods.
Currently, SpinePeriods creates a copy of your DB with the period data added into it. This creates problems when we subsequently want to update the datastore - if we want to avoid having to run SpinePeriods in each execution, we then have to dbs to try and keep in sync. It would be more convenient if SpinePeriods instead created a small sqlite datastore that could be imported into the desired DB. It also gives us the option of having a mimumal SpinePeriods input DB containing just the input data required to generate the representative periods.