Distortion map will be saved to database. Chi-Hung is in charge of the database design.

Sorry, I am probably confused. In the last ICS/PFI+MCS telecon, we talked about storing such key features under pfs_util and refer the information therein through a link to the repository. Here are you talking about something different to do the same thing?

Maybe I miss some things. But just like motor maps, there is a XML file but still we archive the data to database.

hassan and cloomis , could you tell me where I can find our standard way to keep version? 

I think, at this point in time, the best way to version XML files is to generate a SHA. Craig has created ticket INSTRM-519 to help you generate such a value.

A longer term solution (which could be using SHAs) needs to be thought out as a separate activity after the MCS engineering run. This may involve maintaining versions in a database, but such information most likely will need to be replicated across multiple databases. And the master DB would need to be persistent from now until the end of operations. So this is something that needs to be thought out more carefully, after this commissioning run.

Looking the INSTRM-519, it seems OK as long as I commit and push in the git standard manner ...? 

I believe so, yes.

I got it. Thank you.