Hi,
I find it difficult to read the values of an axis when the offset is active. The problem is that many time I find myself doing calculations like -1.2345e2-0.048 to find out the value of the tick. I send enclosed a patch and a test file to, in my opinion, improve the readability of the ticks with an offset.
Cheers,
Francisco
offset_readability.diff (1.24 KB)
test_offset_readability.py (920 Bytes)
2009/11/15 Francisco Javier de la Peña <delapena@…55…801…>
Hi,
I find it difficult to read the values of an axis when the offset is active. The problem is that many time I find myself doing calculations like -1.2345e2-0.048 to find out the value of the tick. I send enclosed a patch and a test file to, in my opinion, improve the readability of the ticks with an offset.
Cheers,
Francisco
Hi Francisco,
Could you try this simple case ?
I[6]: a = np.linspace(0.00002, 0.00005, num=9348)
I[7]: plot(a)
Still ticks produce mingled values. Like 1e-10+3.207e-5 after some zooming in.
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what’s new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
–
Gökhan
Hi Gökhan,
I tried your example and I couldn’t find anything wrong with the offset there. However, I agree that this particular mixture of scientific notation and offset looks confusing. Maybe in that case it will be better to write: x1e-10+320700e-10 . Is it what you mean?
Cheers,
Francisco
El 17 de noviembre de 2009 00:58, Gökhan Sever <gokhansever@…149…> escribió:
2009/11/15 Francisco Javier de la Peña <delapena@…801…>
Hi,
I find it difficult to read the values of an axis when the offset is active. The problem is that many time I find myself doing calculations like -1.2345e2-0.048 to find out the value of the tick. I send enclosed a patch and a test file to, in my opinion, improve the readability of the ticks with an offset.
Cheers,
Francisco
Hi Francisco,
Could you try this simple case ?
I[6]: a = np.linspace(0.00002, 0.00005, num=9348)
I[7]: plot(a)
Still ticks produce mingled values. Like 1e-10+3.207e-5 after some zooming in.
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what’s new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
–
Gökhan
–
This message has been scanned for viruses and
dangerous content by
MailScanner, and isbelieved to be clean.
Hi Gökhan,
I tried your example and I couldn’t find anything wrong with the offset there. However, I agree that this particular mixture of scientific notation and offset looks confusing. Maybe in that case it will be better to write: x1e-10+320700e-10 . Is it what you mean?
I think this could be better presented collecting the base terms under the same exponent (i.e 320701e-10 and further 32e-6) Doesn’t this look simpler?
On Tue, Nov 17, 2009 at 4:29 AM, Francisco de la Peña <delapena@…801…> wrote:
Cheers,
Francisco
El 17 de noviembre de 2009 00:58, Gökhan Sever <gokhansever@…149…> escribió:
2009/11/15 Francisco Javier de la Peña <delapena@…801…>
Hi,
I find it difficult to read the values of an axis when the offset is active. The problem is that many time I find myself doing calculations like -1.2345e2-0.048 to find out the value of the tick. I send enclosed a patch and a test file to, in my opinion, improve the readability of the ticks with an offset.
Cheers,
Francisco
Hi Francisco,
Could you try this simple case ?
I[6]: a = np.linspace(0.00002, 0.00005, num=9348)
I[7]: plot(a)
Still ticks produce mingled values. Like 1e-10+3.207e-5 after some zooming in.
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what’s new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
–
Gökhan
–
This message has been scanned for viruses and
dangerous content by
MailScanner, and isbelieved to be clean.
–
Gökhan
Hi Gökhan,
I think that we are understanding differently the notation (what would mean that it is indeed confusing). For me 1e-10+3.207e-5 means: “to get your value read the figure from the axis, multiply it by 1e-10 and add 3.207e-5”. The source of the confusion could be a missing “x” in front of 1e-10.
Anyway the patch that I have submitted is not related to this problem, it only affects the way the offset is calculated, not the way it is displayed. I just tested an unmodified version of matplotlib and the “x” is not displayed there neither. The difference that the patch makes is that instead of 4x1e-8+2.995e-5 you get 99x1e-8+2.9e-5 that I think it is easier to read. In addition, if the number of significant figures in the axis range changes it takes it into account so the offset becomes human friendly for all the axis values.
Cheers,
Francisco
2009/11/17 Gökhan Sever <gokhansever@…149…>
On Tue, Nov 17, 2009 at 4:29 AM, Francisco de la Peña <delapena@…801…> wrote:
Hi Gökhan,
I tried your example and I couldn’t find anything wrong with the offset there. However, I agree that this particular mixture of scientific notation and offset looks confusing. Maybe in that case it will be better to write: x1e-10+320700e-10 . Is it what you mean?
I think this could be better presented collecting the base terms under the same exponent (i.e 320701e-10 and further 32e-6) Doesn’t this look simpler?
Cheers,
Francisco
El 17 de noviembre de 2009 00:58, Gökhan Sever <gokhansever@…149…> escribió:
2009/11/15 Francisco Javier de la Peña <delapena@…801…>
Hi,
I find it difficult to read the values of an axis when the offset is active. The problem is that many time I find myself doing calculations like -1.2345e2-0.048 to find out the value of the tick. I send enclosed a patch and a test file to, in my opinion, improve the readability of the ticks with an offset.
Cheers,
Francisco
Hi Francisco,
Could you try this simple case ?
I[6]: a = np.linspace(0.00002, 0.00005, num=9348)
I[7]: plot(a)
Still ticks produce mingled values. Like 1e-10+3.207e-5 after some zooming in.
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what’s new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
–
Gökhan
–
This message has been scanned for viruses and
dangerous content by
MailScanner, and isbelieved to be clean.
–
GökhanThis message has been scanned for viruses and
dangerous content by
MailScanner, and isbelieved to be clean.
You are right Francisco. I was misinterpreting, and probably not having an “x” is not an issue.
On Tue, Nov 17, 2009 at 1:25 PM, Francisco de la Peña <delapena@…801…> wrote:
Hi Gökhan,
I think that we are understanding differently the notation (what would mean that it is indeed confusing). For me 1e-10+3.207e-5 means: “to get your value read the figure from the axis, multiply it by 1e-10 and add 3.207e-5”. The source of the confusion could be a missing “x” in front of 1e-10.
Anyway the patch that I have submitted is not related to this problem, it only affects the way the offset is calculated, not the way it is displayed. I just tested an unmodified version of matplotlib and the “x” is not displayed there neither. The difference that the patch makes is that instead of 4x1e-8+2.995e-5 you get 99x1e-8+2.9e-5 that I think it is easier to read. In addition, if the number of significant figures in the axis range changes it takes it into account so the offset becomes human friendly for all the axis values.
Cheers,
Francisco
2009/11/17 Gökhan Sever <gokhansever@…149…>
On Tue, Nov 17, 2009 at 4:29 AM, Francisco de la Peña <delapena@…801…> wrote:
Hi Gökhan,
I tried your example and I couldn’t find anything wrong with the offset there. However, I agree that this particular mixture of scientific notation and offset looks confusing. Maybe in that case it will be better to write: x1e-10+320700e-10 . Is it what you mean?
I think this could be better presented collecting the base terms under the same exponent (i.e 320701e-10 and further 32e-6) Doesn’t this look simpler?
Cheers,
Francisco
El 17 de noviembre de 2009 00:58, Gökhan Sever <gokhansever@…149…> escribió:
2009/11/15 Francisco Javier de la Peña <delapena@…801…>
Hi,
I find it difficult to read the values of an axis when the offset is active. The problem is that many time I find myself doing calculations like -1.2345e2-0.048 to find out the value of the tick. I send enclosed a patch and a test file to, in my opinion, improve the readability of the ticks with an offset.
Cheers,
Francisco
Hi Francisco,
Could you try this simple case ?
I[6]: a = np.linspace(0.00002, 0.00005, num=9348)
I[7]: plot(a)
Still ticks produce mingled values. Like 1e-10+3.207e-5 after some zooming in.
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what’s new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
–
Gökhan
–
This message has been scanned for viruses and
dangerous content by
MailScanner, and isbelieved to be clean.
–
GökhanThis message has been scanned for viruses and
dangerous content by
MailScanner, and isbelieved to be clean.
–
Gökhan