pspm_write_channel variable assignment

[teddychao]

Recent development of PsPM aims at generalising the variable options in all pspm functions. channel_action, one of the subfields of options, has been generalised for every function except for pspm_write_channel. For every other function, channel_action is a subfield in options, and it can be whether mandatory or optional. For pspm_write_channel, channel_action is an individual variable which is parallel to options. This is an exception for channel_action and we may want to reconsider where to put it.

We have discussed about this issue in this week's group meeting. Our colleagues have provided their suggestions:

• One of our colleagues suggested channel_action should be prioritised in pspm_write_channel because it plays a vital role in the process of pspm_write_channel. As an individual variable, it will cause attention of users and force them to always provide value for it.
• Another colleague suggested channel_action could be renamed in pspm_write_channel. This is because throughout PsPM, options always tends to have the field channel_action when applicable. Users may become confused whether to specify such value in the individual variable of pspm_write_channel or the field of options in pspm_write_channel.

[teddychao]

Hi @fedmanci and @SerenXia I have put your comments on our last meeting to this issue. I hope this is exactly what you suggest. Please feel free to comment if there is any information missing. It would be grateful if you can let us know your thoughts about this issue @dominikbach . Thanks.