Skip to content

Unpractical longitudinal filenaming #1415

@MatthieuJoulot

Description

@MatthieuJoulot

Hi Clinica devs,

The current longitudinal pipeline does not separate the session ids in the longitudinal id.

What it means is that if you have 3 sessions which are ses-M0, ses-M3, and ses-M6, the longitudinal id will be long-M1M3M6.
However if the sessions are ses-1, ses-2 and ses-3, then you get long-123, which makes it hard to read.

IMHO, adding a separator would enhance the readability and usability of the pipeline. On my side, I used a point as separator which would get the format to be long-1.2.3

Have a good day,
Matthieu

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions