Benchmarking Data Neuroglancer Skeletons are Wrong

[tathey1]

Downloading benchmarking notebook shows improper traces for validation_21 with trace number 2.

We printed out "swc_string" from here, and found improper looking skeleton coordinates.

We concluded that the skeleton objects on s3 for the benchmarking data are wrong. Let's replace them with good ones.

[shreyasingh1]

We narrowed down the issue to Cloudvolume's Skeleton.to_swc() and Skeleton.from_swc() functions, theorizing that calling these functions during the swc upload and download process changes the underlying topology of the swc file. See issue posted to CloudVolume here: seung-lab/cloud-volume#466

[github-actions]

Stale issue message