New logic for plot limits

[cosimolupo]

Changed the logic on plot limits (in config files, 'None' is now accepted as value for t_start/t_stop to plot the entire signal).

[mdenker]

@cosimolupo Possibly already implemented. Please check and close if duplicate.

[mdenker]

Possibly new PR for the change in pipeline/utils/parse.py ?

[cosimolupo]

Dear @mdenker, also in this case I re-aligned the branch to the current HEAD of NeuralEnsemble/cobrawap, and then added back the only changes still needed, after the introduction of the robust_t function in neo_utils.py, which takes care of checking None values and values which are out of the original signal [t_start,t_stop] range.

[mdenker]

From what I can judge, this seems fine to me.

[mdenker]

Here and in the following, does T_START refer to t_start of the Neo object? In that case I would suggest

Suggested change

	PLOT_TSTART: 0 # float (in s) or 'None' -> T_START of the input signal is used
	PLOT_TSTOP: 10 # float (in s) or 'None' -> T_STOP of the input signal is used
	PLOT_TSTART: 0 # float (in s) or 'None' -> t_start of the input signal is used
	PLOT_TSTOP: 10 # float (in s) or 'None' -> t_stop of the input signal is used

[cosimolupo]

Yes, they refer to the attributes of the neo object. I used the uppercase notation as in the config files they are introduced this way. Anyway, let's decide if switch to the lowercase version, and then I will fix them coherently.

[cosimolupo]

@mdenker I adapted the description in config template files, so to make more explicit and clear what means setting PLOT_TSTART and/or PLOT_TSTOP value to 'None'.

[cosimolupo]

Merging Pull Request #61 added some extra spacings, which I fixed in a further commit.

[mdenker]

Merge as soon as version number is increased, e.g., after #62 #63