Graph modification-protected and rescale option

Hi,
I use Igor for scientific data analysis. We prepare finite number of Graphs and layouts for publication purpose. Once data is published, it is obvious that one do not want to change all Graphs and layouts. This is very important for due to many reasons. At the moment, I see a safety log or "Write-protected" only for procedure. Similar option will be very helpful for many users. In case of Graph and layout, I would like to log all possible access except viewing them before unlogging the "modification-protected" button.

Secondly, spectroscopy people often change x or y axis values. So, it would be nice to have option to include formula to rescale the either axis. I am aware that there is an option with axis transform. But, that is plug-in and we do not have any access to see what are the parameter used to create the new axis.

Please try to include such features in forthcoming Igor version.

Best
Maniraj
mslv86 wrote:
Hi,
I use Igor for scientific data analysis. We prepare finite number of Graphs and layouts for publication purpose. Once data is published, it is obvious that one do not want to change all Graphs and layouts. This is very important for due to many reasons. At the moment, I see a safety log or "Write-protected" only for procedure. Similar option will be very helpful for many users. In case of Graph and layout, I would like to log all possible access except viewing them before unlogging the "modification-protected" button.


I don't think adding a write protected feature for graphs and layouts would be a good idea. For example, if your graph displays a wave, and that wave's data changes, it would be very confusing if the graph itself did not also update. Likewise, layouts can be created so that if a graph in the layout changes, the layout updates itself to reflect those changes.

I think there are some existing alternatives to your suggestion that might serve you well:
1. Save backup copies of your experiments/data when you publish your data.
2. You can select a graph and choose File->Save Graph Copy to save the graph's data and recreation macro to a separate experiment.
3. You could save the recreation macros for all of the graphs and layouts that you want to "freeze" to a procedure file and then write-protect that procedure file. That way, as long as the data itself does not change, you should be able to execute those recreation macros to get back the original graphs and layouts. You could also lock the waves used in the graphs for additional protection (execute DisplayHelpTopic "SetWaveLock" for more information.

mslv86 wrote:
Secondly, spectroscopy people often change x or y axis values. So, it would be nice to have option to include formula to rescale the either axis. I am aware that there is an option with axis transform. But, that is plug-in and we do not have any access to see what are the parameter used to create the new axis.

The Transform Axis package allows you to select any axis on the graph to transform. You can also view the code used by the Transform Axis package by loading the package and then selecting the Windows->Procedure Windows->TransformAxis1.2.ipf menu item.
aclight wrote:

I don't think adding a write protected feature for graphs and layouts would be a good idea. For example, if your graph displays a wave, and that wave's data changes, it would be very confusing if the graph itself did not also update. Likewise, layouts can be created so that if a graph in the layout changes, the layout updates itself to reflect those changes.


I might suggest otherwise on a larger scale. I think having a "read only" option for an Igor Pro experiment might be a very useful feature. I would for example feel more at ease to be able to distribute example packages (e.g. demos to students) that are "locked" against changes. I _think_ this could be done at the system level. It could even be done through a hook function in Igor Pro (i.e. OnQuit --> do not save, OnSave --> do not save ...). Of all of these possibilities, best would be to have Igor Pro include a way to "password protect" an entire experiment against changes.

So, I see that locking graphs and layouts can cause the problems you say. However, I read the original post in a completely different way. The intent is to have something that is really future proof against any further changes.

--
J. J. Weimer
Chemistry / Chemical & Materials Engineering, UAH