Save functionality

[csullivan]

When calibrating, one might want to save the raw points that were used to create the fit for later investigation. Perhaps a save button that dumps to a csv?

[csullivan]

A corresponding load button to restore from csv would then also be nice.

[Lunderberg]

I think that this would be a good thing, and should in principle save the entire program state.

Would the primary use case be in saving/restoring within the calibrate program, or for import/export from a different program? Trying to think whether to go for the simplest save format to use from within python, or whether the format that would be simplest to write an external parser for.

[csullivan]

Originally I was thinking export to csv, so that you have the flexibility of testing with an external program. Or, for example, if a user had some way of automatically generating the input data points, it would be burdensome to input the data by hand, if there were many fits to be performed. Less, so if you could point to a csv file, from which the data points could be loaded.

That said, saving the program state is also a nice feature. I guess these are two different features

1. load/save (program state)
2. import/export (data)

[Lunderberg]

Perhaps a hybrid format, then. There could be a # sign, which indicates that the current line is not a data point. These would be used to store non-point data. That way, any external program could still easily read the saved file by ignoring those lines. The extra lines would be placed at the bottom of the file, to help things like excel, which cannot ignore commented lines.

point1_x, point1_y, point1_desc
point2_x, point2_y
point3_x, point3_y, point3_desc
...
pointN_x, pointN_y, pointN_desc
# Degree: 2
# ChannelToEnergy: 1000
# EnergyToChannel:

How does that sound?

[csullivan]

Ah, yes, that makes good sense.