-
Notifications
You must be signed in to change notification settings - Fork 96
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
Improve section savefig/png in chapter output in file output.md #86
Comments
Good ideas. |
You can use |
Thank you for the hint. using Plots;gr() # default window size
x=rand(101); y=rand(101)+10; z=rand(101)+100;
foo=plot(x,y,z,size=(450,300))
png(foo,"Try_save_small_png_v003_plot(x,y,z,size=(450,300))") The problem is, the appropriate function does an upscaling by a factor of 6 for each axis in the png file. This currently means one has to plot into a "stamp" resulting in not nice graphics. Cheers, |
@jheinen is this expected with GR? |
As addendum to the high resolution of png files. according to the table |
After some more and deeper investigations, the gr-backend reacts on the plot attribute dpi, example: foo=plot(x,y,z,dpi=300)
png(foo,"Try_save_small_png_v004_plot(x,y,z,dpi=300))") This results in a png-file which is 3 times larger for each size parameter. |
Proposal of an extended section of 'savefig' in file 'outpout.md' I have no experience with pull requests, ... as I'm new to github and the related workflow. Cheers, |
That looks sensible. It's easier to give feedback if you do a pull request. You can do that here on github by going to JuliaPlots/PlotDocs, clicking "new pull request" then "compare across forks" |
The documentation of section "savefig/png" should be improved to reflect the information available in the source code, for example as comments and real examples. Good for a better learning curve of newcomers.
In addition, some information about the resolution used in the output format. I created some png files for my package using gr() backend. They all had a resolution of 3600 x 2400 pixels which is ways too large.
Being able to define the wanted resolution would be great and could reduce / simplify the related workflow.
The text was updated successfully, but these errors were encountered: