Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit xrange when using xlen #6

Closed
wants to merge 36 commits into from
Closed

Limit xrange when using xlen #6

wants to merge 36 commits into from

Conversation

a3nm
Copy link

@a3nm a3nm commented Jun 11, 2011

Hi,

Here's a very simple fix to avoid the fact that, when using xlen, the plot is initially mostly empty. It seems more logical (at least for what I'm doing) to have its xrange be initially small and grow up to xlen.

What do you think about this? Maybe the best would be to have an option to choose between the two possible behaviors?

Cheers,

Antoine

Dima Kogan added 30 commits February 6, 2011 16:02
…e_xy option to square the

aspect ratio ONLY for the xy axes, allowing z to scale as needed
For example to set a legend for curve 'data' to 'datalegend' I now do
 --legend data datalegend

The previous syntax that used = produced hashes internally, which disregarded
the order of the given options. This resulted in arbitrarily ordered curves.
@dkogan
Copy link
Owner

dkogan commented Jun 11, 2011

Hi Antoine. This patch is too much of a special case so I don't
want to merge it in as is. Another option could work, though. In
your particular case do you essentially want

plotwidth = min(xlen, data_xmax - data_xmin)

Here the plot will never be wider than xlen, and will shrink to maximally show
the existing data, if this is less than xlen. This is different from your
proposal since it won't just kick in at the start; if there's a hole in the data
later on, it will expand the plot then also. Is this what you want, or do you
only want an expanded plot at the start, when the data is filling in?

@dkogan
Copy link
Owner

dkogan commented May 9, 2013

This is old, and I'm not a huge fan of the proposed behavior, so I'm closing this.

@dkogan dkogan closed this May 9, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants