Databases
StackOverflow2013
Postsdbo
POCopying contours from one axes instance to another
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCopying contours from one axes instance to another
    primarykey
    data
    text
    <p>I have a situation where I am producing upwards of 20 different images using matplotlib. This is done many many times. Each of the 20 images has the same set of contours in the background. In order to reduce the processing time, it would be useful to be able to copy the result of <code>countourf()</code> from one <code>Axes</code> instance to another. In order to do this, I have tried this:</p> <pre><code>#!/bin/env python import os import numpy as np from matplotlib import pyplot as plt def copycontours(): #Create figures fig1 = plt.figure() fig2 = plt.figure() fig3 = plt.figure() #Create axes ax1 = fig1.add_axes((0.05,0.05,0.90,0.90)) ax2 = fig2.add_axes((0.05,0.05,0.90,0.90)) ax3 = fig3.add_axes((0.05,0.05,0.90,0.90)) #Create random data data = np.random.normal(25, size=(25,25)) #Add contours to first axes instance and save image contours = ax1.contourf(data) fig1.savefig('test.png') #Add contours to second axes instance from first axes instance for collection in ax1.collections: ax2.add_collection(collection) fig2.savefig('test2.png') #Add contours to third axes instance from for collection in contours.collections: ax3.add_collection(collection) fig3.savefig('test3.png') os.system('display test.png &amp;') os.system('display test2.png &amp;') os.system('display test3.png &amp;') if __name__ == '__main__': copycontours() </code></pre> <p>The first figure (test.png) comes out looking correct. The axes range from 0 to 25 and the full domain is filled. </p> <p><img src="https://i.stack.imgur.com/FUz08.png" alt="test1.png"></p> <p>The other two (test2.png, test3.png) come out differently. Their axes range from 0 to 1 and the contour region only fills the area from 0.0 to approximately 7.9.</p> <p><img src="https://i.stack.imgur.com/eRwa0.png" alt="test2.png"></p> <p>Resetting the axis limits via <code>ax2.set_xlim(0,25)</code> and <code>ax2.set_xlim(0,25)</code> changes the axis ranges, but does not fix the larger problem.</p> <p><img src="https://i.stack.imgur.com/QN1mE.png" alt="test3.png"></p> <p>Does anyone have a thought on how to fix this problem or another method for reusing the results of <code>contourf()</code> in a different way?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USVorticity
    1. USVorticity
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCopying contours from one axes instance to another
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCopying contours from one axes instance to another
      1. USYXD
      1. VTFavorite
    3. VO
      singulars
      1. POCopying contours from one axes instance to another
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI suspect the answer is going to be something like this: http://stackoverflow.com/questions/13299294/adding-a-collection-to-multiple-axis/13301231#13301231 , however getting the collections from contour without the initial axes mixed up in them seems to be difficult.
      singulars
      1. POCopying contours from one axes instance to another
      1. UStacaswell
    2. COHuh, that's interesting. It seems odd to me that a matplotlib object would need to retain information about what axes instance it is attached to, but I haven't ever really looked at the internals of matplotlib. I'll have to dig in a bit and see if I can figure out the reason.
      singulars
      1. POCopying contours from one axes instance to another
      1. USVorticity
    3. COIt is part of the rather complicated rendering stack
      singulars
      1. POCopying contours from one axes instance to another
      1. UStacaswell
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload