AFM-SPM
Changes to test files from PR #876
This PR isolates the changes to tests made in PR #876 so that they can be reviewed/amended separately to the changes to the main tracing code. Suggestions in the comments from @ns-rse have been included here so that they can be addressed before merging to maxgamill-sheffield/800-better-tracing.
Thanks @llwiggins is this ready for review?
I also wonder if it might make more sense to merge this into the maxgamill-sheffield/800-btr_disordered-tracing branch since it addresses issues raised on that branch in #876. Doing so before that is merged into maxgamill-sheffield/800-better-tracing obviously!
Hi @ns-rse, @MaxGamill-Sheffield is going to take a look at this next week. There are some additional changes to be made so best to keep this as a draft PR for now I think!
Hey @ns-rse, this test is now very outdated as both the structure and saved keys of the disordered tracing, nodestats, and ordered tracing stats in the .topostats file differs greatly.
The intention of this test was just to ensure that of the keys that were saved, they were the same but now this needs more manual coercion of the dictionaries which will be done once the final .topostats structure is saved (upon finishing the final splining section). And this PR & branch then serves to save those outputs somewhere findable while keeping the individual section PR's / branches solely focused on their features.
This PR never has any intention of being merged with main or 800-btr as it should already be covered in the main tests, again, it is here just to not break the working tests and save a temporary output.
This PR never has any intention of being merged with main or 800-btr as it should already be covered in the main tests, again, it is here just to not break the working tests and save a temporary output.
Can we close this PR then? If its never going to be merged the work can remain on a branch.
This PR never has any intention of being merged with main or 800-btr as it should already be covered in the main tests, again, it is here just to not break the working tests and save a temporary output.
Can we close this PR then? If its never going to be merged the work can remain on a branch.
Bump...if the PR isn't going to be merged it doesn't really serve any purpose. The changes persist on the branch and can be referenced if needed, can we therefore close it?
/cc @llwiggins @MaxGamill-Sheffield @SylviaWhittle