On Sun, 31 Jan 2016, Sven Schreiber wrote:
Am 31.01.2016 um 15:14 schrieb Allin Cottrell:
> On Sun, 31 Jan 2016, Sven Schreiber wrote:
>
>> Am 31.01.2016 um 12:12 schrieb Sven Schreiber:
>>>
>>> One unrelated thing: I don't remember how the creation of a secondary
>>> y-axis used to work, but now I'm having difficulties finding how to add
>>> that (if it's not added by gretl automatically in the first place).
>
> Example: open Ramanathan data9-7 and create a time-series plot with
> PRIME and UNEMP. The two series share a single y-axis. Open the graph
> editor and select the Lines tab. Under line 1 select "right" from the
> y-axis selector. Click "Apply": this adds a secondary y-axis and
> attaches PRIME to it.
See below.
>
>> P.S.: Wasn't there recently also some "data scaling" option as a
setting
>> for the individual lines? I'm not seeing that with
today's/yesterday's
>> snapshot anymore.
>
> To change the scale, type a different value into its "data scale" box.
> See the attchment. If you have a case where this box is not shown,
> please describe it.
>
Indeed I remember it exactly as you describe it, but it's different here
(= yesterday's snapshot on 32bit Windows 10), and that's the reason: For
each line I'm getting the first four "rows" of settings (up to
"size"),
and I'm not seeing the last row, with "data scale" and "y axis".
HOWEVER: In order to be absolutely sure I also did exactly what you
said, with the Ramanathan dataset, and then it's actually like you say.
Here's a recipe to provoke my problem:
- use the data Ramanathan data9-7
- run the following script:
<hansl>
series s2 = STOCK/10
list pus = PRIME UNEMP s2
matrix m = {pus}
gnuplot 2 3 1 --matrix=m --output=display
</hansl>
- open the graph editor (right-click and edit) and to the lines tab: you
shouldn't see the data scale and y-axis settings
No, I'm not seeing them. The criterion for showing these things
hasn't changed lately. It's debatable, no doubt, but here it is:
Either (a) the plot is a regular time-series plot, or (b) it
contains at least one "line" that is already attached to a secondary
y-axis. (See the function show_axis_chooser() in gui2/gpt_dialog.c.)
A better crtierion might be: the plot contains at least two y-axis
variables (and is not some "special" construction that might fly
apart if a second y-axis were activated).
Allin