file_suffix is not extracted properly

[michaelcroquette]

Hello,

We would like to add a specific string at the end the h5 file when saving data. The seems to be a file_suffix parameter:

def save_acquisition(
        self, update_: bool = True, /, file_suffix: Optional[str] = None, **kwds
    ) -> "AcquisitionAnalysisManager":
        acquisition_finished = time.time()
        if not self._once_saved:
            additional_info: Dict[str, Any] = {
                "acquisition_duration": acquisition_finished - self._acquisition_started,
                "logs": self.logger.getvalue(),
                "prints": self.logger.get_stdout(),
            }
            if self._default_config_files:
                additional_info.update({"default_config_files": self._default_config_files})
            kwds.update({"info": additional_info})

        super().save_acquisition(update_, file_suffix=file_suffix, **kwds)
        self._load_analysis_data()
        return self

But in AcquisitionManager.save_acquisition it is not used:

def save_acquisition(self, update_: bool = True, /, **kwds) -> "AcquisitionManager":

Is this the intended purpose of this suffix ?

It can be a pain to identify a specific curve in a folder when the only differences are the date tag at the beginning of the filename.

[kyrylo-gr]

Hi, can you explain a bit more about your use case? Are you using Python files or notebooks to create acquisitions?

That’s true that "file_suffix" parameters of save_acquisition are not used. It's an artefact. The file name is generated when acquisition is created using, for example:

aqm.acquisition_cell("abc") # in notebook
aq = aqm.new_acquisition("abc") # in Python file

The initial philosophy is to have files separated by experiment name into different directories. So different curves are in different folders and files inside each folder are sorted by date.

If you think it's important to have a suffix for your use case, it's possible to add this functionality. However, before, please provide a bit more examples of your use cases so become more clear. Is it important that you set a suffix with save_acquisition (i.e. at the end of acquisition) or can it be set when creating an acquisition? The first would involve more backend rewriting.

[michaelcroquette]

Hey,

So we are using a notebook. The idea is to be able to distinguished between curves in a folder by something else than the date. The curves are all taken in a same measurement setup so indeed we can have it in different folders and that is what we are doing now but it is not ideal.

The suffix can be set when we create the acquisition.

[kyrylo-gr]

Can you specify what you mean by curves? Do you mean different datasets or different PDFs of curves ?
Do I understand you right that I'd like to have the following folder structure:

- rabi_oscillations
   - dataset1_2026_05_01__00_00_00_rabi_oscillations.h5
   - dataset1_2026_05_01__00_00_01_rabi_oscillations.h5
   - dataset2_2026_05_01__00_00_00_rabi_oscillations.h5
   - dataset2_2026_05_01__00_00_01_rabi_oscillations.h5

How would you like to create such a structure? It would be extremely useful if you can provide with a more concrete example of how you see the final front-end code.