Closed mvdoc closed 5 months ago
Maybe this problem was a problem only for me. But I always hated how the transforms were listed in the __repr__, as it wasn't really easy to understand what transforms were available for a subject.
__repr__
Before the PR they would be listed as
>>> cortex.db.subjects["fsaverage"].transforms Transforms: [atlas,atlas336,atlas_2mm,atlas_3mm]
which is fine for a few transforms, but it becomes quickly unreadable if one has many transforms.
After this PR they are listed as
>>> cortex.db.subjects["fsaverage"].transforms Available transforms for fsaverage: atlas atlas336 atlas_2mm atlas_3mm
This PR also sorts the subjects when running cortex.db and cortex.db.subjects. The unsorted subjects also bugged me in the past.
cortex.db
cortex.db.subjects
Maybe this problem was a problem only for me. But I always hated how the transforms were listed in the
__repr__, as it wasn't really easy to understand what transforms were available for a subject.Before the PR they would be listed as
which is fine for a few transforms, but it becomes quickly unreadable if one has many transforms.
After this PR they are listed as
This PR also sorts the subjects when running
cortex.dbandcortex.db.subjects. The unsorted subjects also bugged me in the past.