Skip to content

file naming convention session safe? #28

@teuben

Description

@teuben

In the hypothetical case when another session has the same source in the same scan ranges.... it seems the filenames would collide:

NGC0001_scan_23_57_window0_feed0_pol0.fits

why not replace the word scan with the sequence number. Wouldn't that solve this extremely rare case? Murphy's law tells me that it will eventually happen.

Related to this, I have mixed feelings if to write a message if the same filename gets overwritten. That could be useful, but also extraneously noisy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions